On a first call with a recruiter, ask about five things: the interview process and timeline, the level you are being considered for, the pay range for that level, how team placement works, and the in-office or remote policy. Get their salary range before you offer a number of your own, because the employer knows its pay bands far better than you do. And pay attention to how the recruiter answers: vague replies about pay, process or why the role is open are the earliest red flags you will get.
The recruiter screen is not a technical round. Recruiters are mostly checking fit — your background, what you want next, your timing and your expectations — and they usually handle the logistics and compensation side of the process. That makes this the one conversation where direct questions about money, level and location are expected rather than awkward. This guide gives you the questions, word-for-word scripts for the salary conversation, and a simple order for running the call.
What the recruiter can (and cannot) answer
Recruiters know the process, pay structure and logistics well. They usually know less about day-to-day engineering work, so match each question to the person who can actually answer it.
| Topic | Ask the recruiter | Save for the hiring manager or team |
|---|---|---|
| Process | Stages, format of each round, timeline, who makes the decision | What a strong performance looks like in each round |
| Level and pay | Target level, pay range, what the range includes | How promotions actually happen on the team |
| Team | Which team, or whether you are matched to one later | Tech stack details, on-call load, roadmap |
| Location | Office days, eligible locations, relocation | Team meeting norms and time-zone spread |
| The role | Why it is open, new headcount or backfill | What success looks like at six and twelve months |
For the questions that belong later in the process, see our list of questions to ask the interviewer, organized by who is across the table.
Questions about the process and the role
Start with the questions that shape everything else; pay, level, team matching and location get their own sections below. Pick the few that matter most to you and write them down before the call.
Process and timeline
- “What are the stages after this call, and what format is each one?” You want to know whether there is an online assessment, a technical phone screen, a take-home or a full loop, so you can plan prep time around the real format.
- “What is the usual time from this call to a decision?” This lets you line up other processes so offers arrive close together.
- “Who makes the final decision: the interviewers, the hiring manager or a committee?” It tells you how much one weak round can hurt and who you ultimately need to convince.
- “Is anything in the job description out of date or weighted differently in practice?” Postings are often written once and reused; the answer tells you what to emphasize.
The role itself
- “Why is this role open — is it new headcount or a backfill?” New headcount often signals growth. A backfill is normal, but a vague answer is worth a gentle follow-up.
- “Are you with the company directly or with an agency?” Agency recruiters may not know the band, the team or the internal timeline, which changes how much weight to put on their answers.
How to ask about the salary range without anchoring
The first number in a negotiation tends to pull everything after it toward itself, even when that number is arbitrary. Harvard's Program on Negotiation says opening first works best when you understand the realistic bargaining range better than the other side does — and it uses an employer who knows its own salary bands as the example of when the candidate does not have that edge. That is your position on the first call: you do not know your level yet, and the recruiter sees the band every day. So the goal is simple: get their number first.
The law often helps. California, Colorado, New York and Washington are among the states that require covered employers to put a pay range in job postings, and California also requires employers to give an applicant the pay scale on reasonable request. The rules differ by state on employer size and on what counts as a range, and more states keep adding similar laws, so check the posting first and treat a missing range as a fair question.
Scripts you can use
- Asking for the range. “Before we go further, can you share the pay range for this role? I want to make sure we are aligned before either of us puts time into interviews.”
- When the posting already lists one. “The posting lists a range. Is that base salary only, and which part of it fits the level you have in mind for me?” Wide posted ranges can span more than one level, so the second half of that question matters. In California, the required “pay scale” is defined as a good-faith estimate of the salary or hourly wage range, so a posted range may say nothing about bonus or equity.
- When they ask for your expectations first. “I am still learning about the scope and the level, so I would rather not put a number on it yet. What range have you budgeted for this level?”
- When they push a second time. Give a researched range rather than a single number, and make the low end a figure you would be glad to accept: “Based on what I have seen for similar roles at this level in this market, I am targeting X to Y in total compensation, depending on level and the equity mix. Is that within your band?” Harvard's PON notes that a range can keep a strong anchor while sounding less aggressive. Keep it realistic, though; an implausible number costs credibility.
- When they ask what you make now. “I would prefer to keep the focus on the market range for this role. What does your band look like?” California and Washington, among other places, bar employers from asking for your pay history, and California's law states plainly that employers can still ask what you expect to earn.
Never quote a number you have not researched. Know recent pay for the level and location, and your walk-away figure. When an offer arrives, put the base, bonus, equity and sign-on into a total compensation calculator so you compare offers on the same basis. The full playbook is in our software engineer salary negotiation guide, and new grads should also read how to negotiate a new grad offer.
Ask about level before the loop, not after
Level is the quiet variable behind everything else. It sets the pay band and the bar the interviewers hold you to, and at many companies it also shapes the loop itself, with more weight on system design and scope for senior roles.
Candidates commonly report that the target level can be set or adjusted after the phone screen or the final round, and down-leveling is reported more often than up-leveling. Practice varies by company, so ask rather than assume:
- “Which level is the loop calibrated to, and do the interviewers know it?”
- “If the feedback points to a different level, would the offer change level, or would I re-interview?”
- “Is the pay range you shared for that level only, or does it span several?”
If the recruiter proposes a lower level than you want, decide now whether you would accept it. Pushing back is much easier before you have spent a week preparing for an onsite than after.
Team matching: hired to a team or into a pool
Companies handle team placement in two broad ways. Some hire for a specific team, so the hiring manager is involved from the start and you know who you would work for. Others run a general loop and match you to a team afterward. Google is the best-known example of the second model: its software engineer process is commonly described as matching candidates to teams after the hiring committee review, though candidates report that the order varies, so confirm it with your recruiter.
Matching after the loop is not a problem in itself, but it changes your timeline and your leverage. Ask:
- “Is the offer contingent on finding a team match?”
- “How long does matching usually take, and how many teams are hiring at this level right now?”
- “Do I get to talk with the hiring managers before choosing a team?”
- “What happens if no match works out?”
Remote, hybrid and location questions
Office policies vary widely between companies and sometimes between teams, and a posting labeled “remote” or “flexible” can mean very different things. Pin it down on the first call:
- Office days. How many days a week, which days, and whether the company or the team sets them.
- Eligible locations. Which offices, states or countries the role can be based in.
- Location-based pay. Whether the range differs by location, and which tier your location falls into.
- Travel and relocation. Expected travel, and whether relocation support exists for an office-based role.
- Policy direction. “Has the in-office policy changed in the past year, and is it expected to?”
Whatever you agree on, make sure the offer letter states the work location or remote arrangement. A verbal “we are flexible” is not a policy.
Red flags to listen for
One vague answer is not a dealbreaker; recruiters juggle many roles and sometimes need to check. A pattern is worth noticing.
- No range at all. “Competitive,” “market rate” or “it depends on the candidate,” especially in a state that requires a range in postings.
- Your number demanded, theirs withheld. Insisting on your expectations or current pay while refusing to say anything about the band.
- A fuzzy process. The recruiter cannot describe the stages, the timeline or who decides.
- Shifting details. The title, level, location or pay changes between the posting and the call without explanation.
- A vague reason the role is open. Worth a polite follow-up, particularly if the team seems to backfill often.
- Pressure before you have interviewed. Being pushed to commit, or to drop other processes, at the screening stage.
- Requests for money or personal details. The FTC warns that honest employers never ask you to pay to get a job, and that personal information handed over for supposed payroll can lead to identity theft. A request to pay, or for bank or ID details before a verified written offer, is a scam signal.
How to run the call, step by step
- Prepare your side. Recruiters commonly ask about your background, why you are looking, what you want next, where you are with other companies and when you could start. Have a 60-second version of your story ready and say it out loud a few times; a free AI mock interview in CoPilot Interview is one way to rehearse it and get feedback.
- Research the range. Check the posting and recent pay data for the level and location, so you know your target and your walk-away number.
- Let them lead first. Answer their questions briefly; most of the screen is theirs.
- Start your questions with process and level. These shape every answer that follows, including the pay range.
- Then pay, team and location. Use the scripts above, and ask for the range before giving a number.
- Close on next steps. “What happens next, and when should I expect to hear from you?”
- Send a short recap. The same day, email a few lines with what you understood: level, range, stages, timeline and location policy. It thanks the recruiter and puts the key facts in writing.
On other processes, share where you are (“I am in final rounds elsewhere”) without naming every company. That is enough for the recruiter to plan the timeline.
Rehearse the screen before the real call
Paste the job description and your résumé into a free AI mock interview, answer out loud, and get a score on each answer with what worked and what to improve. The free plan gives you 15 minutes a day, with no credit card.
Try a free AI mock interviewFAQ
What should I ask a recruiter on the first call?
Ask about the interview stages and timeline, the level the role is being hired at, the pay range for that level, whether you are hired onto a specific team or matched later, and the in-office or remote policy. Two or three well-chosen questions per topic is plenty.
Is it okay to ask a recruiter about salary on the first call?
Yes. Recruiters handle compensation and expect the question, and several states, including California, Colorado, New York and Washington, require covered employers to list a pay range in job postings. Asking early saves both sides time if the numbers do not line up.
What should I say when a recruiter asks for my salary expectations?
Turn it back politely: say you are still learning about the scope and level, and ask what range they have budgeted. If they press again, give a researched range whose low end you would be happy to accept.
Can a recruiter ask how much I make now?
It depends on where the job is. California and Washington, among other places, bar employers from asking for your salary history, though California's law still lets them ask what you expect to earn. Where no ban applies, you can still decline politely and steer back to the market range for the role.
Should I ask what level I am interviewing for?
Yes, before the loop. The level sets the pay band and the bar interviewers hold you to, and candidates commonly report that it can be adjusted after the interviews, so you want to know the target and whether it can change.
What are red flags on a recruiter call?
Refusing to share any pay range, demanding your number while revealing nothing, an unclear process or timeline, details that change from the posting, and pressure to commit before you have interviewed. A request to pay, or for bank details before a verified written offer, is a scam signal.