Most recruiter phone screen templates I've seen are really logistics checklists with a friendly opener. They'll confirm someone can work from Denver and wants roughly what you're paying. They fall short when the same thirty minutes decides who a hiring manager sees next, which is what a phone screen is at most Series A to C companies. This piece is for recruiters running screens across several functions at once. You'll get a 25-minute script you can copy, a way to split pass/fail questions from the ones that actually tell candidates apart, variants for sales, customer success, product, ops and engineering, and a scorecard that holds up in a debrief.
A disclosure before the template, since it colors everything below. Skillvee is a 60-minute "day at work" simulation that replaces the recruiter phone screen and the first interview round. The candidate solves a real challenge, talks to AI teammates to get the information they need, and defends their decisions on a call, while the screen is recorded. It measures how someone works: communication, collaboration, agency, AI leverage, problem solving, quality of output and time management. So I think the phone screen does less than people want from it. I still think you should run a good one until you've replaced it, and this is the version I'd run.
The recruiter phone screen template (copy and paste)
Fill the brackets once per role, with the hiring manager, before the first call. The times add up to 25 minutes.
RECRUITER PHONE SCREEN: [Role title], [Team]
Candidate: [Name] Date: [Date] Screener: [Your name]
0:00-2:00 OPEN
"Thanks for making time, [Name]. Plan for the next 25 minutes: I'll
share a bit about the role, ask about your experience, cover a few
practical things, and leave time for your questions. Sound good?"
Role in one line: "[Role] owns [main outcome] and works most with
[teams]. The hard part of the job is [honest hard part]."
2:00-7:00 KNOCKOUTS (pass/fail, not scored)
K1 Location / remote: "The role is [remote in X / hybrid in Y].
Does that work?"
K2 Authorization: "Are you legally authorized to work in [country]?"
If you can't sponsor: "Will you now or in the future require
visa sponsorship?" Ask every candidate for the role the same way.
K3 Compensation: "The range for this role is [range]. Is that in
line with what you're looking for?"
K4 Timing: "If this moved forward, when could you start?"
K5 Role must-have: [one hard requirement, e.g. "comfortable owning
a quota" / "has run renewals for accounts over $X"]
7:00-19:00 SIGNAL (scored 1-4, quote the answer)
S1 "Walk me through the last time you [core task of the role], step
by step. What did you do first?"
S2 "What happened that you didn't expect, and what did you do?"
S3 [Role-specific question from the variants table]
S4 "What would you do differently if you did it again?"
Probe any vague answer: "Can you give me a second example?"
19:00-23:00 CANDIDATE QUESTIONS
Note what they ask. It's signal too.
23:00-25:00 CLOSE
"Next step is [step] with [person], and you'll hear from me by [date]."
SCORECARD
K1-K5: pass / fail / follow up
S1-S4: 1-4 each, with a quote
Recommendation: advance / hold / decline, plus one sentence why
The opener names the hard part of the job, because candidates who hear it and lean in are telling you something. And S1 through S4 all ask about a real past event, never a hypothetical, because "what would you do if" invites the answer the candidate thinks you want.
Knockout questions vs signal questions
Most templates mix logistics and substance in one list, give everything a score, and end up with a candidate who scored 3.2 because they're in the right timezone.
Knockout questions are gates. Can this person legally take the job, in the place it's done, for money you can pay, on a timeline that works, with the one requirement the hiring manager won't bend on? Each one is yes, no, or "follow up." None of them should ever be averaged into anything.
Signal questions are the evidence. They're the only part of the call that tells two qualified candidates apart, and they get a score, but only with a quote attached.
| Knockout lane | Signal lane | |
|---|---|---|
| Purpose | Rule out candidates who can't take the job | Compare candidates who can |
| Examples | Location, authorization, comp range, start date, one hard must-have | Past-event walkthroughs, the surprise, the do-over, one role-specific question |
| Recorded as | Pass / fail / follow up | 1-4 score plus the candidate's words |
| Time | About 5 minutes | About 12 minutes |
| Fails when | It's skipped and a late-stage offer dies on comp | It's scored from memory an hour later |
Run the knockouts early. If the range is off by forty percent, you both want to know at minute four, not minute twenty-four.
Phone screen questions to ask candidates, by role
S1, S2 and S4 stay the same for every role, which is useful when you carry a mixed req list: your notes stay comparable across functions. S3 is where the role shows up. Here's what I'd put there for the roles I see most often on a Series A to C req list.
| Role | S3 question | A strong answer includes | Red flag |
|---|---|---|---|
| Account executive | "Tell me about a deal you lost that you thought you'd win. When did you find out, and what had you missed?" | A specific moment in discovery they'd run differently | The buyer, the product or pricing is the whole story |
| SDR | "Walk me through how you researched the last account you booked a meeting with." | A named source and why that account, then the angle they used | "I use a template and personalize the first line" |
| Customer success manager | "Tell me about an account you thought was healthy that turned out not to be. What was the first sign you missed?" | A usage or stakeholder signal, and what they now check for | Churn blamed entirely on the product |
| Product manager | "Tell me about a feature you cut or delayed. Who disagreed, and how did it land?" | The trade-off, who they talked to, what the evidence was | A decision with no one on the other side of it |
| Operations / bizops | "Tell me about a process you fixed. How did you know it was broken, and how did you know the fix worked?" | A before and after they measured | "Everyone was happier" |
| Engineer | "Tell me about the last bug that took you longer than it should have. What finally found it?" | The dead ends, in order | A clean story with no dead ends |
Every one of them asks for a real event with a turn in it. A candidate who has done the work can tell you where it went sideways. A candidate who has read about the work can tell you what's supposed to happen.
If the role doesn't fit a row, swap one of these in for S3. They follow the same rule: a real past event with a turn in it.
- "Tell me about a week in your last job that went badly. What happened, and what did you do?"
- "Tell me about feedback that changed how you work. What did you do differently afterward?"
- "Tell me about a time someone depended on you and you couldn't deliver on time. What did you tell them?"
Two motivation questions are worth asking too, in the close, if there's time. Don't score them, just note the answer: "Why are you looking now?" and "What would make you stay where you are?" They tell you whether this is a real move, which matters for the offer stage more than for the shortlist.
If you hire sellers, the sales hiring assessment tools piece goes further on what to watch once you're past the screen.
The phone screen scorecard: a 1-4 scale
A four-point scale works better than five here. It takes away the middle, so the screener has to decide whether an answer was more strong than weak.
| Score | What it means | What you wrote down |
|---|---|---|
| 4 | Specific, first-person, with a turn in it and a lesson they've applied since | A quote with a detail you couldn't have guessed |
| 3 | Specific and first-person, but tidy. No real surprise, or no lesson | A quote with a concrete detail |
| 2 | Mostly general. The "we" does the work, the example is thin | A quote that could fit many jobs |
| 1 | Hypothetical, off-topic, or no example after the probe | What they said instead of an example |
No score without a quote. Write the candidate's actual words next to each number, during the call or straight after it. When the hiring manager asks why someone got a 2, "she said 'we generally try to be proactive with at-risk accounts' and couldn't name one" is an answer. "I didn't get a great sense of her" isn't one, and it tends to track how much the candidate sounded like the person screening them.
When the answer sounds rehearsed or read off a screen
Some candidates on phone and video screens are reading, and none of the templates I've found deal with it. Sometimes it's notes, sometimes an AI tool generating answers in a second window, and you usually can't tell which.
I'd stop trying to tell. I've written about why spotting AI in interview answers misfires on good candidates, and the short version is that the usual tells (polish, pauses, a certain structure) also describe nervous people and well-prepared ones. Accusing someone on a phone screen is a bad trade.
What works better is the second-example probe. When an answer sounds smooth and general, ask for another one: "That's helpful. Can you give me a different example, from a different company?" Then go one level down: "What was the name of the tool? Who pushed back? What did the first version look like?" Rehearsed answers are built one layer deep. Lived experience goes down as far as you want to dig, and it gets messier as you go, with wrong turns and names and the thing they'd still change. Nobody gets accused of anything. You asked for the evidence the scorecard needs, and some answers can't supply it.
Calibrate with the hiring manager before the first call
Any phone screen template for recruiters has brackets, and they're the part that matters. Fifteen minutes with the hiring manager per role, before any screen, saves you the most common failure: a candidate you advanced on your read who the manager rejects on theirs.
Fill in four things together:
- The honest hard part of the job, in one sentence, for the opener.
- The one hard must-have for K5. Only one. If the manager gives you five, ask which one they'd actually reject a great candidate over.
- The S3 question, and what a 4 sounds like, in a sentence you could repeat to a colleague.
- What gets someone to the next round. For example, pass all knockouts and average 3 or better on S1 to S4 with no 1s.
Write it at the top of the template and keep it. With six open roles across four functions this becomes a small library, and after a quarter you can see which managers' criteria held up by the offer stage. If you'd rather do it inside a full intake, the hiring manager intake meeting template folds these four into a 30-minute agenda.
What not to ask on a phone screen
Keep off anything about age, family plans or childcare, religion, national origin, disability, marital status, or health. Don't ask about arrests or convictions either. Many states and cities have fair-chance laws that delay the question, in a lot of places until after a conditional offer, so the phone screen is the wrong moment for it. Ask "Are you authorized to work in [country]?" rather than about citizenship or where someone is from. Many US states and cities now bar employers from asking about salary history, so ask about the range they're targeting and state yours first. Your legal team or employment counsel has the final word for your locations, and it's worth a five-minute check the first time you screen in a new state.
The job-related version of a bad question almost always exists. "Can you work some evenings during quarter end?" is fine. "Do you have kids?" isn't, even if it's the same concern underneath.
What a phone screen can't tell you
My bias, again: a phone screen measures how well someone talks about their work. For some roles that tracks the work. For many it doesn't, and the gap has widened now that a fluent answer is one prompt away.
What the screen never shows is the candidate doing anything. You don't see how a CSM handles an account when the renewal risk is buried in a stakeholder's offhand comment, or how a PM decides when two people want opposite things. You hear their account of it. That's why the work sample test examples piece argues the useful test is whether the candidate has to go and get missing information, which is something a conversation about past work can't observe.
Skillvee replaces the screen and the first round with an hour in which the candidate does a slice of the job and you watch it. If you'd rather keep the phone screen and add a work sample after it, that's a reasonable choice too, and the scorecard above gives you a cleaner shortlist to hand to it.
Where this gets hard
The quote rule is slower. Writing down what someone said, not just a number, adds a few minutes per screen, and it's the first thing people drop in a heavy week. I'd keep it anyway, because it's the part that makes the scorecard worth anything in a debrief.
The hiring manager calibration also gets skipped under pressure. A req opens, the manager is busy, and you screen off the job description. You'll get through the first batch, then discover the manager wanted something the job description didn't say.
And a structured screen feels colder to some candidates. The opener helps. So does saying up front that you ask everyone the same questions so they're compared fairly. In my experience most people take that well.
If you want to see what replacing the screen would look like across your req list, the pricing page lists the plans.