From dashboard overload to a 7 slide mid year recruiting metrics review
Mid May is when every talent acquisition team scrambles to prepare a mid year recruiting metrics review. Those 40 slide decks bury the real hiring story under screenshots from Workday, Greenhouse, Lever or SmartRecruiters, while leaders quietly ask why open positions still sit unfilled and why quality candidates keep vanishing. If you want decisions instead of décor, you need a one page scorecard that ties recruiting metrics and performance metrics directly to business outcomes, with clear thresholds for what “good” looks like.
Start with five anchors on slide one: time to hire, time to fill, cost per hire, quality of hire and regret rate. As a rule of thumb, many tech employers target a median time to hire of 30–45 days for mid level roles and 55–70 days for senior engineers, with time to fill staying within 10–15 percent of those benchmarks. Time to hire and time to fill should be shown by critical tech roles and by sourcing channel, so leaders see where the hiring process actually slows and where the total number of hires hides painful gaps.
Cost per hire and cost to hire belong next to offer acceptance and acceptance rate, because finance cares less about abstract metrics and more about the real cost of each candidate who signs an offer for a hard to fill job. LinkedIn Hiring Lab and regional salary surveys from firms such as Robert Half or Hays often show that cost per hire for experienced software engineers typically ranges from 15 to 25 percent of annual salary once you include sourcing channels, assessment tools and internal time. Use those external benchmarks to flag where your own cost per hire and offer acceptance rate fall outside a reasonable band.
Quality of hire is now the primary headline, not a footnote under time metrics. Use performance indicators from probation reviews, early performance ratings and manager satisfaction to show whether last quarter’s hires are delivering the expected performance in their roles. Many teams set a target that at least 80 percent of new hires meet or exceed expectations at the six month mark, with first year regretted attrition below 10 percent. When you track quality of hire by source of hire and by source effectiveness, you finally connect recruiting activity to downstream performance and expose which sourcing channel generates quality candidates instead of just more candidates.
Pipeline health also belongs on that first slide, but keep it surgical. Show the total number of candidates in process for each priority job family, the fill rate against plan for those open positions and the candidate experience pulse score if you run regular surveys. A simple traffic light view by role cluster lets leaders see where talent acquisition can still hire on time this quarter and where the hiring process already risks missing the headcount plan. For most tech roles, a healthy pipeline means at least three to five qualified candidates at final interview stage for each critical open position.
To make this concrete, your one page sample slide should include: a compact scorecard table with the five core recruiting metrics and target thresholds; a small funnel graphic showing conversion rate by stage; a traffic light grid for pipeline health by role family; and a short narrative box summarizing one key win and one risk. In an appendix, add a definitions page with formulas for time to hire, time to fill, cost per hire, offer acceptance rate, quality of hire and regret rate, plus a downloadable template that combines the scorecard and the seven slide skeleton so teams can plug in their own data.
Slide two and three: what works, and where the funnel leaks
Once the scorecard lands, slide two of your mid year recruiting metrics review should tell a single, sharp story about what is working. Pick one or two talent acquisition metrics that genuinely improved, such as a lower time to hire for senior engineering roles or a higher offer acceptance rate for niche data roles, and explain the specific change in the hiring process that drove it. This is where you connect recruiting analytics to real decisions, not vanity graphs, and where leaders can see which sourcing channels and interview practices actually move performance metrics.
For example, you might show how shifting budget toward one sourcing channel, such as employee referrals or a targeted GitHub campaign, raised the conversion rate from first interview to offer for principal engineers. In one European SaaS company, a six month focus on referrals and structured interview training cut time to hire for senior backend engineers from 72 days to 49 days and lifted offer acceptance from 63 percent to 81 percent, bringing both metrics in line with benchmarks reported in recent LinkedIn Hiring Lab analyses for similar roles. You can then contrast that with another sourcing channel where the source effectiveness looks strong on paper because it generates a high total number of candidates, yet the source of hire for quality hires remains low.
A short narrative here beats ten bullets about generic recruiting activity and keeps the focus on quality candidates and quality of hire. Use this slide to highlight one or two hires that embody the new model. A senior data engineer hired through internal mobility or a boomerang hire can illustrate how a redesigned hiring process, with fewer interview steps and clearer performance metrics, improved both candidate experience and time to fill. For deeper context on how to benchmark these gains against the market, point your readers to a practical internal guide on benchmarking talent in tech hiring that explains how to compare your own recruiting metrics with external standards and set realistic target thresholds.
Slide three then turns to funnel leakage with equal precision and restraint. Break down conversion rate by stage and by source of hire: application to screen, screen to interview, interview to offer, offer to hire, all segmented by key roles. Many high performing tech recruiting teams aim for at least 60–70 percent conversion from screen to interview and 30–40 percent from interview to offer for well defined roles, with offer acceptance above 80 percent. When you track these data points by sourcing channel and by recruiter or hiring manager, you can see where candidates stall, where offer acceptance collapses and where the candidate experience quietly erodes.
Labor market context, headcount versus plan and the real misses
A credible mid year recruiting metrics review never interprets internal metrics in a vacuum. Slide four overlays your data with external labor market signals for the tech roles you hire, using sources such as LinkedIn Hiring Lab, local salary surveys and industry analyst reports on talent acquisition trends. When your time to fill for senior cloud engineers looks long, you need to show whether the wider market has seen similar increases in time to hire and cost to hire for those roles, and whether your own recruiting metrics sit above or below the ranges reported in those external benchmarks.
Use this external lens to reframe internal debates about performance metrics and recruiting metrics. If the total number of qualified candidates per job has halved in a specific region, a flat fill rate might actually signal strong source effectiveness and a resilient hiring process rather than under performance. Conversely, if the market has eased and your time to fill remains stubbornly high, the data points toward internal friction in interview scheduling, offer approvals or hiring manager responsiveness. External data from salary surveys and labor market reports also helps you explain why cost per hire and offer acceptance rate may shift even when your internal process stays stable.
Slide five then tackles headcount versus plan with the same analytical discipline. Show open positions, hires made and fill rate by business unit, but go one level deeper by diagnosing the miss: was it a shortage of quality candidates, a broken sourcing channel, a low offer acceptance rate or an unrealistic salary band. This is where a focused analysis of candidate experience, including survey data and feedback from declined offers, can reveal why candidates exit late in the process and whether your employer value proposition still resonates with the talent you want.
To make this diagnosis actionable, segment by role criticality and by source of hire. A missed target on junior hires from one sourcing channel might be acceptable if internal mobility or referrals are backfilling those roles with higher quality hires and better long term performance. For a structured way to read these patterns and reduce time to hire without sacrificing quality, many TA leaders rely on a six lever diagnostic such as the one outlined in an internal guide on reducing time to hire while protecting quality, which typically covers sourcing channels, assessment design, interview capacity, offer process, hiring manager engagement and candidate experience.
H2 bets, risks and the checklist for a defensible review
The final two slides of your mid year recruiting metrics review should look forward, not backward. Slide six defines two or three specific H2 bets in talent acquisition, each with a named owner, a clear metric target and a realistic time frame. Think of initiatives such as redesigning the hiring process for staff engineers to cut time to fill by 20 percent, or improving offer acceptance for data science roles by reworking compensation bands and clarifying performance expectations. Each initiative should reference the target thresholds you set on the opening scorecard so leaders can see how these bets will move time to hire, cost per hire and quality of hire.
Each bet must tie to a measurable shift in recruiting metrics and performance metrics. For example, a project to streamline interview loops in Greenhouse or Workday should aim to raise the conversion rate from onsite interview to offer by at least five to ten percentage points, while also improving candidate experience scores gathered through a structured survey. If you are piloting AI based analytics to better track source effectiveness and predict quality of hire, you should specify how you will validate those models against real performance data rather than vendor promises, and define what uplift in quality of hire or reduction in time to fill would count as success.
Slide seven then lays out risks and asks with the same clarity. Highlight systemic risks such as chronic delays in offer approvals, under investment in sourcing channels that actually produce quality candidates or gaps in your ability to track the total number of candidates by source of hire across systems. Pair each risk with a concrete ask from finance, IT or business leaders, whether that is budget for a new sourcing channel, integration work between your ATS and HRIS, or governance support for fair use of data in hiring decisions. Where possible, quantify the impact by linking each risk to missed headcount, lower fill rate or higher cost per hire.
To keep yourself honest, run your deck against a simple checklist before the review. Does every slide help leaders understand how you will hire the right candidates for the right roles, at the right time and cost, while protecting candidate experience and long term performance? If a slide does not change a decision about time to hire, cost to hire, offer acceptance, acceptance rate, quality of hire or fill rate for critical open positions, cut it and remember that the real test of your analytics is not the RFP score, but the twelfth month of adoption. A concise, defensible review built on a one page scorecard, a clear seven slide skeleton and a short appendix of definitions and formulas will always beat a dense dashboard tour.
FAQ
How many metrics should a mid year recruiting metrics review include
A focused mid year recruiting metrics review usually highlights five to seven core metrics on the main scorecard. These include time to hire, time to fill, cost per hire, quality of hire, offer acceptance rate and a simple pipeline health view. Additional talent acquisition metrics can sit in an appendix, but the primary slides should stay tightly aligned to business decisions, with explicit target thresholds so leaders can judge performance at a glance.
What is the best way to measure quality of hire in tech roles
Quality of hire in tech roles is best measured through a blend of early performance ratings, objective performance metrics such as code quality or incident rates, and manager satisfaction after three to six months. Many teams also track retention during the first year as part of their quality of hire index and set a target that at least 80 percent of new hires meet or exceed expectations. The key is to use the same definition across roles so you can compare sourcing channels and source of hire fairly.
How can I reduce time to fill without harming candidate experience
Reducing time to fill without damaging candidate experience requires removing internal friction rather than rushing candidates. Streamline interview steps, enforce faster feedback cycles from hiring managers and pre align compensation bands so offers can be issued quickly. At the same time, maintain clear communication with each candidate so the faster process still feels respectful and transparent, and use short post process surveys to track candidate experience as you change the hiring process.
Why should I segment recruiting metrics by sourcing channel
Segmenting recruiting metrics by sourcing channel lets you see which sources generate quality candidates and quality hires, not just more applicants. When you compare conversion rate, offer acceptance and performance metrics by source of hire, you can shift budget toward the channels that deliver long term performance. This approach improves both cost per hire and the overall effectiveness of your talent acquisition strategy, and makes your mid year recruiting metrics review far more actionable.
What slides should I remove from a mid year recruiting review deck
You should remove any slide that lists more than eight KPIs without a clear narrative, as well as retrospective slides that simply restate last quarter’s activity. Leaders rarely act on dense tables of data that lack a decision hook. Focus instead on a concise scorecard, a story about what works, a diagnosis of funnel leaks and a small set of H2 bets with explicit owners, supported by an appendix that holds metric definitions, formulas and a simple template for the seven slide structure.