Interview Drills — Screening & Outreach Role-plays

Open-ended interview questions. Each has a Framework (the structure a strong answer follows), a Model answer (a concise example), and a Rubric (what an interviewer listens for). These are role-plays: in a tech-recruiter interview you'll often be asked to run a screen, probe a vague claim, sell a role, or write/critique an outreach message live. Practice doing the thing, not describing it. The app can role-play these as mock interviews (see mock-interview.md).

The universal recruiter-screen structure: Open warmly & set the agenda → confirm basic fit (experience vs. the role) → understand motivation ("what are you looking for?") → cover logistics (availability, location/remote, work authorization, salary expectations) → sell the opportunity → close with clear next steps. Stay structured and consistent so you compare candidates fairly and bias-free.

D1

difficulty: easy
concept: recruiter-screen Walk me through how you'd run a 30-minute recruiter screen for a mid-level backend engineer. Then role-play your opening two minutes.
Framework: State your goal (assess basic fit, motivation, logistics — not deep technical depth) → list what you'll cover (fit → motivation → logistics incl. salary → sell → next steps) → then deliver a warm opener: introduce yourself and the role in one line, set the agenda and timebox, and hand the floor to the candidate with an open question.
Model answer: "Goal: confirm they roughly match the role, understand what they want, and check logistics — the hiring team tests depth later. I'd cover fit, motivation, logistics including salary, then sell the role and lay out next steps. Opener: 'Hi Maya, thanks for making the time — I'm Dan, a recruiter at Acme. We're hiring backend engineers for our payments team. I've got 30 minutes: I'd love to hear about your work, share more about the role, and answer your questions. To start — tell me a bit about what you're working on now and what's drawing you to look around?'"
Rubric: Strong answers show a clear, repeatable structure, state the screen's real purpose (fundamentals, not deep tech), set an agenda and timebox, and open warmly with an open question that gives the candidate the floor. Weak answers jump straight into rapid-fire questions, blur the screen with a technical interview, or have no structure to compare candidates fairly.

D2

difficulty: medium
concept: behavioral-questions A candidate says, "I led the migration to microservices at my last company." Role-play how you'd probe that claim.
Framework: Acknowledge briefly → ask an open, behavioral follow-up that surfaces their specific role ("walk me through what you personally did") → probe scope and decisions (team size, what they owned vs. the team) → probe outcome and trade-offs ("how did it go, what was hard") → stay neutral and curious, never gotcha. Use the same probing standard for every candidate.
Model answer: "'That sounds like a big effort — walk me through it. What was the situation, and what did you personally own versus the rest of the team?' Then: 'How many services, over what timeframe? What was the hardest call you had to make?' And: 'How did it turn out — anything you'd do differently?' I'm listening for first-person specifics — decisions they made, trade-offs they weighed — not just 'we' statements."
Rubric: Strong answers use open, behavioral follow-ups (situation → their action → result), separate "I" from "we," probe scope and trade-offs, and stay warmly neutral rather than interrogating. Weak answers accept the claim at face value, ask leading yes/no questions, or turn aggressive. Strongest answers note they'd probe every candidate's claims consistently to stay fair.

D3

difficulty: medium
concept: salary-logistics Role-play raising salary expectations with a passive candidate who hasn't brought it up. How do you surface it gracefully — and why early?
Framework: Justify the timing (surface a mismatch now, not after five rounds — respects everyone's time) → frame it as mutual fit, not interrogation → ask about expectations openly and listen → if there's a gap, be honest about the range rather than bluffing → also cover the rest of logistics (availability, location/remote, work authorization) in the same calm spirit.
Model answer: "'Before we go further, I want to make sure the opportunity makes sense for you on the practical side, so we don't both invest time only to hit a mismatch at the end. The band for this role is roughly 150–180K plus equity — does that fit what you're looking for?' If they're above it: 'Totally fair — I'd rather be upfront. Where would you need to land?' I'd treat it as us checking fit together, and I'd also confirm notice period, remote/onsite, and work authorization while we're on logistics."
Rubric: Strong answers explain why early (avoids wasted rounds), frame salary as mutual fit, ask openly and listen, and stay honest about the range instead of fishing or lowballing. Weak answers dodge the topic, treat it as a negotiation to "win," pressure the candidate, or forget the rest of the logistics checklist (availability, location, authorization).

D4

difficulty: medium
concept: selling-the-role "Sell me this role." A strong passive candidate, happy in their current job, has agreed to a quick call. Role-play your pitch.
Framework: Lead with what's in it for them, tied to what you know about them → name 2–3 specific, credible reasons this opportunity beats the status quo (growth, scope, tech, mission, comp, team) → be honest, not hype → invite a low-pressure next step, not a hard sell. Anchor the pitch on their likely motivations, not a generic feature list.
Model answer: "'You've spent four years scaling data pipelines at a big company — what's exciting here is you'd own the data platform end-to-end from an early stage, with real influence on architecture instead of inheriting it. The team's small and senior, comp is competitive with meaningful equity, and the product is used by a few million people, so your work ships and matters fast. I'm not asking you to leave anything — just to have a real conversation and see if it's better than what you've got. Worth a 30-minute chat with the hiring manager?'"
Rubric: Strong answers lead with the candidate's benefit, give specific credible reasons tied to that person's likely motivations, stay honest (no overhyping), and end with a low-pressure ask. Weak answers recite generic company facts ("we're a great culture, fast-growing"), focus on the company's needs over the candidate's, or push too hard. Best answers show they'd tailor the pitch using what they learned about the candidate.

D5

difficulty: medium
concept: outreach-writing Write a cold LinkedIn outreach message to a senior frontend engineer you want for a fintech role. Read it aloud, then explain your choices.
Framework: Personalize the opening with something specific and real about them → who you are + the role in one line → 1–2 reasons it might excite this person (benefit-led) → a clear, low-pressure ask → keep it short and human. Then justify: why personalization, brevity, and benefit-framing drive response rates (vs. ignored spam).
Model answer: "'Hi Sara — I came across your work on the open-source charting library you maintain; the rendering performance is impressive. I'm a recruiter at Lumen, a fintech building consumer investing tools, and we're hiring a senior frontend engineer to lead our charts and data-viz layer — feels close to what you clearly enjoy. You'd own that area end-to-end with a small senior team. No pressure at all — open to a quick chat to compare notes? Either way, nice work on the library.' My choices: a specific, true personal detail proves it's not spam; I lead with what's in it for her (owning data-viz, the thing she's into); it's short and human; and the ask is low-commitment, which lifts reply rates."
Rubric: Strong answers open with a specific, genuine personal detail, state who/role in one line, lead with the candidate's benefit, keep it concise and warm, and end with a low-pressure ask — then explain why each choice helps response rates. Weak answers are generic ("I have an exciting opportunity for a rockstar"), company-centric, too long, or full of corporate jargon. Fabricating fake personalization is a red flag.

D6

difficulty: hard
concept: bias-awareness Critique this outreach/screen note from a teammate, then redo it: "Messaged a guy from a top-3 school, sounds super polished and 'culture-fit', young and hungry — fast-tracking him past the screen." What's wrong, and how would you fix it?
Framework: Name the bias and fairness problems specifically (school prestige, vague "culture fit," age signals, skipping the consistent process) → explain why each is both unfair and bad for hiring (filters out great people, hurts diversity, isn't job-relevant) → redo it grounded in job-relevant criteria and a consistent process → keep the respectful, human tone. Tie back to comparing candidates fairly.
Model answer: "Several issues: 'top-3 school' anchors on prestige, not ability; 'culture fit' is a vague gut feeling that smuggles in bias; 'young and hungry' is an age signal and irrelevant to the job; and fast-tracking past the screen breaks the consistent process we use to compare candidates fairly. Redo: 'Strong match on the role's core skills — 5 years building React data-viz, led the charting rewrite (verified the specifics on the call). Communicates clearly. I'll run him through the same screen as everyone for this role and pass structured notes to the hiring manager.' Same warmth, but anchored on job-relevant evidence and a consistent process."
Rubric: Strong answers spot the specific bias triggers (school, "culture fit," age), explain why they're unfair and bad for hiring, and rewrite around job-relevant skills assessed through a consistent process — without losing respect for the candidate. Weak answers miss the bias, defend "culture fit," or fix the wording without fixing the underlying inconsistency and irrelevant criteria.