
Sajjaad Khader · 13:50 · Watch on YouTube
Summary
An interview with Mihail Eric, Stanford lecturer and head of AI, on where software engineering is actually headed under coding agents. Eric argues the job market squeeze on CS grads is real and measurable, but that the thing being replaced is a shape of work — spec-in, code-out ticket execution — not engineering itself. He names three roles he expects to disappear, three he expects to explode, and the three concrete skills that separate the engineers who thrive: task decomposition, context switching across multiple agents, and building agent-friendly codebases. He closes by pushing back hard on the idea that juniors have no future, and says he's hiring them.
Topics
flowchart TD
A["1 · The junior hiring squeeze<br/>6.1% CS unemployment"] --> B["2 · 3 jobs AI could replace"]
A --> C["3 · The case for junior engineers"]
C --> D["4 · Is a CS degree still worth it?"]
D --> E["5 · Become interdisciplinary"]
E --> F["6 · The top 1% engineer<br/>3 agentic skills"]
F --> G["7 · 3 jobs that will explode"]
B --> G
G --> H["8 · Final advice"]
- The Junior Hiring Squeeze — the 6.1% unemployment number, the vanished ramp-up buffer, and why employers pick seniors
- Three Tech Jobs AI Could Replace — manual QA, entry-level consulting, entry-level data analysis, and the criterion behind all three
- The Case for Junior Engineers — the slope vs. Y-intercept model and why startups need it
- Is a CS Degree Still Worth It? — 2021 vs. 2026 economics, and the meta skills that justify the cost
- How to Avoid Being Replaced: Become Interdisciplinary — the UX-student-to-Vercel-app example and the merge formula
- How to Become a Top 1% Engineer — decomposition, agent context switching, agent-friendly codebases
- Three Tech Jobs That Will Explode — forward deployed engineer, AI platform engineer, AI feature engineer
- Final Advice — the trap to avoid, and Eric's own hiring position
Key takeaways
- Computer science sits at 6.1% unemployment — seventh highest among all college degrees, and Eric attributes it to an expectation gap rather than to AI directly replacing headcount
0:512:02. - The 3–12 month ramp-up buffer for new grads is gone. Facing two candidates for one role, employers now pick the senior specifically because they need less ramp-up — which Eric calls myopic
1:171:38. - The replaceable category is defined by task shape, not title: work describable as a Jira/Linear ticket, where you take a spec and execute it, is easy to outsource to a coding agent — which covers most outsourced and body-shop consulting labor
2:213:36. - Three roles Eric expects to disappear: manual QA engineers, entry-level consultants, entry-level data analysts
2:543:17. - Three roles Eric expects to explode: forward deployed engineer, AI platform engineer (owning eval and inference choices — Brain Trust, Judgment Labs, Fireworks, Modal), and AI feature engineer (bespoke vertical agents on top of that platform)
10:4811:3412:11. - Juniors win on slope, not intercept. Their starting capability is lower, but their rate of picking up new tools is far higher — and Eric says the place seniors stumble is aversion to change, which matters most at speed-driven startups
4:124:33. - The junior hiring freeze is a short-term optimization, not a considered strategy: managers with a head count mandate default to "cut people, throw more cloud tokens at it"
5:436:06. - A CS degree pays off only for meta skills — scoping open-ended projects, talking to people, defining requirements — not for "learn Python, walk out with a job," a framing Eric rejects outright
6:146:42. - Merging a second discipline with coding agents is the strongest defense, demonstrated by a UX student whose system turned rough notebook sketches into a functional Vercel-hosted web app with fidelity Eric called "crazy good" — because the edge is world context, which agents lack
7:167:398:03. - Top-1% engineering is now three skills: decomposing complex tasks with their dependencies, context switching across parallel agents ("you're the scrum master of a team of agents" who are "the most eager interns on the planet"), and preparing agent-friendly codebases
8:238:459:42. - Agent-friendly means strong test coverage and a strong build system, in place first — build the house before anyone adds rooms — and only then is running multiple agents in parallel safe from sloppy output
10:0010:20. - The forward deployed engineer's real job is translation: a customer reporting "this button doesn't work" often needs an entirely different feature they don't know exists
11:08. - "It's a wrong prediction to say that there's no hope for juniors at all in this new world" — and Eric backs it with the statement that he is currently hiring the right kind of junior engineers
13:10.
The full transcript is included in this folder for reference.