Say "better questions" to a business owner when talking about recruitment, and they'll usually assume you mean better interview questions.
Fair assumption, and interview questions matter, but they're only one stop on a much longer road. The businesses that consistently hire well aren't just asking sharper questions in the interview room. They're asking better questions at almost every stage of the process, most of which happen nowhere near an interview.
This article is about all of them: the question that should come before the job ad even exists, the ones that decide who gets to interview stage at all, the ones asked in the room itself, the ones that get skipped once a candidate looks promising and everyone relaxes slightly too soon, and the question your entire process is quietly answering for every candidate whether you meant it to or not.
The first question nobody asks: why would someone choose to work here?
Most job ads start from what the business needs. Someone to do the work, cover the shift, take the pressure off. That's a completely reasonable place to start thinking, and a genuinely bad place to start writing, because it skips the question that actually determines whether a good candidate reads past the first line: why would this specific person want this specific role, at this specific business, over every other option they have?
This question belongs right at the start, before the role is even fully defined, because the answer shapes everything downstream. If you can't articulate what makes the role or the team genuinely worth choosing, that gap doesn't disappear. It just shows up later as a generic ad, a thin applicant pool, or a strong candidate who accepted somewhere else instead.
Asking this early also forces a more honest role definition. It's much easier to write a job description once you know what you're actually trying to sell the role on, rather than working backwards from a task list and hoping the right person reads between the lines.
It's worth actually sitting down and answering this properly, not just assuming it's obvious. What does someone in this role get to do that they wouldn't get to do somewhere else? What's genuinely good about your team, your customers, or the way the business runs, that a candidate wouldn't know unless someone told them? If the honest answer is "not much, we just need the work done," that's worth knowing before you write a single line of the ad, because it changes what the ad needs to work harder to communicate elsewhere.
The questions that decide who gets to interview stage at all
Long before anyone sits down for an interview, screening questions have already done most of the deciding. A shortlist built from vague, box-ticking questions, does the candidate have three years' experience, can they start next month, produces a vague, interchangeable set of candidates. A shortlist built from sharper questions produces a genuinely differentiated one.
The shift here is from questions that confirm eligibility to questions that reveal fit. Instead of only checking whether someone technically meets the criteria, better screening asks what they'd actually bring to the specific problems the role exists to solve. That distinction is what separates a shortlist of five people who all look roughly the same on paper from a shortlist of two or three who are each a genuinely different kind of good fit.
A practical example: instead of a screening question like "do you have experience managing a small team," something closer to "tell me briefly about a team you've managed and what the biggest challenge was" gives you an actual data point rather than a yes. It takes candidates a few extra seconds to answer, and it takes you a few extra minutes to read, but it's the difference between screening for a checkbox and screening for a genuine indicator of how someone operates. Even a single well chosen screening question like this can save hours of interview time spent with people who were never a serious contender.
Better questions in the interview itself
This is the part everyone expects, so it's worth being specific rather than generic about it. The single biggest habit worth breaking is treating the interview as a walkthrough of the resume you've already read. Asking someone to talk you through their last three roles in chronological order feels thorough, but it mostly confirms what you already know and rarely reveals how they'd actually handle the situations your role will throw at them.
The stronger alternative is asking about specific past behaviour tied directly to what the role requires: "tell me about a time you had to make a call with incomplete information," rather than "are you good under pressure." One produces a real story with real detail, the reasoning behind a decision, what actually happened next. The other produces a confident, rehearsed yes that tells you almost nothing about how they'd actually perform.
The same principle applies to follow-up questions. "What would you do differently now?" or "what did that experience change about how you approach things?" pushes past the polished version of the story most candidates have ready, and into something closer to how they genuinely think.
It's also worth watching for a common trap here: letting a confident, likeable candidate coast through on presentation alone. The instinct to soften your questions once someone's made a strong first impression is natural, and it's exactly the moment worth pushing a little further rather than less, because the candidates who are hardest to properly assess are often the ones whose presentation is doing most of the work for them.
The reference check questions that actually matter
Reference checks are where good questioning quietly falls apart for most businesses, because they're treated as a formality rather than a genuine source of information. "Would you rehire them?" and "what were their strengths?" get answered politely and vaguely almost every time, because that's exactly the kind of question a polite, vague answer satisfies.
Better reference questions ask about patterns instead of impressions: how did they handle a specific kind of pressure, what did they need from a manager to do their best work, was there ever a situation where their performance dipped, and what caused it? These questions take a little longer and can feel slightly awkward to ask, but they're far more likely to surface something genuinely useful than a general character reference ever will.
Skipping this step, or reducing it to a five-minute box-tick, throws away one of the few points in the whole process where you're hearing about the candidate from someone other than the candidate. It's also worth asking the same behavioural style question you asked the candidate directly, and comparing the two answers. If a candidate described handling a difficult situation one way, and their referee describes it quite differently, that gap tells you something worth exploring before an offer goes out, not after.
The question your process is quietly answering, whether you mean it to or not
Here's the one most businesses never think to ask at all: what impression is your recruitment process actually leaving? Every candidate who applies is silently forming an opinion about what it would be like to work for you, based entirely on how the process treats them.
A slow, silent process with no updates answers that question with "disorganised" or "we don't prioritise communication." A generic, copy-paste rejection email answers it with "you were never really seen as an individual." A confusing or overly long application answers it with "this is what it'll be like to get anything done here." None of these are the message any business intends to send, but they're exactly the message a badly run process sends anyway.
Your hiring process is, in a very real sense, your employer brand in action, not just your marketing about it. Candidates you don't end up hiring still talk about how the process felt, to their networks, on review sites, in casual conversation. Getting this right isn't just about the person you're trying to hire this time. It's about whether good candidates want anything to do with your business next time.
The fix here isn't complicated, and it doesn't require a big process overhaul. A brief, genuine update at each stage, even just "we're still reviewing and expect to get back to you by Friday," changes the entire impression of the process, even when the underlying timeline hasn't changed at all. Candidates rarely expect instant answers. They do notice being left with no answer at all.
What happens after someone applies matters just as much as what happens once they're shortlisted. A candidate who applies and hears nothing for three weeks, then receives a generic rejection, walks away with a clear impression of your business, and it's rarely a flattering one. That impression follows them into every future interaction with your business, as a customer, a referrer, or simply someone who mentions the experience to a friend who happens to be a great candidate for your next role.
Bringing this together
The theme running through all of this is the same one, applied five different times: a specific, deliberate question produces better information than a generic, comfortable one, and that's true whether the question is about the role you're advertising, the applications you're screening, the interview you're running, the reference you're checking, or the process candidates are quietly forming an opinion of the whole way through.
It's also worth noticing how much these stages depend on each other. A vague role definition produces a vague ad. A vague ad produces an unfocused applicant pool. An unfocused pool makes screening harder, which pushes weaker candidates through to interview, where generic questions then fail to catch the mismatch. Fix the first question, about why someone would choose this role, and every stage after it gets easier almost automatically.
A few worth asking yourself directly:
❓Could you clearly explain why someone should choose this role over their current one?
❓Are your screening questions checking boxes, or genuinely revealing fit?
❓Do your interview questions test memory of the resume, or actual judgement?
❓Do your reference checks confirm dates, or surface real patterns?
❓What would a candidate who didn't get the job say about how they were treated along the way?
Where this connects to a properly run process
None of this requires a recruitment background to improve. It requires treating every stage as worth the same level of care as the interview, which is usually the only stage business owners think to put real effort into. This is also exactly what a properly run process looks like, whether you're running every stage yourself or a Hiring Partner is handling parts of it alongside you: better questions built into the role definition, the screening, the interview and the reference check, with genuine attention paid to how the whole thing feels from the candidate's side throughout.
It's worth being honest that doing this consistently, across every hire, every stage, every candidate, takes real discipline, particularly when you're also running the rest of the business. That's exactly why this tends to slip first when things get busy. The interview still happens because it's on the calendar. The thoughtful screening question, the proper reference check, and the timely update to a candidate who didn't get through are the parts that quietly get skipped, and they're usually the parts that mattered most.
The bottom line
Good recruitment doesn't start with a great candidate walking through the door. It starts long before that, with the questions you ask at every stage of getting there, and the impression your process leaves on everyone who goes through it, hired or not. Fix the questions, at every stage, and the quality of the whole process tends to lift with them.
Which stage of your process do you think is asking the weakest questions right now: the ad, the screening, the interview, the reference check, or the way candidates are treated along the way?
Ash + Emerald HQ Team 💎
Comments