A note on this archive: an earlier version of this site was lost in a migration, with no surviving backup. This piece is a good-faith recreation of our writing from this period, not a recovered original; its date reflects the period it represents. See about this archive.
"Full-stack developer" is the most-requested title we hear right now. It's also the most misunderstood, and that combination costs companies real money in bad hires and long, fruitless searches.
What people think it means
Most job posts that ask for a full-stack developer are quietly asking for a unicorn: someone who designs the database, writes the API, builds the front end, configures the servers, sets up the deploy pipeline, and makes it all look good — at an expert level, on every layer, at the same time.
That person mostly doesn't exist. And the ones who confidently claim to be expert at all of it are usually the ones you should worry about most.
What it actually means
A real full-stack developer can work comfortably up and down the stack and is genuinely deep in at least one part of it. They can pick up a ticket that touches the database and the screen without filing a help-desk request — and, this is the important part, they know where their own edges are. They'll tell you, "I can build this, but for the security piece you want someone who lives in it."
Range, plus honesty about the gaps. That's the actual skill. People call it "T-shaped": broad across the top, deep in the stem.
Why the confusion is expensive
We've written before about how tight the senior market is. When you post for expert-everything in a market like this, one of two things happens: you get no qualified applicants, or you get someone willing to claim skills they don't have. Both cost you weeks.
The fix is to write the post for the person who actually exists. Describe the range you need, name the one or two areas where you need real depth, and say plainly that you don't expect mastery of every layer. Honest postings attract honest applicants.
How to screen for it
When you're evaluating a full-stack candidate, skip the trivia. Instead:
- Give them something that crosses a boundary. A small task touching data, logic, and the screen tells you more than any quiz about which layer they're truly comfortable in.
- Ask what they'd hand off. A developer who can name the parts they'd want help with is showing you judgment, not weakness.
- Watch how they handle "I don't know." The best ones say it early — and then tell you how they'd go find out.
One more thing for small teams
If you're a small company, a strong full-stack senior is worth a great deal — they cover gaps a bigger team would split across three people. Just don't mistake "covers the gaps today" for "is a whole engineering team forever." Bring on the generalist to get moving, then add depth where the product gets serious. We walked through the broader version of this in three steps every company should take to hire a developer.
"Full-stack" isn't a magic word for one person who does everything. It's shorthand for range and judgment. Screen for those two things and you'll do fine.