The shape of a web team has changed more in the last five years than in the ten before. The frameworks changed, the tooling changed, the server came back, and now the tools write code. Here is what I think that does to the roles on a team.
The platform engineer
Every web team sits on a platform, the component library, the build pipeline, the rendering setup, and the conventions that make a codebase feel like one codebase. Someone has to own that, and I think it is the most important role on the team and the hardest to fill.
The job is to make other engineers faster by making the right thing the easy thing. It takes someone who likes building for engineers, can say no to a colleague, and measures success in work other people did.
The quality and accessibility owner
This is not a tester. It is an engineer who holds the line on how the product behaves for everyone, accessible, fast, and correct on the devices people actually use. The role has grown because the cost of getting it wrong has grown, and because tools that generate interface code generate inaccessible code unless something stops them. The owner builds that something, checks in the pipeline, rules in the library, a review habit on the team, and it pays for itself in audits that find nothing.
The product-minded engineer
When code is cheap to produce, deciding what not to build becomes the scarce skill. Every web team now needs an engineer who thinks about the product as a product. Who the users are, what they are trying to do, which of the twenty things the team could build will matter. An engineer who can take a vague ask, find the small version that answers it, and ship that.
Generalists who can move
The rest of the team, and most of it, should work across the stack, a page, the layer that feeds it, the component it needs, the test. The narrow front-end specialist who only did the view layer has been absorbed. What a generalist needs is judgment, not breadth of syntax, and judgment is what I hire for.
The role I would not hire for anymore
A dedicated build or tooling specialist. That work belongs to the platform engineer, and splitting it off produces someone who maintains the pipeline without owning what runs through it.
What this means for hiring
In an interview, I listen for a time the platform engineer made other people faster, whether the quality owner can say what a screen reader does with a page, and something the product-minded engineer chose not to build.
I think the team of 2026 is smaller than the team of 2020 and more senior, with less specialization and more judgment per person. It also sharpens the entry-level question, because a team that only hires judgment has to decide how judgment gets made.
Photo source: https://photos.robertstowe.com/san-diego
