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
What Makes Candidates Choose One Employer Over Another
Salary gets candidates to the table. It rarely closes the deal. Here's what candidates are weighing when they have more than one offer.
Most employers think candidates choose on salary.
For many candidates — the employed, the experienced, the ones you most want to hire — salary is a threshold, not a differentiator. Once an offer clears the level the candidate needs, pay stops being the deciding factor and other things take over.
Those other things are where employers lose candidates they thought they had secured. Not to higher pay. To an employer who understood what the candidate was evaluating and gave them better answers.
The Process Sends a Signal Before the Offer Does
Candidates read the hiring process as a preview of the organisation.
A slow process with poor communication between stages tells a candidate how decisions are made. A disorganised first interview tells them something about management quality. An offer that takes twelve days to generate after a verbal acceptance tells them how much operational weight their joining carries internally.
None of this is fair. A slow HR approval chain is not a reliable indicator of a bad employer. But candidates are making probabilistic judgements with limited information, and the hiring process is the primary data source available to them. They use it.
The employer whose process is fast, communicative, and clearly managed wins candidates at the margin repeatedly. Not because the work is better or the salary is higher, but because the experience of being recruited there felt different from everywhere else.
The Manager Is Often the Decision
Ask candidates who have turned down an offer why, and the answer frequently involves the person they would have reported to.
An impressive company with an uninspiring hiring manager loses candidates to a less impressive company with a manager who clearly knew what they were doing, communicated well, and made the candidate feel that working for them would be challenging in the right way.
Candidates assess the manager throughout the process.
- How prepared they are for the interview.
- Whether their questions are generic or specific.
- How they talk about the team and the work.
- Whether they listen or perform.
By the final stage, a candidate has formed a view about whether this manager is someone whose feedback they would grow from or someone whose management style they would spend energy navigating around.
Employers who involve their best managers visibly in the hiring process win more offers than those who treat the manager as the final interview rather than the primary selling point.
Clarity About the Role and What Comes After It
Candidates accepting a new role are making a two-part decision.
- The job itself
- What the job leads to
An employer who can answer the second question clearly (what does progression look like, what does success in this role make possible, what have people who held this role previously gone on to do) gives the candidate something the vague offer cannot match.
The inability to answer this question is not always a deal-breaker. But when two offers are otherwise comparable, the employer who has articulated a convincing forward picture wins consistently. The candidate does not want to feel that they are accepting a ceiling. They want to feel that they are stepping onto a path.
Honesty Compounds Over Time
The employer who is honest about the hard parts of the role during the recruitment process earns a disproportionate level of trust.
This sounds counterintuitive. Naming the challenges, the current state of the team, the parts of the role that are difficult should discourage candidates. In practice, it does the opposite. Candidates who encounter an employer willing to say "this is where we are struggling and this is what the role will involve in addressing it" are talking to someone they can trust. Every other employer is selling them something.
Trust is the currency candidates are operating in when they make a final decision. The employer who has spent the process building it, rather than managing the candidate's perception of the company, starts the offer conversation from a stronger position.
Candidates who joined on the back of an honest pitch stay longer too. The first month does not produce a credibility gap between what was promised and what is real. That gap, when it exists, is where early attrition starts.
Speed at the Offer Stage
The candidate's enthusiasm for a role is not static. It peaks somewhere around the final interview and declines from there.
An offer that arrives less than four days after a final interview meets a candidate at close to peak enthusiasm. An offer that arrives eighteen days later, after a sign-off chain the candidate was not told about, meets a candidate who has mentally moved on, accepted another role, or simply lost the momentum that made the decision feel exciting.
Speed at the offer stage is not the same as rushing the assessment. It is the natural conclusion of a process that has been well-managed throughout — where the decision-maker was in the process, where the approval was pre-agreed, where generating the offer letter took hours rather than a week.
Employers who consistently lose candidates at the offer stage almost always have an internal process problem, not a candidate problem.
Flexibility and How It Is Communicated
Flexible and hybrid working arrangements have moved from differentiator to expectation in most professional roles.
The employer who offers genuine flexibility and says so clearly wins over the employer who offers the same flexibility but communicates it vaguely or buries it in policy documents. Candidates who cannot get a clear answer about working arrangements during the recruitment process assume the worst.
This is not about the arrangement itself. It is about whether the employer communicates clearly enough that the candidate can make a confident decision. Ambiguity at the offer stage, on a question as significant as where and when the candidate will be expected to work, creates doubt that sometimes tips the decision toward the employer who was clearer.
The Moment That Tips It
When a candidate has two comparable offers, the decision often comes down to a feeling that is difficult to articulate but easy to trace back to specifics.
- The employer who called after the final interview to check in before the offer arrived.
- The hiring manager who sent a personal note rather than letting the process speak for itself.
- The recruiter who was honest about the timeline rather than managing the candidate's expectations with vague reassurances.
These are not grand gestures. They are small signals that the organisation values the candidate as a person rather than a vacancy to fill. Candidates notice them. They do not always name them in the debrief. But they tip the scales at the margin more often than salary negotiations do.
At SquareLogik, we advise clients on candidate decisions, not just candidate pipelines.
The employers who retain the candidates they want share a set of characteristics: a clear and honest pitch, a well-managed process, and an offer that arrived when the candidate was still warm. None of those require a larger budget. All of them require deliberate attention.
Frequently Asked Questions
What do candidates prioritise when choosing between two job offers?
Salary clears the threshold but rarely decides between comparable offers. Candidates weigh the quality of the hiring process as a signal of the organisation, their assessment of the manager they would work for, clarity about progression, and the honesty of how the role was presented. The employer who communicated well, moved at a pace that respected the candidate's time, and gave them confidence in the decision wins at the margin more often than the employer who simply paid more.
How does the recruitment process affect a candidate's decision?
Significantly. Candidates treat the hiring process as a preview of the organisation — how decisions are made, how people are managed, how much operational weight the company places on incoming talent. A slow, poorly communicated process tells a story the employer may not intend to tell. A fast, respectful, well-managed one builds the kind of trust that makes an offer easier to accept and harder to decline.
Does salary determine which employer a candidate chooses?
For candidates under financial pressure, yes. For employed candidates with options, salary functions as a threshold — once it clears the level the candidate requires, it stops being the primary deciding factor. Candidates in this position are weighing career trajectory, manager quality, flexibility, culture signals from the process, and the honesty of how the role was presented. Employers who compete exclusively on pay against candidates who are not primarily motivated by it consistently lose to employers with better answers to the other questions.
What role does the hiring manager play in a candidate's decision?
A central one. Candidates assess the manager throughout the process and form a view about whether working for them would advance their career or complicate it. A strong, credible, well-prepared hiring manager is a selling point that no job ad communicates and no salary matches. Employers who involve their best managers visibly and early in the process win more offers than those who treat the manager as the final stage rather than a primary reason to join.
How important is speed in the offer process?
Candidate enthusiasm peaks around the final interview and declines from there. An offer that arrives promptly meets the candidate at close to maximum motivation. One that takes two weeks to materialise meets a candidate who has mentally recalibrated. Employers who lose candidates at the offer stage almost always have an internal process problem — a sign-off chain, an approval bottleneck, a contract generation delay — rather than a candidate problem. Fixing the internal process converts more offers than improving the compensation package.

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

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