How to Pass the Recruiter Screen With 60 to 90 Second Answers

The recruiter screen is not a test of depth. It is a test of fit, clarity and logistics, and short, focused answers win it. The process is seven steps: build a 60 to 90 second answer frame, write your "tell me about yourself", prepare "why this company", deflect salary expectations, answer logistics in one sentence, ask two or three useful questions, and rehearse with a timer. With three or four evenings of prep you can walk into a 30 minute call with every common question answered in under 90 seconds. This guide is for engineers who ramble, over-explain or get caught off guard by the compensation question. It is not a guide to technical phone screens.

What you need before you start

• The job posting, including any published pay range.
• Your resume, open next to you during the call.
• Two or three facts about the company's product, engineering blog or recent launches.
• A target compensation number and a walk-away number, researched in advance (see our salary negotiation data).
• A timer and a way to record yourself.

Step 1: Build a 60 to 90 second answer frame

Use the same three-part shape for almost every recruiter question: a one-sentence headline, one or two pieces of proof, and a bridge back to the role. Then stop talking.

Why it matters: conversational English runs at about 164 words per minute in a large University of Pennsylvania study of telephone conversations. That puts a 60 to 90 second answer at roughly 165 to 250 words, which is about one short paragraph. Anything longer and the recruiter stops taking notes.

Example: "I am a backend engineer focused on payments reliability (headline). At my current company I own the retry and idempotency layer for checkout, and last year I led the migration to a new payment provider (proof). That is why this platform role caught my eye (bridge)."

Common mistake: answering the question, then answering it again in different words.

Step 2: Write a "tell me about yourself" in present, past, future order

Open with what you do now, add one or two past highlights that support it, and close with what you want next and why this role fits. Keep it inside the frame from Step 1.

Why it matters: recruiters move fast. Ladders' eye-tracking research found that recruiters skim a resume for an average of 7.4 seconds on the initial screen. Your spoken opener gets the same quick judgment, so the headline has to land in the first sentence, not the fourth.

Example (before): "So, I studied computer science, then I did an internship, then my first job was at a small startup, where we did a lot of things..."

Example (after): "I am a senior backend engineer at a fintech company, where I own the services that process card payments. Before that I spent three years on data pipelines, which is why I care about correctness at scale. I am now looking for a platform role with more ownership of reliability, which is exactly what this posting describes."

Common mistake: starting from university and walking forward chronologically.

Step 3: Prepare a specific answer to "Why this company?"

Name two concrete reasons: one about the product or engineering work, one about how it matches your experience or goals. Use something you could only say about this company.

Why it matters: Amazon's official interview guide tells candidates to research the role and team thoroughly using job listings, company blog posts and official career resources. Generic praise ("great culture, big impact") signals you did not.

Example: "Two reasons. Your engineering blog post on moving search to a new indexing pipeline is the kind of migration I have done twice, and this team owns that system. And the role is on-call for customer-facing services, which is where I do my best work."

Common mistake: giving reasons that apply equally to every big tech company.

Step 4: Deflect the salary expectations question, then give a researched range if pressed

First, redirect politely and ask for the band. If the recruiter insists, give a researched range anchored on total compensation, not a single number.

Why it matters: in California, employers may not seek your salary history, but the same law explicitly allows them to ask about your salary expectations (Labor Code 432.3). So expect the question, and know your rights about history. Rules differ by location, so check yours.

Example deflection: "I would rather understand the full scope and level first. Could you share the band for this role?"

Example if pressed: "Based on my research for this level and location, I am targeting total compensation in the range of X to Y, and I am flexible on how it is split between base and equity."

Common mistake: volunteering your current salary or naming a number before you know the level.

Step 5: Answer logistics questions in one sentence each

Have short, honest answers ready for work authorization, location or remote preference, notice period, start date and whether you are interviewing elsewhere.

Why it matters: Amazon describes its initial screen as a 30- to 45-minute discussion with a recruiter or hiring manager who assesses basic qualifications and potential fit, including compensation expectations. Every minute you spend on logistics is a minute not spent on your strengths.

Example: "Yes, I am authorized to work in the US without sponsorship. My notice period is three weeks. I am in final rounds with one other company, so a timeline in the next month would work well."

Common mistake: hiding other offers. A competing process is useful information for the recruiter, not a threat.

Step 6: Ask two or three questions that help you prepare

Use your questions to learn the interview format, the level and the team, so you can prepare for the next rounds.

Why it matters: Amazon's guide advises candidates to come prepared with thoughtful questions about the role, team and growth. In California, employers must also provide the pay scale for a position on reasonable request, so asking for the band is normal.

Example questions:

• "What do the next rounds look like: how many, which types, and is there a system design round at this level?"
• "What level is this role scoped at, and what is the band?"
• "What is the biggest problem this team needs the new hire to solve in the first six months?"

Common mistake: asking about things that are already on the careers page.

Step 7: Rehearse every answer out loud with a timer

Record yourself answering the five core questions (tell me about yourself, why this company, why are you leaving, salary expectations, your questions). Cut anything that runs past 90 seconds.

Why it matters: practicing retrieval beats rereading notes. In Roediger and Karpicke's 2006 study, students who were tested recalled 56% of a passage one week later, against 42% for students who restudied.

Example: run one "why are you leaving" answer three times. First run 2 minutes 40 seconds with a complaint about your manager; third run 70 seconds: "I have grown a lot on this team, and I want broader ownership of platform reliability than my current role offers."

Common mistake: rehearsing silently in your head, where every answer feels short.

How to know it worked

• Every core answer lands between 60 and 90 seconds on the timer, three runs in a row.
• The recruiter asks follow-ups about your experience rather than "sorry, what do you do now?"
• You leave the call knowing the level, the band (or a clear reason it was not shared) and the next rounds.
• You hear back about next steps within the timeline the recruiter gave you at the end of the call.

Troubleshooting

• If you keep running long: write the headline sentence first and say it before anything else.
• If the recruiter will not share a band: give a researched total compensation range and confirm it is negotiable after the onsite.
• If you get a technical question you did not expect: give a short, honest answer and offer to go deeper in the technical rounds.
• If you are asked why you are leaving and the real reason is negative: frame it as what you are moving toward, not what you are escaping.
• If you blank: ask "Can I take five seconds?" and use the headline, proof, bridge frame.

FAQ

How long should answers be in a recruiter screen?

Aim for 60 to 90 seconds per answer, which is roughly 165 to 250 spoken words at a normal conversational pace. That is long enough for a headline and one example, and short enough for the recruiter to note it and move on. Save longer, detailed stories for behavioral rounds.

Should I give a number when asked about salary expectations?

Try to get the band first by asking politely. If the recruiter insists, give a researched range for total compensation at the level and location, not a single number and not your current salary. In California, employers may ask about expectations but may not seek your salary history.

Is the recruiter screen pass or fail?

Yes, in practice. Recruiters check basic qualifications, communication, motivation and logistics such as location and compensation fit. A weak screen can end the process before any technical round, which is why preparing five short answers is worth a few evenings.

What questions should I ask the recruiter?

Ask about the structure of the next rounds, the level and band of the role, and what the team most needs from the new hire. These help you prepare for the technical and behavioral rounds and avoid surprises at the offer stage.

To recap: frame every answer as headline, proof and bridge, then apply it to your intro, "why this company", salary, logistics and your own questions, and rehearse with a timer. Want to practice under real pressure? Book an anonymous mock interview and get a scorecard plus a recording of the session. Then prepare for what comes next with our technical phone screen guide and the behavioral interview guide.