Offer Acceptance Rate & First-Year Attrition

offer acceptance rate & first year attrition understanding, measuring, and improving your two most impactful hiring metrics for recruiters | engineering managers | hr leaders introduction two numbers do more to reveal the health of a technical hiring program than almost any other metric your offer acceptance rate and your first year attrition rate together they tell you whether candidates want to join your team — and whether they decide to stay once they get there this guide is written for technical recruiters and engineering managers who are responsible for hiring software engineers, data scientists, and other technical professionals it covers what these metrics mean, what good and poor performance looks like, how to diagnose problems at your specific company, and — critically — how yogen's structured hiring workflows help you move both numbers in the right direction the stakes are real when these metrics slip, the costs compound quickly failed searches eat recruiter time, rejected offers restart timelines, and early attrition forces you to rehire roles you thought were filled the sections below quantify those costs and give you concrete tools to avoid them part 1 offer acceptance rate (oar) what is offer acceptance rate? offer acceptance rate (oar) is the percentage of formal job offers extended that are accepted by candidates it is calculated as oar (%) = (number of offers accepted ÷ number of offers extended) × 100 for example if your team extended 20 offers last quarter and 14 were accepted, your oar is 70% oar is typically tracked by role type, team, recruiter, and time period for technical roles specifically, it deserves its own tracking lane — the dynamics of a competitive engineering market are quite different from hiring for sales or operations what the numbers mean benchmarks for technical roles industry benchmarks for oar vary by company size, location, and the competitiveness of the role the ranges below reflect norms specifically for technical hiring at companies competing for engineering talent rating oar range what it signals 🟢 excellent 85% – 100% candidates are well prepared, aligned on expectations, and highly motivated your process builds confidence 🟡 good 70% – 84% healthy, competitive market rate some offer losses are normal due to competing offers process is solid 🟠 below average 55% – 69% meaningful signal of misalignment candidates may be surprised by comp, culture, or role scope at offer stage 🔴 poor below 55% critical issue significant rework, cost, and delay root cause analysis is urgent industry context according to shrm and linkedin talent data, average oar across industries typically falls between 65–75% for top tech employers, oars above 85% are achievable and increasingly expected as a signal of process quality startups often see lower rates (60–70%) due to comp constraints or lower brand recognition, but can recover with strong process what drives a low offer acceptance rate? a low oar is rarely about a single factor the most common root causes fall into four categories 1\ compensation misalignment the offer doesn't match the candidate's expectations or competing offers this is the most frequently cited reason candidates decline it is often preventable — candidates will almost always share salary expectations early if asked directly and without judgment 2\ role or scope surprise the candidate expected a different scope of work, level of autonomy, tech stack, or team structure than what was presented at offer this often stems from vague job descriptions or interviewers who over sell the role 3\ slow or fractured process the candidate received and accepted a competing offer while your process was still running technical interview loops frequently extend 3–6 weeks, giving candidates ample time to close other searches speed matters enormously in engineering hiring 4\ poor candidate experience candidates who feel uninformed, disrespected, or ghosted during your process rarely accept disorganized scheduling, inconsistent interviewer feedback, or a lack of communication after final rounds all create doubt how to evaluate oar at your company before you can improve oar, you need to understand where offers are being lost here is a practical evaluation framework segment by role and team a 65% oar across the company may mask a 90% rate in one org and a 40% rate in another teams with chronic low oar often have common patterns — a difficult hiring manager, unrealistic comp bands, or a weak intake process track the reason for every declined offer build a short decline survey and ask every candidate who turns down an offer (even informally) categories to track accepted competing offer, compensation, role misalignment, process concerns, location or remote policy measure time to offer calculate the average number of days from first contact to offer extended then correlate that number with your oar in most cases, longer time to offer corresponds directly to lower acceptance rates review your offer stage dropout rate separately some candidates drop out before an offer is formally extended (post final interview) this pre offer dropout should be measured separately — it often signals candidate experience problems earlier in the funnel benchmark by sourcing channel candidates sourced through referrals typically accept at higher rates than those sourced through job boards if referral oar is dramatically higher, that is a signal your employer brand or jd quality needs work for inbound sourcing the cost of a poor offer acceptance rate the financial and time impact of a low oar is often underestimated a rejected offer doesn't just mean a lost candidate — it means restarting a search that may have taken 4–8 weeks to reach offer stage scenario oar = 75% oar = 50% offers extended per open role (avg) 1 3 offers 2 0 offers time added per hire (at 5 wks/cycle) 1 5 weeks 5 weeks recruiter hours per declined offer 10–15 hrs 10–15 hrs per decline cost of each declined offer (blended) $2,500–$5,000 $2,500–$5,000 each annual cost (10 open tech roles) $7,500 in declined offer costs $25,000–$50,000 in declined offer costs true cost note these figures cover direct recruiter time and sourcing costs only they do not include the cost of the open role itself — every additional week a technical role sits unfilled typically costs the business $3,000–$8,000 in lost productivity for an engineer level position, and significantly more for senior or staff roles how yogen improves offer acceptance rate yogen is designed to address the root causes of low oar at a structural level, not just at the surface structured role intake that sets expectations early yogen's intake workflow prompts hiring managers to define the role clearly before sourcing begins tech stack, level expectations, team structure, growth path, and compensation range this information is surfaced to candidates early in the process — not held until offer stage — so candidates can self select accurately and arrive at offer stage with aligned expectations candidate facing role transparency yogen generates structured role summaries that recruiters can share with candidates during the first conversation when candidates understand the full scope of the role, the team they are joining, and what success looks like in the first 90 days, they are far less likely to be surprised at offer stage regular candidate check ins during the process yogen's pipeline management workflows include structured check in prompts at key stages — after the recruiter screen, after the technical interview, and post final round these check ins accomplish two things they keep candidates engaged, and they surface competing offers or wavering interest before you invest further catching a candidate who is cooling is far less costly than receiving a declined offer fast track workflows that reduce time to offer yogen's interview plan templates allow engineering teams to structure and schedule complete interview loops in significantly less time standardized question sets reduce interviewer prep time, and integrated scheduling reduces coordination lag compressing your loop from 5 weeks to 2–3 weeks is one of the highest leverage changes you can make to oar compensation expectation alignment yogen prompts recruiters to capture and document compensation expectations at the first conversation, and flags discrepancies between candidate expectations and internal bands before the offer stage this simple workflow eliminates the single most common reason candidates decline surprises at the offer stage part 2 first year attrition rate what is first year attrition? first year attrition is the percentage of new hires who leave the company — voluntarily or involuntarily — within their first 12 months of employment it is calculated as first year attrition (%) = (new hires who left within 12 months ÷ total new hires in period) × 100 for example if you hired 40 engineers in a given year and 8 of them left within 12 months of their start date, your first year attrition rate is 20% first year attrition is sometimes called "early attrition" or "new hire turnover " it is distinct from overall company attrition and deserves to be tracked separately, because it is almost entirely driven by the hiring and onboarding process — meaning it is far more controllable than broader retention why the first year is different the first year is when the gap between what was promised and what is real becomes visible to new hires research by bamboohr and others consistently shows that the majority of first year attrition decisions are made in the first 90 days — often within the first month the hiring process and the onboarding experience are the primary determinants of whether a new hire stays what the numbers mean benchmarks for technical hires first year attrition benchmarks for technical roles are generally higher than for other functions, reflecting the competitive market and the frequency of counter offers and recruiter outreach that new hires face rating first year attrition what it signals 🟢 excellent under 10% strong alignment between hire and role new hires are engaged, onboarded well, and feel they made the right choice 🟡 good 10% – 20% normal range for tech some departure is inevitable as expectations meet reality process is generally healthy 🟠 below average 20% – 30% systemic issues present could indicate role misrepresentation, poor onboarding, or team culture problems 🔴 poor above 30% serious problem requiring immediate intervention hiring is generating churn, not growth industry data from linkedin, gallup, and shrm consistently shows that approximately 20% of employee turnover happens within the first 45 days, and nearly half of all new hire attrition occurs within the first year for engineering roles, the numbers skew higher due to competitive market dynamics what drives first year attrition in technical roles? most first year attrition in technical roles traces back to one of five root causes the most striking thing about this list is how many of them originate in the hiring process itself — before the employee's first day 1\ role misrepresentation during hiring the most common driver the candidate accepted based on a description of the role that does not match their actual experience once hired this includes scope, tech stack, team structure, autonomy level, and what "day one" actually looks like interviewers over selling the role is a significant contributing factor 2\ poor onboarding new engineers who are left to figure out the codebase, team processes, and expectations on their own — without a structured ramp — are significantly more likely to disengage within 90 days a disorganized first week sends a strong signal about how the company operates 3\ manager relationship quality gallup research is unambiguous employees leave managers, not companies the quality of the relationship between a new hire and their direct manager is the single strongest predictor of first year retention engineering managers who have too little time for new hires, or who are unclear about expectations, generate early attrition 4\ compensation and competing offers a significant portion of first year attrition — particularly in the 3–9 month window — is driven by new hires receiving more competitive offers from other companies after joining this is especially common when the hiring process was slow and the candidate accepted an offer that was already below market by the time they started 5\ culture and team fit technical candidates who are evaluated primarily on coding ability without structured assessment of how they collaborate, communicate, and handle ambiguity are more likely to leave when the cultural reality of the team diverges from their expectations how to evaluate first year attrition at your company measuring first year attrition requires discipline to set up correctly here is a practical approach for engineering teams establish a 12 month cohort model track every person hired in a given quarter as a cohort, and check their status at 30, 60, 90, 180, and 365 days this gives you a leading indicator — if your 90 day attrition rate is climbing, your 12 month number will follow separate voluntary from involuntary a new hire let go for performance reasons tells a very different story than one who resigns track both, but analyze them separately high involuntary first year attrition typically indicates a hiring quality problem; high voluntary attrition typically indicates a role alignment or culture problem conduct structured exit conversations when a new hire leaves within 12 months, conduct a structured conversation within 48 hours of resignation the closer to the moment of departure, the more candid the feedback ask specifically about what they expected vs what they found, what changed their mind, and what the company could have done differently track by hiring manager first year attrition is often concentrated in particular teams if one manager consistently loses new hires within the first year, that is a coaching and accountability signal that hr and leadership need to address connect hiring data to retention data the most powerful analysis you can run is linking the hiring process (recruiter, sourcing channel, interview scores, time to hire) to first year retention outcomes companies that do this discover surprising patterns — for example, which interview questions most reliably predict long term retention the cost of poor first year attrition the cost of first year attrition is one of the most underestimated expenses in any company's budget when a new technical hire leaves within 12 months, you don't just lose the employee — you lose all of the investment made in hiring and ramping them cost component mid level engineer ($130k) senior engineer ($180k) recruiter time and sourcing $8,000 – $15,000 $12,000 – $22,000 interviewer time (10–15 hrs per loop) $2,000 – $5,000 $4,000 – $9,000 onboarding and training $5,000 – $10,000 $8,000 – $15,000 lost productivity (ramp period) $20,000 – $35,000 $35,000 – $60,000 role backfill (full re hire) $8,000 – $15,000 $12,000 – $22,000 estimated total cost per loss $43,000 – $80,000 $71,000 – $128,000 real world impact at scale a technical team that hires 20 engineers per year with a 25% first year attrition rate (5 departures) is spending $215,000–$400,000 per year replacing people it already hired reducing that rate to 10% (2 departures) saves $130,000–$240,000 annually — without adding a single new headcount that is a significant return on investment in hiring process quality how yogen reduces first year attrition yogen addresses first year attrition at its source the hiring process the platform is built on the principle that retention begins during the interview, not after the start date honest, detailed role expectations shared early yogen's structured intake process captures the real day to day of the role — including challenges, current team pain points, and what the first 90 days actually look like this information is shared with candidates during the process, not withheld until offer candidates who join with accurate expectations stay longer, because the job matches what they signed up for ai powered interview question generation for role fit yogen generates interview questions tailored to both the technical requirements of the role and the working style of the team this includes questions that assess how candidates approach ambiguity, collaboration, and independent work — dimensions that predict cultural fit and long term retention far better than algorithmic coding tests alone structured candidate check ins that surface misalignment early yogen's pipeline workflows prompt recruiters to check in with candidates at each stage of the process — not just to confirm logistics, but to ask directly whether the role still aligns with what they are looking for catching a misalignment at stage two of an interview process costs almost nothing discovering it six months after a start date costs $50,000–$100,000 and two months of backfill time interview plans that include expectation setting conversations yogen's interview plan templates include a dedicated stage for a candid role preview conversation, typically conducted by the hiring manager this is not a sell — it is a two way assessment of whether the candidate and the role are genuinely a fit teams that conduct this conversation consistently report lower first year attrition because candidates arrive with fully open eyes fair, consistent evaluation that builds confidence in the hire when interviewers use a consistent, structured rubric — as yogen's interview plans provide — hiring decisions are more defensible and more accurate this reduces the likelihood of a hiring error that results in involuntary attrition, and it builds candidate confidence in the fairness of the process, which positively affects their initial engagement after joining onboarding continuity yogen's interview plan and role documentation do not disappear at offer acceptance the structured role information, defined success criteria, and documented expectations created during the hiring process can be handed directly to the onboarding team, ensuring continuity between what was promised during interviews and what is delivered on day one part 3 combined impact on time and cost to hire the compounding effect of both metrics offer acceptance rate and first year attrition are deeply connected a company that struggles with both is caught in a particularly expensive loop hard to fill positions require multiple offer rounds, and when those hires eventually come in, a significant portion leave within the first year — forcing the cycle to restart the table below illustrates the compounding effect across a hypothetical technical team trying to fill 10 open engineering roles metric poor performance strong performance offer acceptance rate 50% 85% first year attrition 30% 10% offers needed to fill 10 roles 20 offers 12 offers offers to replace first year departures +6 offers +1 offer total offers extended (year) 26 offers 13 offers estimated total recruiting cost $130,000 – $260,000 $65,000 – $130,000 estimated time to stable team 12–18 months 4–6 months the difference in cost between the poor and strong performance scenarios — $65,000 to $130,000 in direct recruiting costs alone — does not include the productivity cost of roles sitting open, or the organizational disruption caused by constant onboarding and re onboarding cycles a practical roadmap to improvement for teams that are starting from a position of below average oar or elevated first year attrition, the following sequence represents the highest leverage improvements, roughly in priority order step 1 fix the intake process (week 1–2) before you improve anything else, ensure that every open role has a detailed, accurate intake document — one that captures real expectations, not a recycled job description yogen's intake workflow structures this process and takes less than 30 minutes for most roles this single step typically improves both oar and first year attrition by reducing misalignment step 2 establish comp alignment early (week 1) add a compensation expectations conversation to your first recruiter screen, and document it flag any candidates whose expectations diverge significantly from your bands before investing in a full interview loop this eliminates the most common cause of offer declines step 3 add structured check ins to your pipeline (week 2–3) implement check in touchpoints at each stage of your interview process these do not need to be long calls — even a brief message asking "how are you feeling about the role at this stage?" can surface misalignment and competing offers before they result in a declined offer or an early departure step 4 reduce time to offer (ongoing) audit your current interview loop how many stages? how many days between stages? where is time being lost? yogen's interview plan templates allow you to pre build loops that can be scheduled and executed in under three weeks every week you compress from your current timeline increases the probability of offer acceptance step 5 measure, report, and hold teams accountable (month 1 onward) oar and first year attrition should be reviewed in every recruiting team meeting and every quarterly business review for any organization that is actively hiring without measurement, the issues remain invisible yogen's reporting surfaces both metrics automatically, segmented by team and role summary what good looks like metric poor industry average with yogen offer acceptance rate < 55% 65–75% 80–90%+ first year attrition > 30% 20–25% < 12% avg time to fill 90+ days 45–60 days 25–35 days cost per hire (fully loaded) $20k–$35k $15k–$25k $10k–$18k the bottom line offer acceptance rate and first year attrition are not lagging indicators that you can only observe after things go wrong they are process metrics — and they improve when your hiring process improves yogen provides the structure, tooling, and workflows that give technical recruiting teams consistent leverage over both numbers, from intake to offer to day one and beyond © 2025 yogen all rights reserved | yogen io