Technical Recruiter Interview Questions and Scorecard
Free technical recruiter interview questions for teams hiring engineers without HR: 6 question sets, good-answer notes, and a scorecard. Download as DOCX.
Technical Recruiter Interview Questions and Scorecard
Six question sets for companies hiring engineers without a recruiting department: core, sourcing, intake, technical screening, closing, and a 1-to-5 scorecard. Every question comes with why it is worth asking and what a strong answer sounds like. Download as DOCX.
Hiring a technical recruiter is an odd interview to run, because you are evaluating someone at the exact skill you lack. The candidate interviews for a living. They will be warm, fluent, and full of process vocabulary. Fluency is not the thing you are buying, and at a small company the cost of confusing the two is a year of unfilled engineering roles.
At FirstHR, we build for companies that hire without an HR department, where a founder or an engineering lead runs this interview between everything else. The way through is to ask questions whose answers cannot be improvised: a real search described end to end, an outreach message they actually sent, a search they failed to fill.
This page gives you six question sets, every question paired with the reason it is worth asking and what a strong answer sounds like, plus a 1-to-5 scorecard and a red-flag checklist. Pair it with the matching technical recruiter job description so the posting and the interview test the same things.
TL;DR
Interview a technical recruiter on five things: sourcing craft, technical literacy, hiring manager partnership, screening design, and closing. Force specifics: the last search end to end with numbers, a real outreach message, a search they failed to fill. Score seven areas 1 to 5 immediately after. Download six question sets and the scorecard as DOCX.
What a Technical Recruiter Is Hired to Do
A technical recruiter finds, screens, and closes engineering candidates, and translates between a hiring manager who thinks in systems and a market that thinks in titles. The screening is not technical judgment, which your engineers still own. It is depth: what the candidate built, what broke, what they changed.
That distinction decides the whole interview. If you test for engineering knowledge, you will hire a former developer who may or may not be able to source. If you test for search craft, calibration, and closing, you get someone who fills roles. The hiring process is the product they deliver, and it is what the questions below measure.
One more thing worth naming early: at your size the recruiter is the entire recruiting function. There is no coordinator to book loops and no manager to calibrate the search. Interview accordingly, and weight the questions about working with a busy engineering lead more heavily than you would at a larger company.
Which Question Set Should You Use?
Pick the sets by the problem you actually have, not by covering everything evenly. The core set works for any technical recruiter hire. The other four target a specific failure mode, and the scorecard runs alongside whichever you choose. Use this guide to decide.
Core Questions
Start here
The end-to-end search, funnel ratios, written notes, and a failure they own. Works for any technical recruiter hire, in-house or contract.
Sourcing and Outbound
Can they find people?
Channels beyond the obvious one, a real outreach message, referrals from your engineers, and early metrics. Use it when most hires come from outbound.
Intake and Partnership
Can they manage a lead?
Intake checklists, converting a manager’s taste into written criteria, disagreement with evidence, and getting busy engineers to interview on time.
Technical Screening
Depth or keywords?
Telling depth from keyword matching, explaining concepts plainly, designing a fair take-home, and knowing what a selection procedure is.
Closing and Offers
Can they land it?
Compensation raised early, competing offers tracked, declines mined for reasons, and the gap between signature and first day owned.
Scorecard and Red Flags
Score, do not guess
A 1-to-5 rubric across seven areas, a red-flag checklist, and reference-check prompts. Use it with any set above.
Choose the Sets From Your Last Failed Search
Think about the last engineering role you struggled to fill and name where it broke. If almost nobody applied and outbound went nowhere, weight the sourcing and outbound set. If your engineering lead rejected candidate after candidate without being able to explain the pattern, weight intake and partnership. If you reached finalists and then lost them, weight closing and offers. If your engineers spent hours screening resumes that should never have reached them, weight technical screening. Run the core set with every candidate regardless, and always finish with the scorecard.
6 Free Question Sets to Download
Download all six as a single Word document or copy individual sets. Each follows the same structure: when to use it, the questions with a reason to ask and a strong-answer note, what to listen for, and space for notes. Pick 8 to 10 questions total and add your own.
Download All 6 Question Sets
Core, sourcing, intake, technical screening, closing, and a scorecard with red flags. All in one DOCX.
Set 1: Core Technical Recruiter Questions
The starting set for any technical recruiter hire: the last search end to end, funnel ratios, requirement pushback, written notes, and a failure they own. Start here.
Core Technical Recruiter Interview Questions
CORE TECHNICAL RECRUITER INTERVIEW QUESTIONS
Candidate: __
Company: __
Interviewer: __
Date: _
HOW TO USE THIS SET
This is the starting set for any technical recruiter hire. Ask 6 to 8 of these.
Each question lists why it is worth asking and what a strong answer sounds like,
so you can judge the answers without being an engineer yourself. Score the
candidate on the rubric in Set 6 immediately after the interview.
CORE QUESTIONS
1. Walk me through the last engineering role you filled, from intake to signed
offer.
Why ask it: the whole job is in this one answer, and it is very hard to fake
a sequence you have not lived.
Strong answer: names the role and level, describes the intake conversation,
the channels used, how many candidates reached each stage, where the search
stalled, and what they changed. Ends with a date and an outcome.
Weak answer: describes a generic process with no numbers, no stall point,
and no decision they personally made.
2. What is the difference between a back-end engineer and a platform engineer at
a company our size?
Why ask it: tests whether they understand roles rather than keywords. You do
not need the perfect answer, you need to hear them reason about scope.
Strong answer: explains that the line moves by company, that at a small team
the same person may do both, and asks what your stack and team look like
before answering in detail.
Weak answer: recites a definition, or claims the titles are interchangeable.
3. A hiring manager sends you a requirement with twelve must-have technologies.
What do you do?
Why ask it: over-specified requirements are the single most common reason a
small company cannot fill an engineering role.
Strong answer: pushes back with market evidence, asks which three items are
genuinely non-negotiable, and offers to run a sample search to show what the
full list yields.
Weak answer: takes the list as written and starts posting.
4. How many candidates do you expect to contact to make one engineering hire,
and what does the funnel look like in between?
Why ask it: a recruiter who has really done the work carries rough ratios in
their head.
Strong answer: gives ranges rather than a single number, notes the ratios
swing hard by seniority and market, and says which stage they would measure
first at your company.
Weak answer: a confident, precise number with no caveats, or no idea at all.
5. Tell me about a search you failed to fill. What went wrong?
Why ask it: the answer separates people who diagnose from people who blame.
Strong answer: names a specific search, owns at least one of their own
mistakes, and describes what they would do differently.
Weak answer: blames the hiring manager, the budget, or the market entirely.
6. How do you write up a candidate for a hiring manager who has ten minutes?
Why ask it: written screening notes are the recruiter deliverable you will
read most often.
Strong answer: describes a short structured note tied to the agreed criteria,
with evidence and an explicit recommendation, not a resume summary.
Weak answer: says they forward the resume and let the manager decide.
7. What would you need from me in your first two weeks to be effective?
Why ask it: tests whether they know they need calibration, access, and a
decision-maker, or whether they plan to work in isolation.
Strong answer: asks for intake time with the hiring manager, the salary band,
the interview loop, and permission to speak about the product credibly.
Weak answer: says they just need the job descriptions.
8. How do you keep a candidate warm when our interview loop takes three weeks?
Why ask it: slow loops are the reality at a small company, and losing
finalists to silence is the most common avoidable loss.
Strong answer: sets expectations up front, commits to a fixed check-in
cadence, and pushes you to compress the loop rather than only managing around
it.
Weak answer: says they follow up when there is news.
WHAT TO LISTEN FOR
•Specific searches, with roles, levels, timelines, and numbers
•Willingness to push back on a requirement with evidence
•Ownership of failures rather than blame
•Questions asked back to you about the team, the stack, and the band
NOTES
__
__
Set 2: Sourcing and Outbound Questions
For a search that depends on outbound rather than applications: channels beyond the obvious one, a real outreach message, referrals from your own engineers, and week-one metrics.
Sourcing and Outbound Questions
SOURCING AND OUTBOUND QUESTIONS
Candidate: __
Company: __
Interviewer: __
WHEN TO USE THIS SET
Use this set when most of your engineering hires will come from outbound rather
than inbound applications. That is the normal case for a small company with a
name nobody recognizes yet. Sourcing skill is what you are actually buying.
QUESTIONS
1. Where do you find engineers who are not applying to jobs?
Why ask it: a technical recruiter who only works inbound applications will
not solve your problem.
Strong answer: names several channels beyond the obvious one, including code
hosting profiles, engineering communities, conference and meetup networks,
open source contributors, and referrals from your own engineers.
Weak answer: one channel, described as if it were the whole job.
2. Show me an outreach message you have actually sent. What made it work?
Why ask it: outbound response rate is a craft skill and the message is the
artifact.
Strong answer: brings or recites a real message that references something
specific about the person, states the role honestly, and is short. Knows their
own response rate roughly.
Weak answer: a template with a merge field and a list of company perks.
3. Our engineers are the best referral source we have. How would you use them?
Why ask it: referrals are the highest-yield channel at a small company and
the easiest one to run badly.
Strong answer: describes a light, repeatable ask that respects engineer time,
gives them a shortlist to react to rather than an open question, and closes
the loop on what happened.
Weak answer: sends a company-wide email and waits.
4. How do you source for a role when you cannot match the pay at the top of the
market?
Why ask it: this is your actual situation, and the answer reveals whether
they can sell something other than money.
Strong answer: shifts the search toward candidates who value scope, autonomy,
ownership, or remote flexibility, and is honest about which candidates are
out of reach.
Weak answer: says they would just ask for a bigger budget.
5. How do you keep a pipeline for a role you are not hiring for right now?
Why ask it: a recruiter who rebuilds from zero every time is slow and
expensive.
Strong answer: keeps a warm list with notes on timing and interest, checks in
without a pitch, and can say who they would call first if a role opened
tomorrow.
Weak answer: starts fresh with every requisition.
6. What do you do in the first 48 hours of a new search?
Why ask it: the first two days predict the next two months.
Strong answer: intake with the hiring manager, a calibration search to test
the requirement against the market, and a shortlist shown back to the manager
before mass outreach begins.
Weak answer: writes a posting and starts sending messages.
7. How do you measure whether your sourcing is working, in week one rather than
week six?
Why ask it: leading indicators are what let you correct a search early.
Strong answer: response rate to outreach, screen-to-manager pass rate, and
calibration feedback on the first shortlist.
Weak answer: only names time to fill, which you learn far too late.
WHAT TO LISTEN FOR
•Multiple real channels, not a single tool
•A specific, personal outreach message they can show you
•Comfort selling scope and ownership rather than only pay
•Early metrics, not just end-of-search metrics
NOTES
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Set 3: Intake and Hiring Manager Partnership Questions
For the relationship that decides everything downstream: intake checklists, converting an unstated preference into written criteria, productive disagreement, and getting a busy lead to interview on time.
Intake and Hiring Manager Partnership Questions
INTAKE AND HIRING MANAGER PARTNERSHIP QUESTIONS
Candidate: __
Company: __
Interviewer: __
WHEN TO USE THIS SET
At a small company the technical recruiter works directly with an engineering
lead, a founder, or both. There is no talent team to absorb friction. This set
tests whether the candidate can run that relationship, disagree productively, and
keep a search moving when the hiring manager goes quiet.
QUESTIONS
1. What do you ask in an intake meeting, and how long does it take?
Why ask it: intake quality sets the ceiling on everything downstream.
Strong answer: a real list including the problem the hire solves, the level,
the salary band, the three must-haves with proof points, who is in the loop,
and the decision date. Usually 30 to 45 minutes.
Weak answer: says they take the job description and go.
2. A hiring manager rejects your first five candidates but cannot say why.
What do you do?
Why ask it: this is the most common failure mode in technical recruiting and
it has a technique attached.
Strong answer: stops sourcing, brings three profiles side by side, and asks
the manager to rank and explain, converting taste into written criteria.
Weak answer: sends five more candidates.
3. Tell me about a time you disagreed with a hiring manager. How did it end?
Why ask it: a recruiter who never disagrees is an order taker.
Strong answer: a specific disagreement, evidence brought to the conversation,
and a decision that stuck, including cases where they lost the argument and
said so.
Weak answer: says they never disagree because it is the manager’s call.
4. How do you get an engineering lead who is busy shipping to actually do
interviews on time?
Why ask it: at your size the biggest scheduling constraint is the person you
cannot escalate to.
Strong answer: books the loop in advance, batches interviews, sets a standing
slot, and makes the cost of delay visible with real examples of lost
candidates.
Weak answer: says they send reminders.
5. How do you write interview questions for a role you do not personally
understand?
Why ask it: they will have to build loops for roles outside their background.
Strong answer: pulls the questions from the essential functions of the job,
drafts with the engineering lead, and gets the scoring criteria agreed in
writing before the first candidate.
Weak answer: searches for a list online and uses it as-is.
6. How would you run a debrief with three interviewers who disagree?
Why ask it: unmanaged debriefs default to whoever is most senior or loudest.
Strong answer: collects written scores before anyone talks, opens with the
evidence rather than the verdicts, and holds the group to the agreed criteria.
Weak answer: says they let the hiring manager decide in the room.
7. What do you do when the salary band and the market do not match?
Why ask it: someone has to say this out loud, early, and it should be them.
Strong answer: brings market evidence to the hiring manager within the first
week, then presents the options plainly: raise the band, lower the level, or
change the scope.
Weak answer: keeps searching and hopes.
WHAT TO LISTEN FOR
•A real intake checklist, not a vague conversation
•A technique for converting taste into written criteria
•Willingness to disagree with evidence and then commit
•Treats the hiring manager as a partner to manage, not a boss to obey
NOTES
__
Set 4: Technical Screening and Assessment Questions
The set that separates a technical recruiter from a generalist: telling depth from keyword matching, explaining concepts plainly, and designing a take-home that is fair, capped, and scored.
Technical Screening and Assessment Questions
TECHNICAL SCREENING AND ASSESSMENT QUESTIONS
Candidate: __
Company: __
Interviewer: __
WHEN TO USE THIS SET
This is the set that separates a technical recruiter from a generalist
recruiter. You are not testing whether they can code. You are testing whether
they can hold a credible conversation with an engineer, tell depth from
keyword matching, and design a screening step that is fair and job related.
QUESTIONS
1. You are not an engineer. How do you tell a strong engineer from someone who
interviews well?
Why ask it: this is the core skill of the job, stated plainly.
Strong answer: probes ownership and depth. Asks what the candidate personally
built, what broke, what they changed, and what they would do differently.
Follows the answer down one more level than the candidate expected.
Weak answer: says they rely on the technical interviewers entirely.
2. Explain to me, as a non-engineer, what an API is and why our team would care.
Why ask it: a recruiter has to explain your product and roles to candidates
every day. Clarity here predicts outbound quality.
Strong answer: a plain, accurate, short explanation with a concrete example,
delivered without condescension.
Weak answer: jargon, or an apology for not knowing.
3. A candidate lists ten technologies on a resume. How do you find out which
ones they actually know?
Why ask it: resume inflation is the daily reality of technical sourcing.
Strong answer: asks for the one they know best and the one they know least,
then asks for a specific decision they made using it and why.
Weak answer: matches keywords to the requirement and moves on.
4. How would you design a take-home exercise for an engineer at our company?
Why ask it: the recruiter usually owns the design of the screening step, and
a bad one costs you candidates and creates legal exposure.
Strong answer: builds it from the actual work, caps the time and says the cap
out loud, scores it with a written rubric agreed before the first submission,
and applies it identically to every candidate.
Weak answer: an open-ended project with no time cap and no rubric.
5. Any test used to make a hiring decision is a selection procedure. What does
that mean for how we run a coding exercise?
Why ask it: a technical recruiter should already know this. If they do not,
you are the one carrying the risk.
Strong answer: says the exercise must be job related and consistent with
business necessity, administered and scored the same way for everyone, and
that the employer owns validity even when a vendor supplied the test.
Weak answer: has never thought about it.
6. A candidate asks whether we sponsor visas. What do you say?
Why ask it: this question arrives in the first outreach reply, and a wrong or
evasive answer wastes weeks for both sides.
Strong answer: says the honest company position immediately, knows that the
cap-subject route runs on an annual registration cycle rather than on demand,
and flags timing implications before the candidate invests in a loop.
Weak answer: promises to check later, or guesses.
7. What is the shortest screen you can run that still tells you something real?
Why ask it: at a small company the recruiter screen is often the only filter
before an engineer’s time is spent.
Strong answer: 20 to 30 minutes covering motivation, one depth probe, the
band, and timing, with written notes tied to the agreed criteria.
Weak answer: a long unstructured chat with no notes.
WHAT TO LISTEN FOR
•Probes for depth and ownership rather than keyword matching
•Can explain technical concepts plainly without condescension
•Designs assessments from the job, with a time cap and a written rubric
•Knows that a test used for a hiring decision is a selection procedure
NOTES
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Set 5: Closing, Offers, and Candidate Experience Questions
Where small companies lose the most finalists: compensation raised early and lawfully, competing offers tracked, declines mined for the real reason, and the gap before day one owned.
Closing, Offers, and Candidate Experience Questions
CLOSING, OFFERS, AND CANDIDATE EXPERIENCE QUESTIONS
Candidate: __
Company: __
Interviewer: __
WHEN TO USE THIS SET
Sourcing gets you candidates. Closing gets you hires. A small company loses more
engineering finalists at the offer stage than anywhere else, usually to a
competing offer that was never discussed. This set tests whether the candidate
manages the close instead of hoping for it.
QUESTIONS
1. When do you first ask a candidate about compensation, and how do you phrase
it?
Why ask it: discovering an expectation mismatch at the offer stage wastes
everyone’s time, and the phrasing has to respect the law where you hire.
Strong answer: raises the band early, states your range rather than demanding
a number, and knows that asking for salary history is restricted in a growing
number of jurisdictions.
Weak answer: waits until the offer, or leads by asking what they currently
make.
2. How do you find out about competing offers without making the candidate
defensive?
Why ask it: you cannot win a race you do not know you are in.
Strong answer: asks about the whole process early and neutrally, tracks other
companies and expected decision dates, and revisits it at every stage.
Weak answer: waits for the candidate to volunteer it.
3. Talk me through a close you almost lost. What did you actually do?
Why ask it: real closing stories contain specifics that cannot be improvised.
Strong answer: names the competing factor, the person who made the difference,
and the concrete step taken, such as pulling the founder into a call or
restructuring the offer within the band.
Weak answer: a general statement about building relationships.
4. How do you sell a company nobody has heard of against a name candidates
recognize?
Why ask it: this is your permanent competitive position.
Strong answer: leads with scope, ownership, proximity to decisions, and the
specific technical problem, and can articulate who that appeals to and who it
does not.
Weak answer: leads with perks or a culture statement.
5. A candidate declines. What do you do next?
Why ask it: the decline is information, and most recruiters waste it.
Strong answer: asks for the real reason, records it, feeds the pattern back
into the band or the process, and keeps the relationship open for later.
Weak answer: moves on immediately.
6. How do you handle the candidates you reject?
Why ask it: rejected engineers talk to each other, and your reputation in a
small technical community is a hiring asset.
Strong answer: a fast, clear, human response for anyone who spoke to a person,
without inventing feedback that invites argument.
Weak answer: silence, or an automated message weeks later.
7. What happens between the signed offer and the first day?
Why ask it: the gap is where accepted offers quietly fall apart.
Strong answer: stays in contact, gets the paperwork moving immediately, hands
off to onboarding deliberately, and confirms the start date more than once.
Weak answer: considers the job finished at signature.
WHAT TO LISTEN FOR
•Compensation raised early and lawfully
•Actively tracks competing offers rather than waiting
•Sells scope and ownership, not perks
•Owns the gap between signature and first day
NOTES
__
Set 6: Technical Recruiter Scorecard and Red Flags
A seven-area 1-to-5 rubric with space for evidence, a ten-item red-flag checklist, and reference-check prompts. The asset most question lists leave out. Use it with any set above.
Technical Recruiter Scorecard and Red Flags
TECHNICAL RECRUITER INTERVIEW SCORECARD
Candidate: __
Company: __
Interviewer: __
Date: _
HOW TO SCORE
Fill this in immediately after the interview, while the answers are fresh. Rate
each area from 1 to 5 and write the evidence, meaning the thing the candidate
actually said. If more than one person interviews, each scores alone before the
group talks. Compare written evidence first, opinions second.
Multiple real channels, a personal message, honest response rates
Technical literacy ___ _
Explains concepts plainly, probes depth, does not match keywords
Hiring manager partnership ___ _
Real intake checklist, disagrees with evidence, converts taste to criteria
Screening and assessment design ___ _
Builds from the job, caps the time, scores with an agreed rubric
Closing and candidate experience ___ _
Raises the band early, tracks competing offers, owns the pre-start gap
Metrics and self-diagnosis ___ _
Carries rough funnel ratios, names a failure, says what they changed
Communication and written notes ___ _
Screening notes a busy manager can act on in ten minutes
TOTAL: ____ / 35
RECOMMENDATION: [ ] Hire [ ] Second interview [ ] No
RED FLAGS
[ ] Cannot describe a single search end to end with real numbers
[ ] Blames hiring managers, budget, or the market for every failure
[ ] Treats an over-specified requirement as fixed and starts posting
[ ] Only works inbound applicants and calls it sourcing
[ ] Outreach is a template with a merge field and a perks list
[ ] Waits until the offer stage to discuss compensation
[ ] Has never thought about a coding test as a selection procedure
[ ] Promises specific hire counts by a specific date on no information
[ ] Speaks about candidates as inventory rather than people
[ ] Cannot name one thing they would need from you to succeed
REFERENCE CHECK PROMPTS
•Which roles did they fill for you, and at what level?
•What did they change about a search that was not working?
•How did they handle disagreement with a hiring manager?
•Would you hire them again for a search you had to fill yourself?
NOTES
__
__
Testing Technical Literacy Without Being an Engineer
You test technical literacy by asking the recruiter to explain and to distinguish, not by quizzing them on syntax. A recruiter who can explain a concept plainly can write outreach engineers respond to, and a recruiter who reasons about scope can tell two similar-sounding roles apart. Neither requires you to know the answer.
Ask
What a strong answer includes
What a weak answer looks like
Explain what an API is and why our team would care
Plain, short, concrete example, no condescension
Jargon, or an apology for not being technical
Back-end versus platform engineer at our size
Says the line moves by company, asks about your stack first
A recited definition, or claims the titles are the same
A resume lists ten technologies. Which does the candidate know?
Asks for the best and worst, then a specific decision made with it
Matches keywords to the requirement and moves on
How do you judge an engineer without judging the code?
Probes ownership: what was built, what broke, what changed
Defers all judgment to the interview loop
Design a take-home for a role at our company
Built from the real work, time capped, rubric agreed in advance
An open-ended project with no cap and no scoring
The follow-up matters more than the question. When a candidate gives you an answer you cannot evaluate, ask them to say it again for someone who has never worked in software. Recruiters who genuinely understand a role can compress it. The ones who are repeating what an engineer told them cannot, and the second attempt exposes it quickly.
The Compliance Knowledge You Are Buying
A technical recruiter designs screening steps and answers legal-adjacent questions on your behalf, so their compliance knowledge becomes your exposure. Two areas come up constantly in engineering searches: assessments and sponsorship. Ask about both directly, because the wrong answer is expensive and you will not see it coming.
Know the answer before the question arrives
Ask the candidate what they would say to an engineer who asks about sponsorship. A technical recruiter should be able to state your company position in one sentence, immediately, without promising to check.
Timing, not just yes or no
The cap-subject route runs on an annual registration cycle rather than on demand, so a yes can still mean a long wait. A strong candidate raises that timing before anyone invests in a loop.
Tests are selection procedures
Any exercise used to make a hiring decision has to be job related and applied the same way to everyone, and the employer owns validity even when a vendor supplied the test.
Pay questions have rules too
Asking for salary history is restricted in a growing number of states and cities, and posting requirements differ by jurisdiction. A recruiter who does not know this creates exposure you carry.
A Coding Exercise Is a Selection Procedure
Any test used to make an employment decision, including a take-home or a live coding session, is a selection procedure that must be job related and consistent with business necessity. The Equal Employment Opportunity Commission sets out the framework in its guidance on employment tests and selection procedures, which explains that the Uniform Guidelines on Employee Selection Procedures describe recognized ways to show a test is job related, and that responsibility for validity sits with the employer rather than with whoever supplied the test. If your recruiter has never considered this, the risk is yours, not theirs. This is general information, not legal advice.
Sponsorship deserves the same directness. Ask what they would tell an engineer who asks whether you sponsor, and listen for whether they mention timing rather than only a yes or a no. The cap-subject route is annual and numerically limited: USCIS puts the regular cap at 65,000 with an additional 20,000 reserved for holders of a US master’s degree or higher.
A recruiter who knows that will not let a candidate spend three weeks in your loop on a timeline that cannot work. One who does not know it will promise to check, and by the time the answer arrives the candidate has taken another offer. The same applies to salary history questions, which are restricted in a growing number of jurisdictions.
What a Strong Answer Sounds Like
Strong answers contain friction. A real search has a stall point, a wrong assumption, a specific week when something changed, and rough numbers the candidate remembers because they lived them. Rehearsed answers are smooth and general. That contrast is the single most useful signal in this interview.
Walk me through the last engineering role you filled, from intake to signed offer.
Strong answer: Names the role and the level, describes what came out of the intake conversation, says which channels produced candidates, gives rough numbers at each stage, and identifies the point where the search stalled and what they changed. Ends with an outcome and a date. The specificity is the signal: a lived search has friction in it.
Weak answer: A clean, frictionless process description with no numbers, no stall point, and no decision the candidate personally made. Real searches are never that tidy.
You are not an engineer. How do you tell a strong engineer from someone who interviews well?
Strong answer: Describes probing ownership and depth rather than checking technologies: what did you personally build, what broke, what did you change, what would you do differently. A strong candidate says they follow the answer one level deeper than expected and listen for whether the person can explain their own decisions.
Weak answer: Says they leave technical judgment entirely to the engineers in the loop. That is a coordinator, not a technical recruiter, and it means your engineers screen every resume themselves.
A hiring manager rejects your first five candidates but cannot say why.
Strong answer: Stops sourcing rather than sending more. Puts three profiles side by side and asks the manager to rank them and explain the ranking, which converts an unstated preference into written criteria everyone can use. Then re-runs the search against the new criteria and confirms with a fresh shortlist.
Weak answer: Sends five more candidates and hopes one lands. This is the most expensive mistake in technical recruiting and it is entirely avoidable.
Notice what the strong answers have in common: a named situation, a decision the candidate personally made, and an outcome they will state out loud including when it was bad. If you get two of the three, keep probing. If you get none across three questions, the interview is telling you something.
What to Probe For (and Red Flags)
The prepared questions open the door; the follow-ups are where you learn. Push for the number, the name, the date, the actual message. A recruiter who has done this work has that detail available; one who has watched it done from nearby does not.
Craft signals
A real search described with friction in it
An outreach message they can show you
Rough funnel ratios carried in their head
Partnership signals
An intake checklist, not a vague chat
Disagrees with evidence, then commits
Converts a manager’s taste into written criteria
Judgment signals
Pushes back on a twelve-item requirement
Raises a band and market mismatch in week one
Asks you questions about stack, level, and budget
Red flags
Promises a hire count with no information
Only works inbound applicants
Talks about candidates as inventory
The most useful single follow-up is some version of what happened next. It works on every answer, it cannot be prepared for, and it separates a candidate describing their own experience from one describing a process they observed. Ask it three or four times in an interview and the pattern becomes obvious.
Scoring the Interview
Score every candidate on the same rubric immediately after the interview, while the answers are still exact. Rate the same seven areas for everyone and write down the evidence, meaning the thing the candidate actually said, so you compare on record rather than on whichever conversation felt best. Use a standard evaluation form if you prefer a general version.
Scoring area
What a 5 looks like
Sourcing and outbound craft
Several real channels, a personal message, honest response rates
Technical literacy
Explains plainly, probes depth, reasons about scope
Hiring manager partnership
Real intake checklist, converts taste into written criteria
Screening and assessment design
Built from the job, time capped, rubric agreed in advance
Closing and candidate experience
Band raised early, competing offers tracked, pre-start gap owned
Metrics and self-diagnosis
Carries funnel ratios, names a failure, says what changed
Communication and written notes
Screening notes a busy manager can act on in ten minutes
If two people interview, each should score alone before anyone talks. Written scores compared first, opinions second. That habit is the core of a structured interview, and it feeds a cleaner interview feedback conversation before you decide. Keep the completed scorecards with the candidate record so the decision is reconstructable months later. Applicant tracking is coming soon to FirstHR.
Fair, Legal, and Structured Interviewing
A fair interview and an accurate one are the same interview. Asking every candidate the same job-related questions keeps you compliant, reduces bias, and gives you a comparison you can trust. That matters more than usual here, because recruiters are professionally good at steering a loose conversation.
Ask about the job, not the person
Federal anti-discrimination law prohibits basing a hiring decision on protected characteristics, and a question that probes one creates risk even when it is asked as small talk. Keep every question tied to finding, screening, and closing engineers. The traps in a recruiter interview are the friendly ones: where are you originally from, do you have kids who limit your travel, how old were you when you started recruiting. None of them tell you anything about the work, and all of them create exposure. The question sets on this page are written to stay on the job. This is general information, not legal advice.
Same core questions, every candidate
Asking every candidate the same core questions is fairer and it also produces better hires, because it lets you compare answers rather than impressions. This matters more than usual for a recruiter hire: recruiters interview for a living and are unusually good at steering an unstructured conversation toward their strengths. A fixed question set takes that advantage away and shows you what they can actually do. Write the questions before the first interview, ask them in the same order, and take notes as you go rather than reconstructing afterwards.
Score independently, then discuss
When two or three people interview, have each one fill in the scorecard alone before the group talks. This stops the most senior or most enthusiastic voice from anchoring everyone else, which is how good candidates get talked out of and weak ones get talked into. Compare the written evidence first and the verdicts second. For a founder who is also the hiring manager and the only interviewer, the scorecard still earns its place: it forces you to write down what the candidate actually said before your impression hardens into a decision.
Match the questions to the hires you need
A recruiter who will fill two engineering roles a year at a ten-person company is a different hire from one running a continuous pipeline for a growing platform team. Weight the sets accordingly. If your problem is that nobody applies, lean hard on sourcing and outbound. If your problem is that your engineering lead rejects everyone, lean on intake and partnership. If you keep losing finalists, lean on closing. Decide which of those three describes your last failed search, then weight the interview toward it rather than covering everything evenly.
Structure Beats a Good Conversation
A structured interview, where every candidate answers the same questions scored against a consistent rubric, predicts on-the-job performance more reliably than an unstructured conversation, and asking the same job-related questions of everyone also keeps you within the EEOC rules against basing decisions on protected characteristics. For a recruiter hire the effect is amplified: structure is the only thing that stops a professional interviewee from running your interview for you.
Keep every question tied to finding, screening, and closing engineers, and avoid the friendly traps about age, family, or origin. Browse the rest of the hiring templates if you need the postings and forms that surround this interview. This is general information, not legal advice.
What a Technical Recruiter Costs
There is no separate federal occupation code for technical recruiters, so the closest published benchmark is human resources specialists, the classification that covers recruiting roles. Use it as a floor and adjust upward: engineering searches are harder and the recruiters who run them well are in demand.
Median $75,940 a Year for the Closest Federal Classification
Human resources specialists, the occupation that covers recruiters, reported a median annual wage of $75,940, with the 25th percentile at $58,610, the 75th at $99,380, and the top 10 percent above $128,720, according to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), published at bls.gov. The classification held about 944,300 jobs and is projected to grow faster than average through 2034.
Technical recruiters typically sit in the upper half of that range, and many roles add a bonus tied to hires made or to acceptance rate. Before you set a number, decide the shape of the hire: a full-time in-house recruiter costs salary plus benefits year round, while a contract recruiter bills only while a hiring burst lasts. Compare that against your real recruitment costs today.
Interviewing a Technical Recruiter Without HR
At a large company this candidate runs a panel with a talent leader who has filled the same roles and knows exactly what to probe. At a small company the interviewer is usually the founder or the engineering lead, doing it between everything else. Here is how to make that interview as rigorous as the panel version.
You are hiring someone to do the job you are worst at judging
Most owners hiring a first technical recruiter cannot evaluate recruiting craft, and the candidate in front of them interviews professionally for a living. That combination flatters everyone. The fix is not to become an expert, it is to ask questions whose answers cannot be improvised: describe your last search end to end with numbers, show me an outreach message you actually sent, tell me about a search you failed to fill. Lived experience contains friction, specific dates, and named mistakes. Rehearsed experience is smooth. You do not need to grade recruiting technique to notice the difference between the two.
One recruiter, no talent team, and your engineering lead is shipping
At a large company a technical recruiter sits inside a function that absorbs friction: coordinators book the loops, a manager calibrates the search, and a system tracks the pipeline. At your company the recruiter is the entire function, working with an engineering lead who would rather be writing code. That changes what you interview for. Weight the intake and partnership set heavily, because getting a busy lead to do intake, to explain rejections, and to interview on time is most of the job. A recruiter who has only ever worked inside a machine may not know how to build one.
The recruiter will need a system on day one, and you probably do not have one
A new technical recruiter arrives and asks where the pipeline lives, where the interview notes go, and how offers get signed. At a small company the honest answer is often a spreadsheet and a shared inbox. Decide before the first day: where candidate records live, who writes the screening notes, and how the scorecards get stored with the candidate. FirstHR handles the part that starts once someone accepts, with e-signature for the offer, document management for signed paperwork, and task workflows for access and policy sign-off. FirstHR is an onboarding and HR platform, not an applicant tracking system. Applicant tracking is coming soon to FirstHR.
What you need
In-house recruiter
Contract recruiter
Continuous engineering hiring all year
A burst of hiring with a clear end date
Deep product knowledge built over years
A pipeline that outlives the current search
Cost stops when the hiring stops
The simplest rule: if you expect to keep hiring engineers for the next year and want someone who learns the product deeply, hire in-house and weight the intake and partnership questions. If you have a defined burst of roles and no capacity, a contract recruiter is cheaper and the sourcing set matters most. Either way, run the same core questions.
From Interview to Onboarding
The interview is step one. Once you choose a recruiter, the work shifts to getting them productive fast, which for this role means access and a first intake rather than a long ramp. A recruiter blocked on tooling or waiting for the engineering lead spends week one idle, and you will not get that week back. Send a clear offer letter and start the paperwork the same day.
Send the offer and confidentiality agreement
Confirm the role, the compensation, and the start date in writing. A recruiter will see salary bands and candidate data, so a confidentiality agreement belongs in the packet.
Grant access before day one
Job postings, the candidate pipeline, the calendar, and permission to speak for the company. A recruiter blocked on access spends week one waiting instead of sourcing.
Book the first intake in week one
Put the recruiter and the engineering lead in a room early, with a real open role. The first intake is the fastest way to see whether the hire will work.
Store the records
Keep the signed offer, the confidentiality agreement, the I-9, the W-4, and the interview scorecards organized and easy to find later.
FirstHR connects the offer, the confidentiality agreement, e-signatures, the new-hire paperwork, and the access checklist in one place, and stores the signed documents on the employee profile, so a company without an HR department can onboard a recruiter from one system. Pair it with an onboarding template for the first week. FirstHR is an onboarding and HR platform, not an applicant tracking system, so connect that separately. Applicant tracking is coming soon to FirstHR.
Key Takeaways
Interview a technical recruiter on sourcing craft, technical literacy, hiring manager partnership, screening design, and closing.
Force specifics: the last search end to end with numbers, a real outreach message, and a search they failed to fill.
Technical literacy means explaining plainly and reasoning about scope, not writing code or reciting definitions.
Weight the sets by where your last search broke: nobody applied, the lead rejected everyone, or you lost the finalist.
Ask directly about assessments and sponsorship, because the recruiter’s compliance knowledge becomes your exposure.
Score seven areas 1 to 5 immediately after the interview with written evidence, and compare records before opinions.
Frequently Asked Questions
What questions should I ask a technical recruiter in an interview?
Ask questions that force specifics rather than philosophy. The five that reveal the most are: walk me through the last engineering role you filled from intake to signed offer; where do you find engineers who are not applying to jobs; a hiring manager rejects your first five candidates but cannot say why, what do you do; you are not an engineer, so how do you tell a strong engineer from someone who interviews well; and tell me about a search you failed to fill. Each of these is hard to answer well without having lived it, because a real search contains friction, rough numbers, and a named mistake. Add a question about how they design a take-home exercise, since the recruiter usually owns that step and a badly built one creates legal exposure. This page includes six ready-to-use sets and a scorecard.
Do I need to be technical to interview a technical recruiter?
No. You need to recognize a specific answer from a rehearsed one, which does not require an engineering background. Every question in these sets comes with a note on what a strong answer sounds like, so you can judge without grading recruiting technique yourself. The pattern is consistent: strong answers name the role and the level, give rough numbers at each stage of the funnel, identify the point where a search stalled, and own at least one mistake. Weak answers are smooth, general, and frictionless. It helps to bring your engineering lead into one round to test whether the recruiter can hold a credible conversation about your stack, but the judgment questions about intake, pushback, and closing are ones an owner can run alone.
What is the difference between a technical recruiter and a sourcer?
A sourcer finds and contacts candidates; a technical recruiter owns the search end to end. The sourcer builds the top of the funnel through outbound research and outreach and usually hands warm candidates to someone else. A full-cycle technical recruiter runs intake with the hiring manager, sources, screens for depth, manages the interview loop and the debrief, and closes the offer. At a small company you almost always want the full-cycle version, because there is nobody else to pick up the middle and the end. If you split the role, be explicit about who owns the close, since that is where a small company loses the most finalists. Interview a sourcer mainly on the sourcing and outbound set, and a full-cycle recruiter on all six.
How do I test whether a technical recruiter actually understands engineering roles?
Ask them to explain a technical concept to you in plain language, then ask them to distinguish two roles that sound similar. A good pair is: explain what an API is and why our team would care, and what is the difference between a back-end engineer and a platform engineer at a company our size. You are not checking for a textbook answer. You are checking whether they can reason about scope, whether they know the line moves by company, and whether they ask about your stack before answering in detail. Follow with a resume-depth question: a candidate lists ten technologies, how do you find out which ones they actually know. A strong recruiter asks for the one the candidate knows best and least, then asks for a specific decision they made with it. Keyword matching is the weak answer.
What are the red flags in a technical recruiter interview?
The clearest red flag is a candidate who cannot describe a single search end to end with real numbers. Others worth weighting heavily: blaming hiring managers, budget, or the market for every failure without owning anything; treating an over-specified twelve-item requirement as fixed and starting to post; working only inbound applicants and calling it sourcing; outreach that is a template with a merge field and a list of perks; waiting until the offer stage to discuss compensation; and promising a specific hire count by a specific date before knowing anything about your band or your loop. Talking about candidates as inventory rather than people matters too, because your reputation in a small technical community is itself a hiring asset. The downloadable scorecard on this page includes the full red-flag checklist.
Should I hire an in-house technical recruiter, a contract recruiter, or an agency?
It depends on how many engineering roles you expect to fill and how long the need lasts. An in-house recruiter makes sense when you have continuous hiring, usually several engineering roles a year, and want someone who learns your product deeply and builds a pipeline that outlives any single search. A contract recruiter fits a burst of hiring with a clear end date, and costs nothing once the burst is over. An agency shifts the risk to a contingent or retained fee per hire and suits a company filling one or two roles with no internal capacity at all. Whichever you choose, the interview questions are largely the same, but weight the sourcing set more heavily for a contract or agency recruiter and the intake and partnership set more heavily for an in-house hire who has to build the relationship over years.
How much does a technical recruiter cost?
Pay varies by market, seniority, and whether the role is in-house or contract. There is no separate federal occupation code for technical recruiters, so the closest benchmark is human resources specialists, the classification that covers recruiting roles. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), that occupation reported a median annual wage of $75,940, with the 25th percentile at $58,610 and the 75th at $99,380, and the top 10 percent above $128,720. Technical recruiters typically sit above the median for the classification because engineering searches are harder and the market for them is competitive. Contract recruiters bill hourly or monthly and cost nothing once a hiring burst ends, while agencies charge a percentage of first-year salary per hire. Benchmark to your local market and the scope you need.
What questions are illegal to ask a technical recruiter candidate?
Avoid anything that probes a characteristic protected under federal law, which the EEOC enforces: age, race, color, religion, national origin, sex, pregnancy or family plans, disability, or genetic information. In a recruiter interview the traps tend to be friendly rather than hostile, such as asking where someone is originally from, whether they have children who limit travel, or how old they were when they started recruiting. You may ask whether the candidate can perform the essential functions of the job and whether they are legally authorized to work. Note also that asking a candidate for their salary history is restricted in a growing number of states and cities, a rule that applies to your interview as much as to the ones the recruiter will run. Keep every question tied to finding, screening, and closing engineers. This is general information, not legal advice.
