Two job offers can look wildly different on paper and end up paying almost the same amount. One quotes $62,000 a year. The other quotes $31 an hour. Unless you convert both into the same unit, you're comparing a number you can't picture against a number you can't picture either, just in a different way.
This happens constantly: negotiating a raise, weighing a full-time offer against freelance work, or trying to figure out if that new hourly contract role is actually a pay cut. The fix is simple math, but it's math people skip because it feels like a formality. It isn't. Getting it wrong can mean walking into a negotiation undervaluing yourself by thousands of dollars a year.
It also shows up in smaller, quieter moments than a job offer. Deciding whether to pick up a few hours of overtime instead of a side project, figuring out if a part-time role is worth the drop in guaranteed income, or just wanting to know what a bonus actually works out to per hour worked. All of it comes back to the same handful of conversions, done consistently instead of estimated on the fly.
Why the Same Job Offer Can Look Totally Different in Salary or Hourly Terms
Employers often present offers in whichever unit sounds more attractive. A high hourly number sounds impressive until you realize it's for 30 guaranteed hours a week, not 40. A high salary sounds generous until you notice it assumes 50-hour weeks are normal for the role.
Neither number is dishonest on its own. The problem is that most people evaluate them in isolation instead of converting both to a common baseline, usually annual income or hourly rate, before deciding which is actually better. Once you do that conversion, the comparison usually stops being close.
The Basic Math: Converting Annual Salary to an Hourly Rate
The standard formula divides annual salary by the number of hours worked per year. For a typical 40-hour week with two weeks of unpaid time off, that's 2,000 hours a year. A $60,000 salary divided by 2,000 hours works out to $30 an hour.
Where people go wrong is assuming every job uses that same 2,000-hour baseline. A role with 37.5-hour weeks, or one with five weeks of paid vacation instead of two, changes the real hourly number noticeably even though the salary figure on the offer letter stayed identical. Adjusting hours per week and weeks per year, rather than defaulting to the generic formula, is the difference between an estimate and an accurate number.
Going the Other Direction: Turning an Hourly Rate Into an Annual Number
The reverse conversion multiplies hourly rate by hours per week, then by weeks per year. A $25-an-hour job at 40 hours a week, worked all 52 weeks, comes out to $52,000. But almost nobody works all 52 weeks without some unpaid time, a slow season, or a stretch of reduced hours, so the honest version of that math usually lands a bit lower.
This direction matters most for hourly workers trying to answer a very ordinary question: is this actually the equivalent of the salaried offer sitting next to it. Without doing the conversion, it's easy to undervalue an hourly role that's genuinely competitive, or overvalue one that only looks competitive because the number itself is large.
Photo by Khwanchai Phanthong on Pexels
A Worked Example: Two Offers That Look Closer Than They Are
Say you're weighing a salaried role at $58,000 a year against a contract position paying $32 an hour, capped at 35 hours a week with no guaranteed overtime. On the surface the hourly number sounds like a clear win once you multiply it out casually in your head.
Run the actual conversion and the picture changes. At 35 hours a week for 50 working weeks, the contract role comes out to about $56,000 a year, before accounting for the fact that contract work rarely includes paid time off or health coverage. The salaried role, once you divide it back down, works out to roughly $27.90 an hour across a standard 2,080-hour year. Neither number is obviously better on its own, which is exactly the point. The decision comes down to how much you value guaranteed hours and benefits versus a higher quoted rate, not which number looked bigger at first glance.
Comparing Two Job Offers Without Getting Fooled by the Bigger Number
When two offers use different pay structures, the temptation is to just pick whichever number looks bigger. That's how people accidentally take a pay cut while feeling like they got a raise.
The more reliable approach: convert both offers into the same unit, then layer in anything that changes take-home value, like different work weeks, different amounts of PTO, or a commute that eats into unpaid time. A $70,000 salary at a 45-hour-a-week culture and a $34-an-hour role at a strict 40-hour week aren't the apples-to-apples comparison they look like until you run both through the same conversion and account for the hours actually being asked of you. EvvyTools' tools directory has calculators built for exactly this kind of side-by-side comparison, so you're not rebuilding the formula from scratch every time a new offer shows up.
Where Overtime Changes the Calculation
Overtime complicates the picture because it isn't a flat multiplier applied evenly across every job. Under federal rules, many hourly employees are entitled to time-and-a-half pay for hours worked beyond 40 in a week, but eligibility depends on how the role is classified. The U.S. Department of Labor maintains the current rules on who qualifies and how overtime pay has to be calculated.
Salaried roles muddy this further because many are classified as exempt, meaning no overtime applies no matter how many extra hours get worked. That single classification detail can be the biggest factor separating two offers that otherwise look similar on paper, and it's worth confirming directly rather than assuming.
Photo by Abdullah Firat on Pexels
Is That Raise Actually Worth It? Doing the Real Math
A raise announcement usually comes as a percentage or a flat dollar amount, not as a change to your effective hourly rate. That framing can hide what's really happening. A 5% raise that comes bundled with a new expectation of longer hours or added responsibilities might barely move your hourly number at all.
Converting the new salary to an hourly rate, using your actual hours rather than the standard 40, shows whether a raise is keeping pace with what's being asked of you. It also gives you a concrete number to bring into the conversation if you decide the raise on the table isn't enough, rather than relying on a vague sense that something feels off.
Freelance and Contract Work: Why Your Hourly Rate Needs to Be Higher Than You Think
Freelancers frequently set their rates by taking a past salary and dividing it by 2,080 hours, the standard full-time year. That number is almost always too low, because it doesn't account for unpaid admin time, gaps between projects, self-employment tax, or the benefits an employer used to quietly cover.
A freelance rate needs to be built from a higher baseline to land in the same real-world place as a salaried equivalent. The IRS has guidance on self-employment tax obligations that's worth reading before setting a rate, since that tax alone can take a meaningful bite out of what looks like a straightforward hourly number.
Photo by Mo3ath photos on Pexels
Benefits, PTO, and the Costs That Don't Show Up in Either Number
Neither a salary figure nor an hourly rate captures the full picture on its own. Health insurance, retirement matching, and paid time off all have real dollar value, and losing them when moving from a salaried role to hourly or freelance work effectively lowers your real pay even if the rate itself looks higher.
The Society for Human Resource Management publishes research on benefits costs that gives a sense of how much employer-provided coverage is typically worth, which is useful context when you're trying to decide whether a higher hourly number actually offsets what you'd be giving up.
Photo by Erik Mclean on Pexels
Common Mistakes People Make When Comparing Pay
A few patterns show up constantly. People compare a gross salary figure to a take-home hourly estimate, mixing pre-tax and post-tax numbers without realizing it. They use a generic 40-hour, 52-week baseline for a job that doesn't actually follow that schedule. They forget that hourly roles frequently come with fewer guaranteed hours than the number on the offer implies.
Another common one: treating a signing bonus or a one-time relocation payment as if it were part of the ongoing hourly rate, which inflates the real number for exactly one pay period and then quietly disappears from every calculation after that. Spreading a one-time payment across a full year's worth of hours before comparing offers avoids that particular trap, and it's a five-minute fix once you know to look for it.
The Bureau of Labor Statistics tracks wage and hours data across industries, and comparing your own numbers against that kind of baseline can be a useful reality check when a rate feels unusually high or low for the type of work involved.
Putting It Together: A Simple Way to Compare Any Two Offers
Start by converting every offer into the same unit, using your actual hours per week and weeks per year rather than defaults. Add back anything that has real dollar value but doesn't show up in the base number, like benefits or guaranteed overtime. Then compare what's left.
Write the two final numbers down side by side before making a decision, rather than trying to hold both in your head while a recruiter or hiring manager is waiting on an answer. A number on paper is a lot harder to talk yourself out of than a rough feeling that one offer seemed better, and it's the same number you'll want on hand if you decide to negotiate either one further.
That process takes a few minutes with EvvyTools' free calculators rather than a spreadsheet built from scratch, and it turns a decision that's usually made on gut feeling into one made on an actual number. For a deeper look at related pay and budgeting math, EvvyTools' blog hub has more breakdowns worth reading before your next negotiation, and the Consumer Financial Protection Bureau also publishes plain-language guidance on evaluating pay and benefits that pairs well with the tool itself.
