Question: is there even a need for junior engineers if AI is already as good as most software engineers? Eric's answer is an unambiguous yes 3:45.

What juniors uniquely offer

  • Nimbleness in picking up tools and skills, and tackling problems in a way that is "unopinionated in a good way" 3:45.
  • Where Eric sees seniors stumble is an aversion to change, in a world that is evolving very quickly 4:12.

The slope vs. Y-intercept model

Eric's framing for junior vs. senior value 4:12:

  • Y-intercept = starting capability. The junior's is lower than the senior's.
  • Slope = rate of picking up new tools and skills. The junior's is "incredibly high" and "a lot more robust."
flowchart LR
    S["Senior: high Y-intercept, flatter slope<br/>risk = aversion to change"]
    J["Junior: low Y-intercept, high slope<br/>edge = adapts to new tools fast"]
    S -.->|"tradeoff in a fast-changing tool landscape"| J
  • This matters especially for smaller companies: startups run on speed and the ability to adapt to problem spaces and change on a moment's notice — a meta skill juniors already have 4:33.

The tension in the interview

  • Juniors are valuable and companies aren't hiring them. Eric resolves this not by denying junior value but by blaming employer short-termism — see 01 — The Junior Hiring Squeeze 5:43.