Many founders start with one question: how much does it cost to hire a software developer hourly? The honest answer is a range, and the range is wide because an hourly rate prices time, not outcomes. A low rate can still produce a high bill, while a higher rate can produce a cheaper project. This article shows what published figures say, what they leave out, and how to turn a rate into a budget you can defend.
You do not need to read code to make this decision. You need to know what the number covers, who carries the risk when estimates are wrong, and how to test a developer before you commit. We cover each of those, and the section on hidden costs matters most, because that is where budgets tend to slip.
Published figures run from about $10 to about $100 per hour, depending on where the developer works and what they do. Upwork's cost page for software developers reports a median hourly rate of $20, with typical rates between $10 and $100 on its marketplace. A commenter in a Hacker News discussion on contractor rates says contract work through contract services generally pays $40 to $100 per hour, depending on location and skill set. Both are dollar figures from public sources, and neither is a quote for your project.
| Source | Reported figure | What it measures | What to keep in mind |
|---|---|---|---|
| Upwork cost page for software developers | Median $20 per hour; typical range $10 to $100 | Rates on one freelance marketplace | A midpoint across all listed developers, not matched to your scope |
| Hacker News discussion on contractor rates | $40 to $100 per hour for contract work through contract services | A commenter's view, tied to location and skill set | Describes pay to the engineer; an opinion, not a survey |
| Hacker News worked example | $105.77 per hour, or $220,000 per year | The rate a contractor needs to replace an employee income | One person's arithmetic, but it shows why rates look high |
Read these numbers with care. The Upwork median is a midpoint across every developer listed, so it says little about the specific work you need. The Hacker News figure describes what contract work pays the engineer, which is not necessarily the price a client sees. As a result, you should treat both as a sanity check rather than a benchmark for your own quote.
Studio and agency rates appear in neither source. When you speak to a studio, ask for its rate in writing and ask which roles the rate covers, such as engineering, design, and project management. A single blended rate and the rate for one developer are not comparable numbers, even when they look alike.
Location, experience, and specialization drive most of the spread. Upwork's own range runs from $10 to $100, a tenfold gap, and the Hacker News commenter ties the $40 to $100 band to location and skill set. So the question of how much does it cost to hire a software developer hourly has no single answer until you know who stands behind the rate.
Location also affects the cost of working together. Jeff Atwood, a founder of Stack Exchange and Discourse, argues that hiring from a global pool lets you find stronger people than hiring only nearby. Overlap in working hours still matters, because it decides how quickly your questions get answered, which means communication cost belongs in your comparison next to the rate.
An hourly rate is a price per unit of time, so the final bill equals the rate multiplied by the hours. Hours are the one variable you cannot see at the start. A developer who needs twice as long to understand your system costs more at a lower rate than a faster developer at a higher one. That is the reason to compare expected total hours, not rates alone.
Data that JetBrains reports in an InfoQ article on AI for software developers shows where those hours go. Programmers spend about 35% of their time understanding code, 5% writing it, 10% on other coding-related activities, and 50% on non-coding work. So most of what you pay for is reading, judging, and communicating. Typing is the smallest slice.
That split matters for budgets in two ways. First, experience shortens the understanding phase, which is the largest block of coding-related time. Second, an existing codebase lengthens it, which explains why work on older systems is harder to estimate. If your product already runs on aging software, our explanation of what a legacy software system is will help you judge how much of the budget goes to understanding before anyone changes anything.
An hourly rate prices time. Your budget depends on how many hours the problem actually needs.
It leaves out nearly everything around the hours: the developer's own overhead, the time they cannot bill, and your cost of managing the work. Each of these lands in your budget eventually, whether or not the quote mentions it. The three parts below take them one at a time.
A freelancer's rate has to replace what an employer would otherwise provide. One commenter in the Hacker News thread on contract engineer pay argues that moving from employee to contractor roughly doubles the hourly figure a person needs. The worked example reaches $105.77 per hour, or $220,000 per year. Behind it sit taxes, health and life insurance, paid leave, retirement savings, contractor insurance, legal and accounting fees, training, hardware, software, and hosting.
The same commenter also expects dry spells between clients, which means the rate has to cover unbilled weeks too. For you, a very low rate can mean the person works in a lower-cost location, bills more hours, or has not counted these costs. Each explanation can be legitimate, but each affects availability and how long the engagement lasts, so ask directly.
Your own costs rarely appear in a quote, yet they decide whether the project lands on budget. Count these before you compare offers:
Rework deserves special attention. Every change in scope adds hours at the same rate, so a vague brief is the most expensive input you control. A written requirements brief therefore protects the budget more reliably than a negotiated discount. Good briefs state the goals, the users, the must-have features, and what is explicitly out of scope.
Asking how much it costs to hire a software developer hourly now includes a question about AI tool usage, because many developers work with coding assistants and that usage has a price. Gartner predicts that AI coding costs will overtake the average developer salary by 2028 as large language model token consumption keeps rising, according to its June 2026 press release on AI coding costs. Whether those costs sit inside the hourly rate, appear as a line item, or fall to you is a question to settle before work starts.
Do not assume AI tools shorten the bill automatically. The JetBrains authors in InfoQ note that AI-written code may speed up small tasks but not necessarily large projects, and that critics find Copilot's output often verbose and hard to read. Since understanding code is already the biggest block of time, unclear generated code can lengthen it. Ask the developer how they use these tools and who reviews the result.
Hourly billing suits work you cannot define yet, fixed price suits work you can, and a retainer suits ongoing capacity. The real difference is who carries the risk when estimates prove wrong. Once you know how much it costs to hire a software developer hourly, compare that figure with a fixed-price quote for the same scope, and use the table below to see how each model shifts the risk.
| Model | Best suited to | Who carries estimate risk | What to confirm |
|---|---|---|---|
| Hourly (time and materials) | Exploration, small fixes, unclear scope | You, because hours accumulate until you stop | Weekly cap, reporting, who approves extra hours |
| Fixed price | A defined scope with written acceptance criteria | Mostly the provider, until the scope changes | What counts as a change, payment milestones, acceptance process |
| Retainer | Ongoing improvement or support | Shared; you pay for reserved capacity | Hours included, rollover rules, response times |
If your product has a defined scope, a studio can price the whole job against a written brief. Studios that build custom products, such as Xerx custom software and web app development, can quote this way, which moves much of the estimating risk from you to the provider. The hourly rate then matters less than the scope, the milestones, and the acceptance terms. Those three items decide what you pay, so read them as closely as the price.
Under fixed price, the change request is the main source of friction, because every change reopens the price. Agree up front how changes are estimated and approved. Contract terms, tax treatment, and how a freelance relationship is classified differ by country, so have a lawyer or tax adviser confirm what applies to your case.
Atwood describes the method in First Round Review's article on hiring the best and the brightest. He recommends an audition project: a real unit of work from your actual product, billed at an hourly rate, with a clearly defined mission. Keep it small, a few days or at most a week or two, and let the candidate choose whether to work in the office or remotely.
Atwood wrote about hiring employees, but the logic carries over to contractors and studios. You see how they communicate, whether they deliver on time, and how many hours real work takes, which gives you a data point for estimating the larger project. If the trial fails, he calls the cost a cheap exit compared with a long interview process. He also reports that candidates who passed the audition worked out for him, which is one experienced founder's observation, not a guarantee.
He raises one more point that applies to cheaper hires. Remote work handles mentoring poorly, because junior engineers need a rapid series of back-and-forth exchanges, so his teams hired at higher experience levels. If you hire a less experienced freelancer to save on the rate, you may end up as the mentor, and your time is part of the cost.
To answer how much does it cost to hire a software developer hourly for your own project, start from outcomes and work back to hours. Ask for estimates as ranges, split by phase, so you can see where the uncertainty sits. Then add your own cost lines and a contingency that reflects how well the scope is defined.
Then agree how progress is reported. Atwood suggests judging output rather than attendance, and he asks people to leave a record of the useful things they have done, a done list rather than a to-do list. For hourly work, a weekly done list next to the hours billed shows whether spend matches progress. The habit costs minutes and gives you early warning when hours drift.
The same method applies to other kinds of projects. If you are building a shop, our breakdown of headless e-commerce implementation costs shows how platform choices change the hours involved. If the work involves AI agents, our guide to connecting AI to your business explains what the integration side of those projects covers.
Asking how much does it cost to hire a software developer hourly is the right first question, but it is not enough on its own. Quotes only become comparable when each one answers the same follow-ups.
Put the answers side by side and the quotes become comparable, even when the rates are not. A higher rate with a clear scope and a short trial can cost less than a lower rate with open-ended hours, and these five questions show you which one you are looking at.
Upwork's cost page reports a median of $20 per hour, with typical marketplace rates between $10 and $100. A commenter in a Hacker News discussion puts contract work through contract services at $40 to $100 per hour. Studio rates are not covered by those figures, so ask any studio for its rate and what the rate includes.
Neither is cheaper by default. Hourly billing suits unclear scope but leaves estimate risk with you, while fixed price works when the scope and acceptance criteria are written down and moves more of that risk to the provider. Confirm how changes are priced under either model.
A contractor's rate has to cover costs an employer would otherwise carry, such as taxes, insurance, paid leave, training, equipment, and gaps between clients. A Hacker News commenter argues this roughly doubles the hourly figure needed to match an employee income.
Jeff Atwood, writing in First Round Review, suggests a small real task that takes a few days and at most a week or two, billed at an hourly rate with a clear definition of the work.
Not automatically. The JetBrains authors in InfoQ say AI may speed up small tasks but not necessarily large projects, and Gartner predicts AI coding costs will exceed the average developer salary by 2028. Ask how the developer uses these tools and who pays for them.
Keep reading
A quote for a headless shop looks larger than the platform price suggests. Here is where the money goes, what founders underestimate, and when the spend pays back.
A plain-language guide for founders and business owners on writing a specification your studio can price, build and test against, without writing any code.
A compact worked example of a requirements document, with the quality targets most briefs leave out. Use it to brief a studio and get a quote you can compare.
