Questions to Ask Software Engineer Recruiter
Questions for the first call with a recruiter about a software engineering role, covering level and pay band, equity terms, the interview process, why the role is open, and what a recruiter can and cannot answer.
The questions
Open any question for the note
Are you in-house at the company, or working for an agency?
Why ask it
This decides what they know and how they are paid. An agency recruiter earns a fee on placement and may never have met the team; an in-house recruiter can usually get an answer out of the hiring manager the same day.
Have you spoken with the hiring manager, or are you working from a job description?
Why ask it
The difference is large. A recruiter who has had a kickoff call can tell you what the manager actually cares about; one working from a posting will read the posting back to you in different words.
Is the role approved and funded, or are you building a pipeline?
Why ask it
Unapproved requisitions and pipeline conversations dressed as live roles are both common. Ask whether the headcount is signed off for this quarter, because the answer decides how much of your time this deserves.
Why is the role open: growth, backfill, or a reorganization?
Why ask it
Those three produce three different jobs. Recruiters usually answer this plainly, and it is the quickest way to learn whether the team is expanding or repairing itself.
How long has it been open, and how many candidates have you run through it?
Why ask it
A role open for six months is either very picky, mis-leveled, or paid below market. Any of the three is worth knowing before your fourth interview, and few recruiters refuse the question.
What level does this map to, and what is the band for that level?
Why ask it
Level sets the pay band, the expectations, and often the interview loop. Being run one level below where you actually sit is the most common way a candidate loses a large sum without noticing.
Where in that band have recent offers actually landed?
Why ask it
Recruiters know this and will sometimes share it if you ask politely and specifically. If you are told offers land across the whole band, ask about the last two hires at this level instead.
How is the package split between base, bonus, and equity?
Why ask it
Quoted totals assume every component pays out in full. Ask for the base on its own, since that is the part you can plan around, then ask what the bonus has actually paid for the last two years.
If there is equity, is it options or restricted stock, and what is the vesting and cliff?
Why ask it
The two behave very differently and the paperwork matters more than the headline figure. Ask about the vesting schedule, the cliff, the exercise window if you leave, and the share price or valuation being used.
Is this remote, hybrid, or on-site, and does the offer letter say so?
Why ask it
Verbal flexibility evaporates when a manager changes. If remote work matters to you, ask whether it appears in writing in the offer, because that is the only version that survives a reorganization.
Does the company sponsor visas or support relocation for this role?
Why ask it
Both are policy questions with yes or no answers and recruiters know them cold. Ask early rather than late; sponsorship in particular can void a process after five rounds of interviews.
What is the full process: how many rounds, in what format, over what period?
Why ask it
Ask for the count, the format of each stage, and the total elapsed time. Six rounds over eight weeks is a real cost, and you are entitled to see it up front rather than one stage at a time.
What does the technical screen cover, and what are they grading?
Why ask it
Recruiters are usually permitted to describe the format and topics, and many will send preparation notes if asked. Not asking simply leaves that help unused.
Who makes the final decision, and does anyone in the loop have a veto?
Why ask it
Loops often contain one person whose objection ends the process regardless of the rest. Knowing who that is changes how you prepare for that particular conversation.
What has stopped candidates at this stage before?
Why ask it
A recruiter has watched several people fail at this exact stage and is usually willing to say why. The answers tend to be specific and fixable: thin system design, no example of owning a project end to end, salary raised before the loop was finished.
How many candidates are ahead of me, and how far along are they?
Why ask it
Position in a pipeline affects timing more than merit does. If someone is at final stage, your window is short, and it is better to know that before you slow down your other applications.
Have you placed anyone on this team before, and are they still there?
Why ask it
Retention is the one thing a recruiter can vouch for personally. If someone they placed left inside a year, ask what happened, and note how comfortable they are answering.
How does the company handle a competing offer or a deadline?
Why ask it
Ask before you have an offer rather than after. Some companies will hold an offer open or compress a loop, others will not, and knowing which lets you sequence your other processes sensibly.
If this role is not the right fit, what else are you working on?
Why ask it
Recruiters keep a list, and a candidate who is straightforward to work with gets shown the better roles on it. The answer also shows whether they recruit at your level at all.
What is the best way to reach you, and when will you get back to me?
Why ask it
Recruiters carry many candidates at once and silence is usually workload rather than rejection. Agreeing a date and a channel turns your follow-up into a scheduled item instead of a nudge.
Working with an engineering recruiter
Practical guidance for the conversation itself
Understanding who you are talking to
- An in-house recruiter is measured on hires who stay; an agency recruiter is paid on placement. Both can be useful, and they will push you in different directions.
- Recruiters cannot answer technical questions about the codebase. Save those for the engineers, and do not judge the company on a recruiter's vague answer to one.
- The first call screens in both directions. They are checking level, salary expectation, and availability, and you can check the same three things about the role.
- Assume anything you say about your current pay or your other processes will be passed to the hiring team.
Talking about money on the first call
- You will be asked for a number early. Asking for the band first is normal and rarely counts against you.
- If you give a range, put the base you actually want at the bottom of it, and say the figure depends on level and on the rest of the package.
- If pushed, say you would rather understand the level and band before quoting, and ask what has been budgeted.
- Where pay transparency rules apply, the band may already be in the posting. Read it before the call so you do not negotiate against yourself.
Keeping your own records
- Write down the level, the band, the process, the dates, and who told you each thing. Details often differ between two recruiters at the same company.
- Ask for the load-bearing commitments by email. Remote arrangements, level, and sign-on bonuses are the ones that go missing.
- Track where each process stands. If one company reaches an offer, tell the others plainly rather than stalling them.
- Save the job description as posted. Roles are sometimes rewritten mid-process, and having the original makes that easy to raise.
When to step back
- The role, the level, or the band keeps shifting between conversations.
- You are asked for your current salary and refused any band in return.
- You are pressed to accept before anything is in writing, or handed a deadline of a day or two.
- An agency recruiter will not name the company before sending your resume out.