What a full-stack developer does
A full-stack developer builds a whole application — the part users see and the machinery behind it — and can carry a small product from idea to live site alone. In practice they combine what a frontend developer and a backend developer do: interface, database, user accounts, payments, and deployment.
The honest truth about the title: nobody is equally expert across the entire stack. Most full-stack developers lean one way and are competent on the other side. That’s fine, and for most small projects it’s ideal — one skilled generalist ships faster and communicates more simply than a two-person split, because there’s no handoff between front and back. The deliverable is a working, deployed app plus documentation and credentials in your name.
What it costs
Independent full-stack developers typically charge $60–$180 per hour. Straightforward apps against a clear spec sit near the bottom; work involving payments, real scale, or an existing codebase sits at the top. Three things move the rate:
- Stakes — anything touching money, personal data, or regulation demands experience, and experience bills for it.
- Scale — an app for 100 users and one for 100,000 are different engineering problems that share a description.
- Legacy — safely changing an existing codebase costs more per hour than building fresh, because first they have to understand it.
See the full breakdown in our full-stack developer cost guide.
How to evaluate one
Ask for one thing they built end to end that real people use — a live URL, not a tutorial clone. Then probe the seam between front and back: how do they keep data consistent, handle a failed payment, or manage a user who does something unexpected? A true full-stack developer thinks across that boundary naturally.
Find their weaker side and ask what they’d do when a project needs deep work there. “I’d bring in a specialist” is a good answer; “I’m equally expert at everything” is a warning. Get scope in writing, because “build my app” can honestly mean $5,000 or $50,000 — a statement of work forces the conversation. And decide up front whether you want hourly or fixed-price billing for the build.
When one generalist beats a team
For an MVP, an internal tool, or a first version you’ll test with real users, one full-stack developer is usually the right call: cheaper, faster, and simpler to manage. There’s no coordination overhead and one person owns the whole picture.
You outgrow that when the product succeeds — when the front end needs a design specialist’s polish and the back end needs to handle serious scale at the same time. That’s the moment to split the roles. Until then, hiring two people for a job one can do just adds meetings. If you’re not sure the project needs custom code at all, our DIY website vs hiring a developer comparison is worth reading first.
Questions to ask before you hire
- Can you show me something you built end to end, from the interface down to the database?
- Where will my app be hosted, and what will it cost to run each month after launch?
- How do you document and hand off, so I'm not locked to you forever?
- What part of the stack are you strongest in, and where would you bring in help?
- How do you handle security for user data and payments?
Red flags
- Claims to be expert at everything with equal depth. Real full-stack developers have a stronger side.
- No live product with real users, only tutorials and demos.
- Won't discuss ongoing hosting and maintenance costs before you sign.
- Resists documentation. An undocumented app built by one person is a single point of failure.