I Got Hired as a Software Engineer With No Experience (Here's How)

Main Ideas / Concepts / Lessons

• Fear about AI replacing developers is understandable but misguided.

  • The speaker argues that AI will change how developer work looks, but software jobs are not disappearing.
  • Companies are also still figuring things out, just like candidates are.

• Hiring is not purely about technical ability—especially in early rounds.

  • Candidates often fail not because they can’t code, but because they don’t show the right qualities in conversation:
    • energy
    • curiosity
    • confidence
    • engaged, meaningful answers
    • interest in learning and contributing

• Real-world experience (and consistency) matters more than coursework alone.

  • The speaker’s advantage came from working consistently in a developer role while studying, building context about:
    • why decisions were made
    • which parts of the codebase are hard/unwanted
    • how a real team system works over time
  • This context can’t be fully learned from tutorials.

• Early career progress can happen even with limited experience.

  • The speaker started with:
    • no computer science background
    • no coding experience
    • minimal projects
    • heavy tutorial “copy-pasting”
  • Despite this, they were hired—because of their motivation and learning intent.

• Software engineering is broader than “writing code.”

  • The speaker compares AI’s role to kitchen appliances: they help, but they don’t remove the need for judgment and creativity.
  • Real job responsibilities include:
    • understanding problems
    • communicating with stakeholders
    • making architectural decisions
    • debugging confusing issues
    • deciding which technical approach fits a specific team and codebase

---

Methodology / Step-by-Step Guidance (Detailed)

What to Focus on to Get a First Software Engineering Job (Concrete Instructions)

1. Build something real

   • Create a project because you have a real problem you want to solve.
   • It should be not just a step-by-step tutorial project.
   • Requirements:
     • doesn’t have to be new
     • doesn’t have to be impressive
     • must be real (tied to an actual need/problem)

2. Be honest about AI usage—and use it to accelerate thinking, not replace it

   • AI is a tool.
   • Use AI to go faster, but write/understand the work yourself so you learn how real projects behave.
   • Distinguish between:
     • Using AI to go faster (good)
     • Using AI to avoid thinking (bad—leads to not understanding what’s happening)

3. Apply before you feel fully ready

   • Apply even if you don’t meet the domain/framework requirements.
   • Example from speaker:
     • applied to an Angular front-end role without having used Angular before
     • the interview + job taught more than months of coursework

4. In interviews, be a person—not a list of technologies

   • Focus on:
     • what you’re curious about
     • what you’re trying to figure out
     • why you want that specific role
   • Speaker’s claim: curiosity gets you hired, while a framework/tech checklist does not.

5. Stop asking “Will AI take my job?” and ask “How can I use it better?”

   • The competitive advantage in 2026 is not avoiding AI—it’s using AI in a way that improves your performance and learning beyond what others do.

6. Actively apply for roles even if you meet only part of requirements (challenge)

   • Speaker’s directive:
     • open LinkedIn
     • find one junior dev role or working student position
     • apply today
     • even if you meet only ~60% of the requirements

---

Speakers / Sources Featured

• Jules (the video’s narrator/speaker; software engineer studying computer science; working student background; shares personal hiring experience)
• YouTube tutorials (mentioned as a learning source the speaker used initially)