The front of the front-end, three years on

Brad Frost named the split in 2021: front-of-the-front-end developers own HTML, CSS, presentational JavaScript, accessibility and design systems; back-of-the-front-end developers own data, state, auth and infrastructure. The essay gave a job description to people who had spent years being told their half of the discipline was the easy half. Three years and one AI wave later, the divide has not closed. It has become the org chart.

What changed

The title stuck, for one. "Design engineer" job postings were a curiosity in 2022; now most serious product companies have the role, sitting where I have always worked — the seam between a Figma file and a merged pull request. The work did not change so much as get named, budgeted and promoted against.

The platform also quietly absorbed a decade of workarounds. Container queries, :has(), OKLCH, subgrid, view transitions, native popovers and anchor positioning all shipped in stable browsers. A striking amount of what used to require a front-of-the-front-end specialist to hack together in JavaScript is now a CSS one-liner — which sounds like the role shrinking, and is actually the opposite. The specialist is the person who knows the one-liner exists.

Then the machines started writing markup

The uncomfortable question of the moment: if a model can generate a component from a screenshot, what is the front of the front-end for? Having spent two years reviewing generated UI code, my answer is: more than before. Models are extraordinary at producing plausible interfaces and indifferent to whether the tab order works, the contrast passes, the div soup means anything to a screen reader, or the styles cohere with the other four hundred components in the product.

Generated code amplifies whatever system it lands in. A codebase with a real token contract and accessible primitives turns AI output into leverage — the model reads the pattern and extends it. A codebase without one turns AI output into sediment, plausible-looking layers of it, faster than any team can review. The design system is no longer just how you scale humans. It is how you constrain machines.

The seam is the job

Three years on, I would sharpen Frost’s framing: the front of the front-end was never really about owning CSS. It is about owning the translation layer where design intent becomes durable code — tokens, primitives, motion, accessibility, the stuff both designers and back-end engineers assume someone else is handling. That seam has only widened. Someone has to live in it, and it remains the best seat in the industry.