The three-way split between engineering, product, and design is collapsing at the center
Companies no longer want clean handoffs between engineers, product managers, and designers. They want people who can do more than one job at once, and some are already restructuring teams around that premise.
The three-way division of engineering, product, and design is losing its organizational logic. Adam Ward describes what companies actually want today as a squeezing together of the three disciplines: designers who can build, and deep technical engineers who carry genuine product sense. The old model, where each role handed off cleanly to the next, is not breaking down at the edges. It is breaking down at the center.
The staffing implications are already showing up in how teams are being composed. Ian Silber points to startups that are now considering something close to two designers for every one engineer, a ratio that would have been nearly unthinkable against the traditional balance in which designers were vastly outnumbered by engineering headcount. The logic behind that inversion is not that code has become less important. It is that the supply of people who can build has expanded enough to change what scarce talent actually means.
Martin Casado, a general partner at Andreessen Horowitz, supplies the founder-level version of the same pressure. Pitching without a live product is now disqualifying at any stage, he argues, because building has become so accessible. The bar that once separated a founder with a working product from one without has dropped enough that showing up without something live reads as a signal about judgment, not just resources. Casado also observes that the dominant founder archetype is shifting: fewer business-background generalists, more technically sophisticated early-career researchers. He is direct about the tradeoff, noting that business sophistication is lower in this cohort, but technical sophistication is dramatically higher.
Our engineers stopped coding around a year ago. So since then they didn't code. What they have is hundreds of AI engineers that they code for them. Matteo Franceschetti
Matteo Franceschetti, co-founder of Eight Sleep, pushes the trajectory to a point that reframes the conversation entirely. His engineers stopped writing code roughly a year ago. What they have instead, he says, is hundreds of AI engineers coding on their behalf. The human engineers did not disappear. Their work reconstituted around direction and judgment rather than implementation. That is a different job description, and it sits some distance from the current consensus about what engineering hiring should look for.
What the evidence does not yet resolve is whether the reconstituted role is genuinely new or whether it is a return to something older: the full-stack generalist who existed before organizations grew large enough to justify specialization. Casado’s observation about founders, Ward’s framing of what companies want, and Silber’s inverted ratio all point to a hiring market that is still working out what to optimize for. The old ratio, the old interview process, the old job description, all of these were built around assumptions about what was hard to do alone. Those assumptions are changing faster than the org charts that encoded them.
The result is not a skills shortage in the traditional sense. It is a mismatch between the profiles companies now say they want and the pipelines that were built to produce the profiles companies used to hire. Engineers trained to treat product judgment as someone else’s responsibility, and designers who never needed to think about implementation, are the product of an organizational logic that is actively being revised. The revision is not gradual.