The Difference Between Time to Hire and Time to Fill
Many HR teams spend a lot of time optimising a metric they haven't quite defined — and wondering why the numbers keep looking fine whilst the hiring keeps feeling broken. Time to hire and time to fill are two different measurements that track two different problems. Mixing them up means you're probably solving the wrong one. This article explains what each metric actually measures, why the difference matters, and how tracking both together gives you a clearer picture of where your hiring process is losing time, candidates, and money.

A business complains that hiring is taking too long.
You pull the data.
The numbers look reasonable — average time to fill is sitting around 35 days, which is broadly in line with industry benchmarks. You report back. Everyone nods. The problem is apparently not that bad.
And yet. The engineering team is still waiting on someone they needed six weeks ago. Three candidates dropped out mid-process last month. The offer that finally went out last Tuesday took nine days to get sign-off on.
Something is wrong. The metrics say otherwise. And the disconnect is quietly driving everyone mad.
This is often what happens when time to hire and time to fill get used interchangeably. They sound like the same thing. They measure different things. And if you're tracking one when you should be tracking the other — or tracking both but not understanding what each one means — you end up optimising for a number that isn't telling you what you think it is.
Let's sort this out.
What Is Time to Fill?
Time to fill measures the number of days between a job requisition being opened and an offer being accepted.
It starts the moment someone officially approves the need to hire — the job requirement is signed off, the headcount is confirmed, the vacancy is open. It ends when a candidate accepts an offer.
Everything in between counts. The time it takes to write and post the job. The time before the first applications come in. Every stage of the interview process. The time spent deliberating. The offer stage. All of it.
Time to fill is a business planning metric. It answers the question: from the moment we decided we needed someone, how long until we had someone?
That's useful for workforce planning, for setting expectations with hiring managers, and for calculating the true cost of a vacancy. If you need to hire a Head of Finance and you know your average time to fill for senior roles is 60 days, you can plan accordingly. Or at least stop promising the CFO that it'll be wrapped up by end of month.
What Is Time to Hire?
The calculation for time to hire measures the number of days between a specific candidate entering your recruitment pipeline and that candidate accepting an offer.
Same endpoint. Very different starting line.
Time to hire doesn't care when the job was posted or how long the vacancy sat open before the first decent application came in. It starts the clock on a specific person — typically from the moment they applied, or were sourced, or made first contact with your process. It ends when they say yes.
Time to hire is a candidate experience metric and a process efficiency metric. It answers a different question: once we had a good candidate in the pipeline, how quickly and smoothly did we move them through?
That's useful for diagnosing where your process loses people, how competitive you are on speed relative to other employers those candidates are talking to, and whether your assessment stages are proportionate or padded.
Why the Difference Actually Matters
If time to fill is slow, the problem might have nothing to do with your recruitment process.
- Maybe the headcount approval took three weeks because two senior leaders were on holiday.
- Maybe the job description sat in a queue waiting for sign-off before it could be posted.
- Maybe the role had budget uncertainty that delayed the official open date by a fortnight. None of that is a recruitment problem. It's an internal governance problem. And no amount of streamlining your interview process will fix it.
If time to hire is slow, the problem is almost certainly inside the process.
- Scheduling delays.
- Slow feedback loops between stages.
- Too many interview rounds.
- An offer that takes a week to generate and another week to get approved.
These are things you can actually fix.
The reason it matters to separate them is that they point at completely different root causes. Conflating them means you end up auditing your interview process when the real blockage is a two-week approval chain that nobody has ever questioned. Or the reverse — you renegotiate headcount approval timelines while your candidates are dropping out mid-process because nobody's following up between stages.
Fix the right thing. Use the right metric.
The Hidden Time That Neither Metric Captures
Both metrics have a blind spot. Neither of them tells you what's happening in the gaps.
Time to fill captures the full elapsed period but doesn't tell you which parts of that period involved meaningful activity and which parts were just... waiting. Time to hire captures process speed but only for the candidates you actually tracked properly — which, in most ATS systems, means the ones who made it far enough into the pipeline to have a proper record.
The gaps are where the real problems hide.
- The three days between an interview and the feedback being shared with the candidate.
- The week where the hiring manager was travelling and nothing moved.
- The fortnight between the verbal offer and the written contract.
- The candidates who withdrew before hitting any formal stage because nobody followed up after the screening call.
These gaps inflate both metrics without appearing in either one's narrative. And they're the most fixable part of the process, because they're usually not about assessment quality at all. They're about communication, scheduling, and internal accountability.
If you want to genuinely improve your hiring metrics, map the gaps. Not just the stages.
Time to Hire vs Time to Fill: How They Relate
Think of it like this.
Time to fill is the whole journey from "we need someone" to "we have someone." Time to hire is the sprint at the end — from "here's a candidate" to "they've accepted."
The difference between those two numbers is the time your process spent before a suitable candidate even appeared. That pre-pipeline period — job approval, job posting, waiting for applications, early-stage sifting — isn't captured by time to hire at all. It can represent days, weeks, or in some cases an embarrassingly large fraction of the total time to fill.
For most organisations, that pre-pipeline gap is one of the biggest drags on total time to fill. And it's almost entirely invisible if you're only tracking time to hire.
Meanwhile, time to hire on its own can look perfectly healthy even when candidates are having a genuinely poor experience — if you're only measuring the candidates who stayed in the process long enough to be tracked, you're missing the ones who dropped out or withdrew, who are arguably the most important signal of all.
Used together, the two metrics give you something neither can give you alone: a picture of where time is going across the whole hiring journey, not just the part that feels most like "recruiting."
What Good Looks Like for Each Metric
Benchmarks are tricky because they vary significantly by industry, seniority, and the labour market conditions at any given time. Anyone claiming a single universal benchmark for either metric is probably simplifying more than is useful.
That said, here's a rough orientation.
For time to fill, most professional roles across sectors average somewhere between 30 and 45 days. Technical and senior roles regularly run longer — 60 to 90 days isn't unusual for a Director-level hire or a specialist engineering role. If you're consistently above those ranges, it's worth investigating whether the delay is in the pre-pipeline phase or the process itself.
For time to hire, the picture is more compressed. Once a strong candidate is in your pipeline, most competitive processes move to offer acceptance within two to four weeks. Beyond that, you're testing the patience of candidates who have other options — and statistically, the ones with the most options are the ones most likely to quietly disappear.
For more information on time to hire benchmarks, click here to read the full report.
The more useful benchmark than any industry average, though, is your own historical data. Are your metrics improving? Are they consistent across teams and roles? Are there outliers that suggest specific problems rather than systemic ones? That's where the actionable insight lives.
Practical Ways to Track Time to Hire and Time to Fill
You don't need a sophisticated people analytics platform to track these properly. You need clear definitions and consistent data entry.
Start by agreeing what triggers the start of each metric in your organisation.
- When exactly does the clock start for time to fill — requisition approval, budget sign-off, or job posting?
- When does time to hire begin — application received, screening call completed, or first interview scheduled?
There's no universally correct answer, but there needs to be a consistent one, applied across every hire, or the numbers aren't comparable.
Then track the stages between. Most ATS systems will log timestamps at each stage if your team is entering data consistently, which is a big if, but worth enforcing. The goal isn't just an end-to-end number — it's being able to see where time accumulates so you can do something about it.
Review both metrics together, by team, by role type, and by hiring manager. Patterns at that level of granularity are far more useful than company averages. If one hiring manager's roles consistently show inflated time to hire, that's a different conversation than if one department's time to fill is long because headcount approval always stalls at the same sign-off level.
You may also want to check out our tips to reduce time to hire. Click here to read the full article.
How Squarelogik Looks at Both
When we work with a new client, one of the first things we try to understand is where their time is actually going.
Not just the headline numbers — those are useful context but rarely diagnostic on their own. We want to know whether delay is accumulating before the pipeline exists or inside it. Whether candidates are withdrawing at a particular stage. Whether offers are being extended at a speed that's competitive for the market and the role. Whether the gap between "verbal yes" and "signed contract" is adding unnecessary risk at the end of an otherwise efficient process.
Both metrics together, tracked at the stage level, give you an honest map of your hiring process — not just how long it takes, but where it's working and where it isn't.
If you're finding that your numbers look fine on paper but hiring still feels like it takes forever, that's usually a sign that the right metrics aren't being tracked, or that something significant is happening in the gaps between them.
That's a solvable problem. And it's usually a more interesting conversation than the headline numbers suggest.
Frequently Asked Questions
What is the difference between time to hire and time to fill?
Time to fill measures the days between opening a job requisition and a candidate accepting an offer — it covers the entire hiring journey including pre-recruitment delays. Time to hire measures the days between a specific candidate entering your pipeline and accepting an offer. Same endpoint, different starting point. Time to fill tells you about business planning efficiency. Time to hire tells you about process efficiency and candidate experience. You need both to understand where your hiring is losing time.
Which is more important: time to hire or time to fill?
Neither is more important — they answer different questions. Time to fill matters more for workforce planning and understanding the true cost of vacancies. Time to hire matters more for diagnosing process bottlenecks and candidate drop-off. If you're only tracking one, you're likely misidentifying where problems originate. An organisation with a slow time to fill but healthy time to hire probably has an internal approval or job-posting problem, not a recruitment process problem.
What is a good time to fill benchmark?
For most professional roles, 30–45 days is broadly typical, though this varies significantly by sector, seniority, and current labour market conditions. Technical and leadership roles regularly run 60–90 days. The more useful comparison is your own historical data — whether your numbers are improving, and whether there are meaningful differences between teams, roles, or hiring managers that suggest specific rather than systemic problems.
What is a good time to hire benchmark?
Once a strong candidate is in your pipeline, most competitive processes move to offer acceptance within two to four weeks. Beyond that, you risk losing candidates to employers who move faster. The most relevant benchmark is how quickly your competitors are moving for the same candidate profiles — which varies by market and role type. Consistent tracking of your own data over time is more useful than chasing an industry average.
Why do candidates drop out during the hiring process?
Usually one of three things: they received and accepted another offer, the process took longer than their patience allowed, or something in the experience made the employer less attractive than it seemed at the start. Time to hire is the most direct lever here — the longer candidates wait between stages, the more likely they are to accept something else. But communication matters too. A fast process with poor communication can lose candidates just as effectively as a slow one.
Can you track time to hire and time to fill in an ATS?
Yes, most modern applicant tracking systems log timestamps at each pipeline stage and can report on both metrics. The challenge is data quality — the system can only report accurately if your team is entering data consistently, using agreed definitions for when each metric starts and ends. Before pulling reports, it's worth auditing whether your ATS data is actually reliable, particularly for candidates who withdrew early or were sourced rather than applied directly.
A business complains that hiring is taking too long.
You pull the data.
The numbers look reasonable — average time to fill is sitting around 35 days, which is broadly in line with industry benchmarks. You report back. Everyone nods. The problem is apparently not that bad.
And yet. The engineering team is still waiting on someone they needed six weeks ago. Three candidates dropped out mid-process last month. The offer that finally went out last Tuesday took nine days to get sign-off on.
Something is wrong. The metrics say otherwise. And the disconnect is quietly driving everyone mad.
This is often what happens when time to hire and time to fill get used interchangeably. They sound like the same thing. They measure different things. And if you're tracking one when you should be tracking the other — or tracking both but not understanding what each one means — you end up optimising for a number that isn't telling you what you think it is.
Let's sort this out.
What Is Time to Fill?
Time to fill measures the number of days between a job requisition being opened and an offer being accepted.
It starts the moment someone officially approves the need to hire — the job requirement is signed off, the headcount is confirmed, the vacancy is open. It ends when a candidate accepts an offer.
Everything in between counts. The time it takes to write and post the job. The time before the first applications come in. Every stage of the interview process. The time spent deliberating. The offer stage. All of it.
Time to fill is a business planning metric. It answers the question: from the moment we decided we needed someone, how long until we had someone?
That's useful for workforce planning, for setting expectations with hiring managers, and for calculating the true cost of a vacancy. If you need to hire a Head of Finance and you know your average time to fill for senior roles is 60 days, you can plan accordingly. Or at least stop promising the CFO that it'll be wrapped up by end of month.
What Is Time to Hire?
The calculation for time to hire measures the number of days between a specific candidate entering your recruitment pipeline and that candidate accepting an offer.
Same endpoint. Very different starting line.
Time to hire doesn't care when the job was posted or how long the vacancy sat open before the first decent application came in. It starts the clock on a specific person — typically from the moment they applied, or were sourced, or made first contact with your process. It ends when they say yes.
Time to hire is a candidate experience metric and a process efficiency metric. It answers a different question: once we had a good candidate in the pipeline, how quickly and smoothly did we move them through?
That's useful for diagnosing where your process loses people, how competitive you are on speed relative to other employers those candidates are talking to, and whether your assessment stages are proportionate or padded.
Why the Difference Actually Matters
If time to fill is slow, the problem might have nothing to do with your recruitment process.
- Maybe the headcount approval took three weeks because two senior leaders were on holiday.
- Maybe the job description sat in a queue waiting for sign-off before it could be posted.
- Maybe the role had budget uncertainty that delayed the official open date by a fortnight. None of that is a recruitment problem. It's an internal governance problem. And no amount of streamlining your interview process will fix it.
If time to hire is slow, the problem is almost certainly inside the process.
- Scheduling delays.
- Slow feedback loops between stages.
- Too many interview rounds.
- An offer that takes a week to generate and another week to get approved.
These are things you can actually fix.
The reason it matters to separate them is that they point at completely different root causes. Conflating them means you end up auditing your interview process when the real blockage is a two-week approval chain that nobody has ever questioned. Or the reverse — you renegotiate headcount approval timelines while your candidates are dropping out mid-process because nobody's following up between stages.
Fix the right thing. Use the right metric.
The Hidden Time That Neither Metric Captures
Both metrics have a blind spot. Neither of them tells you what's happening in the gaps.
Time to fill captures the full elapsed period but doesn't tell you which parts of that period involved meaningful activity and which parts were just... waiting. Time to hire captures process speed but only for the candidates you actually tracked properly — which, in most ATS systems, means the ones who made it far enough into the pipeline to have a proper record.
The gaps are where the real problems hide.
- The three days between an interview and the feedback being shared with the candidate.
- The week where the hiring manager was travelling and nothing moved.
- The fortnight between the verbal offer and the written contract.
- The candidates who withdrew before hitting any formal stage because nobody followed up after the screening call.
These gaps inflate both metrics without appearing in either one's narrative. And they're the most fixable part of the process, because they're usually not about assessment quality at all. They're about communication, scheduling, and internal accountability.
If you want to genuinely improve your hiring metrics, map the gaps. Not just the stages.
Time to Hire vs Time to Fill: How They Relate
Think of it like this.
Time to fill is the whole journey from "we need someone" to "we have someone." Time to hire is the sprint at the end — from "here's a candidate" to "they've accepted."
The difference between those two numbers is the time your process spent before a suitable candidate even appeared. That pre-pipeline period — job approval, job posting, waiting for applications, early-stage sifting — isn't captured by time to hire at all. It can represent days, weeks, or in some cases an embarrassingly large fraction of the total time to fill.
For most organisations, that pre-pipeline gap is one of the biggest drags on total time to fill. And it's almost entirely invisible if you're only tracking time to hire.
Meanwhile, time to hire on its own can look perfectly healthy even when candidates are having a genuinely poor experience — if you're only measuring the candidates who stayed in the process long enough to be tracked, you're missing the ones who dropped out or withdrew, who are arguably the most important signal of all.
Used together, the two metrics give you something neither can give you alone: a picture of where time is going across the whole hiring journey, not just the part that feels most like "recruiting."
What Good Looks Like for Each Metric
Benchmarks are tricky because they vary significantly by industry, seniority, and the labour market conditions at any given time. Anyone claiming a single universal benchmark for either metric is probably simplifying more than is useful.
That said, here's a rough orientation.
For time to fill, most professional roles across sectors average somewhere between 30 and 45 days. Technical and senior roles regularly run longer — 60 to 90 days isn't unusual for a Director-level hire or a specialist engineering role. If you're consistently above those ranges, it's worth investigating whether the delay is in the pre-pipeline phase or the process itself.
For time to hire, the picture is more compressed. Once a strong candidate is in your pipeline, most competitive processes move to offer acceptance within two to four weeks. Beyond that, you're testing the patience of candidates who have other options — and statistically, the ones with the most options are the ones most likely to quietly disappear.
For more information on time to hire benchmarks, click here to read the full report.
The more useful benchmark than any industry average, though, is your own historical data. Are your metrics improving? Are they consistent across teams and roles? Are there outliers that suggest specific problems rather than systemic ones? That's where the actionable insight lives.
Practical Ways to Track Time to Hire and Time to Fill
You don't need a sophisticated people analytics platform to track these properly. You need clear definitions and consistent data entry.
Start by agreeing what triggers the start of each metric in your organisation.
- When exactly does the clock start for time to fill — requisition approval, budget sign-off, or job posting?
- When does time to hire begin — application received, screening call completed, or first interview scheduled?
There's no universally correct answer, but there needs to be a consistent one, applied across every hire, or the numbers aren't comparable.
Then track the stages between. Most ATS systems will log timestamps at each stage if your team is entering data consistently, which is a big if, but worth enforcing. The goal isn't just an end-to-end number — it's being able to see where time accumulates so you can do something about it.
Review both metrics together, by team, by role type, and by hiring manager. Patterns at that level of granularity are far more useful than company averages. If one hiring manager's roles consistently show inflated time to hire, that's a different conversation than if one department's time to fill is long because headcount approval always stalls at the same sign-off level.
You may also want to check out our tips to reduce time to hire. Click here to read the full article.
How Squarelogik Looks at Both
When we work with a new client, one of the first things we try to understand is where their time is actually going.
Not just the headline numbers — those are useful context but rarely diagnostic on their own. We want to know whether delay is accumulating before the pipeline exists or inside it. Whether candidates are withdrawing at a particular stage. Whether offers are being extended at a speed that's competitive for the market and the role. Whether the gap between "verbal yes" and "signed contract" is adding unnecessary risk at the end of an otherwise efficient process.
Both metrics together, tracked at the stage level, give you an honest map of your hiring process — not just how long it takes, but where it's working and where it isn't.
If you're finding that your numbers look fine on paper but hiring still feels like it takes forever, that's usually a sign that the right metrics aren't being tracked, or that something significant is happening in the gaps between them.
That's a solvable problem. And it's usually a more interesting conversation than the headline numbers suggest.
Frequently Asked Questions
What is the difference between time to hire and time to fill?
Time to fill measures the days between opening a job requisition and a candidate accepting an offer — it covers the entire hiring journey including pre-recruitment delays. Time to hire measures the days between a specific candidate entering your pipeline and accepting an offer. Same endpoint, different starting point. Time to fill tells you about business planning efficiency. Time to hire tells you about process efficiency and candidate experience. You need both to understand where your hiring is losing time.
Which is more important: time to hire or time to fill?
Neither is more important — they answer different questions. Time to fill matters more for workforce planning and understanding the true cost of vacancies. Time to hire matters more for diagnosing process bottlenecks and candidate drop-off. If you're only tracking one, you're likely misidentifying where problems originate. An organisation with a slow time to fill but healthy time to hire probably has an internal approval or job-posting problem, not a recruitment process problem.
What is a good time to fill benchmark?
For most professional roles, 30–45 days is broadly typical, though this varies significantly by sector, seniority, and current labour market conditions. Technical and leadership roles regularly run 60–90 days. The more useful comparison is your own historical data — whether your numbers are improving, and whether there are meaningful differences between teams, roles, or hiring managers that suggest specific rather than systemic problems.
What is a good time to hire benchmark?
Once a strong candidate is in your pipeline, most competitive processes move to offer acceptance within two to four weeks. Beyond that, you risk losing candidates to employers who move faster. The most relevant benchmark is how quickly your competitors are moving for the same candidate profiles — which varies by market and role type. Consistent tracking of your own data over time is more useful than chasing an industry average.
Why do candidates drop out during the hiring process?
Usually one of three things: they received and accepted another offer, the process took longer than their patience allowed, or something in the experience made the employer less attractive than it seemed at the start. Time to hire is the most direct lever here — the longer candidates wait between stages, the more likely they are to accept something else. But communication matters too. A fast process with poor communication can lose candidates just as effectively as a slow one.
Can you track time to hire and time to fill in an ATS?
Yes, most modern applicant tracking systems log timestamps at each pipeline stage and can report on both metrics. The challenge is data quality — the system can only report accurately if your team is entering data consistently, using agreed definitions for when each metric starts and ends. Before pulling reports, it's worth auditing whether your ATS data is actually reliable, particularly for candidates who withdrew early or were sourced rather than applied directly.
Related Articles
What Makes Candidates Choose One Employer Over Another
Salary gets candidates to the table. It rarely closes the deal. Here's what candidates are weighing when they have more than one offer.
Most employers think candidates choose on salary.
For many candidates — the employed, the experienced, the ones you most want to hire — salary is a threshold, not a differentiator. Once an offer clears the level the candidate needs, pay stops being the deciding factor and other things take over.
Those other things are where employers lose candidates they thought they had secured. Not to higher pay. To an employer who understood what the candidate was evaluating and gave them better answers.
The Process Sends a Signal Before the Offer Does
Candidates read the hiring process as a preview of the organisation.
A slow process with poor communication between stages tells a candidate how decisions are made. A disorganised first interview tells them something about management quality. An offer that takes twelve days to generate after a verbal acceptance tells them how much operational weight their joining carries internally.
None of this is fair. A slow HR approval chain is not a reliable indicator of a bad employer. But candidates are making probabilistic judgements with limited information, and the hiring process is the primary data source available to them. They use it.
The employer whose process is fast, communicative, and clearly managed wins candidates at the margin repeatedly. Not because the work is better or the salary is higher, but because the experience of being recruited there felt different from everywhere else.
The Manager Is Often the Decision
Ask candidates who have turned down an offer why, and the answer frequently involves the person they would have reported to.
An impressive company with an uninspiring hiring manager loses candidates to a less impressive company with a manager who clearly knew what they were doing, communicated well, and made the candidate feel that working for them would be challenging in the right way.
Candidates assess the manager throughout the process.
- How prepared they are for the interview.
- Whether their questions are generic or specific.
- How they talk about the team and the work.
- Whether they listen or perform.
By the final stage, a candidate has formed a view about whether this manager is someone whose feedback they would grow from or someone whose management style they would spend energy navigating around.
Employers who involve their best managers visibly in the hiring process win more offers than those who treat the manager as the final interview rather than the primary selling point.
Clarity About the Role and What Comes After It
Candidates accepting a new role are making a two-part decision.
- The job itself
- What the job leads to
An employer who can answer the second question clearly (what does progression look like, what does success in this role make possible, what have people who held this role previously gone on to do) gives the candidate something the vague offer cannot match.
The inability to answer this question is not always a deal-breaker. But when two offers are otherwise comparable, the employer who has articulated a convincing forward picture wins consistently. The candidate does not want to feel that they are accepting a ceiling. They want to feel that they are stepping onto a path.
Honesty Compounds Over Time
The employer who is honest about the hard parts of the role during the recruitment process earns a disproportionate level of trust.
This sounds counterintuitive. Naming the challenges, the current state of the team, the parts of the role that are difficult should discourage candidates. In practice, it does the opposite. Candidates who encounter an employer willing to say "this is where we are struggling and this is what the role will involve in addressing it" are talking to someone they can trust. Every other employer is selling them something.
Trust is the currency candidates are operating in when they make a final decision. The employer who has spent the process building it, rather than managing the candidate's perception of the company, starts the offer conversation from a stronger position.
Candidates who joined on the back of an honest pitch stay longer too. The first month does not produce a credibility gap between what was promised and what is real. That gap, when it exists, is where early attrition starts.
Speed at the Offer Stage
The candidate's enthusiasm for a role is not static. It peaks somewhere around the final interview and declines from there.
An offer that arrives less than four days after a final interview meets a candidate at close to peak enthusiasm. An offer that arrives eighteen days later, after a sign-off chain the candidate was not told about, meets a candidate who has mentally moved on, accepted another role, or simply lost the momentum that made the decision feel exciting.
Speed at the offer stage is not the same as rushing the assessment. It is the natural conclusion of a process that has been well-managed throughout — where the decision-maker was in the process, where the approval was pre-agreed, where generating the offer letter took hours rather than a week.
Employers who consistently lose candidates at the offer stage almost always have an internal process problem, not a candidate problem.
Flexibility and How It Is Communicated
Flexible and hybrid working arrangements have moved from differentiator to expectation in most professional roles.
The employer who offers genuine flexibility and says so clearly wins over the employer who offers the same flexibility but communicates it vaguely or buries it in policy documents. Candidates who cannot get a clear answer about working arrangements during the recruitment process assume the worst.
This is not about the arrangement itself. It is about whether the employer communicates clearly enough that the candidate can make a confident decision. Ambiguity at the offer stage, on a question as significant as where and when the candidate will be expected to work, creates doubt that sometimes tips the decision toward the employer who was clearer.
The Moment That Tips It
When a candidate has two comparable offers, the decision often comes down to a feeling that is difficult to articulate but easy to trace back to specifics.
- The employer who called after the final interview to check in before the offer arrived.
- The hiring manager who sent a personal note rather than letting the process speak for itself.
- The recruiter who was honest about the timeline rather than managing the candidate's expectations with vague reassurances.
These are not grand gestures. They are small signals that the organisation values the candidate as a person rather than a vacancy to fill. Candidates notice them. They do not always name them in the debrief. But they tip the scales at the margin more often than salary negotiations do.
At SquareLogik, we advise clients on candidate decisions, not just candidate pipelines.
The employers who retain the candidates they want share a set of characteristics: a clear and honest pitch, a well-managed process, and an offer that arrived when the candidate was still warm. None of those require a larger budget. All of them require deliberate attention.
Frequently Asked Questions
What do candidates prioritise when choosing between two job offers?
Salary clears the threshold but rarely decides between comparable offers. Candidates weigh the quality of the hiring process as a signal of the organisation, their assessment of the manager they would work for, clarity about progression, and the honesty of how the role was presented. The employer who communicated well, moved at a pace that respected the candidate's time, and gave them confidence in the decision wins at the margin more often than the employer who simply paid more.
How does the recruitment process affect a candidate's decision?
Significantly. Candidates treat the hiring process as a preview of the organisation — how decisions are made, how people are managed, how much operational weight the company places on incoming talent. A slow, poorly communicated process tells a story the employer may not intend to tell. A fast, respectful, well-managed one builds the kind of trust that makes an offer easier to accept and harder to decline.
Does salary determine which employer a candidate chooses?
For candidates under financial pressure, yes. For employed candidates with options, salary functions as a threshold — once it clears the level the candidate requires, it stops being the primary deciding factor. Candidates in this position are weighing career trajectory, manager quality, flexibility, culture signals from the process, and the honesty of how the role was presented. Employers who compete exclusively on pay against candidates who are not primarily motivated by it consistently lose to employers with better answers to the other questions.
What role does the hiring manager play in a candidate's decision?
A central one. Candidates assess the manager throughout the process and form a view about whether working for them would advance their career or complicate it. A strong, credible, well-prepared hiring manager is a selling point that no job ad communicates and no salary matches. Employers who involve their best managers visibly and early in the process win more offers than those who treat the manager as the final stage rather than a primary reason to join.
How important is speed in the offer process?
Candidate enthusiasm peaks around the final interview and declines from there. An offer that arrives promptly meets the candidate at close to maximum motivation. One that takes two weeks to materialise meets a candidate who has mentally recalibrated. Employers who lose candidates at the offer stage almost always have an internal process problem — a sign-off chain, an approval bottleneck, a contract generation delay — rather than a candidate problem. Fixing the internal process converts more offers than improving the compensation package.

How to Find Candidates When You Have No Employer Brand
No employer brand doesn't mean no candidates. It means a different approach. Here's how to find and hire excellent people before anyone has heard of you.
Most employer brand advice assumes you have six months and a content budget.
If you are reading this, you probably have neither.
You have an open role, a sparse LinkedIn page, and the faint hope that someone excellent will apply anyway.
They might. But waiting for inbound applications without brand recognition is a low-probability strategy. The candidates you want are almost certainly employed elsewhere, not browsing job boards for companies they have never heard of.
The good news: you do not need a famous brand to hire well. You need enough credibility for the specific candidate you are trying to reach.
Build Trust Without an Employer Brand
Brand recognition and trust are different things.
A large employer with a recognisable name has recognition working in its favour. But a small or unknown employer needs to build trust during the process itself through:
- The quality of the outreach
- The specificity of the role
- The honesty of what is on offer
- The credibility of the people involved
This is achievable without a marketing department. It requires deliberate attention to how the company presents itself at every touchpoint a candidate encounters.
- Start With Your Network
The most direct route to candidates when you have no brand is the founder's network, the leadership team's connections, and the existing employees' professional relationships.
A direct message from a founder to someone they respect — explaining what they are building and why this person would be excellent for it — converts at an excellent rate because:
- It arrives with implicit credibility
- The sender is known to the recipient
- The context is specific
- The ask is personalised
This works at small scale, which is the scale most no-brand companies are operating at. You are not trying to reach ten thousand people. You are trying to reach ten or fifteen credible individuals and have a real conversation with five of them.
Map your network before posting anywhere. The right candidate is more likely to be two connections away than browsing Indeed.
- Write a Highly Specific Job Ad
Without a known name on the listing, the job ad itself carries the full burden of communicating why this opportunity is worth a strong candidate’s attention.
Generic ads fail doubly for unknown companies. The candidate has no prior reason to trust the organisation and the ad gives them no new reason. A specific, honest, well-written ad compensates for the absence of reputation by giving the reader something concrete to assess.
- Name the problem the role is solving.
- Describe the first three months of work in practical terms.
- Be direct about what the company is, how far along it is, what the challenges are.
- Include the salary.
Yes, salary. An unknown employer that hides its compensation is asking candidates to take a leap of faith with almost no information, and many will not bother.
Specificity signals that a real person wrote this ad about a real job.
- Use Referrals Early and Aggressively
Employee referrals work better for unknown companies than for well-known ones, for a counterintuitive reason.
When a candidate receives a referral from someone they trust, that trust transfers to the opportunity. The referring person becomes the employer brand proxy. The candidate is not evaluating a company they have never heard of — they are responding to a recommendation from someone whose judgement they respect.
A single strong referral from a credible person in your network is worth more than a week of sponsored job postings. Ask specifically and ask early.
Not "do you know anyone looking?" but "we are hiring a senior data engineer with experience in X — who is the strongest person you have worked with in this space?"
- Build Micro-Credibility Fast
You cannot build a brand overnight. But you can build enough credibility for the candidate in front of you.
- A careers page with one good paragraph about the company, the team, and the role beats a blank page.
- A LinkedIn profile for the founder with a few posts about what they are working on beats a dormant one.
- A short video from the hiring manager explaining why this role exists and what success in it looks like beats a templated job description.
None of this requires a grand marketing strategy. It requires spending 2-3 hours creating something specific that a curious candidate can find when they search the company name after seeing your outreach.
Because they will search.
Every candidate who receives a direct approach and considers responding will look you up. Give them something to find that confirms the opportunity is real and the company is credible enough to invest their time in.
What Not to Do When Recruiting Without a Brand
Two approaches consistently backfire for no-brand employers.
- Overstating what the company is.
Candidates research. A job ad describing a "leading innovator" in a space where the company is eighteen months old and has twelve employees puts your credibility at risk. Honesty about stage, size, and challenge attracts candidates who want exactly that context — and there are excellent people who prefer an early-stage environment to a corporate one.
- Posting everywhere simultaneously.
Scattering the same job across every available platform without the brand to support it produces volume from the wrong pool and signals desperation to anyone paying attention. Two or three targeted, relevant channels performed well outperform ten mediocre ones.
How SquareLogik Finds Candidates for New Brands
We place candidates into companies that candidates have not heard of. The work is in our approach — how the opportunity is framed, who is approached, and what they are told about the role and the organisation.
For companies without established employer brand, the briefing process we run is different. We need to understand what makes the role genuinely compelling before we approach anyone, because we are carrying the credibility conversation the company cannot yet carry itself.
If you are hiring at a stage where your brand is not doing any of the work for you, we can help.
Frequently Asked Questions
Can you hire good candidates without an employer brand?
Yes, through a combination of network-led sourcing, specific and honest job advertising, and referrals that transfer trust from someone the candidate already knows. Brand recognition accelerates hiring by doing credibility work before any conversation starts. Without it, that credibility must be built during the process itself — through specificity, honesty, and the quality of the outreach.
What do candidates look for when researching an unknown company?
Evidence that the company is real, that the role is genuine, and that the people behind it are credible. A functional website, a LinkedIn presence with some activity, a founder or hiring manager who has a professional footprint, and consistent information across platforms. Candidates who receive direct outreach and are considering responding will search the company name before replying. Give them something substantive to find.
How do referrals help companies with no employer brand?
A referral transfers the trust the candidate has in the person making the recommendation to the opportunity being recommended. For an unknown company, this shortcut is particularly valuable — the candidate is responding to a trusted person's judgement rather than evaluating an unfamiliar organisation from scratch. Referrals from credible sources within your network are the fastest route to candidates who will take an unknown employer seriously.
How should an unknown employer write a job ad?
With more specificity than a known employer needs. Name the problem the role will solve, describe the first three months concretely, be direct about the company's stage and size, and include the salary. An unknown employer asking candidates to apply without this information is asking for trust it has not earned. A specific, honest ad does the credibility work that a recognisable brand would otherwise do automatically.
When should a no-brand company use a recruitment agency?
When the role requires reaching candidates who will not find the company through its own channels — passive candidates in specialist fields, senior hires who need a credible third-party introduction, or roles where the candidate pool is too small for job board advertising to produce results. A recruiter with relevant sector relationships can carry the credibility conversation on behalf of a company that cannot yet carry it itself.

Employee Onboarding Best Practices That Reduce Early Attrition
Early attrition is expensive and largely preventable. Here are the onboarding practices that keep new hires from becoming costly short-tenure regrets.
The average employee decides whether a job was the right move within the first two weeks.
Not officially. Not consciously. But the doubt that turns into a resignation in a few months often gets planted earlier — during a chaotic first week, an absent manager, or the creeping realisation that the role was described more attractively than it operates.
Early attrition is the most expensive form of turnover because it generates the full replacement cost with none of the productivity return. An employee who leaves at month three has cost the organisation recruitment fees, onboarding time, and lost team output, and delivered almost nothing in exchange.
Most of it is preventable. Here is how.
1. Set Expectations Immediately
Onboarding begins before the contract is signed, not on the morning of the first day.
New hires who arrive with a clear picture of the role, the team, and the first month's priorities outperform those dropped into ambiguity. It is good practice to send a pre-start communication covering:
- Who they will meet in the first week
- What their first project or focus area will be
- What the practical logistics look like.
- Any small details like parking, dress code, where to go, who to ask for
2. Structure the First 30 Days
The first thirty days are not an orientation period. They are a retention window.
A new hire left to navigate the organisation without structure — working out the informal rules, the real reporting relationships, the unwritten norms — is spending cognitive energy on problems that have nothing to do with the job they were hired for. That energy is finite. When the job eventually feels hard on top of everything else, the decision about whether to stay comes up.
Structured onboarding in the first thirty days covers three things:
- A scheduled introduction to every team or person the new hire will work closely with.
- A defined first project with clear scope and a clear owner to report progress to.
- A named point of contact for the questions too small to escalate but too persistent to ignore.
3. Plan Check-Ins Every 30, 60, and 90 Days
Schedule conversations with specific questions:
- Is the role what you expected?
- What is harder than anticipated?
- What do you need that you do not currently have?
- What would make the next thirty days more effective?
These conversations catch problems before they become resignations. A new hire who is struggling, asked directly whether the role matches expectations, will tell you.
4. Hold Managers Accountable
Onboarding documentation, induction programmes, and structured check-in schedules all fail the same way: the manager does not run them.
The manager is the onboarding. Not HR, not the buddy system, not the welcome pack.
The direct manager's behaviour in the first 90 days determines whether a new hire feels set up to succeed or left to muddle through. Their availability, the quality of feedback they provide, and whether they proactively clear blockers or expect the new hire to figure it out independently shapes the experience more than any formal programme.
Holding managers accountable for onboarding outcomes, including monitoring early attrition within their teams, converts onboarding from a process that exists on paper into one that functions in practice. When managers know that early departures are tracked and attributed, behaviour changes.
5. Surface the Unwritten Rules Early
Every organisation has rules that are not in the handbook.
- How decisions are really made.
- Who has informal influence.
- What escalation looks like in practice versus how it is supposed to work.
- Which meetings are for show and which ones matter.
New hires who discover these slowly — by making avoidable mistakes — find the process demoralising. Those told early arrive faster and feel less like outsiders.
This does not require a formal session. A candid conversation with the manager in the first week, covering how the team actually operates, does the job. A buddy who is not the manager helps too — someone the new hire can ask questions too small to escalate but important enough to require assistance.
6. Do Not Onboard in a Vacuum
New hires need context, not just content.
An induction that covers the company history, the product roadmap, the organisational values, and the benefits package tells a new hire a great deal of information and almost nothing about what the next six months of their working life will feel like.
Context means something different:
- Why the company exists and where it is trying to go, explained by someone who believes it rather than read from a slide
- Where the team sits in the organisation and why that matters to the work
- What the industry landscape looks like and how the company competes within it
- What the biggest challenges on the horizon are (and not the sanitised version)
New hires who understand the broader picture invest in it. Those given information without context do their job and nothing more.
7. Extend Onboarding for Senior Hires
A 90-day onboarding programme is appropriate for most roles. For senior and leadership hires, it is the minimum.
A new Director or VP walking into a complex organisation, with existing team dynamics, historical decisions to understand, and strategic priorities to shape, cannot be effectively integrated in three months. The risks of a senior hire feeling unsupported, overloaded, or isolated in the first quarter are higher than at any other level — and the cost of losing them is proportionally larger.
For senior hires specifically:
- Extend the formal onboarding structure to six months
- Include a stakeholder mapping exercise in the first month — who the new hire needs to build relationships with, in what order, and why
- Schedule structured conversations with the CEO or relevant executive not just in week one but monthly through the first quarter
- Create explicit space for the new hire to share observations about the organisation without those observations being treated as criticism — a senior hire's external perspective is an asset in the first months before it is socialised away
Boost Retention by Improving the Recruitment Process
In case early attrition persists despite strong onboarding points to a hiring problem, not an onboarding one.
A new hire who was given an inaccurate picture of the role during recruitment, or whose values and working style were not assessed alongside their technical capability, will struggle regardless of how well the first ninety days are managed. Onboarding cannot compensate for a placement that was wrong from the start.
When SquareLogik provides recruitment services, we set expectations at placement, not after. Before a candidate starts, we ensure they have a true picture of the role, the team, and the first month.
We also track placements at three, six, and twelve months. Patterns of early attrition in a specific role are almost always correctable at the brief and hiring stage, not the onboarding stage. The earlier that conversation happens, the cheaper the fix.
If you’d like to learn more about our recruitment process and how we manage high employee retention rates for our clients, connect with us today.
Frequently Asked Questions
What is the most effective onboarding practice for reducing early attrition?
Structured check-ins at thirty, sixty, and ninety days. A direct conversation asking whether the role matches expectations, what is proving difficult, and what the new hire needs, catches problems before they become departures. New hires who are asked these questions directly are significantly more likely to raise concerns rather than quietly disengage. The conversations cost an hour per check-in and prevent the full cost of replacement.
How long does onboarding take to complete?
Effective onboarding runs for ninety days minimum, not one week. The first week covers logistics and introductions. The first month builds the working relationships and context a new hire needs to be effective. Days thirty to ninety are where performance expectations sharpen and the psychological contract between employer and employee solidifies. Organisations that treat onboarding as complete after the induction week see disproportionately high early attrition in months two through four.
What causes early attrition in new employees?
The most consistent causes are a gap between how the role was described during recruitment and how it operates in practice, insufficient structure in the first thirty days, an absent or disengaged manager, and unmet expectations about pace, culture, or progression. Early attrition is rarely caused by capability. It is caused by misalignment — between what the new hire expected and what they found — that structured onboarding surfaces and addresses before it tips into departure.
How does pre-boarding reduce attrition?
Pre-boarding converts the gap between offer acceptance and start date from a period of growing uncertainty into one of increasing confidence. A new hire who receives clear information about their first week, their initial priorities, and the people they will meet arrives settled rather than apprehensive. That difference in psychological state compounds: a confident start produces faster integration, faster productivity, and lower early attrition.
Who is responsible for onboarding — HR or the line manager?
The line manager. HR designs the process and provides the structure. The manager executes it and owns the outcome. The most common failure in onboarding is a well-documented programme that the manager does not follow because there is no accountability for early attrition outcomes within their team. Linking manager performance metrics to ninety-day retention rates of new hires changes the incentive structure and, with it, the behaviour.