By Johnny Campbell
Introduction
Count the messages that leave your talent team in a week. The coordinator sends most of them. They confirm the interview, they move it when the hiring manager’s calendar changes, they tell the candidate where to park, they answer the email that arrives at 11pm asking whether the panel will be on Teams or Zoom. For the overwhelming majority of your candidates, the coordinator is the only human being at your company they will ever exchange words with. The recruiter sells the role once; the coordinator is the relationship. And yet the job gets scoped as scheduling admin, hired in a fortnight, and paid accordingly. The actual competency on test is composure in front of a queue that never empties, held together by judgement about who to disappoint and how kindly.
Three mistakes show up again and again. The first is hiring for calendar mechanics — probing which ATS they have touched, whether they know Calendly, how fast they can build a five-person panel — when the real job is triage and communication under pressure. The second is dismissing candidates with no office experience. A person who has run a Saturday shift in a busy restaurant, handled a returns desk in December, or organised a 200-person student ball has already done the load-bearing parts of this job under worse conditions and for less money. The third is never testing the moment that defines the role: two interviewers and a candidate all want different slots, the req is hot, and somebody has to be told no.
This page gives you 24 behavioural questions across the five capabilities that actually predict performance, plus red flags, a loop that does not punish junior applicants, and answers to the questions TA leaders ask us most. This is often someone’s first job in talent acquisition, so every question is written to pull evidence from wherever that evidence lives — retail, hospitality, a part-time bar job, a university society, a family business.
Core Competencies for a Great Recruiting Coordinator Hire
The non-negotiable is Attention to Detail, because a wrong time zone in a calendar invite costs you a candidate, not a meeting. Pair it with Communication Skills — clear, warm, brief writing at volume — and Service Oriented instinct, the reflex to treat the person on the other end as a guest rather than a ticket. Strong coordinators also show Ownership of outcomes they cannot fully control, Empathy for a candidate who has taken unpaid leave to attend your final stage, and Decision Making fast enough to break a scheduling deadlock without escalating every time. Finally, look for Collaboration with interviewers who outrank them and forget things.
Scheduling and Logistics at Volume
What good looks like
A strong candidate can describe a day or week with real volume attached — a number of people, a number of moving pieces — not a general sense of being busy. They can point to the moment something was about to fall through the cracks and describe exactly how they caught it. Their examples don’t have to come from an office: a kitchen pass, a rota, a wedding all carry the same evidence if they can be specific about what they tracked and how.
Behavioural questions
- Tell me about the busiest day you have ever worked, in any job, and what you had to leave undone.
- What job was this, and what made that day the busiest?
- What specifically did you leave undone, and how did you choose it?
- Who noticed, and what did you tell them?
- What would you do differently if that day happened again tomorrow?
- Describe a time you had to fit several people’s availability together to make something happen.
- How many people’s availability were you juggling, and how far apart were they?
- What tool or method did you use to track it?
- What almost didn’t fit, and how did you solve it?
- How long did the whole thing take you to pin down?
- Tell me about a time an arrangement you had already made fell apart at short notice.
- What was the arrangement, and how much notice did you get?
- What was your first move once you found out?
- Who did you have to contact, and in what order?
- What did the new version look like compared to the original?
- Walk me through the most complicated thing you have ever organised on behalf of other people.
- What were you organising, and how many people or moving parts were involved?
- What was the hardest piece to lock down?
- What went wrong on the day, if anything?
- What would you build differently next time?
- Describe a time you were responsible for something running on time when you had no authority over anyone involved.
- What was the thing, and why did you have no authority over the people involved?
- How did you get people to actually do what needed doing?
- What happened when someone wasn’t cooperating?
- Did it run on time in the end?
Situational scenario
You’re scheduling a five-person interview panel for a role that needs to move fast. Two panellists are in different time zones, one has a hard stop for a flight, and the hiring manager wants the whole loop done inside three working days.
Walk me through how you’d put this together.
Then introduce a constraint: “The night before, the panellist with the flight messages you to say they need to move an hour earlier, which now clashes with someone else’s only free slot. What do you do?”
What to listen for
whether they have an actual method for sequencing constraints rather than just trying options at random, whether they communicate the change clearly and quickly to everyone affected, and whether they protect the candidate’s experience while the schedule is falling apart around them.
Candidate Communication and Experience
What good looks like
A strong candidate can recall specific wording — a line they changed in an email, a sentence they added to soften bad news — not just a claim that they’re a clear communicator. They notice discomfort in the other person before it’s said out loud, and they can describe a mistake that reached someone outside their team without minimising it. The correction matters as much as the apology.
Behavioural questions
- Tell me about a mistake you made that reached a customer, a candidate, or a member of the public.
- What was the mistake, and how did it reach them?
- How did you find out it had gone wrong?
- What did you say to them directly?
- What did you change afterwards so it wouldn’t happen again?
- Describe a time you had to give someone news they did not want to hear.
- What was the news, and who were you delivering it to?
- How did you decide how to phrase it?
- What was their immediate reaction?
- What did you do in the minutes right after telling them?
- Tell me about a time someone was angry with you about something that was not your fault.
- What were they angry about, and why wasn’t it your fault?
- What did you say to them in the moment?
- Did you correct the record, or just let them be angry?
- How did the situation end?
- Describe a time you rewrote a message because the first version was not clear enough.
- What was wrong with the first version?
- What specifically did you change in the second?
- What told you the first one wasn’t landing?
- Did the rewritten version actually work better?
- Tell me about a time you noticed someone was having a poor experience before they said anything about it.
- What tipped you off that something was wrong before they said anything?
- What did you actually do about it?
- Did you say anything to them directly, or fix it quietly?
- How did they respond once they realised you’d noticed?
Situational scenario
A candidate has just finished a final-stage interview and messages you afterwards saying the panel felt disorganised and one interviewer was late without explanation. You know the interviewer was pulled into an urgent client call.
Walk me through how you respond to the candidate.
Then introduce a constraint: “The candidate then asks you directly whether this is normal for how the company runs things. What do you actually say?”
What to listen for
whether they acknowledge the candidate’s experience without either over-apologising or dismissing it, whether they’re honest rather than defensive when asked the direct question, and whether they follow up internally so the same thing doesn’t happen to the next candidate.
Prioritisation When Everything Is Urgent
What good looks like
A strong candidate has a real method for deciding what actually goes first, even if they’ve never called it that, and they can describe a specific moment they told someone their request would wait. They can name something they missed because their attention was elsewhere, and what that taught them. The nerve to disappoint someone on purpose is the signal, not the volume of tasks completed.
Behavioural questions
- Tell me about a time three different people needed something from you at the same time.
- What did each of the three people actually need?
- How did you decide the order?
- Did anyone push back on being second or third?
- What happened to the two who had to wait?
- Describe a time you decided that something labelled urgent could actually wait.
- What was labelled urgent, and who labelled it that way?
- What told you it could actually wait?
- Did you say that out loud to the person who sent it?
- What happened when you didn’t act on it immediately?
- Tell me about a time you told someone you would not get their request done that day.
- What was the request, and who made it?
- How did you tell them, and what words did you use?
- What was their reaction?
- Did you offer them anything in place of it?
- Describe a time you missed something because your attention was somewhere else.
- What were you focused on instead?
- What did you miss, specifically?
- How did you find out you’d missed it?
- What did you do once you realised?
- Tell me about a time you were interrupted repeatedly while working towards a deadline.
- What was the deadline, and what kept interrupting you?
- How did you protect the time you had left?
- Did you miss the deadline, or make it?
- What would you do differently with the interruptions next time?
Situational scenario
You have three tasks due by end of day: confirming a final-round panel for tomorrow, responding to a candidate who’s asked to reschedule twice already, and updating the ATS for a compliance audit due first thing tomorrow. You get a message that a fourth, unplanned thing needs doing right now.
Walk me through how you decide what happens in what order.
Then introduce a constraint: “Halfway through the afternoon, the hiring manager for tomorrow’s panel messages to say they’ve realised they’re double-booked. Does that change your order?”
What to listen for
whether they can articulate the actual reasoning behind their ranking rather than just listing what they did, whether they communicate proactively with whoever’s request drops down the list, and whether the new information genuinely changes their priorities or they just bolt it on top.
Accuracy and Systems Hygiene
What good looks like
A strong candidate can describe a specific error they caught that other people were relying on, and what they did once they found it, not just that they’re detail-oriented. They’ve built or maintained some system, however informal, to keep track of something over time, and they can describe repetitive work without contempt for it. Following a process they privately think is wrong, correctly, while also flagging it, is a strong signal.
Behavioural questions
- Tell me about a time you found an error in a record or a list that other people were relying on.
- What was the record, and who was relying on it?
- How did you find the error?
- What did you do once you found it — fix it quietly, or flag it?
- Did you check for the same error anywhere else?
- Describe a system you set up yourself to keep track of something.
- What were you keeping track of, and why didn’t an existing system cover it?
- What did you actually build — a spreadsheet, a checklist, something else?
- How did you keep it updated over time?
- Is it still in use, or did it get replaced by something better?
- Tell me about the longest stretch of repetitive work you have done.
- What was the work, and how long did the stretch last?
- What did you do to keep the quality up as it went on?
- What mistakes crept in, if any, and when?
- What did you learn about your own attention span from it?
- Describe a time you had to follow a process you thought was inefficient.
- What was the process, and what was inefficient about it?
- Did you follow it anyway, or push back first?
- If you followed it, what did you do with your concerns?
- Did the process ever actually change?
Situational scenario
You inherit a candidate tracking spreadsheet that’s been maintained by three different people over the past year. You find duplicate entries, at least one candidate marked as rejected who’s actually still in process, and no consistent naming convention for stages.
Walk me through how you clean this up.
Then introduce a constraint: “Halfway through, you realise the rejected candidate who’s actually still active was told nothing; they’ve been waiting three weeks for news that should have come already. What do you do?”
What to listen for
whether they prioritise the live candidate mistake over finishing the cleanup, whether they build something that prevents the same drift happening again rather than just fixing today’s mess, and whether they own telling the candidate the truth rather than quietly closing the gap.
Working with Interviewers and Hiring Managers
What good looks like
A strong candidate can describe telling someone more senior than them that their preferred option wasn’t possible, and can say specifically what they said. They can describe chasing someone who was ignoring them without becoming either invisible or difficult about it, and they can name a small change they made unprompted that saved someone else real time.
Behavioural questions
- Tell me about a time you had to tell someone more senior than you that their preferred option was not possible.
- What did they want, and why wasn’t it possible?
- What exactly did you say to them?
- How did they react?
- What did you offer them instead?
- Describe a time you had to chase someone who was ignoring your messages.
- Who were you chasing, and what did you need from them?
- How many times did you have to follow up, and through what channels?
- Did you change your approach as the chasing went on?
- What finally got them to respond?
- Tell me about a time you worked closely with someone disorganised.
- What made this person disorganised, specifically?
- What did their disorganisation cost you directly?
- What did you put in place to work around it?
- Did you ever raise it with them, or just absorb it?
- Describe a time you were given an instruction you did not understand.
- What was the instruction, and who gave it to you?
- Did you ask for clarification, or guess?
- What happened when you acted on your best guess, if you did?
- What would you do differently next time you got an unclear instruction?
- Tell me about a small change you made that saved someone else time.
- What was the change, and whose idea was it?
- How did you know it would actually save time?
- Did anyone ask you to make it, or did you do it unprompted?
- Did it get adopted more widely, or stay just yours?
Situational scenario
An interviewer keeps arriving late to panels or cancelling with almost no notice, and it’s happened three times in the last fortnight with the same hiring manager’s reqs. The hiring manager hasn’t said anything about it.
Walk me through what you do.
Then introduce a constraint: “When you raise it with the interviewer directly, they tell you they’re overloaded and it’s not really their priority right now. What’s your next move?”
What to listen for
whether they go to the hiring manager rather than just absorbing the disruption personally, whether they can be specific about the cost — candidates rescheduled, time lost — rather than vague frustration, and whether they find a structural fix rather than just hoping it improves.
Red flags to watch for in Recruiting Coordinator interviews
The candidate is missing from their own story. They describe a rescheduling mess entirely from the interviewer’s point of view — whose calendar, whose escalation, whose annoyance — and never once mention the person who booked a day off for it.
No opinion about the work. They cannot name a single thing they would change about a process they have worked inside, in any job. Coordinators see every crack in your funnel; one who never notices will never tell you.
Apology as a strategy. Asked about the mistake that reached a candidate, they describe saying sorry and stop there. No correction, no message sent, no change afterwards.
Blanket compliance. Every story ends with them absorbing the request. Nobody is ever told no, nothing is ever pushed back, and the extra hours are worn as a badge. That coordinator burns out in a year.
Vagueness about volume. They cannot tell you roughly how many interviews, shifts, covers or customers they handled in a typical week. People who genuinely worked at volume remember the numbers.
Detail failures during the process itself. They turn up to the wrong link, get your company name wrong in the follow-up email, or ignore your written instructions. This is the one interview where the process is the work sample.
How to structure a Recruiting Coordinator interview loop
Start with the obvious point: a five-stage loop for an entry-level coordinator is itself a candidate experience failure, and every applicant you reject has now watched you run the process they were meant to fix. Two stages, plus a short exercise, done inside ten working days.
Stage one — screen (25 minutes, recruiter). Three or four questions from Scheduling and Candidate Communication. You are checking for clarity, warmth and real examples from any context. Do not filter on recruitment experience.
Stage two — working session (60 minutes, hiring manager plus a coordinator from the team). Split it: thirty minutes of behavioural questions from Prioritisation and Working with Interviewers, then thirty minutes on the exercise.
The exercise. Give them a genuinely conflicting schedule: a candidate available Tuesday morning only, one interviewer in another time zone, a second interviewer who has just declined the slot, and a hiring manager pressing for the offer this week. Ask them to talk you through what they would send and to whom. Then hand them a rude email from a candidate who has been waiting nine days for feedback and ask them to draft a reply, out loud or on paper. You will learn more in these thirty minutes than in three more interviews.
Then make the loop repeatable — same questions, same order, same scoring, every candidate, so you are comparing evidence rather than remembering who you liked. See how Interview Intelligence standardises this across your team →
Frequently asked questions
Can you hire a Recruiting Coordinator with no recruitment experience?
Yes, and some of the best coordinators come in this way. The transferable evidence sits in hospitality, retail, front-of-house, events and student societies — high-volume scheduling, difficult conversations with strangers, and composure when the queue builds. Test for that directly rather than for ATS familiarity. Systems take a fortnight to learn; the instinct to protect someone else's experience while being told off does not.
How much should we weight ATS experience?
Less than most job specs suggest. Someone fluent in Greenhouse will still take weeks to learn your workflows, your req naming, your approval chain and your interviewer quirks. What matters is whether they keep records accurately without being chased, and whether they notice when data looks wrong. Ask about any system they have kept clean, including a rota or a spreadsheet.
How do we assess a candidate with almost no work history?
Change where you look, not what you look for. University societies, sports clubs, volunteering, caring responsibilities and part-time work all generate the same evidence: competing demands, unreliable people, limited authority. Ask for the specific occasion, the specific decision and the specific outcome. A candidate who can describe running a 200-person event has shown you more than one who lists three internships and owned nothing in any of them.
What does good look like in the first 90 days?
By week four they should be scheduling standard loops unsupervised and answering candidate queries without templates for everything. By week eight they should be spotting problems before you do — an interviewer who keeps cancelling, a stage where candidates go quiet. By week twelve, expect at least one suggestion about how the process should change. If none of that has happened, the issue is usually onboarding rather than the hire.
Should the Recruiting Coordinator role be a stepping stone to recruiter?
For some people, yes, and pretending otherwise loses you good candidates. But be honest in the interview about timelines, and do not assume everyone wants it. Career coordinators exist, they are extremely valuable, and they leave when the organisation treats their job as a waiting room. Ask what they want next, then say plainly what you can and cannot offer.