Recruiter Interview Questions

For hard-to-fill roles I start by building a detailed profile with the hiring manager before I write a single job description. That conversation surfaces the non-negotiables versus the nice-to-haves, which shapes every sourcing decision. My core channels are LinkedIn Recruiter for Boolean searches, targeted outreach to alumni networks, and referrals from current employees in adjacent functions. For senior or niche roles I also attend relevant professional communities and conferences. I track response rates by channel and message variant so I can iterate quickly. On a recent search for a machine learning engineer, I achieved a 34% InMail response rate by personalising each message around the candidate's published work rather than leading with the job description. The key is treating passive candidates as people with careers, not entries in a database.

A CV tells me what someone has done; an interview tells me how they think and work. My assessment framework has three layers. First, I use a structured phone screen with consistent questions for every candidate in the same role, which reduces bias and makes comparisons easier. Second, I probe for specific evidence using the STAR method: I ask candidates to walk me through real situations rather than hypothetical ones. Third, I calibrate against the scorecard I built with the hiring manager before the process began, so my recommendation is always tied to agreed criteria rather than gut feel. I also ask candidates what they found most difficult in their previous role, which often reveals more than a standard strengths question. Before extending an offer, I do reference checks focused on the specific competencies the role requires.

I use my ATS as the single source of truth and update candidate stages immediately after every interaction, not at the end of the day. For each active role I maintain a one-page brief covering the key requirements, current pipeline status, and the hiring manager's availability for interviews. Each morning I triage by urgency: roles with an offer expiring, candidates who have been in a stage for more than five business days, and interviews scheduled that week. I use templated messages for routine communications but personalise the key touchpoints: initial outreach, post-interview feedback, and offer calls. When I was managing twelve open roles simultaneously at my last company, I kept average time-to-fill at 28 days by reviewing pipeline health daily and flagging stalled stages within 48 hours.

AI has become part of several stages of my workflow. For job descriptions, I use it to generate first drafts that I then edit for accuracy and tone: it is particularly good at structuring requirements clearly. For outreach, I use it to draft personalised messages at scale: I give it the candidate's background and the role context and get a starting point I adapt for each person rather than writing from scratch. For interview preparation, I use it to generate role-specific questions and to check that my question set covers the competencies in the job description rather than defaulting to the same questions every time. What I am deliberate about is where I do not use AI: I do not use it to screen CVs autonomously, because the risk of amplifying bias in that step is real and I want a human judgment on every candidate who gets through to the shortlist. AI assists my process; it does not replace the decisions that carry legal and ethical weight.

At one organisation I worked with a hiring manager who rejected every candidate after the first interview without clear feedback, which made it impossible to calibrate the search. After the third rejection I requested a 30-minute calibration meeting rather than asking for written feedback by email. In that meeting I used a simple scorecard with the competencies we had agreed at the start of the process and asked him to rate each rejected candidate against those criteria. That conversation revealed that his requirements had shifted since the role was opened: he now wanted someone with direct industry experience he had not originally specified. I rewrote the brief, relaunched the search with the updated criteria, and filled the role within three weeks. The lesson I took was that unclear rejections usually signal a requirements gap, not a sourcing problem.

I once had to reject a candidate who had been through four interview rounds and felt certain they would receive an offer. The decision came down very late on a Friday. Rather than sending an email, I called them within two hours of receiving the decision. I was direct but specific: I told them the role had gone to a candidate with more direct experience in a particular technical area, and I gave them one piece of genuine positive feedback from the panel. The candidate was upset initially and asked whether they could speak to the hiring manager directly. I acknowledged how frustrating the situation was and offered to keep their profile for upcoming roles that matched more closely. Six months later I reached out when a more senior position opened and they came back into the process. Treating people well in rejection is one of the highest-value things a recruiter can do for their long-term pipeline.

When I joined my previous organisation, time-to-fill for commercial roles was averaging 67 days and hiring managers frequently complained that candidates were withdrawing mid-process. I audited the last twelve completed searches and found two consistent problems: the interview process had five stages when three would cover the same ground, and candidates were waiting an average of eight days between stages. I put a proposal to the Head of People to reduce the process to three stages and introduce a 48-hour feedback commitment from interviewers. We piloted it on the next five roles. Time-to-fill dropped to 38 days on average and candidate withdrawal fell from 31% to 12%. I then documented the revised process and trained the interview panel. The hiring managers became strong advocates because it saved their time too.

I have worked extensively with Greenhouse, Lever, and Workday, and I have used Ashby more recently. My approach to any ATS is the same: set up the pipeline stages before you open the first role, not mid-search, and agree on what each stage means with the hiring team. That consistency makes reporting accurate. In Greenhouse I build custom scorecards for every role and use the interview kit feature to share structured questions with the panel. I also use the reporting suite to track time-in-stage and identify where candidates are dropping. One change I made at a previous organisation was adding a disqualification reason field to every rejection: that data showed us that 40% of rejections at screen stage were for a qualification we could have screened for upfront with a single application question, which we added and saved around 200 hours of interviewer time in the following six months.

I track four core metrics: time-to-fill, offer acceptance rate, 90-day retention of placed candidates, and hiring manager satisfaction. Time-to-fill tells me how efficient the end-to-end process is. Offer acceptance rate tells me whether my expectation-setting during the process is accurate: if candidates decline offers regularly, there is usually a disconnect between what I described and what they experienced in interviews. Ninety-day retention is the one most recruiters underuse, but it is the closest proxy for hire quality. If a high proportion of hires leave within their first three months, it usually means the role was misrepresented or the candidate was not properly assessed. I review all four metrics monthly and share them with my manager. At my last role my offer acceptance rate was 87% against a team average of 71%, which I attribute mainly to better expectation-setting on compensation early in the process.

I treat diversity as a sourcing and process question, not a compliance one. On the sourcing side, I actively look for channels that surface candidates from underrepresented groups: specialist communities, relevant university partnerships, and referrals from diverse employees. I also audit job descriptions for language that research shows discourages applications from certain groups, for example, long lists of requirements that tend to deter women from applying unless they meet every point. On the process side, I use structured interviews with consistent questions and a scorecard so that every candidate is assessed against the same criteria by the same framework. I push for diverse interview panels where possible, because research consistently shows that panel composition affects outcomes. I track diversity at each stage of the funnel and flag drop-off points to the hiring manager so we can investigate root causes rather than just measure outcomes.