ExamopotamiaWhy test recruiter skills before you hire?
Recruiters are usually very good at interviews, because interviewing is their job. That makes it harder to tell a strong recruiter from a confident one. The difference shows when a search is hard, a hiring manager keeps saying no, or a top candidate has a better offer elsewhere. A short test puts candidates in those situations and checks the practical knowledge, from Boolean strings to acceptance rates, that keeps a hiring pipeline healthy.
What this template covers
- Sourcing: Boolean search, passive candidates and judging which channels are worth paying for.
- Working with hiring managers: intake meetings and fixing repeated late-stage rejections.
- Interviewing and fairness: the STAR method, structured scoring, reducing bias and handling adjustment requests.
- Candidate experience: how and when to deliver bad news.
- Offers and metrics: salary requests above the range, offer acceptance rate and time to fill.
How to run it well
Use all twelve questions with a 15 minute limit. For an in-house recruiter or talent partner, a pass mark around 70% is fair; a recruitment coordinator could start at 60%. Shuffle the questions and answer options, and make sure the metric questions allow a calculator or a scrap of paper.
When results come in, the three hard questions on offers, recalibration and channel value show whether someone thinks like a partner to the business or just fills a pipeline. Use any wrong answers in the interview: ask the candidate to walk you through the last time a hiring manager rejected all of their shortlist.
Who this test is for
Use it for in-house recruiters, talent acquisition partners, recruitment coordinators, sourcers, and agency consultants joining your team or your preferred supplier list. It is also useful for HR generalists who are taking on recruitment and want to check what they already know, and for hiring managers who run their own searches and want a shared standard with the talent team.
Make it yours
Add questions on your own process: the stages a candidate goes through, who signs off offers, what your applicant tracking system expects recruiters to record, and how you advertise roles. Technical recruiting teams could add questions about the roles they hire most, so recruiters can tell a front-end developer from a data engineer. Every question can be edited, and the AI generator can draft more. Review the per-question statistics after your first batch of candidates and replace any question that nearly everyone answers correctly.