# The Recruiter Screen, Transcribed, With What Each Question Scores

*You will hear any recruiter-screen question, name the scorecard field it fills and the pass/fail signal, and answer to that field.*

- Canonical URL: https://www.refolk.ai/candidates/guides/recruiter-screen-transcribed-scorecard
- Pillar: Interviewing
- Format: Teardown
- Published: 2026-08-03
- Last reviewed: 2026-08-03
- Reading time: 17 min

A recruiter screen is a 20 to 30 minute call whose job is to fill a scorecard, not to have a conversation. This guide is for the candidate reading the night before, who wants to hear each question and know the exact field it is quietly populating. Below is one screen carried end to end, with every turn annotated to the scorecard field behind it, so you answer the hidden field instead of the surface words.

## What a recruiter screen actually scores

A recruiter screen scores a small, fixed set of fields, and most of your talk-time lands in none of them. A representative screening scorecard rates only two dimensions: role alignment, and whether your salary preference sits in the right range. At this stage the interview is not assessing specific skills, so skills depth is not a scored field. That single fact reorganizes how you should answer everything.

Broader templates add a few more slots: candidate and role name, a role-fit score on a 1 to 5 or 1 to 10 scale, must-have skills scored individually, relevant experience, evidence pulled from your resume or the call, strengths, gaps or risks, a recommendation, and the next step. A minimal screening record is even leaner: your strongest evidence, the main concern, the recommended next step, and any scheduling or accommodation detail. In an applicant tracking system, the disposition is a coded status. A Phone Screen code in Workday means a screen was conducted, and the notes become part of the recruitment record.

So the fields in play at a screen are role alignment, comp band, the binary knock-outs, motivation and flight-risk, and a routing recommendation. Everything the recruiter asks maps to one of these. The screen exists to surface major deal-breakers - salary mismatch, work authorization, notice period - and to assess enough interest and fit to route you to the hiring manager. Nothing more.

**2 - Fields a documented screening scorecard scores**

Role alignment and salary-in-range; skills depth is not scored at this stage (homerun.co).

The practical consequence: if you answer a screen the way you would answer a technical interview - depth, nuance, edge cases - you are pouring effort into fields that do not exist yet. The winning moves are narrow. Match yourself to the role in plain language, land your comp inside their band, clear every knock-out honestly, and read as genuinely interested. Refolk builds a resume from your own history and scores how well you actually fit a posting before you ever get on the phone, which is the same match read the recruiter is about to make by voice.

## The transcript, turn by turn, with the field each question fills

Here is a single 30-minute screen, annotated. The candidate is a mid-level engineer applying to a growth-stage startup. Read each recruiter turn, then the field it fills and the pass/fail signal behind it.

**Recruiter (0:00):** "Hi, thanks for making the time. This should take about 25 minutes. Is now still good?"
*Field: none yet. This is the agenda-set. Most calls confirm identity and whether now works, then state length and goals. The signal is only that you are present and organized. Answer briefly and let them drive.*

**Recruiter (0:02):** "So tell me a bit about yourself and what you're doing now."
*Field: role alignment and communication. This is not a request for a life story; the recruiter wants a concise career summary that matches the role. Pass looks like current title, one relevant proof point, and why this role, in about 90 seconds. Fail looks like a warm biography that never touches the job. This is the single most predictive moment on the call.*

**Recruiter (0:05):** "Why are you looking to leave your current role?"
*Field: motivation and flight-risk. Pass is a specific, role-tied reason. Fail is "I'm open to opportunities" or "I heard good things about your company," both of which read as no specific reason for applying. The recruiter is quietly asking whether you will stay if hired.*

**Recruiter (0:09):** "Before we go further - what are your salary expectations?"
*Field: comp band. This dropped early, almost offhand, inside the first ten minutes, which is exactly where it usually lands. Its function is a budget filter: it tests whether they can afford you, and it quietly decides how much they will pay you if they can. Pass is a researched range. Fail is a single low number you named first.*

**Recruiter (0:12):** "And are you authorized to work in the US without sponsorship?"
*Field: knock-out. Binary, legal, non-negotiable. Pass is a truthful yes or a truthful no. There is no clever answer here.*

**Recruiter (0:13):** "What's your notice period, and are you able to come into the office two days a week?"
*Field: knock-out or informational. Authorization was a hard filter; notice and location often just help the recruiter organize the pipeline. Answer plainly and give the real date.*

**Recruiter (0:15):** "What questions do you have for me?"
*Field: motivation, scored. Generic questions or "not really" signal you did not prepare, and prep is the interest read that routes you to the hiring manager. Pass is two or three specific questions about the role, team, or process.*

**Recruiter (0:24):** "Great. Next step would be a call with the hiring manager. I'll write you up and we'll be in touch this week."
*Field: recommendation and next step. The recruiter is telling you the disposition path. Confirm the timeline and who owns it.*

#### The screen as a scored sequence

1. **Intro + agenda** - Confirms you are present; nothing scored
2. **Background walkthrough** - Fills role alignment in ~90 seconds
3. **Why leaving** - Fills motivation and flight-risk
4. **Comp + knock-outs** - Fills comp band and binary must-haves
5. **Your questions** - Fills motivation as a scored interest read
6. **Next step** - Sets the advance / hold / decline recommendation

*Each stage of a screen writes to exactly one scorecard field.*

## The comp question is a filter, and it runs before rapport

The salary question is a budget filter applied early, and the number you say sets the ceiling for the rest of the process. A recruiter drops it early, almost offhand, usually in the first ten minutes. That timing is the tell: it lands before rapport because its job is to decide affordability, not to reward a good conversation. A shower-number stated too early caps you before anyone has argued your value.

The most common self-inflicted wound is naming a number first and anchoring low. Candidates shave their number down, deciding it is "probably too much." But you do not know the budget. Let them tell you it is too high, if it even is. Give a researched range instead of a single figure, and base that range on real benchmarking, not a guess.

Here is the part every listicle skips: over-budget is not always a no. It is an escalation trigger. If your expectations are about 20% higher than the top of their budgeted range, a recruiter might be able to advocate for additional budget or up-level you. A published recruiter-and-hiring-manager dialogue shows the recruiter naming the budget and the paygrade cap to the hiring manager as the escalation path. So a lowball band you hear is not necessarily final, and a number of yours that reads "too high" can move budget rather than end the process.

> **Rule:** Do not name the number first
>
> You do not know the budget. Give a researched range and let the recruiter tell you it is too high, because "too high" can trigger advocacy or up-leveling rather than a rejection.

**Answering "what are your salary expectations?"**

```
"Based on the scope of this role and what I'm seeing for similar positions, I'm targeting somewhere in the range of X to Y. I'm flexible depending on the full package and level. What range has this role been budgeted for?"
```

*Swap in your own researched range; keep the range tight and defensible.*

That closing question matters. It hands the range-naming back to the recruiter, which is where you want it. If they name a band below yours, you now know it is potentially a level or band issue that can be escalated, not a dead end.

## Knock-outs are binary, so honesty is the only winning move

Knock-out questions filter on hard, non-negotiable requirements, and answering one dishonestly only defers the rejection. A knock-out filters on must-have criteria: work authorization, required licenses, certifications, availability, location, willingness to travel, minimum experience, or language proficiency. These are best used for hard, binary, non-negotiable requirements - authorization, specific licenses, logistical non-starters.

The strategy here is simple because the field is binary. A dishonest yes may buy you one extra step and then wreck your credibility later. There is no partial credit for a knock-out, and there is real downside for a false one. Answer the binary directly.

Not everything that sounds like a knock-out is one, though. A work-authorization or license question is often a genuine knock-out, while a notice-period or office-location question may simply help the recruiter organize the pipeline. Over-hedging on notice or location treats an informational field like a disqualifier and wastes your credibility on a non-issue. Read the register of the question. Legal and operational requirements are hard; timing and geography usually are not.

| Knock-out category | Usually binary? | How to answer |
|---|---|---|
| Work authorization | Yes | Direct yes or no, no hedging |
| Required license or certification | Yes | Direct; name the credential and status |
| Availability / start date | Sometimes | Give the real date; it may only organize the pipeline |
| Location / office days | Often informational | Answer plainly; do not over-hedge |
| Willingness to travel | Depends on role | State your true limit |

> **Watch out:** A false yes only defers the rejection
>
> Answering a knock-out dishonestly may buy one extra step and then wreck your credibility when it surfaces. There is no clever answer to a binary legal or operational requirement.

## The procedure: answer to the field, not the words

Here is the sequence to run, from before the call to the moment you hang up. It follows the documented screening procedure and maps each move to the field it fills.

#### Answering to the scorecard, step by step

1. **Map the two scored fields before the call** - Know that the scorecard rates only role alignment and salary-in-range, and that knock-outs are confirmed as binary. Be able to name the field behind each likely question before you pick up.
2. **Answer the background walkthrough to role match** - When they say tell me about yourself, give current title, one relevant proof point, and why this role in about 90 seconds, so the recruiter can match your resume to the req without a follow-up.
3. **Give why-leaving a specific, role-tied reason** - Tie your reason for moving to something concrete in this role, not "I'm open to opportunities," which populates motivation as low flight-risk.
4. **Handle comp as a band filter, not a commitment** - Expect comp in the first ten minutes; give a researched range and let them tell you it is too high before you shave it, signaling band-fit without anchoring low.
5. **Answer knock-outs truthfully and briefly** - For authorization, licenses, availability, and location, answer the binary directly, since a false yes only defers the rejection.
6. **Read notice and location as informational** - Treat notice period and office location as pipeline-organizing questions, not automatic disqualifiers, and answer plainly without over-hedging.
7. **Use candidate questions as a scored motivation field** - Ask two or three specific questions about the role, team, or process, because generic questions signal no prep and prep is the interest read that routes you to the hiring manager.
8. **Confirm the next step and its owner** - Before hanging up, ask what happens next and who owns it, since the recruiter forwards your resume plus knock-out, geography, and base-comp bullets to the hiring manager.

Behind this sits an intake step you never see: 30 to 60 minutes before any candidate call, the hiring manager walks the recruiter through expected outcomes, and the recruiter shares high-level knock-out questions and gets feedback. The must-haves, comp band, and knock-outs are agreed there. By the time you are on the phone, the questions are fixed and the fields are already ruled on a form. That is why answering to the field beats answering to the words.

## How much time you get, and why brevity is a scoring choice

A screen typically runs 20 to 30 minutes, and long answers cost you scored fields, not just goodwill. Recruiters run 20- or 30-minute screens across a large batch of candidates to decide who moves forward. That volume is the reason to be tight: the clock is real, and unscored talk crowds out the turns that matter.

Sources disagree on both length and structure, which is worth knowing so you are not thrown by a call that runs differently than you expected.

| Source | Stated screen length | Time for candidate questions |
|---|---|---|
| coursera.org | 20-30 min | "a few" questions at end |
| glitter.io agenda | 30 min | 15 min |
| inspireambitions.com | recruiter 10-15 min | not specified |

One documented 30-minute agenda allocates 5 minutes intro, 15 minutes for your questions, 5 minutes company pitch, and 5 minutes logistics and comp. Another framework buckets the 30 minutes into background, why-this-role, two or three behavioral examples, salary and timeline, and your questions. Different recruiters weight these differently, but the fields are the same. Aim for answers around 45 to 90 seconds each. The single biggest predictor of advancing is articulating a relevant accomplishment in under 90 seconds without rambling.

> Long, wandering answers do not just bore the recruiter; they leave scored fields blank and end the call on a vague maybe.

## Where this goes wrong: seven failure modes

Most screens are lost not to a wrong answer but to answering the wrong field. Each failure below feels like success in the moment, which is what makes it dangerous. The pattern is the same: a surface behavior that reads as competent while a scored field goes unfilled or gets filled against you.

- **Treating "tell me about yourself" as biography.** The false positive is a warm, long life story that feels like connection but never matches the role. Check: did you name current title, one relevant proof point, and why this role in about 90 seconds? If not, the role-alignment field is blank.
- **Naming a salary number first and anchoring low.** The false positive is feeling clear and cooperative while capping yourself. Check: did you give a range and hand the number back, or did you shave yourself down deciding it was "probably too much"? You do not know the budget until they tell you.
- **Answering a knock-out dishonestly.** The false positive is passing one extra step. Check: is every yes true? A dishonest yes buys one step and then wrecks your credibility later.
- **Rambling and losing the call to the clock.** The false positive is "we had a nice chat." Check: were the comp, motivation, and next-step fields all actually filled? Long, wandering answers mean key topics get skipped and the recruiter finishes with a vague maybe.
- **A generic answer to "any questions?"** The false positive is that asking anything counts. Check: were your questions specific to this role and team? "Not really" or generic questions signal you did not prepare, and prep is the scored interest read.
- **Reading a lowball band as final.** The false positive is walking away, or over-anchoring to their number. Check: could this be a level or band issue the recruiter can escalate? The ~20%-over advocacy path exists for exactly this.
- **Assuming notice and location are always disqualifiers.** The false positive is over-hedging on a field that was only informational. Check: was the question legal and operational, or logistical? Notice and location often just organize the pipeline.

#### Honesty and specificity on a knock-out or motivation answer

Horizontal axis runs from Vague to Specific. Vertical axis runs from Dishonest to Honest.

| Quadrant | What it means |
| --- | --- |
| Honest but vague | Reads as unprepared; recruiter finishes with a maybe |
| Honest and specific | Fills the field cleanly; you advance |
| Dishonest and vague | Wastes the turn and risks the record |
| Dishonest but specific | Buys one step, then wrecks credibility later |

*The safe quadrant is honest and specific; everything else costs you a field.*

The through-line: every failure mode is a case of answering the surface words instead of the field. Fix the aim and the answers fix themselves.

## After the call: what gets forwarded, and how to keep the picture current

After the screen, the recruiter converts your answers into a coded disposition and a short evidence bundle sent to the hiring manager. The recommendation is a discrete choice: move forward, hold, reject, or needs hiring-manager review. It must be backed by written evidence, because justifying every rating with written evidence replaces "I just liked this candidate better" with something defensible. What gets forwarded is your resume plus a few bullet points: the recruiter's interpretation of your knock-out responses, your geographic preferences, and the base compensation you require.

That is the whole output of a screen. Three data points and a resume. Knowing this tells you what to optimize: make your knock-out answers unambiguous, make your location and comp preferences clean to write down, and make your one proof point easy to quote in a bullet. Notes are retained as recruitment records, in one documented policy for three years, so the write-up outlives the call.

#### Before you call the screen done

- [ ] I can name the scorecard field behind each question the recruiter is likely to ask.
- [ ] My "tell me about yourself" hits title, one proof point, and why this role in about 90 seconds.
- [ ] My reason for leaving is specific and tied to this role, not "I'm open to opportunities."
- [ ] I have a researched salary range ready and will hand the number back rather than name it low.
- [ ] Every knock-out answer I plan to give is truthful and binary.
- [ ] I have two or three specific questions prepared for the end of the call.
- [ ] I will confirm the next step, the timeline, and who owns it before hanging up.

Recruiter capacity varies enormously by market, which changes how a screen feels. In Refolk's index of professional profiles, there are 20,535 US professionals with a Technical Recruiter title against just 679 in the UK - the US market is roughly 30 times larger.

| Market | "Technical Recruiter" count | Share of US |
|---|---|---|
| United States | 20,535 | 1.00x |
| United Kingdom | 679 | 0.033x |

In Refolk's index there are also 7.9 times more US Technical Recruiter titles than US "Talent Acquisition" titles, at 20,535 against 2,600.

| Title | US count | Ratio to Talent Acquisition |
|---|---|---|
| Technical Recruiter | 20,535 | 7.9x |
| Talent Acquisition | 2,600 | 1.0x |

The practical read: in thinner markets one recruiter runs more reqs, so screens skew shorter and more knock-out-heavy, and your background answer has to land even faster. If you want to see who runs these screens at the companies you are targeting, search Refolk's index directly.

Ask me this: `Senior technical recruiters who run engineering phone screens at growth-stage startups.` - [run the search](https://www.refolk.ai/start?q=Senior%20technical%20recruiters%20who%20run%20engineering%20phone%20screens%20at%20growth-stage%20startups.).

*Returns named recruiters who own the exact screen this guide describes, so you can see who is likely to be on the other end of your call.*

To keep this current for your own search, re-check three moving parts locally. First, comp bands drift, so benchmark your range against fresh data before every screen rather than reusing an old number. Second, the order of the screen varies by recruiter and company, so treat the transcript above as the set of fields, not a fixed script. Third, knock-outs are role-specific; read the posting for licenses, authorization, and location requirements, and prepare a clean binary answer for each. The fields are stable. The values are not.

## Frequently asked questions

### What do recruiters actually write down after a phone screen?

Documented screening scorecards record a small fixed set of fields, not open notes. A representative screen scorecard scores only two dimensions: role alignment and whether your salary preference is in range. Broader templates add a role-fit score, must-have checks, main concern, a recommendation of move forward, hold, reject, or needs hiring-manager review, and the next step. The recruiter then forwards your resume plus bullets covering knock-out interpretation, geography, and base comp required.

### How should I answer salary expectations in a recruiter screen?

Give a researched range rather than a single low number, and expect the question in the first ten minutes. Comp is a budget filter that tests whether they can afford you and quietly decides what they will pay if they can. Candidates often shave their number deciding it is probably too much; you do not know the budget, so let them tell you it is too high, if it even is. A number about 20% over the top of the range can trigger advocacy or up-leveling rather than a rejection.

### What are recruiters really looking for in a phone screen?

They are surfacing major deal-breakers and gauging enough fit to route you to the hiring manager. The deal-breakers are salary mismatch, work authorization, and notice period. The fit read is role alignment plus specific motivation. Skills depth is not scored at this stage, so answering to technical detail wins nothing; the fields to hit are match, band, cleared knock-outs, and genuine interest.

### How long is a recruiter screen and how much time do I get for questions?

Screens commonly run 20 to 30 minutes, though sources disagree and some recruiter screens are 10 to 15. One documented 30-minute agenda allocates 5 minutes intro, 15 minutes candidate questions, 5 minutes company pitch, and 5 minutes logistics and comp. Plan for answers around 45 to 90 seconds each so key fields get scored, and prepare two or three specific questions of your own.

### Is it bad to give my notice period or location if it is not ideal?

Often not. A work-authorization or license question is usually a hard knock-out, but a notice-period or office-location question may simply help the recruiter organize the pipeline. Over-hedging on notice or location treats an informational field like a disqualifier. Answer plainly, and if timing is genuinely awkward, say so and give the real date rather than dodging.

### What happens if my salary number is over their budget?

It is not automatically a no. The documented recruiter procedure is to escalate to the hiring manager for more budget or a level change. A published dialogue shows the recruiter naming the budget and paygrade cap to the hiring manager as the escalation path. As a rule of thumb, if your expectations sit about 20% over the top of the range, a recruiter may be able to advocate for additional budget or up-level you.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/recruiter-screen-transcribed-scorecard*