The new shape of the team
1. Teams got smaller and denser
In 2015, a team that owned a single product surface — say, the checkout flow at a mid-sized company — was eight to twelve engineers. By 2026, the same surface is owned by four to seven.
The team didn't lose work. It absorbed the same workload with fewer people because each engineer ships more code, and ships it faster, with the model in the loop. The headcount went down. The leverage per head went up.
Three things follow from smaller, denser teams. Each one matters for how the day works.
First, every engineer is closer to the business. There's no layer of engineers shielded from product decisions. If you're on a five-person team, you're in the room when the priorities get set.
Second, every engineer reviews more code. When a team of six ships what a team of ten used to, the review load per engineer goes up. Reviewing well is the senior tax that keeps the small team from shipping the wrong things.
Third, every mistake is more visible. On a team of ten, your bad call gets caught by one of the other nine. On a team of five, it gets caught by one of the other four, or it doesn't get caught at all. The margin for sloppy work shrank.
2. Junior engineers still exist, and they do different work
The pattern isn't "no juniors." The pattern is "fewer juniors, doing higher-leverage work earlier."
A 2015 junior spent the first three months on small, isolated changes. A 2026 junior is, by week six, drafting whole features with the model and shipping them under a senior's review. The ramp got steeper because the floor of useful contribution moved up.
What this looks like in practice:
- A junior is expected to write a clear spec for a small feature on day one. The senior helps them sharpen it. They don't start with "fix this typo" tickets.
- A junior is expected to read the model's output critically from the start. That used to be a senior skill. It's now table stakes.
- A junior is expected to ask better questions, because the model handles the easy ones. Their colleagues' time goes to the hard ones.
The juniors who do well are the ones who treat the model as a tool, not an answer. The juniors who struggle are the ones who ship whatever the model produced and call it done.
3. Architects and implementers split a little more
In 2015, the senior IC role was a continuum. Some seniors leaned toward architecture (designing systems). Others leaned toward implementation (shipping the systems). The split was real but soft.
In 2026, the split is sharper. Architecture skills — designing the right system, picking the right tradeoffs, communicating the design — got more valuable per hour, because the model amplifies whatever design you give it. Implementation skills — taking a design and turning it into working code — got cheaper, because the model does most of the turning.
This doesn't mean there are now two job titles. It means a senior engineer who's strong on architecture and weak on implementation is more useful than they were, and a senior engineer who's strong on implementation and weak on architecture is less useful than they were. The market values the architecture half more.
4. PM and engineer roles blur a bit
Specifications used to be a back-and-forth between product managers and engineers, with the PM writing the product requirements and the engineer writing the technical design.
Now the spec is the central artifact, and whoever writes it sets the quality of what ships. Sometimes that's the PM. Sometimes it's the engineer. Often it's both, in a shared document.
The result: PMs are more technical than they used to be, because they need to write specs that survive contact with the model. Engineers are closer to product than they used to be, because they're often the ones turning a fuzzy idea into a concrete spec. The roles don't merge. They just touch more.
5. The new standard role — AI-output reviewer
Every team now has a function called "the careful reader." It isn't a job title in most companies, but it's a role on every team.
The careful reader is the person who reads what the model produced — code, tests, docs, specs — and catches the subtle wrong thing. Sometimes that's a senior engineer. Sometimes it's a technical PM. Sometimes it's a security or platform person reviewing the team's pull requests.
What changed isn't that careful reading exists. People reviewed code in 2015 too. What changed is volume and stakes. Every shipped change has model-generated content in it. Every shipped change needs a careful reader. The role used to be 10% of someone's day. It's now 30 to 40% of every senior engineer's day.
If you're new to the field and wondering what skill to build first, build this one. Careful reading travels with you to every team you'll ever join.
6. Team shape, side by side
| Aspect | 2015 team | 2026 team |
|---|---|---|
| Size for a product surface | 8 to 12 engineers | 4 to 7 engineers |
| Ratio of seniors to juniors | Roughly 1:1 | Roughly 2:1 or 3:1 |
| Time per senior spent reviewing | 10 to 15% | 30 to 40% |
| Time per senior spent writing code from scratch | 50 to 60% | 15 to 25% |
| Architects and implementers | Soft split | Sharper split |
| PM and engineer overlap | Hand-off, with discussion | Shared spec document |
| Engineers per product manager | 4 to 6 | 3 to 4 |
| The careful reader role | Informal, occasional | Explicit, every change |
| Onboarding time for a new hire | 3 to 6 months to first useful contribution | 2 to 6 weeks to first useful contribution |
7. What this means for you
If you're entering the field, the team you join will be smaller, denser, and closer to the business than the team your mentors joined. You'll be expected to contribute earlier, read more code, and write fewer lines yourself.
If you've been in the field a decade, the team you're on now is reshaping under you. Lean into the architecture half of senior work. Spend more time reviewing well. Mentor the juniors on reading the model's output, because that's the skill that will let them grow.
That's the end of Chapter 1. The next chapters zoom in on how engineers work day to day, which skills carry the most weight, what the career path looks like, the mindset that helps, and where to go from here.