Desired Hourly Rate: What to Put, and How to Set Your Desired Hourly Compensation

Put a researched hourly range in a desired hourly rate field, with your target at the top of it, and give one clean figure only where the form will not accept anything else. Build the number from the whole cost of the role rather than by dividing a salary by 2,080, because that division ignores employment taxes, health premiums, retirement contributions, and unpaid time off. For a contract engagement, matching a 120,000 dollar salaried job takes roughly 76 dollars an hour, not the 57.69 the simple math produces. If you have no market figure yet, say what scope you are quoting for before you name a rate.

That is the short answer. The rest of this is the arithmetic behind it, and what to type when a form gives you one box and no context.

The mistake that costs contractors the most: dividing the salary by 2,080

There are 2,080 working hours in a standard US year, so a 120,000 dollar salary looks like 57.69 an hour. Almost every rate conversation starts there, and it is wrong in two directions at once. It counts only the salary, ignoring everything else the employer was paying on top of it, and it assumes you will bill all 2,080 hours, which no contractor does.

Federal data puts a number on the first half. In March 2026 the Bureau of Labor Statistics measured private industry compensation at 46.60 dollars an hour, of which 32.60 was wages and 14.01 was benefits. Benefits are 30.1 percent of the total, which is the figure usually quoted, but measured against wages, which is what you are converting from, they add about 43 percent on top. Here is what that looks like on a real salary.

So the honest conversion is about 76 an hour, not 57.69. That is 32 percent higher than the simple division, and the gap is not padding or a negotiating cushion. It is the cost of the things that quietly stopped being someone else's problem. Family coverage widens it considerably: KFF puts the average family premium at 26,993 with the employer paying roughly 20,143, which on the same math pushes the equivalent rate past 82 an hour.

Then there is utilization, which is the part people discover in year two. Nobody bills every available hour. Time spent on proposals, contracts, invoicing, and chasing payment is real work that no client pays for, and at 85 percent utilization the same package needs about 89 dollars an hour. Some of that overhead is worth automating early rather than absorbing, since getting those invoices actually paid on time is the difference between a good rate and a good year. Track your billable percentage from the first month, because it is the number that decides whether your rate was right.

What to put for desired hourly rate on an application

The field type decides the answer, exactly as it does for desired salary on an application. What you are really reading is whether a person or a database is on the other side of the box.

One thing worth saying plainly: whatever number you write, expect the engagement to be built at the bottom of it. If you would resent working at the bottom of your own range, the range is wrong. Our guide to salary requirements covers why the wording of the question pulls people toward naming a floor.

"What is your expected hourly rate for this role?"

Answer this one with a question of your own before you answer it with a number. Ask what the engagement is scoped at, whether it is W-2 or 1099, and how many hours a week they expect. Those three facts move a defensible rate by twenty dollars or more, and answering without them means guessing. If they will not say, give a range and attach the assumption: "Around 75 to 85 for a 1099 engagement at roughly 20 hours a week, and I would revisit that for full time or W-2."

Naming the assumption does more work than the number. It shows you price on scope rather than on hope, and it gives you a clean, non-awkward reason to revise the figure later when the scope turns out to be different, which it usually does.

Setting a desired hourly rate when you have never contracted before

Start from the salaried package you would otherwise be taking, run the conversion above, and treat the result as your floor rather than your ask. That anchors you to something real instead of to whatever rate a forum thread suggested. Then adjust for three things: how specialized the work is, how long the engagement runs, and how much of the risk you are carrying.

Long engagements can justify a lower rate because they cut your unbillable sales time. Short, urgent, or highly specialized work justifies more. Fixed-scope work where you carry the overrun risk should price above hourly work where the client does. And if the client is asking you to work through a staffing agency, remember the agency takes its margin out of the same budget, so the rate you are quoted is not the rate the client is paying.

Questions people ask about desired hourly rate

What should I put for desired hourly rate?

Put a narrow range built from market data for that exact role and metro area, with your target at the top. Where only one figure fits, give a single number near the top of your band. Build it from the full cost of the equivalent salaried job, not from the salary alone, and state whether the figure is W-2 or 1099.

How do I convert my salary to an hourly rate?

For a salaried job, divide by 2,080. For contract work, add the employer's payroll taxes, health premium, and retirement contribution to the salary first, then divide by the hours you will actually bill after time off. On a 120,000 salary that is roughly 142,705 divided by 1,880, or about 76 an hour, rather than 57.69.

Should I give a range or a single hourly rate?

Give a range wherever the field allows text, and a single figure only where it does not. A range keeps you inside a screening filter while its top sets the anchor. Keep it about ten to fifteen percent wide, because a spread of forty dollars an hour reads as someone who has not priced the work.

What is the difference between desired hourly rate and desired salary?

Desired salary is annual and normally assumes benefits, paid time off, and employer payroll taxes on top. A desired hourly rate for contract work usually assumes none of them, which is why the two numbers should never be simple multiples of each other. Our desired salary guide covers the annual version of the question.

Is a desired hourly rate negotiable after you have given it?

Yes, and more easily than an annual salary, because scope changes give you a natural reason to revisit it. A rate quoted for 20 hours a week of defined work is not a promise about a different engagement. Say what your figure assumed when you give it, and changing it later is a clarification rather than a reversal.

What if the rate they offer is below my number?

Ask what the budget is and what it covers before you decide, then look at what else can move: a shorter payment term, a minimum guaranteed number of hours, or a narrower scope at your rate rather than a wider one at theirs. Contract work has more adjustable parts than salary does. The same logic applies when a full offer comes in low, which we work through in how to counter offer salary on a job offer.

The number to walk in with

The reason the 2,080 division survives is that it is easy and it sounds like arithmetic. It just happens to answer a different question than the one being asked. Run the real conversion once, write down the three figures it gives you, and you will never have to improvise a rate into a text box again.

Counteroffer builds that band for you: paste the role, the level, and the location, and it returns the floor, the figure to lead with, and the ceiling the market will support, in annual or hourly terms.