The recruiter call

A recruiter call lasts about twenty minutes and ends in a short form that the hiring manager reads before deciding whether to spend an hour on you. The recruiter is a screener, not the decider, and wants a candidate who passes the filter, has a date to plan around and a pay expectation the budget can carry. You control one thing: whether the form that reaches the manager is accurate, specific and consistent with your resume.

Before you pick up

What the call is for. A filter, not an interview: the recruiter's note covers level fit, pay against budget, notice, location and your other processes. An agency recruiter is paid on placement and needs your figures to submit you against a budget. Either way, make each line something you can document.

What the recruiter sees. Before the call they have what you typed into Naukri, LinkedIn or Instahyre, and your resume; they cannot see payslips, Form 16 or your letter. A company's own checks at the offer stage may set your statements against documents. Open each profile in a private window and compare every field with your letter and latest payslip. A profile that says "30 days" over a letter that says 90 spends your first minute on a correction. Fields: lessons 2 and 3.

Have on the desk: appointment letter, last three payslips, the resume from lesson 3, and each form line written in one sentence from those papers. A line that needs "around" for something your payslip states exactly has not been looked up.

Next stop: The nine questions, and two probes, 6 min

The nine questions, and two probes

The questions come in this order; the two probes can come anywhere. Each has the move (the author's judgement) and what the answer rests on. Samples are invented.

1. Background. Sample (Arjun, invented; eight years, applying for lesson 3's PAY-114, Senior Software Engineer): "I own refunds at a payments company, about 40 merchants. With two engineers I moved them from a nightly batch to Kafka events: refunds that took a day now complete in minutes, and refund-status tickets fell by a third. This role's settlement work is that move at a larger scale." The recruiter's note is one line; a pitch that differs from your resume is what a manager notices.

3. Expectation. If you say "30 per cent hike" the offer is tied to your current pay (the author's reading of how offers are built). Decide two numbers at home: the range you ask, built from the level's band, and a floor that stays private (lesson 2). When a recruiter states a budget under your ask, put one question first: "Is that the top of the band for this level, or this opening's budget?" A band's top moves with level; an opening's budget sometimes has room for a joining bonus or an exception (the author's reading).

Below your floor, ask for the higher loop if your evidence fits it. If not, this is the one time to say the floor: once, aloud, never in writing, because the other way out is ending the process. "[Floor] fixed is the lowest that works at this level. If the manager round goes well, is there room in the band?" No joining-bonus offer on this branch: it covers year one and leaves the base gap.

4. Notice. A recruiter who says "our joining date is fixed at 30 days" may be stating a filter or a preference; nobody found measures how often it moves. Find out which, then give the earliest date you can honestly keep and what it depends on. An HR practitioner's article (ThePeoplesBoard, 13 Jul 2026) says notice length is used as an early filter, sometimes before technical fit; it is one article, not a survey.

10. Rating. Sample (Arjun, invented): "Java, eight years, all of it production. Kafka, three years. On Java I would say 8, where 10 is someone who works on the JVM itself: I wrote the refund service that took refunds from a day to minutes. Kafka, 7: I design topics and consumers and handle replays, but I have not operated the brokers." A rating with a stated scale and limit is hard to catch out, because the limit is already on the table; a bare 9 invites the interviewer to find the gap.

11. Why us. Sample: "Your posting says settlement moves from batch to events next year. I made that move for refunds, and the hard part was replaying events without paying a refund twice; I would like to do it for settlement." If you found no checked fact, say what you read and ask: "Is that this team's work this year?"

Less common questions (scripts are the author's constructs, untested; the brackets take your facts):

Next stop: Pay pushes at SDE-1 and SDE-2, 1 min

Pay pushes at SDE-1 and SDE-2

For: SDE-1, SDE-2.

Three pushes, hardest on a move from a services to a product company (author's estimate, not measured). Scripts are the author's, untested; a hike's worth in hand: lesson 2.

Next stop: Make the recruiter your advocate, 1 min

Make the recruiter your advocate

The manager often reads the recruiter's note before your resume, and a recruiter who expects you to clear the loop argues your case in it: for the level, a later joining date, the top of the band (the author's reading; no source measures it). What moves them is what you hand over and how easy you are to schedule.

What to give them. A summary email within an hour, in lines the recruiter can paste into the note, like Arjun's below. Scheduling replies within the working day with two or three slots. Your other processes with dates, so the recruiter can move your loop up. No surprises: when a fact changes, the recruiter hears it from you first.

  Subject: PAY-114, Arjun: summary of today's call

  Thanks for your time. For the manager's note:
  Now     as stated in my letter; documents at offer stage
  Ask     27 to 29 fixed at SDE-3
  Notice  90 days per letter; early release asked only after
          a written offer
  Level   SDE-3: 8 years; owns refunds for 40 merchants; led
          the batch-to-events move with two engineers
  Why     the posting's plan to move settlement to events
  Other   one final round elsewhere, decision in about 2 weeks
  Slots for the manager round: Tue or Thu, 10:00 to 13:00

Three questions that help you clear the next round. Ask near the end; the recruiter has sat in the debriefs.

1. "What does the hiring manager screen for at this level?" Listen for one or two words (ownership, depth on one system, hiring) and build your walk-through around them.
2. "Where have recent candidates at this level fallen short?" A general answer ("design depth") is your preparation list.
3. "Which round carries the most weight, and is there preparation material?"

Next stop: Senior scripts: level and pay, 2 min

Senior scripts: level and pay

For: SDE-3, Staff, Principal.

At SDE-3 the two questions that matter are which level the loop is for and what you hold in stock. Wordings are the author's constructs, untested. If two of your stories sit in the SDE-3 row of lesson 1's titles table, ask for the SDE-3 loop. How to quote stock (granted, vested, still to vest) and what a vest costs in tax: lesson 2. Ask for the band before you name any figure: "Which level is this, and what are the fixed and stock ranges? I compare four-year totals, not the first year's cash."

The recruiter pushes a lower level. "My last two years were a system across three teams, and I hired three engineers, two since promoted a level. That reads as SDE-3 to me. Can the loop assess SDE-3, with the hiring manager deciding after the first round?" If no: "Then I would take the SDE-2 loop only if the offer states SDE-3 by a date, in writing, or I can see the SDE-2 band and decide." What next depends on what else you hold (the author's reading, untested). With no other process, declining over a level can cost the job: take the loop, ask for level, band and a review date in the offer letter, and decide on the written offer. With a second process live, or a band below what you would accept at any level, declining is affordable. A level fixes the band and the stock grant, and moving up later is harder than starting there.

Next stop: Staff and Principal: the pitch and the search call, 2 min

Staff and Principal: the pitch and the search call

For: Staff, Principal.

Here the first call often comes from a search firm or your network, and the seat may not exist yet (lesson 12). Ask more than you answer; scripts are the author's, untested.

The pitch, at your level's scope: the cross-team problem, the direction you set, what changed in numbers, who did the work; at Principal, the company objective, the bet and its cost, the Staff engineers you grew.

Staff or Senior, at the screen. Ask lesson 12's four recruiter questions here, then: "If the panel is calibrated at Senior, I would rather know now, because a Senior panel cannot produce a Staff decision." If the seat is Senior, decide at home with lesson 12's down-level section before taking the loop.

Ask a search firm, or at Principal anyone, before you share a resume:

A confidential search. If you are visible in your company, say on the first call and again in writing: "My name goes to a client only after I say yes to that client by name. References come once we agree terms in principle, and my current manager is not one until I resign."

Next stop: The hiring-manager screen: Meera at SDE-3, 3 min

The hiring-manager screen: Meera at SDE-3

For: SDE-3, Staff, Principal.

At many companies the next call after the recruiter's is with the hiring manager (30 to 45 minutes, the author's reading), built from your resume, one question per bullet. Meera has ten years but is SDE-3: her scope is one platform, and lesson 1 levels by scope. Her invented plan for 45 minutes: 5 introductions, 3 for her walk-through, 25 follow-ups, 7 on people, 5 for her questions. The walk-through is the one answer she prepares word for word, because every follow-up hangs off it.

On people, expect "a disagreement with a peer" and "a time the brief was unclear". Answer each with one situation and a measure: Meera settled the outbox disagreement with a test that killed the service 1,000 times and lost 3 events, and put relay lag on her peer's dashboard; she turned "make on-call bearable" into pages a month (about 20 to 4) and declined a dashboard rebuild that would not move it. Her two questions: "What would I own in the first six months, and who depends on it?" and "What will the level decision rest on?" If the manager turns technical, run lesson 8's round in miniature: clarify, estimate with a "so", one deep dive (options, a decision, its cost, how it fails), then its four Operate-it lines. A coding warm-up is lesson 6: say the approach before you type.

Next stop: The last 48 hours, 1 min

The last 48 hours

• Every form line written from your papers; profiles match the letter.
• Nine answers said aloud once each with a timer, under a minute apiece; the three you stumble on written down.
• Your range decided at home, and your floor, which stays off every form; the level question rehearsed.
• Three advocate questions chosen; the summary email drafted with blanks.

Pitfalls. A number typed to pass a filter becomes the number on the form. "Negotiable" without a clause that says so. An invented offer.

Practice with an AI: the prompt kit in the appendix has 4 cards for this lesson.

Sources