Fully Loaded Cost of an Engineer (It's Not the Salary)
IT'S NOT THE SALARY
The fully loaded cost of an engineer is far more than salary - and every waste calculation depends on it. How to compute yours, and what to do with it.
TL;DR: The salary in the offer letter is the sticker price, not the cost. Once employer taxes, benefits, equipment, seats, and recruiting are counted, an engineer usually costs somewhere between 1.25× and 1.4× their base salary, before you add a laptop or a single SaaS invoice. If you run any waste math - review queues, incident hours, meeting load - on raw salary, every number you produce is flattering and wrong. Compute your loaded cost once, honestly, and reuse it everywhere.
What is the fully loaded cost of an engineer?
The fully loaded cost of an engineer is everything your organization pays to have that engineer working for a year: base salary, employer-side taxes and contributions, benefits, equipment, software and tooling seats, workspace (or remote stipend), and a fair share of recruiting and onboarding. It is the number finance actually budgets, and the number every engineering-waste calculation should use.
Most engineering leaders can quote salaries to the euro and have never once written down the loaded figure. That is a problem, because the gap between the two is not a rounding error. It is the difference between "reviews are a bit slow" and "our review queue is a six-figure line item."
What actually goes into the number
The components, roughly in order of size:
- Base salary. The known quantity. Also the smallest honest version of the truth.
- Employer taxes and contributions. Social security, pension contributions, unemployment insurance. The exact mix depends on your country, and in much of Europe it is substantial.
- Benefits. Health coverage, retirement matching, insurance, paid leave. The U.S. Bureau of Labor Statistics measures this continuously: in March 2025, benefits accounted for 29.7% of total employer compensation costs for private-industry workers; wages were only 70.3% of what employers actually paid (BLS Employer Costs for Employee Compensation, March 2025). That is the average across all private industry; knowledge workers with good packages often sit higher.
- Equipment and tooling. Laptop, monitors, cloud dev environments, the CI bill, the observability bill, every per-seat SaaS your team touches.
- Workspace. Office cost per head, or the remote stipend and co-working budget that replaced it.
- Recruiting and onboarding, amortized. Agency fees or sourcing time, plus the months where a new engineer is learning your codebase faster than they are shipping to it. Spread over expected tenure, this is real money per year.
How to calculate it (the honest version)
You have two options, and both are defensible if you disclose the method.
Option one: the multiplier. MIT senior lecturer Joe Hadzima's widely cited rule of thumb puts an employee's real cost at 1.25 to 1.4 times base salary once payroll taxes and benefits are included (How Much Does an Employee Cost?). That range explicitly excludes equipment, space, and recruiting. It is a floor, not a ceiling.
Option two: compute it from your books. Take one real (or representative) engineer. Sum the actual annual figures for each component above. Divide by 2,080 hours - the standard full-time convention - or by your own honest denominator if you subtract leave and holidays. Either is fine; hiding the choice is not.
A worked example, purely illustrative: an engineer on a $120,000 salary at a conservative 1.35× multiplier costs $162,000 a year. At 2,080 hours, that is about $78 per hour - roughly $625 per working day. Every hour of that engineer's time you spend on a stuck review, a flaky pipeline, or a meeting that should have been a comment now has a price tag. That is the entire point.
One honesty rule: the loaded cost is a chosen input, so treat it like one. State your multiplier, state your denominator, and use the same figure everywhere.
A waste calculation that quietly switches between salary and loaded cost depending on which number looks more dramatic deserves to be laughed out of the room. A CFO will do exactly that.
What to do with it once you have it
The loaded cost is an exchange rate. On its own it does nothing; multiplied against where time actually goes, it becomes the most persuasive number in engineering leadership:
- Price your queues. A pull request that waits idle is payroll paying for a queue. The math - and why it moves people when "reviews feel slow" doesn't - is in What Slow Code Review Costs You in Payroll.
- Ground your capitalization. Loaded cost per hour is also the basis finance uses when engineering time becomes a balance-sheet asset: see Capitalizing Software Development Costs in Agile.
- Judge the drains. Once every workflow has a price, you can rank what to fix by what it costs instead of by who complains loudest. That is what a money view of engineering is for: the same loaded-cost arithmetic, run continuously against your actual delivery data instead of a spreadsheet you update twice a year.
The door out: compute the number this week. It takes an afternoon with your finance lead, and it upgrades every argument you will make for the next year: from "this feels wasteful" to "this costs us a mid-level salary annually, and here is the receipt."
Frequently asked
What is the fully loaded cost of an engineer?
It is the total amount your organization pays for one engineer per year: base salary plus employer taxes, benefits, equipment, software seats, workspace, and the amortized cost of recruiting and onboarding. It is always meaningfully higher than the salary alone.
What multiplier should I use for fully loaded cost?
A widely used rule of thumb, published by MIT's Joe Hadzima, is 1.25 to 1.4 times base salary for payroll taxes and benefits. Your real multiplier depends on your country's employer contributions and your benefits package - compute it once from your own books rather than borrowing someone else's.
Why does fully loaded cost matter for engineering metrics?
Because it converts time into money. A pull request that waits three days, a flaky CI suite, a meeting-heavy sprint - none of these move anyone until they are priced. Loaded cost per hour is the exchange rate that turns process problems into budget conversations.
How do I convert fully loaded cost to an hourly rate?
Divide the annual loaded cost by the hours you consider worked - 2,080 is the standard full-time convention (52 weeks × 40 hours). If you subtract holidays and leave, say so explicitly. The denominator is a choice; the honest move is to state it.