Files
WebinarNotes/wiki/concepts/seniority-and-the-junior-squeeze.md

2.2 KiB
Raw Blame History

Seniority and the Junior Squeeze

#concept

Summary

Counter-intuitively, AI has raised demand for seniors and made juniors "completely irrelevant" in the market — even though a junior + Claude could, in theory, produce the same output. The differentiator is judgment as risk reduction.

Current Understanding

  • Why seniors win: 20 years of experience = knowing where things typically go wrong, so you don't let the AI make those mistakes. "AI does the same mistakes humans do because it's trained on our mistakes." The senior's real product is judgment — see product-ownership.
  • The junior risk (a security argument): the habit of clicking "yes… yes… allow for all future" is how "API keys are leaked, databases get dumped or deleted." A junior can't evaluate a 250-line bash script; a senior at least could. "Give a junior fresh out of university access to this almighty Claude and… the codebase — they will [wreck] it in two days." Read what you approve.
  • Team shape: the ~8-person scrum team (scrum master + PM + requirements engineer + big dev team) collapses to 23 people — one coordination/ownership role plus one or two who manage the coding agents, sharing responsibilities.
  • Leveling caveat: on pure programming skill, AI levels senior and junior (same output). The senior's edge is entirely in judgment, verification, and knowing failure modes — not typing speed. Contrast with connections-as-moat, where the edge is relationships.

Evidence

Contradictions / Uncertainty

  • Tension: if a junior + Claude can match a senior's output, "juniors are irrelevant" may reflect today's hiring psychology more than a permanent truth — and it raises an unspoken pipeline problem (where do future seniors come from?). Status: tentative.

Next Questions

  • If juniors can't get in, how does the industry produce the next generation of seniors?