How to Find the Right Candidate for a Job
At Squarelogik, we talk to hiring managers every week who are frustrated by the same problem: they've interviewed a dozen people and none of them felt right. Sometimes the pipeline is too thin. Sometimes it's flooded with the wrong applicants. Sometimes the shortlist looks great on paper and disappoints in person. This article covers how to find the right candidate for a job — from defining what "right" actually means, to where to look, how to assess properly, and why most hiring processes are set up to find acceptable rather than excellent.
Here's a conversation that happens constantly.
A hiring manager has been through eight interviews. Their recruiter has sent over fifteen CVs. Three people made it to the final stage. None of them felt quite right. The role is still open. Everyone is tired. And somewhere in the background, the business is getting increasingly pointed about when this position is going to be filled.
So what went wrong?
Nine times out of ten, the answer isn't that the right candidates don't exist. It's that nobody clearly defined what "right" meant before the process started. The hiring manager had one version in their head. The job ad described a slightly different version. The recruiter was screening for a third version based on the job description from eighteen months ago that nobody had updated.
Three different targets. Fifteen CVs. Zero good matches.
Finding the right candidate for a job is not primarily a sourcing problem. It's a clarity problem. You cannot reliably find something you haven't precisely defined. And most hiring processes — if we're being honest — are built around a brief that's vague enough to mean almost anything, which is why they produce shortlists that feel almost right but not quite.
This is fixable. Let's get into it.
Step One: Define What "Right" Actually Means (Properly, Not Just on Paper)
Before you post a single job ad or brief a single recruiter, you need to answer a question that sounds simple and usually isn't.
What does success look like for this person in twelve months?
Not "what skills do they need." Not "what experience are we looking for." What does a good hire actually achieve in this role, by when, and against what standard?
If you can answer that question specifically — not "they'll manage the team well" but "they'll have reduced average response time from 4 days to 48 hours and have rebuilt the relationship with the three accounts that are currently at risk" — then you have a hiring brief. If you can't, you have a job description, which is a different thing.
Job descriptions describe the role. Hiring briefs describe success. The distinction matters enormously because it changes what you're assessing for. Competencies that look identical on a CV can produce radically different outcomes depending on which definition of success you're working from.
The brief also needs to cover the things that rarely appear in job descriptions: the team dynamics, the challenges the previous person struggled with, the cultural realities of the environment the new hire is walking into. A candidate who'd thrive in a highly structured, process-driven team might be genuinely miserable — and underperforming within six months — in a fast-moving, ambiguous startup environment. Same skills. Completely different outcome.
Spend two hours on the brief before you spend two months on the process.
Step Two: Understand Exactly Who You're Looking For (Not Just What)
Most job ads describe a set of requirements. The best hiring processes describe a person.
There's a difference. Requirements are a checklist. A person is a combination of skills, motivations, working style, and career trajectory that produces a specific type of outcome in a specific type of environment.
Think about the best hire you've ever made in a similar role. What made them excellent? Was it purely their technical skills, or was it how they applied them? Was it their experience level, or their attitude toward problems? Was it something on their CV, or something that only became clear in the first month?
Now think about a hire that didn't work out. What was the gap? Was it about capability — they couldn't do the job — or was it about fit, motivation, or values? Bad hires are more often the latter than the former. People are rarely hired into roles they can't technically perform. They're hired into roles that don't match who they are.
Define both dimensions. What does this person need to be able to do, and what kind of person thrives in this environment? The second question is harder to answer and more important than the first.
Step Three: Look in the Right Places (Which Might Not Be Where You're Currently Looking)
Once you know who you're looking for, the question of where to find them becomes much easier to answer — because different candidate pools live in very different places.
Posting on a general job board and hoping the right candidate applies is a bit like opening your front door and hoping the person you're looking for happens to be walking past. It works occasionally. It's not a strategy.
Active vs passive candidates. The candidates who apply to your job ad are actively looking. That's a subset of the people who might be right for your role. Often not the most interesting subset. The best candidates for many roles are currently employed, performing well, not looking, and therefore not seeing your ad. Reaching them requires proactive sourcing — direct outreach, recruiter networks, professional communities — rather than waiting for inbound applications.
Where your candidates actually spend their time. A software engineer is probably findable on GitHub and specialist tech communities. A senior finance professional is more likely to respond to a warm introduction from a trusted contact than to a cold LinkedIn message. A specialist in a niche technical field might be best reached through a professional association, a conference, or a university department. The right sourcing channel depends on who you're trying to reach, not on which channels are easiest to use.
Your own network and previous pipelines. One of the most underused sources of strong candidates is the people who almost got the last job. Strong candidates who were a close second for a role three months ago. Previous employees who left on good terms. Referrals from high performers in your team who know the field well. These people are warm — they're already familiar with your organisation, and the qualification barrier has partly been cleared.
A good recruitment agency earns its fee primarily in this area — not by posting your job to the same boards you could post it to yourself, but by maintaining relationships with passive candidates who aren't findable through standard channels and who are credible because the agency already knows their work.
Step Four: Write a Job Ad That Attracts the Right Person, Not Just the Most People
Volume is not the goal. Relevance is.
A job ad that generates 200 applications, 180 of which are irrelevant, has not done its job well. It has created work. A job ad that generates 30 applications, 25 of which are worth reading, is worth considerably more — even though it looks worse on an applications dashboard.
The way to attract relevant candidates is to be specific and honest about what the role actually involves. Not aspirationally vague. Not a list of every possible desirable quality. Specific and honest.
What does a typical week look like? What are the hard parts of the job — the bits that aren't glamorous, the challenges the team is currently facing, the aspects that have tripped people up before? What does the culture actually feel like to work in, not what does the culture page on the website claim?
Counterintuitively, the things that might put some candidates off — "this is a high-pressure role with significant ambiguity," "the team is going through a period of change," "this requires someone who's comfortable working without much structure" — are precisely the things worth including. They filter out the candidates who'd struggle and attract the candidates who'd thrive.
The candidates you want are the ones who read a genuine description of the role and think yes, that's exactly what I'm looking for. You're not going to reach them with corporate language and a list of buzzword competencies.
Step Five: Screen for Signal, Not Just Suitability
Most CV screening is filtering for absence of red flags. That's not the same as finding the right person.
A CV tells you whether someone has broadly done similar things before. It doesn't tell you how well they did them, why they made the choices they made, how they handled the difficult parts, or whether the version of the role they performed previously matches the version you're hiring for now.
Screen for signal. What in this candidate's background actually suggests they'd be excellent at this specific role, rather than merely eligible for it? Is there evidence of the outcomes you care about, not just the activities? Does the career trajectory suggest someone who's genuinely motivated by this type of work, or someone who's applying broadly and your role happens to fit their search criteria?
Structured screening calls — fifteen to twenty minutes, consistent questions, scored against the same criteria for every candidate — are faster and more accurate than either CV review alone or unstructured "get to know you" conversations. They also make it much easier to compare candidates fairly, because you're comparing responses to the same questions rather than impressions from conversations that went in completely different directions.
What you're listening for in a screening call: specificity. Candidates who can speak precisely about what they achieved, how they did it, and what they'd do differently tell you something useful. Candidates who speak in generalities about "driving results" and "leading teams through change" are giving you the language of a CV, not the substance of an actual track record.
Step Six: Assess What the Role Actually Requires
The most common assessment failure in hiring isn't asking the wrong questions. It's assessing the wrong things entirely.
Most interview processes measure how well a candidate can talk about their experience. That's a useful signal, but it's not the same as measuring how well they'd do the job. And for many roles, the gap between the two is significant.
The question to ask about every assessment stage is: does this test what the role actually requires? If the role requires analytical thinking under pressure, does your interview process include anything that assesses analytical thinking under pressure — or does it ask candidates to describe a time they demonstrated analytical thinking, which is a different thing entirely?
Practical assessments, case studies, work samples, and structured simulations — done proportionately and with respect for candidates' time — consistently outperform interview-only processes on predictive accuracy. They're also fairer, because they give candidates who are less polished in interview settings an opportunity to demonstrate capability rather than just poise.
The caveat is that assessments need to be role-relevant and reasonable in scope. A three-hour unpaid case study for a £30,000 role is not a great look for your employer brand and will lose you good candidates who are fielding multiple offers. Keep assessments proportionate to the seniority and complexity of the role.
Step Seven: Move Decisively When You Find Them
Here's a mistake that happens more than it should.
A strong candidate goes through a well-designed process. Everyone thinks they're excellent. The hiring manager takes a fortnight to confirm. The offer takes another week to generate. By the time it arrives, the candidate has accepted something else.
The right candidate is rarely only talking to you. If they're strong enough for you to want, they're probably strong enough for two or three other employers to want as well. And those employers may be moving faster.
Decision-making speed at the end of a process is not the same as rushing the process. It's the natural conclusion of having done the front-end work properly. If you've defined success clearly, assessed rigorously, and reached genuine agreement that this is the right person — the offer should follow within 24 to 48 hours of that decision, not drift into the following fortnight while sign-offs are obtained.
Pre-approved salary bands and standard contract templates exist precisely for this purpose. Use them.
The Pattern Behind Failed Hires
Before we wrap up, it's worth naming the pattern that sits behind most of the "we hired the wrong person" conversations we have.
It's rarely that the candidate was dishonest or that the recruiter was careless. It's almost always that the brief was fuzzy, the assessment tested the wrong things, and the warning signs that did appear were rationalised away because the timeline pressure was significant and this candidate was, at least, not obviously wrong.
Finding the right candidate is not about finding someone who clears every bar. It's about being clear enough on what the bar is that you'd recognise the right person if they were standing in front of you — and confident enough in the process that you don't second-guess it when they are.
How Squarelogik Approaches Finding the Right Candidate
We're going to be honest: we've seen all of the failure modes above, including in our own processes.
A vague brief that generated a great-looking pipeline of mediocre matches. An assessment process that everyone felt good about right up until the six-month performance review. A strong candidate lost to a competitor offer because an internal approval took nine days to materialise.
What we try to do differently is treat the brief as the most important part of the process — not the admin that happens before recruitment starts, but the foundation everything else is built on. We spend real time on it. We push back when success criteria are vague. We ask the uncomfortable questions about what went wrong with previous hires before we start trying to find a better one.
We use AI to find candidates who aren't in the active market, and human judgement to decide whether those candidates are actually right for the specific environment they'd be walking into. Both parts matter.
And we follow up after placement, because the only reliable way to know whether we found the right candidate is to check.
If you're finding that your process is generating lots of candidates but not the right ones — or not enough candidates at all — we're worth talking to. The first conversation is just a conversation.
FAQs
How do you find the right candidate for a job?
Start with a precise definition of what success looks like in the role — not just skills and experience, but what a good hire would actually achieve in the first twelve months. Then source in the places where your ideal candidates actually spend their time, which often means proactive outreach to passive candidates rather than waiting for inbound applications. Assess against role-relevant criteria, not just interview performance. And when you find the right person, move quickly — the candidates worth hiring are rarely only talking to you.
What makes someone the right candidate for a role?
The right candidate has both the capability to do the job and the characteristics to thrive in the specific environment it exists in. Skills and experience matter, but fit — with the team dynamic, the working style the role demands, the culture of the organisation — is what separates a hire that works from a hire that looked good on paper. Most failed hires are not capability failures. They're fit failures that were visible in the assessment process and rationalised away under time pressure.
How do you attract the right candidates for a job?
Write job ads that are specific and honest about what the role actually involves — including the hard parts. Vague aspirational language attracts everyone and filters nobody. Specific, accurate descriptions attract candidates who are genuinely motivated by what the role requires and filter out those who wouldn't enjoy it. The volume of applications may fall. The relevance of those applications will rise, which is the metric that actually matters.
How important is the job brief when looking for candidates?
It's the most important part of the process, and the most commonly skipped. A vague brief means everyone involved in the process — recruiter, hiring manager, interviewer — is looking for something slightly different. That produces shortlists that feel close but not right, decisions that get delayed, and hires that disappoint. A precise brief that defines success criteria before sourcing begins compresses timelines, improves shortlist quality, and makes the final decision substantially easier.
Should you use a recruitment agency to find the right candidate?
For roles where the right candidate is likely to be passive — currently employed and not actively looking — a good recruitment agency adds significant value because it has relationships with those candidates and can make a credible approach. For roles where the right candidate is easily findable through standard channels, the value is more in process management than sourcing. The question worth asking any agency is not "can you find candidates" but "do you have relationships with the specific type of candidate we need, and how will you know if someone is right rather than just eligible?"
How do you assess whether a candidate is right for a job?
Structured interviews with consistent, scored questions are more predictive than unstructured conversations. Practical assessments that mirror actual job tasks — case studies, work samples, simulations — are more predictive than interview performance alone. Reference calls that go beyond "did they work here" to ask specific questions about how they worked and what they found challenging are consistently underused and consistently valuable. The goal is to test capability in the way the role actually requires it, not to test how well someone can describe their past experience.
What are the most common reasons the wrong candidate gets hired?
Usually a combination of: an unclear brief that meant nobody was assessing against the same standard; timeline pressure that led to a "good enough" decision rather than the right one; an assessment process that measured presentability rather than capability; and warning signs that were visible but rationalised away. The decisions that produce bad hires rarely feel like bad decisions at the time. Which is precisely why the brief, the assessment framework, and the decision criteria need to be established before the pressure to fill the role sets in.
Here's a conversation that happens constantly.
A hiring manager has been through eight interviews. Their recruiter has sent over fifteen CVs. Three people made it to the final stage. None of them felt quite right. The role is still open. Everyone is tired. And somewhere in the background, the business is getting increasingly pointed about when this position is going to be filled.
So what went wrong?
Nine times out of ten, the answer isn't that the right candidates don't exist. It's that nobody clearly defined what "right" meant before the process started. The hiring manager had one version in their head. The job ad described a slightly different version. The recruiter was screening for a third version based on the job description from eighteen months ago that nobody had updated.
Three different targets. Fifteen CVs. Zero good matches.
Finding the right candidate for a job is not primarily a sourcing problem. It's a clarity problem. You cannot reliably find something you haven't precisely defined. And most hiring processes — if we're being honest — are built around a brief that's vague enough to mean almost anything, which is why they produce shortlists that feel almost right but not quite.
This is fixable. Let's get into it.
Step One: Define What "Right" Actually Means (Properly, Not Just on Paper)
Before you post a single job ad or brief a single recruiter, you need to answer a question that sounds simple and usually isn't.
What does success look like for this person in twelve months?
Not "what skills do they need." Not "what experience are we looking for." What does a good hire actually achieve in this role, by when, and against what standard?
If you can answer that question specifically — not "they'll manage the team well" but "they'll have reduced average response time from 4 days to 48 hours and have rebuilt the relationship with the three accounts that are currently at risk" — then you have a hiring brief. If you can't, you have a job description, which is a different thing.
Job descriptions describe the role. Hiring briefs describe success. The distinction matters enormously because it changes what you're assessing for. Competencies that look identical on a CV can produce radically different outcomes depending on which definition of success you're working from.
The brief also needs to cover the things that rarely appear in job descriptions: the team dynamics, the challenges the previous person struggled with, the cultural realities of the environment the new hire is walking into. A candidate who'd thrive in a highly structured, process-driven team might be genuinely miserable — and underperforming within six months — in a fast-moving, ambiguous startup environment. Same skills. Completely different outcome.
Spend two hours on the brief before you spend two months on the process.
Step Two: Understand Exactly Who You're Looking For (Not Just What)
Most job ads describe a set of requirements. The best hiring processes describe a person.
There's a difference. Requirements are a checklist. A person is a combination of skills, motivations, working style, and career trajectory that produces a specific type of outcome in a specific type of environment.
Think about the best hire you've ever made in a similar role. What made them excellent? Was it purely their technical skills, or was it how they applied them? Was it their experience level, or their attitude toward problems? Was it something on their CV, or something that only became clear in the first month?
Now think about a hire that didn't work out. What was the gap? Was it about capability — they couldn't do the job — or was it about fit, motivation, or values? Bad hires are more often the latter than the former. People are rarely hired into roles they can't technically perform. They're hired into roles that don't match who they are.
Define both dimensions. What does this person need to be able to do, and what kind of person thrives in this environment? The second question is harder to answer and more important than the first.
Step Three: Look in the Right Places (Which Might Not Be Where You're Currently Looking)
Once you know who you're looking for, the question of where to find them becomes much easier to answer — because different candidate pools live in very different places.
Posting on a general job board and hoping the right candidate applies is a bit like opening your front door and hoping the person you're looking for happens to be walking past. It works occasionally. It's not a strategy.
Active vs passive candidates. The candidates who apply to your job ad are actively looking. That's a subset of the people who might be right for your role. Often not the most interesting subset. The best candidates for many roles are currently employed, performing well, not looking, and therefore not seeing your ad. Reaching them requires proactive sourcing — direct outreach, recruiter networks, professional communities — rather than waiting for inbound applications.
Where your candidates actually spend their time. A software engineer is probably findable on GitHub and specialist tech communities. A senior finance professional is more likely to respond to a warm introduction from a trusted contact than to a cold LinkedIn message. A specialist in a niche technical field might be best reached through a professional association, a conference, or a university department. The right sourcing channel depends on who you're trying to reach, not on which channels are easiest to use.
Your own network and previous pipelines. One of the most underused sources of strong candidates is the people who almost got the last job. Strong candidates who were a close second for a role three months ago. Previous employees who left on good terms. Referrals from high performers in your team who know the field well. These people are warm — they're already familiar with your organisation, and the qualification barrier has partly been cleared.
A good recruitment agency earns its fee primarily in this area — not by posting your job to the same boards you could post it to yourself, but by maintaining relationships with passive candidates who aren't findable through standard channels and who are credible because the agency already knows their work.
Step Four: Write a Job Ad That Attracts the Right Person, Not Just the Most People
Volume is not the goal. Relevance is.
A job ad that generates 200 applications, 180 of which are irrelevant, has not done its job well. It has created work. A job ad that generates 30 applications, 25 of which are worth reading, is worth considerably more — even though it looks worse on an applications dashboard.
The way to attract relevant candidates is to be specific and honest about what the role actually involves. Not aspirationally vague. Not a list of every possible desirable quality. Specific and honest.
What does a typical week look like? What are the hard parts of the job — the bits that aren't glamorous, the challenges the team is currently facing, the aspects that have tripped people up before? What does the culture actually feel like to work in, not what does the culture page on the website claim?
Counterintuitively, the things that might put some candidates off — "this is a high-pressure role with significant ambiguity," "the team is going through a period of change," "this requires someone who's comfortable working without much structure" — are precisely the things worth including. They filter out the candidates who'd struggle and attract the candidates who'd thrive.
The candidates you want are the ones who read a genuine description of the role and think yes, that's exactly what I'm looking for. You're not going to reach them with corporate language and a list of buzzword competencies.
Step Five: Screen for Signal, Not Just Suitability
Most CV screening is filtering for absence of red flags. That's not the same as finding the right person.
A CV tells you whether someone has broadly done similar things before. It doesn't tell you how well they did them, why they made the choices they made, how they handled the difficult parts, or whether the version of the role they performed previously matches the version you're hiring for now.
Screen for signal. What in this candidate's background actually suggests they'd be excellent at this specific role, rather than merely eligible for it? Is there evidence of the outcomes you care about, not just the activities? Does the career trajectory suggest someone who's genuinely motivated by this type of work, or someone who's applying broadly and your role happens to fit their search criteria?
Structured screening calls — fifteen to twenty minutes, consistent questions, scored against the same criteria for every candidate — are faster and more accurate than either CV review alone or unstructured "get to know you" conversations. They also make it much easier to compare candidates fairly, because you're comparing responses to the same questions rather than impressions from conversations that went in completely different directions.
What you're listening for in a screening call: specificity. Candidates who can speak precisely about what they achieved, how they did it, and what they'd do differently tell you something useful. Candidates who speak in generalities about "driving results" and "leading teams through change" are giving you the language of a CV, not the substance of an actual track record.
Step Six: Assess What the Role Actually Requires
The most common assessment failure in hiring isn't asking the wrong questions. It's assessing the wrong things entirely.
Most interview processes measure how well a candidate can talk about their experience. That's a useful signal, but it's not the same as measuring how well they'd do the job. And for many roles, the gap between the two is significant.
The question to ask about every assessment stage is: does this test what the role actually requires? If the role requires analytical thinking under pressure, does your interview process include anything that assesses analytical thinking under pressure — or does it ask candidates to describe a time they demonstrated analytical thinking, which is a different thing entirely?
Practical assessments, case studies, work samples, and structured simulations — done proportionately and with respect for candidates' time — consistently outperform interview-only processes on predictive accuracy. They're also fairer, because they give candidates who are less polished in interview settings an opportunity to demonstrate capability rather than just poise.
The caveat is that assessments need to be role-relevant and reasonable in scope. A three-hour unpaid case study for a £30,000 role is not a great look for your employer brand and will lose you good candidates who are fielding multiple offers. Keep assessments proportionate to the seniority and complexity of the role.
Step Seven: Move Decisively When You Find Them
Here's a mistake that happens more than it should.
A strong candidate goes through a well-designed process. Everyone thinks they're excellent. The hiring manager takes a fortnight to confirm. The offer takes another week to generate. By the time it arrives, the candidate has accepted something else.
The right candidate is rarely only talking to you. If they're strong enough for you to want, they're probably strong enough for two or three other employers to want as well. And those employers may be moving faster.
Decision-making speed at the end of a process is not the same as rushing the process. It's the natural conclusion of having done the front-end work properly. If you've defined success clearly, assessed rigorously, and reached genuine agreement that this is the right person — the offer should follow within 24 to 48 hours of that decision, not drift into the following fortnight while sign-offs are obtained.
Pre-approved salary bands and standard contract templates exist precisely for this purpose. Use them.
The Pattern Behind Failed Hires
Before we wrap up, it's worth naming the pattern that sits behind most of the "we hired the wrong person" conversations we have.
It's rarely that the candidate was dishonest or that the recruiter was careless. It's almost always that the brief was fuzzy, the assessment tested the wrong things, and the warning signs that did appear were rationalised away because the timeline pressure was significant and this candidate was, at least, not obviously wrong.
Finding the right candidate is not about finding someone who clears every bar. It's about being clear enough on what the bar is that you'd recognise the right person if they were standing in front of you — and confident enough in the process that you don't second-guess it when they are.
How Squarelogik Approaches Finding the Right Candidate
We're going to be honest: we've seen all of the failure modes above, including in our own processes.
A vague brief that generated a great-looking pipeline of mediocre matches. An assessment process that everyone felt good about right up until the six-month performance review. A strong candidate lost to a competitor offer because an internal approval took nine days to materialise.
What we try to do differently is treat the brief as the most important part of the process — not the admin that happens before recruitment starts, but the foundation everything else is built on. We spend real time on it. We push back when success criteria are vague. We ask the uncomfortable questions about what went wrong with previous hires before we start trying to find a better one.
We use AI to find candidates who aren't in the active market, and human judgement to decide whether those candidates are actually right for the specific environment they'd be walking into. Both parts matter.
And we follow up after placement, because the only reliable way to know whether we found the right candidate is to check.
If you're finding that your process is generating lots of candidates but not the right ones — or not enough candidates at all — we're worth talking to. The first conversation is just a conversation.
FAQs
How do you find the right candidate for a job?
Start with a precise definition of what success looks like in the role — not just skills and experience, but what a good hire would actually achieve in the first twelve months. Then source in the places where your ideal candidates actually spend their time, which often means proactive outreach to passive candidates rather than waiting for inbound applications. Assess against role-relevant criteria, not just interview performance. And when you find the right person, move quickly — the candidates worth hiring are rarely only talking to you.
What makes someone the right candidate for a role?
The right candidate has both the capability to do the job and the characteristics to thrive in the specific environment it exists in. Skills and experience matter, but fit — with the team dynamic, the working style the role demands, the culture of the organisation — is what separates a hire that works from a hire that looked good on paper. Most failed hires are not capability failures. They're fit failures that were visible in the assessment process and rationalised away under time pressure.
How do you attract the right candidates for a job?
Write job ads that are specific and honest about what the role actually involves — including the hard parts. Vague aspirational language attracts everyone and filters nobody. Specific, accurate descriptions attract candidates who are genuinely motivated by what the role requires and filter out those who wouldn't enjoy it. The volume of applications may fall. The relevance of those applications will rise, which is the metric that actually matters.
How important is the job brief when looking for candidates?
It's the most important part of the process, and the most commonly skipped. A vague brief means everyone involved in the process — recruiter, hiring manager, interviewer — is looking for something slightly different. That produces shortlists that feel close but not right, decisions that get delayed, and hires that disappoint. A precise brief that defines success criteria before sourcing begins compresses timelines, improves shortlist quality, and makes the final decision substantially easier.
Should you use a recruitment agency to find the right candidate?
For roles where the right candidate is likely to be passive — currently employed and not actively looking — a good recruitment agency adds significant value because it has relationships with those candidates and can make a credible approach. For roles where the right candidate is easily findable through standard channels, the value is more in process management than sourcing. The question worth asking any agency is not "can you find candidates" but "do you have relationships with the specific type of candidate we need, and how will you know if someone is right rather than just eligible?"
How do you assess whether a candidate is right for a job?
Structured interviews with consistent, scored questions are more predictive than unstructured conversations. Practical assessments that mirror actual job tasks — case studies, work samples, simulations — are more predictive than interview performance alone. Reference calls that go beyond "did they work here" to ask specific questions about how they worked and what they found challenging are consistently underused and consistently valuable. The goal is to test capability in the way the role actually requires it, not to test how well someone can describe their past experience.
What are the most common reasons the wrong candidate gets hired?
Usually a combination of: an unclear brief that meant nobody was assessing against the same standard; timeline pressure that led to a "good enough" decision rather than the right one; an assessment process that measured presentability rather than capability; and warning signs that were visible but rationalised away. The decisions that produce bad hires rarely feel like bad decisions at the time. Which is precisely why the brief, the assessment framework, and the decision criteria need to be established before the pressure to fill the role sets in.
Related Articles
Top Recruiting Tools to Find Strong Candidates
100s of recruiting tools claim to find you better candidates. Most of them overlap. Here's what works, for which roles, and when the tool is never the whole answer.
Here is a thing that happens in HR teams everywhere.
Hiring is slow. The pipeline is thin. The quality of candidates isn't where it needs to be.
Someone senior suggests that maybe the problem is the tools.
- A procurement process begins.
- Several platforms are demoed.
- A decision is made.
- A significant amount of money changes hands.
And six months later, hiring is still slow, the pipeline is still thin, and the quality of candidates is largely the same — except now there's a dashboard showing it in slightly better resolution.
Recruiting tools are useful. But no tool fixes a vague brief, compensates for a weak employer brand, or replaces the human judgement that makes the difference between a candidate who looks right and a candidate who actually is.
Here is a guide to the recruiting tools worth knowing about, what each of them actually does well, where they fall short, and how to think about building a sourcing stack that finds better candidates rather than just processing the same ones faster.
How to Find Candidates on LinkedIn
LinkedIn is the default answer to most sourcing questions. It is also the most widely misused recruiting tool in existence.
The platform has over a billion members. LinkedIn Recruiter — the premium sourcing tool — gives access to advanced search filters, InMail credits to contact candidates who aren't in your network, and pipeline management tools that let you track candidates across searches. For professional and specialist roles, it's the closest thing to a universal talent database that currently exists.
Most recruiters using LinkedIn Recruiter are sending variations of the same message to variations of the same search result. "I came across your profile and thought you'd be a great fit for an exciting opportunity." Every experienced candidate — which is to say, every candidate worth reaching — has received this message approximately forty times.
What actually works on LinkedIn is specificity. A message that demonstrates you read their profile, references something specific about their experience or work, and explains clearly and briefly why this particular role is relevant to them right now. This takes longer per message. It produces dramatically better response rates — and the candidates who do respond have been pre-qualified by the fact that the role actually matches their background.
The other underused capability is LinkedIn's Boolean search functionality. Most recruiters use the basic filters. Boolean operators — AND, OR, NOT, combined with quoted phrases and field-specific searches — let you build searches precise enough to surface candidates who'd never appear in a standard keyword search. The difference between a good Boolean search and a mediocre one on a platform with a billion profiles is the difference between a shortlist and a haystack.
For all its virtues, LinkedIn has real limitations. It skews toward white-collar professional roles and is less effective for blue-collar, trades, and many technical operational roles. It's also expensive — LinkedIn Recruiter seats are a meaningful budget line — and the quality of self-reported profile data varies significantly. A candidate's LinkedIn profile is their best-foot-forward summary, not a verified record.
How to Find Candidates on Indeed (+ When to Use Alternatives)
Indeed is the world's most visited job site. For volume hiring and roles with broad candidate pools, it's often the fastest way to generate applications at scale.
The model is simple: post a role, candidates apply. Indeed's sponsored listings put your ad in front of more relevant candidates and can meaningfully improve application volume for roles where the talent pool is active. The platform's resume search function also allows employers to find and contact candidates who've uploaded their CVs — a passive sourcing capability that's often underused relative to job posting.
What Indeed does well: volume, speed, and breadth.
What Indeed does less well: specialist, senior, and niche roles. The platform's strength is its scale, which also creates its central limitation. You're fishing in a large pond, but the fish you want may not be swimming there. Technical specialists, senior leaders, and passive candidates are not, as a rule, refreshing Indeed on a Tuesday morning.
Indeed also has a well-documented quality problem at high volume. A role that generates 300 applications may contain 20 relevant ones and 280 people who applied in 90 seconds because the platform made it easy to do so. The cost of processing those 280 is real, even if it's invisible in the platform's pricing.
Alternatives to Indeed for finding candidates:
Totaljobs and Reed are the dominant UK-specific job boards for professional roles, with strong brand recognition among UK job seekers. Reed has a particularly large CV database that's worth exploring for active candidates. Both are generally more cost-effective than Indeed for UK-specific hiring and tend to produce better-matched applicants for mid-market roles.
Stack Overflow Jobs and GitHub are significantly more effective than generalist boards for technical roles. Developers and engineers spend time on these platforms as practitioners, not just job seekers. The audience is smaller but dramatically more relevant.
Handshake dominates the graduate and early-career space in the UK and US, with deep penetration into university campuses. For entry-level hiring and early talent programmes, it reaches students and recent graduates more effectively than any generalist board.
Wellfound (formerly AngelList Talent) is particularly strong for startup and scale-up hiring, reaching candidates who are specifically interested in early-stage environments and are unlikely to be applying via generalist platforms.
The best place to find job candidates is wherever your specific candidates spend their time — which varies by role, level, and sector.
Top ATS Platforms for Finding Candidates
ATS — Applicant Tracking Systems — are primarily thought of as candidate management tools. They receive applications, track candidates through stages, and store data. But the best modern ATS platforms do considerably more than that.
The traditional ATS sits at the end of the sourcing funnel. Candidates arrive from job boards or recruiter outreach, enter the system, and get tracked through the process. The ATS itself contributes nothing to finding them.
The modern CRM-enabled ATS works differently. It maintains warm candidate pools from previous searches, flags candidates who applied for similar roles in the past, tracks engagement signals, and surfaces relevant profiles when a new role opens — so that you're not starting from zero every time a vacancy appears.
The top ATS platforms for finding candidates — rather than just managing them:
Greenhouse is widely used in mid-market and enterprise technology companies. Its sourcing features include structured pipeline management, multi-channel integration, and strong analytics. Its main strength is structured, consistent process rather than breakthrough sourcing capability.
Lever combines ATS and CRM functionality more tightly than most, which means candidate relationships built during previous searches are actively surfaced for new roles. For organisations hiring at volume in competitive talent markets, this relationship-continuity feature is genuinely valuable.
Workday Recruiting dominates large enterprise, primarily because of its integration with the rest of the Workday HR suite. It is powerful and comprehensive. It is also notoriously complex to configure and use, and sourcing recruiters regularly describe it as better at compliance than at actually helping them find people.
Ashby has emerged as a strong option for high-growth technology companies, with better analytics than most competitors at its price point and a cleaner recruiter experience than enterprise-grade platforms.
Pinpoint is worth specific mention for UK-based teams. It's built for in-house HR and talent teams rather than agency recruiters, has strong UK job board integrations, and its reporting is more accessible than most enterprise alternatives.
Teamtailor is particularly strong on employer brand integration — candidate-facing career sites, application experience, and brand presentation are genuinely better than most ATS platforms. For organisations where employer brand is a strategic priority, this matters.
In our opinion, ATS is better at managing candidates who arrive than at finding candidates who aren't looking. If your sourcing strategy is weak, the most sophisticated ATS in the market will process your weak pipeline with admirable efficiency.
Resume Databases and Their Effectiveness
Resume databases — platforms where candidates upload CVs that employers can search and contact — represent an older model of passive sourcing that's neither as effective as it used to be nor as useless as some newer sourcing evangelists suggest.
The effectiveness of resume databases for finding candidates depends significantly on the role type and the database in question.
For roles where candidates actively submit CVs to public databases — many mid-level professional, administrative, and operational roles — platforms like Reed's CV database, CV-Library, and Totaljobs' candidate search still produce relevant results, particularly for UK-based hiring. The key variable is recency: a CV that was uploaded three years ago tells you about where a candidate was three years ago. Database platforms that surface recently active candidates — those who've updated their profile or applied to roles in the past few weeks — are dramatically more useful than raw profile counts suggest.
The core limitation is self-selection. The candidates in most resume databases are, by definition, those who chose to put themselves there. For senior, specialist, and passive candidates — the people who are currently performing well and not actively looking — that's precisely the group least likely to be in any database. You can search every resume database on the market and still not find your ideal candidate for a niche or leadership role, because they haven't uploaded anything anywhere.
That said, for roles where active candidates are genuinely suitable and the volume of good applications matters more than the scarcity of the talent pool, resume databases remain cost-effective and underused. Most employers who claim databases don't work have either searched them poorly or are looking for roles where the relevant candidates don't self-submit.
Sourcing Tools Beyond the Big Platforms
The sourcing technology market has grown considerably, and there are specialist tools worth knowing about beyond the main platforms.
SeekOut and Entelo are AI-powered talent intelligence platforms designed specifically for sourcing passive candidates. They aggregate data across multiple public sources — LinkedIn, GitHub, research publications, conference speaker lists, professional databases — and allow sophisticated filtering that surfaces candidates who'd never appear in a single-platform search. For specialist and technical roles where the talent pool is deep but scattered, these tools meaningfully extend reach beyond what LinkedIn alone provides.
HireEZ (formerly Hiretual) does similar work, with particular strength in technical and engineering sourcing. Its AI matching surfaces candidates based on skills inference rather than just keyword matching — which matters because many technical professionals don't describe their skills in the same language that job descriptions use.
Fetcher and Beamery are CRM-focused sourcing tools that emphasise building and nurturing candidate relationships over time rather than one-shot outreach. For organisations serious about talent pipelining — maintaining warm contact with candidates who might be right for future roles — CRM-first tools produce better long-term outcomes than transactional sourcing platforms.
Textkernel and Sovren are resume parsing and skills-extraction tools primarily used in conjunction with ATS platforms to improve the quality of structured data from unstructured CV content. Useful infrastructure rather than standalone sourcing tools.
One category worth naming separately: AI-powered interview scheduling tools like GoodTime and Calendly's recruiting integrations. These don't find candidates, but they eliminate one of the most consistent sources of process delay — the back-and-forth of scheduling that adds days to every stage. In a competitive talent market, days matter.
Recruiting Analytics: Tools for Sourcing Insight
Recruiting analytics is the category most often discussed in job descriptions and least often used effectively in practice.
The most effective recruiting analytics for sourcing candidates do three things. They tell you where your best hires are coming from. They tell you where your best candidates are dropping out. And they tell you which parts of your process are adding value versus adding time.
Source quality reporting is the foundational capability. Not source volume — where the most applications come from — but source quality: which channels produce candidates who proceed furthest in the process, receive offers, and perform well after joining. These are different lists. The channel producing the most applications is often not the channel producing the best hires. Without source quality data, you're optimising spend based on quantity rather than outcome.
Funnel conversion analytics show you where candidates are being lost. If 40% of candidates who complete a first interview don't proceed to a second, that's either a signal about candidate quality (first interviews are surfacing unsuitable people who should have been filtered earlier), interviewer calibration (different standards being applied inconsistently), or process speed (candidates are being lost to competing offers between stages). You can't know which without the data.
Time-in-stage tracking identifies where delay accumulates. Most ATS platforms can produce this if the data is entered consistently — but the value depends entirely on data quality. A report that shows average time in stage based on partially completed records is not a reliable diagnostic.
Offer acceptance analytics — tracking whether accepted offers were first, second, or third choice — is one of the most underused insights in recruiting. Consistently hiring your third-choice candidate is a signal that your preferred candidates are either going elsewhere during the process or finding the offer insufficiently compelling. Both are actionable problems. Neither is visible without tracking it.
Platforms like Visier, Tableau (configured for HR data), and the analytics modules within enterprise ATS platforms like Greenhouse and Lever can produce this reporting. The honest caveat: most organisations have the tools to run this analysis and lack either the data discipline to populate them reliably or the cross-functional alignment to act on what they find.
Building a Sourcing Stack That Actually Works
With all of this, the question becomes: what should you actually use?
The answer depends on your hiring volume, role types, seniority levels, and budget — but here's a framework for thinking about it.
For the majority of professional mid-level roles: A quality ATS with CRM capability, LinkedIn Recruiter for active outreach, one or two relevant job boards (not eight), and a structured employee referral programme will cover most of what you need. The value comes from using each well, not from adding more.
For high-volume, broad-pool roles: Indeed or relevant sector boards, an ATS with strong bulk communication capability, and resume database access for roles where active candidates are genuinely suitable. Analytics on source quality are worth the effort to configure properly.
For specialist, niche, and technical roles: LinkedIn Boolean search, specialist sourcing tools like SeekOut or HireEZ, and GitHub or Stack Overflow for engineering. Resume databases are unlikely to be your best source here. Referrals from people already doing the role are underrated.
For senior and leadership roles: The tools matter less than the network. A well-connected specialist recruiter with genuine relationships in the relevant market will outperform any combination of sourcing software for roles where the candidates are largely passive. Use tools to support that process, not to replace it.
Across all of the above: Consistent, reliable data entry into your ATS. Funnel analytics that tell you where quality is being produced and where it's being lost. Source quality tracking that tells you what's actually working, not just what's producing volume.
How SquareLogik Simiplifies Everything
Instead of managing an entire stack of recruiting tools, you could choose the SquareLogik approach.
We use technology throughout our process — AI for initial screening and candidate matching, sourcing tools to extend reach beyond active markets, CRM systems to maintain relationships with passive candidates across search cycles, and analytics to track what's actually working across our placements.
The tools extend our reach and reduce our administrative burden.
- They don't tell us whether a candidate will thrive in a specific team dynamic.
- They don't catch the warning signs in a reference conversation.
- They don't make the call to a passive candidate who's trusted us for two years and whose instinct is to listen when we suggest something is worth considering.
The honest position on recruiting tools is this: the right stack, used well, makes a good process faster and a good recruiter more effective. It doesn't fix a bad brief, rescue a weak process, or replace the human judgement that separates finding a candidate from finding the right one.
If you're reviewing your sourcing technology and want a second opinion on what's likely to actually move the needle for your specific hiring challenges, we're happy to have that conversation. No product recommendations that happen to benefit us — we don't sell software.
Frequently Asked Questions
What are the best recruiting tools to find candidates?
The most effective tools depend on what you're hiring for. LinkedIn Recruiter is the closest thing to a universal starting point for professional roles, but it needs to be used with specific, personalised outreach rather than mass messaging. For volume roles, Indeed and relevant sector boards generate applications quickly. For specialist and passive candidates, dedicated sourcing tools like SeekOut or HireEZ extend reach beyond standard platforms. A CRM-enabled ATS ties it together by maintaining warm pipelines from previous searches rather than starting from zero each time.
How do you find candidates on LinkedIn effectively?
Use Boolean search operators to build precise, targeted searches rather than relying on basic filters. Write personalised outreach that references specific details of the candidate's experience and explains clearly why this role is relevant to them — not a template sent at volume. Invest in your company's LinkedIn presence so that candidates who receive outreach can find evidence of who you are and what working there involves. LinkedIn is most effective as a relationship-building tool rather than a broadcast channel.
How do you find candidates on Indeed?
Post well-written, specific job ads rather than generic ones — Indeed's algorithm favours relevance and engagement, and candidates are more likely to apply to ads that clearly describe what they're looking for. Use Indeed's sponsored listings for competitive roles where visibility matters. Explore Indeed's resume search for active candidates rather than relying purely on inbound applications. For specialist, senior, or niche roles, manage expectations: Indeed's strength is volume in broad markets, and it's less effective for roles where the best candidates aren't actively looking.
What is the best place to find job candidates?
There isn't a single best place — it depends on who you're trying to find. LinkedIn for professional and specialist roles, sector-specific job boards for mid-level UK hiring, technical platforms like GitHub and Stack Overflow for engineering, Handshake for early careers, and warm referral networks and specialist recruiters for senior and passive candidates. The most common mistake is defaulting to the same one or two channels regardless of what the role requires, rather than going to where the specific candidates you need actually spend their time.
What are the best alternatives to Indeed for finding candidates?
In the UK, Totaljobs and Reed are the strongest generalist alternatives, with large CV databases worth searching alongside posting. Glassdoor reaches candidates who are actively researching employers. Stack Overflow and GitHub are significantly more effective than generalist boards for technical roles. Wellfound targets startup and scale-up candidates specifically. Handshake dominates graduate and early-career hiring. The right alternative depends on the role type — a single alternative isn't better across all categories.
How effective are resume databases for finding candidates?
Moderately effective for roles where strong candidates actively submit CVs — many mid-level, administrative, and operational positions. Less effective for senior, specialist, and passive candidates who are unlikely to have uploaded a CV anywhere. The key variable is recency: databases surfacing recently active candidates produce better results than raw profile counts suggest. The fundamental limitation is self-selection — the candidates you most want are often precisely those least likely to be in any public database. Use them as one source among several, not a primary strategy.
What recruiting analytics actually improve sourcing outcomes?
Source quality reporting — which channels produce candidates who get hired and perform well, not just which produce the most applications. Funnel conversion data — where candidates are dropping out and why. Time-in-stage tracking — where delays accumulate across the process. And offer acceptance analytics — whether your preferred candidates are accepting or going elsewhere, and at what stage you're losing them. Most organisations have access to this data through their ATS but don't configure or act on it consistently. That gap is where sourcing improvement usually lives.
.png)
What Is Recruitment Process Outsourcing (RPO)? The Complete Guide
Recruitment process outsourcing covers more ground than most providers make clear. This complete guide explains what RPO is, how the models differ, what you'll pay, when it's worth it, and when it isn't.
Recruitment process outsourcing is when a company hands its recruitment function — or a significant chunk of it — to an external specialist to manage.
Not just "find us some candidates." Manage.
Sourcing, screening, assessment, interview coordination, offer management, compliance, analytics. The whole system, or the parts of it you're choosing to hand over. The provider runs it on your behalf, typically embedded into your organisation, using your employer brand, and accountable to your hiring outcomes.
That's the short version.
The longer version is worth understanding because RPO covers several quite different arrangements, has real limitations alongside the genuine benefits, and is frequently proposed as the answer to problems it cannot actually solve.
RPO vs a Recruitment Agency
A recruitment agency fills roles. You have a vacancy, they find candidates, someone gets hired, a fee changes hands, and the relationship concludes. Clean. Transactional. The agency had its process, you had yours, and the two met briefly over a shortlist.
An RPO provider manages your recruitment function. They're not filling one role — they're running the operation. Their team becomes an extension of yours. They use your name in candidate communications. They live inside your process rather than operating alongside it.
The relationship is structurally different.
With an agency, you're a client. With an RPO provider, you're a client the provider has moved into. The infrastructure, data, and process become intertwined in ways that take real thought to unwind. Which isn't a reason to avoid RPO — it's a reason to choose carefully.
What Recruitment Process Outsourcing Covers
Depending on the model, RPO can cover some or all of the following.
Workforce Planning
Mapping what you'll need to hire before the vacancy formally exists, rather than scrambling when a seat goes empty. Obvious in principle. Practised infrequently.
Job Advertising and Employer Brand
Writing and placing roles, managing channel strategy, ensuring every candidate gets a consistent experience regardless of which team they're applying to join.
Sourcing
Finding candidates who aren't looking — passive talent, specialist communities, previous strong applicants who came close last time. This is where serious RPO providers invest heavily in technology, and where the gap between a good provider and a mediocre one shows up most clearly.
Screening and Assessment
First-pass review, structured screening calls, competency-based interviews, assessments. The provider delivers a shortlist, not a haystack.
Interview Logistics
Scheduling, feedback collection, keeping candidates warm between stages. The connective tissue of hiring that everyone underestimates until they're doing it at volume.
Offer and Onboarding Support
In some models, the RPO provider manages offer stage and pre-employment checks. In others, this stays internal. Clarify upfront.
Analytics and Reporting
Time to hire, cost per hire, source effectiveness, quality of hire over time. One of the underappreciated advantages of a well-run RPO engagement: someone is consistently measuring what's happening, and the data compounds into something genuinely useful for workforce planning.
Recruitment Process Outsourcing Models
RPO is not one thing. It's a category containing several different engagement structures. Knowing which one is being proposed tells you a great deal about the commitment required and whether it fits your situation.
Full RPO
The provider owns the recruitment function end to end. Sourcing, assessment, offer management, analytics, employer brand — all of it. Your internal HR team sets direction and retains final hiring decisions, but the operational engine is external.
This is the model most people have in mind when they say "RPO." It requires the most trust, the longest commitment, and the most careful provider selection. When it works, the results are genuinely significant. When it doesn't, it's expensive, slow to fix, and contractually awkward to exit.
Best for: large organisations with significant, consistent hiring volume across multiple functions, often during rapid growth or major process transformation.
Project RPO
A specialist team deploys for a defined, time-limited need. Thirty engineers for a product launch. A new site opening. A seasonal surge that the internal team can't absorb. The engagement has a scope, a timeline, and an end date.
Much more accessible than full RPO. Faster to stand up, easier to exit, and considerably better as a way to evaluate a provider than reading their case studies. If you're uncertain whether RPO is right for your organisation at all, a project engagement is a sensible way to find out.
Best for: defined short-term volume needs, or organisations testing the RPO model before a longer-term commitment.
Hybrid RPO
The provider takes responsibility for specific stages — typically sourcing and compliance, or sourcing and initial screening — while the internal team manages assessment, decision-making, and offers. Both run in parallel, each doing what it's better equipped for.
Often the most practical model for mid-sized organisations. You keep the parts of hiring that benefit from internal knowledge and cultural familiarity. You outsource the parts that are resource-intensive, administratively heavy, or where specialist capability adds clear value.
Best for: organisations with adequate internal assessment capacity but insufficient sourcing infrastructure, or where full outsourcing isn't feasible.
The Cost of Recruitment Process Outsourcing
There's a full breakdown in our RPO cost guide, but here's the version you need for orientation.
Management Fee Model
A fixed monthly fee per embedded recruiter, covering their time, tooling, account management, and reporting. Typical UK range: £6,500 to £12,000 per recruiter per month. Predictable. Runs regardless of hire volume, which is comfortable in busy months and pointed in quiet ones.
Cost Per Hire
A fixed fee per successful placement. Typical range: £2,500 to £6,500 for mid-level professional roles, higher for senior or specialist positions. Aligned to results. Tends to be more expensive at scale than a management fee, because the provider prices in the risk of not filling roles.
Hybrid
A reduced monthly fee plus a per-hire success component. The most common enterprise structure. Keeps the core team stable while preserving performance incentives.
The economics improve significantly with volume. Under fifteen to twenty annual hires, RPO rarely makes financial sense against the alternatives. Above fifty, the cost per hire is typically 40% to 60% lower than equivalent contingency agency spend. The break-even sits somewhere in between, depending on your current cost base and the quality of your existing arrangements.
Benefits of Recruitment Process Outsourcing
Scalability
Hiring demand isn't constant. RPO lets you flex up for a volume surge and down when the business needs it, without maintaining a permanent internal team sized for peak demand.
Cost Efficiency at Scale
The provider's fixed infrastructure — technology, management overhead, sourcing tools — spreads across more hires than your internal function would. At meaningful volume, the cost per hire drops considerably compared to agency.
Process Consistency
One external team managing hiring across multiple departments means every candidate gets a similar experience. This matters more than it sounds when you've seen how differently five teams can interpret "running a recruitment process."
Compounding Data
An RPO provider measuring the same metrics across every hire, over years, builds quality intelligence that enables actual workforce planning. Rather than the traditional approach, which might be described as "hoping for the best and panicking when it goes wrong."
Limitations of Recruitment Process Outsourcing
RPO doesn't fix problems that originate outside the process.
If your roles are hard to fill because the salary is below market, RPO will source candidates more efficiently for the salary you're offering — which is to say, not efficiently at all. An RPO provider is not a compensation consultant and cannot make your offer more competitive by running a better process around it.
If your brief is unclear, RPO makes the unclear brief run faster. Which is a different problem, not a solution to the one you have.
If your hiring managers won't respond to interview requests within a week, won't commit to feedback deadlines, and treat recruitment as someone else's job — an embedded RPO team will bump into that reality repeatedly and at some cost to everyone involved.
RPO also requires trust in a way that a contingency agency doesn't. The provider is inside your organisation, using your brand, handling your candidate relationships. The data, the process, and sometimes the people become genuinely intertwined. Exit clauses and transition provisions matter more than they seem at contract stage. Read them before you need them.
RPO vs The Alternatives
In-House Recruitment
This is the right default when hiring volume is consistent and manageable, the internal HR function is well-resourced, and cultural alignment in assessment matters more than specialist sourcing capability. Underperforms when volume spikes, when specialist hiring outstrips internal expertise, or when one overworked recruiter is managing thirty open roles simultaneously.
Contingency Agencies
These are right for one-off or infrequent roles, particularly specialist or senior positions where the agency's network is the value. Fast to engage, no commitment, expensive per hire, and provides no cumulative process improvement. Useful in the right circumstances. Ruinous at scale.
Retained Executive Search
This is right for senior leadership hiring where the pool is largely passive, the stakes are high, and the firm's relationships are the primary access mechanism. Not a volume model.
Recruitment Process Outsourcing
This is right when volume is significant and consistent, internal capacity is genuinely insufficient, process consistency and quality measurement matter, and you're ready for a structural relationship rather than a transactional one.
The organisations that struggle most with recruitment are usually the ones using the wrong model for their situation. That's fixable. Picking the right tool is the most important decision in the process.
When RPO Probably Makes Sense
Multiple of these apply to your organisation.
Your internal team is permanently overwhelmed — not just busy, but consistently unable to hire at the pace the business needs. Hiring managers are going around the process because working directly with agencies feels faster. Agency spend grows year on year with no corresponding improvement in quality. You're hiring across multiple locations or functions and the candidate experience is inconsistent everywhere. You're about to scale significantly and the current infrastructure won't survive it.
Any one of these is worth a conversation. Several together is a fairly clear signal.
When RPO Probably Doesn't
You hire fewer than twenty people a year and your current arrangements work reasonably well. You need one specialist role filled urgently — that's an executive search or specialist recruiter conversation. Your fundamental problem is a poorly defined brief, a below-market salary, or a culture that candidates consistently decline politely. Or you need something in two weeks and RPO's mobilisation period is definitionally incompatible with that timeline.
Also, if the idea of an external team embedded in your organisation — using your employer brand, communicating with your candidates, sitting in your hiring manager's diary — makes you significantly uncomfortable, that instinct is worth taking seriously. RPO requires a degree of trust that not every organisation is ready for, and there is nothing wrong with that.
How SquareLogik Fits Into This
We're not a global enterprise RPO operation with a proprietary platform and a 15-country footprint. We combine AI-assisted sourcing, structured quality tracking, and real recruiters who know their markets — for organisations that want consistent, quality hiring without surrendering their recruitment function to a three-year contract.
If your situation calls for large-scale embedded RPO across a multinational workforce, there are better-resourced players to speak to. We'll tell you so.
If it calls for something more targeted — consistent support across specific hiring areas, quality measurement that feeds back into how the next search is briefed, and a recruitment partner you can have a straight conversation with — that's where we tend to do our best work.
Either way, the first conversation is just a conversation.
Frequently Asked Questions
What does RPO stand for?
RPO stands for Recruitment Process Outsourcing. It refers to the practice of transferring part or all of a company's recruitment function to an external provider. The provider manages the process — sourcing, screening, assessment, compliance, analytics — on behalf of the client organisation, typically operating as an embedded extension of the internal HR team rather than as a separate external agency.
How is RPO different from using a recruitment agency?
A recruitment agency fills individual vacancies on a fee-per-placement basis and operates independently of your internal process. An RPO provider manages the recruitment function itself — operating under your employer brand, using your systems, and accountable for the sustained performance of how you hire over time. The agency relationship is transactional. The RPO relationship is structural. Both have legitimate uses; they are not interchangeable.
What are the main types of RPO engagement?
The three main models are full RPO, where the provider manages the entire recruitment function end to end; project RPO, a time-limited engagement for a specific hiring surge or initiative; and hybrid RPO, where the provider manages specific stages while the internal team retains others. Each requires a different level of commitment and suits different situations. Full RPO is the most comprehensive and the highest commitment; project RPO is the most accessible entry point.
How much does RPO cost?
RPO is priced on three main models. Management fee: a fixed monthly fee per embedded recruiter, typically £6,500 to £12,000 per month for UK-based delivery. Cost per hire: a fixed fee per successful placement, typically £2,500 to £6,500 for mid-level roles. Hybrid: a reduced management fee plus a per-hire component — the most common enterprise structure. The economics improve significantly with hiring volume; below roughly twenty hires per year, RPO is rarely cost-effective compared to alternatives.
What are the benefits of RPO?
The primary benefits are scalability during hiring surges without permanent internal overhead; cost efficiency at meaningful volume, typically 40% to 60% lower cost per hire than equivalent agency spend; consistent candidate experience across multiple teams and locations; access to sourcing technology and specialist expertise; and compounding quality data over time that enables genuine workforce planning. The benefits are most pronounced at high volume; at low volume, they are largely theoretical.
What are the risks of RPO?
RPO doesn't fix problems that originate outside the process — unclear briefs, below-market salaries, and disengaged hiring managers will all remain exactly as problematic inside an RPO engagement. The structural integration required means exit is more complex than ending an agency relationship, so contract terms matter considerably. And the quality of outcomes depends heavily on the provider's specific team, not the brand name on the door — which makes provider selection the most important decision in the process.
Is RPO right for my organisation?
Probably worth exploring if: your internal team is consistently unable to hire at the pace the business needs, agency spend is growing without quality improvement, you're hiring at significant volume across multiple functions, or you're about to scale in a way your current recruitment infrastructure won't survive. Probably not the right answer if: you hire fewer than twenty people per year, you need a single role filled urgently, or the fundamental problem is compensation or culture rather than process.
How to Choose the Best Recruitment Process Outsourcing Company
The wrong RPO company is an expensive mistake that takes a year to untangle. Here's a framework for choosing the right one.
Here is how most organisations choose an RPO company.
They put out a request for proposal. Three or four providers respond with polished decks, impressive client logo carousels, proprietary methodology names, and promises of transformative hiring outcomes.
Someone from each provider does a confident presentation. The procurement team scores against a weighted criteria list.
The one with the highest score — or the lowest price, depending on which way the wind is blowing that quarter — gets the contract.
Twelve months later, the metrics are underwhelming.
The account manager has changed twice. The hiring managers are quietly going around the process. And the organisation is staring at an exit clause that makes leaving more painful than staying.
This is not a rare story.
Choosing the best RPO company for your organisation requires asking different questions from the ones most RFP processes ask. Not "how big is your global footprint?" but "who specifically will work on our account and what have they placed in the last six months?" Not "what is your methodology?" but "show me a client at similar volume to ours and tell me what their quality of hire metrics looked like twelve months into the engagement."
The gap between the pitch and the reality is where most poor RPO decisions live. This guide is about closing that gap before you sign anything.
Start With the Problem You're Trying to Solve
Before you evaluate a single RPO company, spend an hour getting precise about what you're actually buying.
Not "we need to improve our recruitment" — that's a category, not a problem. The specific problem.
- Time to hire is too long and we're losing candidates to faster-moving competitors.
- Quality of hire is inconsistent across teams and we can't work out why.
- We're scaling fast, need fifty hires in six months, and our internal team can't absorb the volume.
- Agency spend is unsustainable and we need a structural alternative.
- Compliance is a bottleneck and candidates are dropping out before they start.
Each of these problems has a different solution. And each solution requires different things from an RPO provider.
A provider excellent at high-volume, process-driven hiring may be mediocre at the specialist, passive-candidate-heavy searching required for senior technical roles. A provider with deep compliance infrastructure for healthcare may have no relevant experience in fintech. A provider set up for enterprise multinational hiring may be completely the wrong scale for a 200-person company with thirty annual hires.
If you start the evaluation without being precise about the problem, you will evaluate providers against the wrong criteria and select the one that presented most compellingly rather than the one that will actually fix what's broken.
The Questions to Ask in the Request for Proposals Process
Standard RFP scoring criteria tend to cluster around things that are easy to measure and hard to interpret: company size, years in business, number of countries covered, technology partnerships, client retention rate. These are fine as background checks. They're not sufficient as selection criteria.
Here are the questions that tell you what you need to know.
Who will work on our account?
Not which partner presents in the pitch meeting. Not which senior figure signs the contract. Who are the actual recruiters, account managers, and sourcers who will run your day-to-day process? What are their names? What are their backgrounds? What roles have they placed in your sector in the last twelve months?
This question makes RPO sales teams visibly uncomfortable, which is itself informative. The best providers answer it specifically and confidently. The others deflect to team capacity, methodology, and training programmes — all of which tell you about the factory, not the product.
Can we speak to a reference client at similar volume and complexity?
Not the reference client the provider selects, who has been thoroughly pre-prepared and will tell you the engagement is going well. A client you find independently — ask for a list of current clients in your sector or at your scale and call one that isn't on the curated reference list. The conversation that results is worth considerably more than any case study.
What does your quality of hire data look like for placements in our sector?
Not just time to hire and cost per hire — those metrics tell you about process speed and efficiency. Ask about retention at six months and twelve months. Ask about hiring manager satisfaction scores. Ask what happened when a placement didn't work out and how they managed it. If they can't produce specific quality of hire data for comparable placements, either they haven't been measuring it or they don't want to show it. Neither is reassuring.
How do you handle the brief?
Ask them to describe their process for defining the hiring brief with a new client. If the answer is primarily about job description review and role profiling, probe further. A brief that only captures skills and experience isn't a brief — it's a job description with a different name. The best RPO providers spend meaningful time understanding what success looks like in the role, the team dynamics, the cultural environment, and the realistic candidate market. Ask how long this typically takes and what questions they'd ask your hiring manager. The answer reveals a lot about how they'll actually approach your roles.
What happens when a hire doesn't work out?
Every RPO provider has a guarantee policy. Most guarantees involve rerunning the search at no additional cost if a placement leaves within a defined period. Understand the period, the conditions, and what "rerunning at no cost" actually means in practice — does it include sourcing from scratch, or just processing referrals you provide? Also ask how frequently they invoke this guarantee. An honest answer to that question is considerably more useful than the policy document.
What does the exit clause look like?
Ask this before you're negotiating. The exit provisions in an RPO contract are often where the real commercial risk sits. Minimum notice periods, data return obligations, technology dependency at contract end, staff TUPE considerations if the provider has recruiters embedded in your team — these are not edge cases. They're the difference between a partnership you can exit if it's not working and one that's structurally very difficult to leave.
Evaluating Sector Expertise in RPO Companies
One of the most important — and most undersold — factors in RPO selection is genuine sector expertise.
An RPO provider that "works across all industries" is a provider with generalist recruiters who can run a process in any sector. That's a different thing from a provider with deep specialist knowledge of your talent market, your candidate community, and the specific compliance or credentialling requirements that apply to your hires.
The distinction matters most in three situations.
When your roles are specialist or scarce.
If you're hiring data scientists, clinical psychologists, cloud security architects, or any role where the qualified candidate pool is small and largely passive, you need sourcers who have relationships and credibility in that community — not generalists who can construct a Boolean search and hope. Ask specifically: how many roles at this level in this discipline have you filled in the last year? Who on your team has personal relationships with candidates in this space?
When compliance requirements are sector-specific.
Healthcare, financial services, legal, education — these sectors have compliance requirements that generic recruitment processes aren't built around. A provider that adds a compliance checklist to a standard process is not the same as one that has built their process around the compliance requirements from the start.
When employer brand is sector-specific.
The way an organisation presents itself to candidates in professional services is different from how it presents in creative industries, in technology, or in the public sector. An RPO provider who doesn't understand those cultural registers will present your employer brand in ways that either feel generic or actively miss the mark with the candidates you're trying to reach.
Ask every provider for specific examples of comparable roles filled in your sector. Not case study summaries. Specific roles, specific timelines, specific quality metrics. Then call the client and verify.
Evaluating Technology in RPO Companies
Most RPO providers lead with technology in their pitches, because it's a visible and impressive thing to demonstrate. Proprietary platforms, AI-powered matching, real-time analytics dashboards — the technology story is compelling and often genuinely useful.
It's also frequently oversold. Here's how to cut through it.
What does the technology actually do in the process?
Not what it can do in principle — what does it do in your engagement, day to day? Which decisions does it inform? Which stages does it automate? Where does human judgement take over, and on what basis?
Does the technology produce better candidates or just faster process?
Speed without quality improvement is not a technology benefit — it's a process change. Ask for evidence that their technology has measurably improved quality of hire outcomes for clients, not just compressed time to hire.
What technology do you expect us to bring, and what do you provide?
If the provider expects to integrate with your ATS, understand what that integration actually means — data flows, access levels, system compatibility — before assuming it's seamless. If they're providing an ATS as part of the engagement, understand what happens to your candidate data when the engagement ends.
Is AI used in screening, and if so, how is bias monitored?
AI screening tools can introduce bias if the training data reflects historical hiring patterns that weren't themselves unbiased. Any provider using AI in early-stage screening should be able to explain how they monitor for bias, what their oversight process looks like, and what human check exists on AI-generated recommendations.
Technology is an amplifier. It makes a good process faster and a bad one more consistently bad. The technology story should follow the quality story, not precede it.
Finding RPO Agencies for Scale and Volume
This is a selection factor that people often get backwards.
The instinct, particularly in large organisations, is to choose the biggest, most established RPO provider — the one with the global footprint, the enterprise client list, and the headquarters in a glass building. Safety in scale.
The practical reality is that the largest RPO providers are optimised for the largest clients. Their processes, their account management structures, their technology stacks, and their incentive models are built around enterprise-scale engagements. If you're a 500-person organisation hiring forty people a year, you are not their priority client. You may not be able to get their best talent. You may find that your engagement is managed by a team that's learning on your account because their senior people are busy elsewhere.
Equally, choosing a small boutique provider for a large, complex, multi-geography engagement is a different kind of mismatch. The provider may have excellent people and real expertise, but insufficient infrastructure to deliver at the volume and coordination level the engagement requires.
The best fit is a provider whose typical client is roughly your size, with roughly your hiring volume and complexity. Ask them directly: where does our organisation sit in your client portfolio? Are we a large client, a mid-sized client, or a small one? What does that mean for how the account will be resourced and who will run it?
The honest answer to that question is more useful than any reassurance about being treated as a valued partner.
Asking About Diversity, Equity, and Inclusion
Most RPO providers have a DEI section in their pitch. Most DEI sections in RPO pitches describe commitments, frameworks, and values rather than results.
What you want is results. Specifically:
What does the diversity of shortlists actually look like across their current client base? Not across all hires — shortlists, which is where sourcing strategy determines who gets assessed in the first place.
What sourcing channels do they actively use to reach underrepresented candidates? Not what channels they're aware of — which ones do they actually use in practice?
What structured assessment processes do they use to reduce bias in evaluation? And are those processes verified against outcomes, or implemented on faith?
How do they handle a client brief that — intentionally or not — contains criteria that would disproportionately filter out diverse candidates?
A provider who can answer these questions specifically, with data and examples, has actually operationalised their DEI commitment. A provider who answers them with mission statements and training initiatives has a policy, not a practice.
Contract Terms Worth Negotiating Before You Sign
The commercial negotiation in most RPO selections focuses almost entirely on price. The contract terms that actually determine how the relationship functions — and how painful it is to exit — get less attention than they deserve.
Performance-linked terms matter.
If the contract specifies time to hire and cost per hire targets but nothing about quality of hire, you have a contract that rewards speed without accountability for outcome. Push for quality metrics — retention at six and twelve months, hiring manager satisfaction scores — to be included in the performance framework. The provider's willingness to include these tells you a lot about their confidence in their own quality.
Exclusivity provisions deserve scrutiny.
Some RPO contracts require you to use the provider for all hires within a defined scope. If you have specialist roles where a sector-specific agency or executive search firm would genuinely outperform the RPO provider, you want the flexibility to use them. Understand where the exclusivity applies and where it doesn't.
Data ownership is non-negotiable.
Candidate data collected during the engagement — applications, assessments, correspondence — should be clearly yours, available in a usable format at contract end, and not retained by the provider in ways that create competitive conflicts. This is increasingly important as talent pipeline data becomes a strategic asset.
Transition provisions determine how gracefully you can exit.
If the engagement ends — whether because it worked and you're bringing the function in-house, or because it didn't and you're moving on — what does the handover look like? How long does it take? Who owns the in-flight searches? These aren't hypothetical edge cases. They're scenarios with a real probability of occurring and significant cost implications if they're not covered in the contract.
Review and termination rights give you leverage throughout the relationship.
Annual performance reviews with defined remediation processes, and a termination right tied to sustained underperformance, keep the provider accountable throughout the engagement rather than only at the point of renewal.
RPO Red Flags to Walk Away From
Not every red flag is a deal-breaker. Some are just signs that the conversation needs to go deeper. But a few are worth treating as signals to slow down considerably.
A provider that can't name specific people who will run your account during the pitch is a provider that either hasn't assigned the resource yet or is pitching capacity they don't yet have. Both are problems.
A provider that resists reference conversations with clients you identify yourself — rather than clients they suggest — is a provider whose reference list doesn't represent the full picture of their performance.
A provider that can't produce quality of hire data beyond time to hire and cost per hire is either not collecting it or not prepared to show it. In either case, quality measurement is not a core part of how they operate.
A provider that dismisses your concern about exit clauses as "we're confident in the relationship" is a provider that knows the exit clauses are onerous. Confidence in a relationship is not a substitute for fair exit terms.
A provider that prices significantly lower than comparable alternatives without a clear explanation of how they're achieving that cost structure is either about to deliver a significantly reduced service or is pricing to win the contract and renegotiate later. Both happen. Ask the question.
How SquareLogik Approaches This Conversation
We start every prospective engagement by trying to understand whether we're genuinely the right fit — not in a performatively humble way, but because placing ourselves in an engagement where we're not equipped to deliver is bad for the client, bad for the candidates, and bad for us.
We'd rather have an honest conversation about whether something else might serve you better than win a contract we'll spend the next year underdelivering against.
We specialise in combining AI-assisted sourcing and structured quality tracking with human recruiters who know their markets. We work best with organisations that have consistent hiring needs across specific functions, that care about quality of hire as much as speed, and that want a recruitment partner rather than a procurement supplier.
If that sounds like your situation, the conversation is worth having. If it doesn't, we'll probably tell you so — and point you toward something that fits better. Which is, honestly, how this choice should work.
Frequently Asked Questions
How do you choose the best RPO company for your organisation?
Start by being precise about the problem you're trying to solve — not "improve recruitment" but the specific failure: slow time to hire, inconsistent quality, unsustainable agency spend, compliance bottlenecks, or volume your internal team can't handle. Then evaluate providers against that specific problem rather than generic capability. The best RPO company for your organisation is the one whose expertise, scale, and sector knowledge match your actual situation — not the one with the most impressive presentation or the largest global footprint.
What should you look for when evaluating RPO companies?
The factors that matter most are: who specifically will work on your account (not just who presents in the pitch), demonstrated quality of hire outcomes in comparable placements, genuine sector expertise rather than cross-industry generalism, scale fit with your hiring volume, fair and transparent contract terms including exit provisions, and the ability to speak to reference clients you identify yourself rather than ones the provider selects. Technology and methodology matter, but they're secondary to the quality and experience of the people actually running your recruitment.
What questions should you ask an RPO provider?
The most revealing questions are: Who are the specific recruiters and sourcers who will work on our account? Can we speak to a current client at similar volume that we identify, not one you suggest? What does your quality of hire data look like for placements in our sector — including retention at six and twelve months? How do you define and refine the hiring brief? What happens contractually when a placement doesn't work out? And what does the exit clause look like? Providers who answer these specifically and confidently are worth shortlisting. Those who deflect are telling you something useful.
How important is sector expertise when choosing an RPO company?
Critically important for specialist, compliance-heavy, or senior hiring. A generalist provider can run a recruitment process in any sector — they can source CVs, schedule interviews, and manage communications. A sector specialist has relationships with the relevant candidate community, understands the compliance requirements from the inside, and knows how to present your employer brand in the register that resonates with the people you're trying to hire. The difference shows up most in the quality and relevance of shortlists rather than in process efficiency.
Should you choose a large or small RPO company?
Neither is automatically better. Large providers are optimised for large clients and have the infrastructure for complex, multi-geography, high-volume engagements — but they may deprioritise smaller clients and assign less experienced teams to mid-market accounts. Smaller boutique providers often have deeper expertise and more senior attention per client, but may lack the scale for significant volume or geographic breadth. The right fit is a provider whose typical client is roughly your size and complexity. Ask directly where your organisation would sit in their client portfolio and how the account would be resourced.
What contract terms are most important when selecting an RPO provider?
Performance metrics that include quality of hire — not just time to hire and cost per hire. Data ownership provisions that ensure candidate data is yours and returned in usable form at contract end. Exit and termination provisions that are fair and don't make leaving prohibitively expensive if the engagement underperforms. Clarity on what's included in the headline price versus what's additional. And defined review rights throughout the contract, not just at renewal. The commercial negotiation usually focuses on price; the terms that determine how the relationship actually functions rarely get the same scrutiny.
What are the warning signs of a poor RPO company?
Inability to name specific people who will run your account during the pitch. Resistance to reference conversations with clients you identify independently. No quality of hire data beyond time to hire and cost per hire. A price significantly below comparable alternatives without a clear structural explanation. Exit clauses defended with confidence in the relationship rather than fair terms. And a pitch that's heavy on proprietary methodology names and light on specific, verifiable outcomes from comparable client engagements. None of these individually is disqualifying, but more than two together should prompt significantly deeper scrutiny.
.webp)