The technical and IT recruiter interview questions that matter, what each one tests, a worked Boolean exercise, and sample answers.
Most technical recruiter interview questions test three things: whether you can talk to engineers and hiring managers without faking it, whether you can find people who are not applying, and whether you can run a hiring process that holds up when it goes wrong. Generic warm-ups like "tell me about yourself" still come up, but the questions that decide the offer are practical: write a search string, run an intake, explain a metric, handle a candidate who backs out. Below are the twelve worth preparing, grouped by what they test, with sample answers and a one-week plan. They apply equally to IT recruiter and tech sourcer roles.
What the interview usually looks like
Expect some mix of a screen with a talent acquisition lead, a conversation with a hiring manager you would support, and at least one practical task. The practical part is where technical recruiting differs from general recruiting. Versions you may meet include a live sourcing exercise ("find me three senior Go engineers"), a mock intake meeting where an interviewer plays the hiring manager, and writing an outreach message to a real profile. If the job post or the recruiter mentions any of these, practise that one first. Answer the behavioural questions with a specific situation, what you did and the result, and use real numbers from your own desk, not round ones.
Fit and motivation
1. Why technical recruiting, and how is it different from general recruiting?
Testing: whether you understand the job's actual difficulty. A weak answer says "I love tech." A stronger one names the differences that change your day: many engineers are not actively applying, so sourcing and outreach often matter more than job posts; you are judged by hiring managers who will notice if you misread a requirement; and candidates often have several processes running at once, so speed and candour matter.
Sample: "In general recruiting I could fill most roles from applicants. When I moved to engineering roles, almost every hire I made came from outreach, and the hiring managers expected me to know why a backend role and a platform role weren't interchangeable."
2. Which roles have you found hardest to fill, and what did you change?
Testing: diagnosis, not complaint. Name the role, say why it was hard (a small talent pool, a salary below market, a requirement list that described three jobs), and what you changed: the search, the pitch, or the requirements themselves. Close with the result, if it is real.
Technical fluency
You are not expected to code. You are expected not to make mistakes an engineer would notice in the first minute of a call.
3. What's the difference between Java and JavaScript?
Testing: basic vocabulary. A quick vocabulary check like this can come up. Mozilla's MDN reference tells readers not to confuse JavaScript with Java and says the two languages have very different syntax, semantics and use. Give a plain answer (JavaScript is best known as the language of web pages and also runs outside the browser, for example in Node.js; Java is a separate language) and move on. If you don't know an answer, say how you would find out. Bluffing is the only wrong answer.
4. How do you keep up with technology trends?
Testing: whether your sources are real and whether you can read them critically. A good answer names two or three sources and shows you understand their limits. For example, the 2025 Stack Overflow Developer Survey found JavaScript the most-used language among respondents (66%), while GitHub's Octoverse 2025 report says TypeScript overtook both Python and JavaScript in August 2025, counted by monthly contributors on GitHub. GitHub itself notes that other indices use different methods. Explaining why both can be true (one surveys developers, the other counts contributors) shows the judgment hiring managers want when you describe the market.
Sourcing
5. Walk me through a Boolean search for this role.
Testing: method under light pressure. It may be done live, so practise out loud. Say you are asked for a site reliability engineer with Kubernetes and Terraform experience, individual contributor level. A workable LinkedIn string:
("site reliability engineer" OR SRE OR "platform engineer") AND (Kubernetes OR k8s) AND Terraform NOT (manager OR director OR recruiter)Then explain your choices, because the explanation is what is being scored:
- Quotation marks keep job titles as exact phrases.
- Parentheses group the alternatives. LinkedIn's help page says it reads quotes first, then parentheses, then NOT, then AND, then OR, so grouping makes the logic do what you mean.
- AND, OR and NOT must be in capitals on LinkedIn.
- No asterisks. LinkedIn says wildcards are not supported, so a string like
develop*will not catch "developer". If you write one in a live exercise, the interviewer may well notice.
Then say what you would do next: check the first page of results and tighten or loosen the string.
6. Where do you source beyond LinkedIn?
Testing: range, and judgment about how you use other platforms. GitHub is the usual answer, and you can be specific: its user search supports qualifiers such as language: (the language of a user's own repositories), location:, repos: and followers:, so language:go location:berlin repos:>10 is a reasonable starting query. Then show you know the limit. GitHub's Acceptable Use Policies say information from the service, whether scraped or collected through the API, may not be used for spam, including unsolicited emails to users, or for selling personal information to recruiters, headhunters or job boards. Saying that you treat GitHub as a place to understand someone's work, then reach out through a channel they chose to make public, is a more senior answer than "I scrape emails from commits."
7. Write an outreach message to this profile.
Testing: whether engineers would answer you. A weak message is a template: "I came across your impressive profile and think you'd be a great fit for an exciting opportunity." A stronger one is short, specific and honest. An illustrative example:
"Hi Sam, I recruit for the platform team at [company]. Your talk on migrating CI to Kubernetes is close to what this team is doing next year. The role is senior IC, remote in the EU, with a salary range of [range]. Worth a 15-minute call? If the timing is wrong, no reply needed."
It names something real from the profile, says what the job is, includes pay if you are allowed to share it, and makes saying no easy. Mention that you would follow up once, not five times.
Working with hiring managers
8. How do you run an intake meeting?
Testing: whether you set up the search before starting it. Indeed's guidance on intake meetings lists the questions to cover: whether the role is new or a backfill, where it sits in the team, must-have versus nice-to-have skills, the salary range and whether it flexes, how soon the hire is needed, and which interview stages and interviewers are involved. One more question worth adding: "Who on your team today would you hire again for this role, and why?" It turns a vague list of requirements into a profile you can search for.
9. A hiring manager insists on requirements nobody in the market meets. What do you do?
Testing: influence without authority. A good answer brings evidence rather than opinion: the number of profiles your search returns with and without the hardest requirement, the salary range candidates mentioned, and two or three real (anonymised) profiles that come close. Then ask which requirement they would trade. If you have a real example, use it; this is the behavioural version of "tell me about a time you pushed back," covered in our answer guide on defending a decision others opposed.
Process, metrics and judgment
10. Which recruiting metrics do you track?
Testing: whether you know what the numbers mean. Be precise about the two that people mix up. Indeed defines time to fill as the time from the start of the hiring process to an accepted offer, and time to hire as the time from when the selected candidate enters your workflow to their accepting the offer. Time to fill tells the business how long the whole hiring process takes from its start to an accepted offer; time to hire tells you how fast your process moves once you have found the person. Add one or two more you have actually used, such as offer acceptance rate or how many candidates you send per hire, and say what you changed because of them.
11. You're not an engineer. How do you screen technical candidates fairly?
Testing: honesty about your limits and a consistent method. Say what you check (role fit, motivation, salary and timing, the candidate's own description of their work) and what you leave to the technical interview. Then talk about consistency: the US Office of Personnel Management describes structured interviews as using set rules for asking and scoring questions, with the highest level of structure asking every applicant the same predefined questions and scoring answers against benchmarks, and says more structure is associated with higher validity and reliability. Asking every candidate the same screening questions, and writing notes the hiring manager can compare, is the practical version of that. If the team's later technical round uses a format you know, such as a live coding round, say so; our guide to technical round interview questions shows what candidates face there.
12. A candidate backs out a day before their start date. What do you do?
Testing: calm, speed and honesty with the hiring manager. A good answer: call the candidate to understand why (a counteroffer, a personal change, something your process missed), tell the hiring manager the same day, check whether a strong runner-up is still available, and restart the search where needed. Then say what you would change, such as staying in closer touch between offer and start date.
Questions to ask them
- What does the current hiring plan look like for engineering this year, and how many roles would I own?
- How do hiring managers and recruiters split the work on sourcing and screening?
- Which tools does the team use, and is there budget for sourcing tools?
- How is a recruiter's performance measured here?
- What happened with the last role that took much longer than planned?
For more ideas tailored to a specific company, the questions-to-ask generator can help you draft a list.
A one-week preparation plan
- Day 1: Read the job post and write down the three engineering roles you would most likely recruit for. Look up what each one does day to day.
- Day 2: Write and test Boolean strings for those three roles on LinkedIn, following its operator rules. Keep the best one ready to explain.
- Day 3: Run equivalent searches for the same three roles on GitHub user search using its qualifiers, and note what you find that LinkedIn missed.
- Day 4: Prepare two real stories with numbers: a hard-to-fill role and a disagreement with a hiring manager.
- Day 5: Draft an outreach message to one real profile and cut it to under 80 words.
- Day 6: Practise answers out loud, especially questions 5, 8 and 10.
- Day 7: Prepare your questions for them and review the company's engineering blog or careers page.
The first round is often a recruiter screen, so our guide to HR screening interview questions is worth a look too.
To rehearse out loud, Verve AI's Mock Interview has an AI recruiter ask questions one at a time, can use your own saved questions or questions generated from a job description, and gives you a performance report with feedback and scoring afterwards.
Sources
- LinkedIn Boolean search rules (capitalised AND/OR/NOT, quotes, parentheses, precedence, no wildcards): https://www.linkedin.com/help/linkedin/answer/a524335
- GitHub user search qualifiers (language, location, repos, followers): https://docs.github.com/en/search-github/searching-on-github/searching-users
- GitHub Acceptable Use Policies, section 7, information usage restrictions (no spam or unsolicited emails, no selling personal information to recruiters): https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies
- MDN on JavaScript not being Java (different syntax, semantics and use): https://developer.mozilla.org/en-US/docs/Web/JavaScript
- Stack Overflow Developer Survey 2025, most-used languages (JavaScript 66%): https://survey.stackoverflow.co/2025/technology
- GitHub Octoverse 2025, TypeScript overtaking Python and JavaScript by monthly contributors in August 2025, and the note on other indices: https://github.blog/news-insights/octoverse/octoverse-a-new-developer-joins-github-every-second-as-ai-leads-typescript-to-1/
- Indeed on intake meetings and the questions to cover: https://www.indeed.com/hire/c/info/intake-meeting
- Indeed definitions of time to fill and time to hire: https://www.indeed.com/hire/c/info/time-to-fill-vs-time-to-hire
- US OPM on structured interviews (same predefined questions, benchmarks, validity and reliability): https://www.opm.gov/policy-data-oversight/assessment-and-selection/other-assessment-methods/structured-interviews/
- Verve AI Mock Interview features (AI recruiter, custom and job-description questions, scored report): https://docs.vervecopilot.com/features/mock-interview
Ryan, CEO of Verve AI
Interview Questions







