The new ladder — junior, senior, staff in the AI era
1. The ladder didn't disappear
You'll hear that AI killed the junior role. It didn't. What it killed was a specific version of the junior role — the one whose main job was to type out code that more senior people had already designed.
The ladder is still there. The rungs got narrower and the work at each rung shifted up. A junior today does work that looked like mid-level work in 2015. A senior today does work that looked like staff work in 2015. The whole stack moved up, because the floor moved up.
That's the headline. The rest of this unit is the detail.
2. The junior in the AI era
A junior engineer in 2026 is still someone in their first one to three years on the job. They still ramp up on a codebase, ask questions, and pick up the team's rhythm.
What changed is the texture of the day. They write fewer lines of code from scratch. They spend more time reading what the model wrote, deciding whether to keep it, and explaining why. They run tests sooner. They ask better questions, because the model has already taken the first pass at the easy ones.
The junior who treats the model as a faster typewriter struggles. The junior who treats it as a peer to argue with grows fast. By month six, the gap between those two juniors is the difference between getting a second-year offer and getting let go.
3. The senior in the AI era
A senior used to be someone who could be trusted to ship a whole feature, end to end, with minimal review. That part hasn't changed.
What's added: a senior now ships several features in parallel by running multiple model sessions, each with a clear specification. They don't type most of the code. They write the spec, set the constraints, review the output, and decide what's good enough. They catch the mistakes the model makes that a junior would miss.
A senior in 2026 has the same depth of system understanding as a senior in 2015. They just spend more of their day deciding and less of it typing.
4. The staff engineer in the AI era
Staff engineers operate above the level of any one team. They set architecture. They influence what gets built across the organization. They mentor seniors. None of that went away.
What got added: staff engineers now set the patterns the whole engineering org uses with the model. Which workflows are sanctioned. Which guardrails exist. What "good use of the model" looks like for the company. They also do the design work for systems whose specifications are AI-shaped — eval pipelines, agent loops, retrieval systems. The architectural surface area grew because there's a new layer to design for.
5. 2015 vs 2026, side by side
| Level | 2015 ladder | 2026 ladder |
|---|---|---|
| Junior | Implements designs handed down. Types a lot of boilerplate. Learns the codebase by writing in it. | Drives the model through small tasks. Verifies output. Reads more than they type. Learns the codebase by reading and explaining. |
| Senior | Ships features end to end. Mentors juniors. Owns a domain. | Same, plus orchestrates several model sessions in parallel. Writes specs and reviews output at scale. |
| Staff | Sets architecture across teams. Influences what gets built. Resolves cross-team design fights. | Same, plus sets the org's AI workflow patterns, guardrails, and eval discipline. Designs the AI-shaped systems. |
The columns aren't replacements. The 2026 column is the 2015 column plus the new work.
6. What this means for you
Whichever rung you're on, the floor moved up. The work that used to fill your day got faster. The expectations for what you ship in a week rose with the speed. The engineers who feel busy are the ones running the new pace. The engineers who feel slow are still operating at the old one.