4.3 KiB
4.3 KiB
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 2–3 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.
- What the levelling actually consumed (thorsten-ball, 2026-07-28): the transferable content of seniority. "What senior engineers used to hand-teach in 2–3 years" — his example is the safe multi-step column-drop migration — "is now a 30-second model output." So the knowledge half of seniority is commoditised while the judgment half is not, which is a sharper version of this page's claim and a harsher one for the pipeline: juniors are squeezed out of the entry-level work and the apprenticeship that work used to constitute. He also notes the end of a lucky historical overlap: the person who loved Haskell on weekends was also the person who modelled the finance backend well; those two skills have now come apart, and only the domain half is scarce.
- The floor rose, not just the ceiling. "You cannot take a programmer who doesn't use AI, they're going to get crushed by a mediocre programmer with AI." Read alongside the levelling caveat, the competitive line is no longer senior-vs-junior but tooled-vs-untooled — which is the same claim allie-miller makes about the irreversible gap, stated about professionals rather than individuals.
Evidence
- Seniors more valuable, juniors squeezed, "allow-all" security habit, junior-wrecks-it-in-2-days, team collapse to 2–3 — 2026-07-14-sebastian-eugene-interview.
- 2–3 years of hand-taught knowledge → 30-second output; the dissolving Haskell/finance overlap; "crushed by a mediocre programmer with AI"; "don't compare yourself to the 1%" — 2026-07-28-agentic-engineering-10x-developer.
Related Pages
- Concepts: product-ownership, enterprise-ai-reality, connections-as-moat, code-as-throwaway, explosion-of-internal-software, shedding-weight
- Entities: sebastian, eugene, thorsten-ball
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.
- Don't generalise from the 1%. Thorsten's caution cuts across this whole page: online debates cite Mitchell Hashimoto (Ghostty, a GPU-accelerated terminal emulator) as proof AI "isn't good enough," but that is one of the best programmers alive on atypical software. Most software is CRUD, "MySQL and something-something," which agents handle fine. The senior's judgment premium is real where failure is expensive and thinner than the discourse suggests everywhere else.
Next Questions
- If juniors can't get in, how does the industry produce the next generation of seniors? (Compounded 2026-07-28 — the apprenticeship content itself is now a 30-second output, so the answer cannot be "they'll learn it on the job.")