What a backend developer does
A backend developer builds the invisible machinery: databases, user accounts, payment processing, and the logic that runs when someone clicks “submit.” If a frontend developer builds the storefront, the backend developer builds the warehouse, the ledger, and the locks.
The deliverable is a working system plus the things that make it survivable: documentation, deployment setup, and credentials in your name. A backend that only its author understands isn’t an asset — it’s a dependency with a monthly invoice.
Adjacent role worth knowing: if your project is mostly about connecting existing systems rather than building new ones, you may want an API developer instead, which is often a smaller job.
What it costs
Independent backend developers typically charge $60–$180 per hour. The range tracks experience with production systems — code that handles real users, real money, and real failures. What moves the rate:
- Stakes — payments, personal data, and anything regulated demand experience, and experience bills accordingly.
- Scale — a system for 100 users and a system for 100,000 are different engineering problems that happen to share a description.
- Legacy — modifying an existing codebase safely costs more per hour than greenfield work, because first they have to understand what’s already there.
Budget scenarios are in our backend developer cost guide.
How to evaluate one
You can’t inspect the work directly, so inspect the thinking. Describe your project and listen for questions about failure: what happens when a payment fails halfway, when two users edit the same record, when traffic spikes. Professionals think in failure modes. Amateurs think in happy paths.
Ask them to explain a past architecture decision to you like you’re smart but non-technical. If they can’t, every status update for the next three months will be a fog. And get the scope in writing — a statement of work matters more here than almost anywhere, because “build the backend” can honestly mean $3,000 or $30,000 of work.
Packages and commitment
Backend systems aren’t finished; they’re launched. Libraries need updates, servers need patches, and the third-party services you depend on change their rules on their own schedule. Before hiring, ask what maintenance looks like: some developers offer a monthly retainer, others bill ad hoc, some disappear after handoff.
There’s no wrong answer, but there is a wrong surprise. A fair setup for most small projects: fixed scope for the build, a 30-day bug-fix window included, then a small monthly retainer or an agreed hourly rate for whatever comes next. Get all three in the contract before work starts.
Questions to ask before you hire
- How will you handle my users' data, and where will it live?
- What happens if the server goes down at 2 a.m. — what breaks, and who gets alerted?
- How do you document what you build so I'm not dependent on you forever?
- What would this system cost to run monthly after you're done?
- Have you built something at the scale I'm describing, or one size smaller?
Red flags
- Vague answers about data security and backups. This is their whole job.
- No mention of ongoing hosting or infrastructure costs — you'll discover those on your first bill.
- Everything they've built is a demo or side project; nothing has real users.
- They resist writing anything down. Undocumented backend work is a hostage situation waiting to happen.