Full-stack developers and the impact on the software industry

The software industry spent fifteen years specialising. Front end split from back end, back end split from infrastructure, infrastructure split from security, and every split created a boundary. Boundaries are where estimates go to die.

What a full-stack developer actually is

A full-stack developer is a hybrid of both disciplines, which means they can tackle global projects rather than a slice of one. That does not mean knowing everything equally. It means being able to carry a feature from an interface decision through to a production deploy without needing three colleagues and two weeks of coordination to do it.

The useful test is simple: can this person diagnose a slow page? A specialist front-end engineer will look at bundle size. A specialist back-end engineer will look at the query. A full-stack engineer will look at both, find the N+1 query that the front end is triggering by fetching in a loop, and fix the actual problem in an afternoon.

Where the money actually goes

On a specialised team, a meaningful proportion of the calendar is coordination. A ticket is written by one person, picked up by another, blocked on a third, clarified in a meeting, and delivered a week after it could have been. None of that is anybody's fault; it is a property of the structure.

Reduce unnecessary handoffs and you reduce the calendar, the meetings and the specification overhead simultaneously. That is the economic argument for cross-functional ownership; it is not an argument for pretending every hard problem needs no specialist.

Where specialisation still wins

Honesty matters more than advocacy here. Specialists are correct in several situations:

• Very large systems. Past a certain size, the domain in each area is deep enough that range stops paying.
• Genuinely hard sub-problems. Cryptography, compilers, real-time graphics and safety-critical systems reward a decade in one place.
• Regulated environments where separation of duties is a requirement rather than an inefficiency.
• Design. A full-stack engineer who can implement an interface is not a substitute for someone who can decide what it should be.

How to hire for range

Look for people who have shipped something end to end and can describe what went wrong. Ask about a decision they reversed. Ask what they would do differently. A candidate who has only ever owned one layer will answer well about that layer and vaguely about the seams — and the seams are where the work is.

The impact on the industry

Cheap, capable tooling has moved the boundary. Managed databases, container platforms and framework conventions mean one engineer can now competently operate territory that needed a team a decade ago. That is not a threat to specialists — it is a change in where the specialist line sits, and it moves further every year.

For a company buying software, the practical consequence is this: ask how many people a feature has to pass through before it reaches production. The answer predicts your timeline better than any other question on the list.