Why I'd Hire a Junior Engineer Over a 10-Year Senior

If I had to choose between a junior engineer and a senior with 10 years of experience who's only ever focused on writing code, I'd pick the junior. Every time. In this solo episode, I explain why junior engineers have an unfair advantage right now, and why the seniors who only think in code are the ones who should actually be worried about AI.

I break down what AI can and can't replace, why starting from the problem instead of the tech stack is the fastest way to grow, and share the story of my first job in 2016 where I accidentally became a product engineer before I even knew the term existed. Plus: a practical playbook for juniors who want to break in, and a wake-up call for engineering leaders who've stopped hiring them.

---

TIMESTAMPS

00:00 I'd Hire the Junior — Here's Why

01:00 The Wrong Question Everyone Is Asking About AI and Juniors

02:00 What AI Can't Do: The Real Work of Software Engineering

06:00 My First Job in 2016: Accidentally Doing Product Engineering

09:00 Why Hyper-Specialisation Is the Real Risk

11:00 The Unfair Advantage of Fresh Eyes

12:00 A Playbook for Getting Started Without a Job

14:00 From Side Project to Entrepreneur

15:00 How Portfolios Have Changed

16:00 A Message to Engineering Leaders

17:00 Three Essential Books for the Product Engineer Path

19:00 Wrap-Up

---

KEY TAKEAWAYS

1. Junior engineers have fresh, unmolded minds — they haven't been "polluted by the old ways." That malleability is their biggest asset in a world where the rules of engineering are changing fast.

2. Writing code is the easiest part of software engineering. Understanding what to build, clarifying messy requirements, talking to users, system thinking — AI can't do any of this. This is where product engineers live.

3. Hyper-specialisation is the real risk. If your value is pattern recognition and applying known solutions, that's exactly what LLMs are good at. Seniors stuck in their ways are more replaceable than adaptable juniors.

4. Start from a real problem, not a tech stack. Look at your life, talk to people, and find a human problem to solve. Build a prototype, run usability tests, iterate. That's your new portfolio.

5. For leaders: stop hiring juniors to write boilerplate. Hire them to solve problems. Put them in front of customers. Make failure safe. Pair them with AI, not against it.

6. The companies that invest in growing junior product engineers now will have a massive advantage in five years. The ones that don't will be fighting over a shrinking pool of senior talent.

---

RESOURCES MENTIONED

- Continuous Discovery Habits by Teresa Torres

- Extreme Programming Explained by Kent Beck

- Don't Make Me Think by Steve Krug

- The Lean Startup by Eric Ries

- Clean Architecture by Robert C. Martin

- Continuous Delivery by Dave Farley

- The Pragmatic Engineer newsletter by Gergely Orosz

- PostHog's Product for Engineers newsletter

- Lovable, v0, Replit — AI prototyping tools

- Cursor — AI-assisted coding

---

CONNECT WITH PRODUCT ENGINEERS

Host: Peppe SillettiLinkedIn: https://www.linkedin.com/in/peppesilletti/Website: https://peppesilletti.io

Product Engineers:

Website: https://productengineers.comNewsletter: https://newsletter.productengineers.comLinkedIn: https://www.linkedin.com/company/product-engineers

---

SUPPORT THE SHOW

If you're a junior developer wondering where you fit in the AI era, or a leader who's stopped hiring juniors — share this episode with someone who needs to hear it. Drop a comment with your biggest takeaway.

This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit

podcast.productengineers.com