How to write it
Claim depth somewhere, or the breadth reads as shallow
"Full stack" is a claim about range, and range alone doesn't get hired at any level above junior. Every full stack resume that works has a centre of gravity — the data layer, the API, the interface, the infrastructure — and says so.
One sentence in the summary is enough: "strongest on the data layer". It converts the breadth from a hedge into a shape. A reviewer now knows what you'd be trusted with on day one and what you'd grow into, which is exactly the question they were trying to answer.
The unit of work is the feature, not the layer
The reason full stack roles exist is that a single person who can take a feature from schema to shipped interface removes a whole class of coordination cost. So write bullets at that altitude: the feature, its layers, and what it did for the business.
"Shipped the reporting product end to end — Postgres schema, Node API, React interface — now 30% of company revenue" makes the argument in one line. Splitting the same work into a frontend bullet and a backend bullet makes you look like two half-engineers.
Deployment counts, and most candidates omit it
In small teams the person who ships the feature also ships it to production. If you have owned deploys, environments, CI pipelines or monitoring, that is a differentiator worth a bullet — it's the difference between a developer who needs a platform team and one who doesn't.
It's also the most common gap in full stack resumes, which makes it cheap signal. Preview environments, a pipeline you built, an incident you handled, a rollback that worked.
Show product sense in the framing
Generalists are usually hired into small teams, where the ability to ask whether a feature is worth building is nearly as valuable as building it. You demonstrate that not with a claim but with framing: say what the work was for.
"Built the SSO integration that unblocked 6 enterprise deals" is a technical bullet with a commercial reason in it. That sentence does two jobs, and the second one is the reason a startup founder reads on.
Keep the stack list honest
A full stack resume is where skills lists go to become unbelievable — four languages, three frontend frameworks, two clouds, six databases. It has the opposite of the intended effect, because a reader assumes the whole list is inflated and stops trusting the parts that were true.
Ten to twelve technologies, all of which you'd be happy to be interviewed on, in groups. Anything you last touched in a tutorial three years ago comes off.