Hiring · August 7, 2026 · 10 min read
Government hiring: the 101-day problem, and the fix
Government hiring runs to a 101-day federal average that policy has ordered down to 80. A guide to compressing the pipeline through evidence, not less rigour.
← Part of The five pillars of hiring: what assessments measure
On this page
- Why does government hiring take 101 days?
- Where the recoverable days actually sit
- The demographic squeeze: low churn, a concentrated retirement wave
- How to hire faster in the public sector without cutting rigour
- How specialised assessments change the screening maths
- Honest limits: what an assessment does not fix
If you are the human-resources lead or hiring manager inside a government agency, you already live with the number this guide is built around, and it is an unusual number because your own employer published it. The US Office of Personnel Management put the government-wide average federal time to hire at 101 days in fiscal year 2024, and the 2025 Merit Hiring Plan then directed agencies to bring that figure to 80 days or less. Government hiring is the one field where the employer measured its own pipeline, printed the result, and ordered it down. That is the frame for everything here. The stakes are a slow process meeting a predictable retirement wave; the reason it is slow is a genuine commitment to fairness and auditability; and the question that matters is how you recover three weeks without weakening a single protective step. The answer is not less rigour. It is evidence earlier.
Why does government hiring take 101 days?
Because the process is engineered for defensibility, and defensibility has a time cost. A federal or state hire is not just a decision; it is a decision that must survive review. Job analysis to establish the criteria, structured rating against those criteria, veterans' preference and category rating, and suitability or security checks each exist for a reason, and each adds days. The 101-day average OPM recorded for fiscal year 2024 is the sum of a system doing exactly what it was designed to do.
It is worth naming those steps precisely, because the instinct when a process is slow is to blame the whole thing, and that instinct is wrong here. Some of the sequence is fixed by law and rightly so. Veterans' preference is a statutory entitlement. Suitability determinations and, for many posts, security clearances have their own timelines that no talent tool touches. Job analysis exists so that the criteria a candidate is judged against are documented before anyone is judged — which is precisely what makes the eventual decision auditable. Picture the hiring manager who writes the job analysis for an analyst post in October and does not shake the successful candidate's hand until February. None of that is waste. The waste, where there is any, sits in a different place entirely.
A useful split for any public-sector requisition: separate the statutory steps — veterans' preference, category rating, suitability and security checks — from the screening and shortlisting around them. The first set is fixed and protective; leave it alone. The recoverable days almost always sit in the second set, where applications wait for a human to read them.
Where the recoverable days actually sit
In the screening backlog before anyone is shortlisted. Certificates for popular public-sector roles can draw hundreds of applicants, and every one has to be read against the rating criteria before category rating or referral can happen. That reading is serial human work, it scales with the size of the pool, and it is the single largest block of time that a redesign can actually move without going near a statutory step.
Here is a deliberately simple worked example — the figures are made up to expose the shape, and no agency measured them. Say a single posting draws 250 applications against a documented set of rating factors. Give each application five minutes of honest review against those factors — that is a real minimum when the review has to be defensible — and you have more than twenty hours of reading for one requisition. An HR specialist carrying a dozen open postings does not have twenty uninterrupted hours, so the review happens in fragments over days, and the applications at the bottom of the certificate get the least attention exactly when the queue is longest. The days accumulate in that gap, between when a strong candidate applied and when a rating officer reached them. If you want to run the same arithmetic against your own posting volumes, the time-to-hire calculator will show the shape with your figures.
Averages also hide the worst cases. A government-wide figure of 101 days is a mean, and a mean is generous to the requisitions that stall — a stuck security check or a certificate that sat unreviewed for a fortnight disappears inside the headline. The way a few slow fills distort an otherwise respectable average is worth understanding before you trust any single number, and mean time to hire works through exactly how that arithmetic misleads. For the public sector the practical lesson is that the 80-day target will be won or lost on the requisitions that currently run to 150, not on the ones already near the average.
The demographic squeeze: low churn, a concentrated retirement wave
Public-sector staffing has an unusual profile: very little day-to-day churn, but a large, predictable wave of retirements arriving at once. Both halves matter, and together they explain why the slow pipeline is about to be tested harder than it has been in years. The everyday stability that makes government workforces steady is exactly what makes the coming turnover concentrated rather than gradual.
Start with churn, because it is the good news. Government quit rates run well below the private sector — directionally somewhere around half to two-thirds of the all-industry rate that Bureau of Labor Statistics JOLTS data tracks, which averaged 2.1% a month across 2024. People stay in public-sector roles longer, so agencies are not fighting the constant backfill treadmill that dominates hourly and high-volume settings. If your problem were ordinary attrition, you would be in an enviable position. It is not, and that is the second half.
The retirements are the pressure. Federal analyses put roughly 15% of the federal workforce as currently retirement-eligible, rising to about 40% eligible within five years, and OPM received 88,157 federal retirement claims in 2024 alone. That is not churn spread thinly across the year; it is a demographic block moving predictably towards the exit. The uncomfortable arithmetic is that a wave of concentrated, foreseeable vacancies is about to meet the slowest hiring pipeline of any sector — a low-quit workforce whose stability was masking how much replacement capacity the process would eventually need. For years that steadiness held the pressure off, and the years when it did so are now running out.
The public-sector staffing challenge is not high turnover — it is a concentrated, predictable retirement wave landing on the slowest pipeline in the economy. Low quit rates mean you cannot rely on a steady flow of practised backfilling to absorb it. The pipeline itself has to get faster before the wave crests, and the fast part to fix is screening.
How to hire faster in the public sector without cutting rigour
By moving the evidence earlier in the process, not by removing steps. The reason a slow public-sector pipeline resists most speed advice is that the usual shortcuts — drop a stage, trust a gut read, skip the paperwork — trade away the auditability the process exists to protect. Evidence-earlier does the opposite: it makes the screening stage more consistent and more documentable, which is faster and more defensible at the same time.
This is where skills-based hiring stops being a slogan and becomes a lever. Skills-based hiring — assessing candidates on demonstrated, job-relevant skills rather than degrees or self-reported experience — is already the direction of federal policy, formalised through moves away from automatic degree screens towards assessment tied to the work itself. It fits the public sector unusually well, because a structured, job-relevant assessment is by its nature standardised and recorded: every applicant meets the same defined criteria, and the result is documented. Compare that with serial CV review, where two rating officers can weigh the same certificate differently and the reasoning lives in someone's head. The structured interviews guide makes the general case that structure improves both consistency and defensibility; in a government setting that is not a nice-to-have, it is the whole point.
There is a fairness dimension that public-sector HR leads think about more than most, and it points the same way. A well-designed, job-relevant assessment scores everyone against the same criteria, which is more auditable than inconsistent human review, but it still has to be checked for adverse impact — the four-fifths rule and why any selection procedure needs monitoring is set out in the four-fifths rule explained, and the broader practices that keep evaluation fair sit in reducing bias in hiring. The point is not that assessment is automatically fairer; it is that structured, monitored assessment gives you the documentation to demonstrate fairness, which is precisely what an audit-ready process requires. Moving evidence earlier and keeping it structured serves speed and defensibility together, rather than trading one for the other.

How specialised assessments change the screening maths
Two capabilities move the screening bottleneck without touching a single statutory step. Per-job generation means an assessment shaped to the actual role — this agency's casework, this analyst post's reasoning demands — can be produced from the position description and reviewed by a person, rather than commissioned as a months-long project. And parallel evaluation means the whole certificate is assessed at once, so the reading queue stops growing with the number of applicants.
The first capability matters because bespoke public-sector assessments were historically expensive to build. A rating instrument tuned to one role meant weeks of subject-matter and validation work, which is why so many postings fall back on generic questionnaires and self-rated experience that measure something adjacent to the job. Generating a job-relevant assessment directly from the position description — human-reviewed before it goes out, and reusable when the role reopens, which in a retirement-driven backfill cycle it will — changes what is affordable at the requisition level. The second capability matters more for the 80-day target. Serial certificate review is the block of time the mean hides; a candidate evaluation that runs across every applicant in parallel turns a rating officer's week from reading application 200 of 250 into reviewing an evidence-ranked shortlist against the documented factors. The statutory steps take exactly as long as before. What shrinks is the unread-queue time in front of them. The same parallel-versus-serial logic, worked through in full for any large applicant pool, sits in the high-volume hiring guide. To see per-job generation run against one of your own roles, you can book a demo.
Honest limits: what an assessment does not fix
The statutory steps are the honest limit, and naming them is not a hedge — it is the reason to trust the rest. An assessment compresses screening and shortlisting. It does nothing to the parts of the public-sector pipeline that are fixed by design, and in government those fixed parts are substantial and, mostly, exactly as they should be.
- Security and suitability checks — these run on their own timelines, protect the integrity of the post, and are entirely outside anything a screening assessment does. A better shortlist reaches them sooner; the checks themselves take as long as they take.
- Veterans' preference and category rating — statutory and non-negotiable. Assessment feeds cleaner, better-documented evidence into these steps; it never overrides or bypasses them.
- Classification and approval — if standing up and approving a requisition takes weeks of internal process, the pipeline starts weeks late, and no downstream tool recovers time that was lost before the posting opened.
- Pay and grade competitiveness — where a public-sector salary trails the private market for a scarce skill, a faster, fairer process delivers a well-evidenced shortlist of candidates who may still take an offer elsewhere. Speed helps; it does not close a pay gap.
So be precise about the division of labour. The 80-day target will not be met by shortening a security check or waiving a preference, and it should not be. It will be met, if it is met, by removing the screening latency that currently sits between the fixed steps — the days a strong applicant spends waiting to be read. That is the one large block of time a public-sector HR team can usually move this year without a statutory change or a budget fight, and it is where the difference between 101 days and 80 will actually be found.
Divide the pipeline into what needs policy and what needs only your own sign-off. Classification reform and pay flexibility fall on the policy side, with the delay that implies. The screening stage between the statutory steps falls on your side, redesignable inside the HR function now. And because a structured, documented assessment is more auditable than serial CV review, the redesign is an easy case to put to the very people who guard defensibility hardest.
The government measured its own pipeline, published 101 days, and set itself 80. Reaching that figure is a matter of compressing the screening stage while every protective step stays exactly as long as it needs to be. Move the job-relevant evidence to the front, where it is consistent and documented, and the recovered days will carry the right candidate through to the statutory checks sooner. That is where the gap between 101 and 80 closes.
Written by
Aayesha Patel · Co-founder, Hanzomon Inc
Co-founder of Hanzomon. Writes about skills-based hiring, fair assessment and building a better candidate experience.