SHRM’s newest recruiting data puts the median cost to fill a nonexecutive role at just $1,300. Show that number to any engineering leader who just closed a senior backend hire and watch the reaction. The gap between the benchmark and the bill is where most hiring budgets quietly break.
That gap exists because most teams run the cost per hire formula correctly but feed it the wrong inputs. They count job board spend and agency invoices. They skip the 20-plus hours of interviewer time senior engineers spend per hire, the assessment platform seats, and the offers that never convert into a joining date. The math is fine. The ledger is incomplete.
For tech roles, an incomplete ledger is expensive. Engineering funnels are narrower than almost any other function, interview loops are longer, and a single senior hire can absorb a full quarter of recruiter capacity. A cost per hire formula that ignores those realities produces a number that looks healthy in a board deck and falls apart the moment finance asks why recruiting spend doubled.
This guide is written from the delivery side of tech hiring: the people who build shortlists, run interview loops, and reconcile recruiting spend against joined headcount every month. It covers the standard cost per hire formula, three worked examples in dollars and rupees, what 2026 data actually says about tech benchmarks, and the specific line items that inflate real numbers several times over.
SHRM’s 2026 Recruiting Executives Benchmarking summary shows that median time-to-fill for nonexecutive roles fell to 39 calendar days. 97% of nonexecutive positions were filled externally, up from 93% in 2025. Extra-large organizations also saw a 67% jump in median requisitions per recruiter. The same research notes that executive cost-per-hire rose substantially while nonexecutive costs stayed relatively stable. None of these figures is broken out for engineering, which is exactly why tech teams need their own math.
TL;DR
This guide explains how the cost per hire formula works, what belongs in it, and how engineering and HR leaders can use it to budget tech hiring for 2026. It is written for anyone who owns a hiring plan and has to defend it to finance.
The biggest takeaway is simple. SHRM’s 2026 median is $1,300 per nonexecutive hire, but our worked example of a 12-person engineering quarter lands near $14,900 per hire once interviewer time and agency fees are counted. Most teams never see that number because they never add it up.
By the end, you will know how to calculate cost per hire for your own team, spot the three costs most teams leave out, and decide whether in-house recruiting, an agency, or an outsourced model gives you the lowest true cost per joined engineer.
What Is Cost Per Hire?
Cost per hire is the total amount an organization spends to recruit and hire employees in a given period, divided by the number of hires made in that period. It combines internal costs, such as recruiter salaries and interviewer time, with external costs, such as agency fees, job ads, and background checks, into one comparable per-hire figure.
The standard cost per hire formula comes from the ANSI/SHRM Cost-Per-Hire Standard, which is why most benchmarks you see quoted trace back to SHRM.
Why the Number on Your Dashboard Is Usually Wrong
Engineering hiring has a funnel problem that most cost models ignore. Gem’s 2026 tech hiring data, built on 165 million applications and 1.2 million hires, shows the engineering application-to-hire rate is half the 0.5% average across all functions. Data science is narrower still, at roughly 1 in 1,000.
A narrow funnel means more screening hours per hire. Gem’s broader 2026 benchmark also finds technical roles now average 35-36 interviews and about 26 hours of interviewer time per hire. At a loaded engineering cost of $90 an hour, that is roughly $2,340 of interviewer time per hire. That is almost double SHRM’s entire median, before a single job ad enters the cost per hire formula.
Then there is recruiter capacity. The same dataset shows hires per recruiter have dropped sharply since 2021 even as application volume rose. Every hour your recruiters spend filtering inbound noise is a cost, and it belongs in the cost per hire formula.
In most engagements we’ve run, teams undercount their true cost per hire by a multiple, not a margin, when they apply the cost per hire formula to engineering roles. The cause is almost always the same: interviewer time and failed offers never reach the spreadsheet.
Cost Per Hire Formula: The Standard Calculation
The ANSI/SHRM version of the cost per hire formula is:
Cost per hire = (Total internal recruiting costs + Total external recruiting costs) / Total number of hires in the period
Three rules make the cost per hire formula usable rather than decorative:
- Use one consistent period. A quarter or a half-year smooths out lumpy agency invoices better than a single month.
- Count joins, not offers. An accepted offer that never shows up is a cost with no hire attached.
- Segment by role family. Blending a data engineer with an executive assistant produces an average that describes nobody.
What Is Included in Cost Per Hire?
This is where the cost per hire formula succeeds or fails. Split every recruiting expense into two buckets.
Internal costs (money spent inside the company):
- Recruiter and sourcer salaries, allocated by the share of time spent on the roles in scope
- Hiring manager and interviewer time, calculated as hours multiplied by loaded hourly cost
- Applicant tracking system, CRM, and assessment platform licences
- Employee referral bonuses
- Employer branding and careers-page content production
External costs (money paid to outside parties):
- Agency or staffing partner fees
- Job board postings and LinkedIn Recruiter seats
- Background verification and reference checks
- Coding assessment credits and take-home review fees
- Candidate travel, relocation, and signing bonuses
Onboarding and training belong in a separate ledger. Mixing them into the cost per hire formula makes your number impossible to benchmark against anyone else’s.
How to Calculate Cost Per Hire in 6 Steps
- Fix the period and scope. Pick one quarter and one role family, for example backend and platform engineering.
- Pull every external invoice tagged to those requisitions: agencies, job boards, assessments, background checks.
- Allocate internal salaries. If a recruiter spent 60% of the quarter on engineering roles, include 60% of their loaded cost.
- Log interviewer hours. Multiply total interview hours by a loaded hourly rate for each interviewer level.
- Count joined hires only. Exclude reneged offers and hires who left inside the probation window.
- Apply the cost per hire formula and track the result quarter over quarter, not against a national average.
Most teams skip step 4, yet it decides whether your cost per hire formula reflects reality. It is usually the largest internal line item for senior engineering roles.
Cost Per Hire Examples: Three Worked Scenarios
The inputs below are illustrative, built to mirror the cost structures we see across fintech, SaaS, and enterprise engineering teams. Swap in your own figures; the cost per hire formula logic stays identical.
Example 1: A US SaaS Company Hiring 12 Engineers in One Quarter
| Cost line | Amount |
| Job boards and LinkedIn Recruiter seats | $9,000 |
| Agency fees (2 senior hires at 20% of $160,000) | $64,000 |
| Assessment platform | $4,500 |
| Background checks (12 hires) | $1,200 |
| Total external | $78,700 |
| Recruiter salaries (2 recruiters, loaded, one quarter) | $60,000 |
| Interviewer time (26 hrs x 12 hires x $90/hr) | $28,080 |
| ATS share | $3,000 |
| Referral bonuses (3 x $3,000) | $9,000 |
| Total internal | $100,080 |
Plugged into the cost per hire formula, ($78,700 + $100,080) / 12 = $14,898 per hire. That is more than 11 times SHRM’s nonexecutive median, and it is a normal number for mid-level and senior engineering.
Example 2: An India GCC Hiring 40 Engineers in Six Months
A Bengaluru-based capability centre hires 40 engineers at an average CTC of ₹24 lakh.
External costs total ₹40.6 lakh:
- Vendor fees on 15 hires at 8.33% of CTC: ₹30 lakh
- Job portals: ₹6 lakh
- Assessments: ₹3 lakh
- Background verification: ₹1.6 lakh
Internal costs total ₹58 lakh:
- A four-person TA team for the period: ₹36 lakh
- Interviewer time at 20 hours per hire and ₹2,000 per hour: ₹16 lakh
- Referral bonuses: ₹4 lakh
- ATS licences: ₹2 lakh
The total of ₹98.6 lakh, divided by 40 under the cost per hire formula, gives ₹2,46,500 per hire. Salary is a separate budget line. Our breakdown of the cost to hire software developer in India covers the compensation bands that sit on top of this recruiting spend.
Example 3: The Same GCC, Adjusted for Drop-Offs
Now assume 4 of those 40 candidates either renege on the offer or leave within 90 days. The spend does not change. The denominator does.
On 36 retained joins, the cost per hire formula now returns ₹98.6 lakh / 36 = ₹2,73,889 per hire, an 11% increase from four lost candidates. Indian tech hiring often involves 60-90 day notice periods, which give candidates months to field counter-offers. That makes this joining-adjusted number the one finance should see.
Average Cost Per Hire in Tech: What 2026 Data Actually Shows
There is no single credible public figure for the average cost per hire in tech. SHRM’s medians cover all nonexecutive roles. What the 2026 data does support is a set of multipliers. They push engineering costs above the general benchmark when you run the cost per hire formula on engineering requisitions:
- Funnel width: engineering converts applicants at roughly half the all-function rate, and data science at a fifth of it.
- Interview load: technical loops average 35-36 interviews and about 26 interviewer hours per hire.
- Recruiter productivity: hires per recruiter have fallen even as applicant volume rose, so each hire carries more recruiter cost.
- Seniority mix: executive cost-per-hire jumped to a $15,000 median in 2026. Staff and principal engineer searches often behave more like executive searches than standard requisitions.
AI and infrastructure roles sit at the top of the range. Teams that need to hire machine learning engineers or LLM specialists compete in the narrowest funnels in the market. Their per-hire cost often lands well above a standard backend role at the same level. The same pattern holds when companies hire DevOps engineers with production Kubernetes depth. The qualified pool is small, and interview loops include hands-on infrastructure exercises.
Choosing a Hiring Model by True Cost Per Hire
The right comparison is not “agency fee versus zero.” It is the output of the same cost per hire formula, run under each model and divided by joined engineers.
| Model | Where the cost sits | Typical fee structure | Speed to shortlist | Best for |
| In-house TA team | Salaries, tools, interviewer time | Fixed overhead | 3-6 weeks for niche tech roles | Steady, predictable hiring volume |
| Contingency agency | Placement fee per hire | Typically 8.33-20% of CTC in India; 20-25% of salary in the US | 2-4 weeks | Occasional senior or hard-to-fill roles |
| Recruitment process outsourcing | Management fee plus per-hire fee | Varies by model and volume | 1-3 weeks once ramped | 20+ hires per quarter, GCC ramp-ups |
| Staffing partner with vetted pool | Monthly billing per engineer | Rate card, no placement fee | 7-10 working days | Fast team extension, contract-to-hire |
For teams hiring 20 or more engineers a quarter, recruitment process outsourcing usually beats per-placement agency fees because fixed costs are spread across volume. If you are weighing structures, our guide to RPO pricing models walks through where the crossover point sits.
For contract or extension roles, working with an IT staffing company in India changes the cost per hire formula entirely. There is no placement fee, so cost per hire shrinks to sourcing and onboarding effort, while the spend moves to a monthly rate card.
Case Studies: Where Cost Per Hire Actually Moves
A Series B fintech scaling its platform team. The company had been running every senior engineering role through contingency agencies, paying a full placement fee on each hire and waiting weeks for every shortlist. Moving to a dedicated sourcing model with a pre-vetted pool removed the per-placement fee and brought shortlists into a 7-10 working-day window. The biggest saving came from fewer interview loops per hire, because candidates arrived already screened on the client’s own technical rubric.
An enterprise GCC ramping from 15 to 60 engineers. The centre’s reported per-hire cost looked healthy until it started dividing by joined hires instead of accepted offers. Offer drop-off during long notice periods was quietly inflating real cost by double digits. The team tightened offer-to-join engagement with weekly touchpoints during the notice period and early team introductions. Joining rates came back in line, and finance got a number it could trust.
Both outcomes follow the same pattern: the cost per hire formula did not change, the inputs did. For more client outcomes across fintech and healthtech hiring, Supersourcing’s case studies document how these shifts play out at scale.
What Most Teams Get Wrong About Cost Per Hire
The most common mistake is treating cost per hire as a number to minimize. A cheap hire who leaves in six months is the most expensive hire on the books. You pay the recruiting cost twice and lose a quarter of delivery.
That is why the output of any cost per hire formula should be read next to quality of hire and retention. If you have never put a figure on attrition, start with our guide to employee turnover cost. Then learn how to measure quality of hire with signals you can track from day one.
Other recurring errors we see across engagements:
- Dividing by offers instead of joins, which hides drop-off cost entirely.
- Benchmarking engineers against SHRM’s all-role median, which guarantees a “we’re overspending” alarm that is not real.
- Leaving interviewer time off the ledger, usually the single largest internal cost for senior roles.
- Averaging across seniority, so one principal-engineer search distorts an entire quarter.
- Folding vacancy cost into recruiting spend. The revenue lost while a seat sits empty is real, but it is a separate metric. Track it alongside, not inside, your recruiting numbers.
Mature teams track a metric that ties these together: the RPO cost per quality hire. It weights spend against 6- and 12-month performance outcomes instead of just counting heads.
How to Reduce Cost Per Hire in Tech Without Hurting Quality
The levers that move the output of the cost per hire formula are mostly structural:
- Rediscover before you source. Gem’s data shows nearly half of sourced hires now come from candidates already in the ATS. Mining your own pipeline is the cheapest sourcing channel available.
- Shrink the interview loop. Calibrate a technical rubric once, then pre-screen against it so senior engineers interview only finalists.
- Expand the geography. Companies that build engineering teams in India or Eastern Europe often cut both salary and recruiting cost per hire, provided vetting standards hold.
- Buy capacity, not placements, at volume. Above roughly 20 hires per quarter, a volume-based model usually beats per-head agency fees.
If you plan to hire offshore developers, build your vetting rubric before you open the pipeline. Fixing quality after the fact always costs more than screening it upfront.
Pressure-Test Your Hiring Costs Before Your Next Ramp-Up
You may be planning a 2026 hiring push and want to know what each engineer will really cost before you commit to agencies, an RPO contract, or a new location. Supersourcing has run this calculation across 527+ IT projects with a 98% candidate joining rate. Bring your current numbers and we will show you where your cost per hire formula is leaking.
Email mayank@engineerbabu.com or book a consultation to get a joining-adjusted cost model for your next quarter.
Frequently Asked Questions
What is the cost per hire formula?
Add total internal recruiting costs to total external recruiting costs, then divide by the number of hires in the same period. That is the cost per hire formula in full. Internal costs include recruiter salaries and interviewer time; external costs include agency fees, job ads, and background checks. This is the ANSI/SHRM standard, and it lets you compare recruiting efficiency across quarters, teams, and hiring models.
What is a good cost per hire for software engineers?
There is no universal “good” figure because seniority, location, and funnel width vary so much. SHRM’s 2026 median is $1,300 for all nonexecutive roles, but fully loaded engineering hires commonly cost several times that. The better benchmark is your own trend line, quarter over quarter, segmented by role family and read alongside 90-day retention.
Is cost per hire the same as cost of a bad hire?
No, the cost of a bad hire is a much bigger figure. Cost per hire measures what you spend to fill a role. The cost of a bad hire adds lost productivity, team disruption, and the cost of replacing that person, which means paying the recruiting spend a second time. A low cost per hire paired with high early attrition is usually more expensive than a higher, stable number.
Should onboarding costs be included in cost per hire?
Under the ANSI/SHRM standard, no. Onboarding, training, and equipment belong in a separate ledger. Keeping them out makes your figure comparable to external benchmarks. Many finance teams track a second “cost to productivity” metric that adds onboarding. That metric is useful internally but should never be compared against published cost-per-hire benchmarks.
How can a company lower cost per hire for tech roles quickly?
The fastest wins come from three changes. Cut unnecessary interview rounds, and re-engage past candidates in your ATS. Once you hire more than 20 engineers a quarter, replace per-placement agency fees with a volume-based model. If you want an outside view of where your current spend leaks, a short hiring-cost audit with a delivery team that runs these loops weekly is a practical next step.
How often should cost per hire be recalculated?
Quarterly is the practical minimum for re-running the cost per hire formula. Monthly figures swing too much with lumpy agency invoices, while annual figures arrive too late to change hiring decisions. Recalculate whenever you change your hiring model, open a new location, or start a major ramp-up such as a GCC launch.
