Questions to Ask a Technical Recruiter
Questions to ask a technical recruiter, from the first call to the offer, written for engineers and anyone else being hired into a technical team. The 62 questions are in six groups: the essentials for when the call is short, the role and the company behind it, how the engineering team works day to day, the interview loop, pay and level, and next steps. Which questions to ask tech recruiters depends partly on whether yours is in-house or at an agency, so the one that settles it is in the first group. If you came here wondering what a technical recruiter will ask you, or whether recruiters ask technical questions at all, the guide after the list covers that side of the call.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Essentials
Can you walk me through the interview process and how many rounds there are?
Why ask it
Anyone who runs this loop every week can list the rounds from memory, so a hazy answer suggests the process is still being worked out. The count also tells you how many evenings and days off this application is going to cost you.
What does the technical assessment involve: live coding, a take-home, system design?
Why ask it
Each format wants different preparation: timed practice for live coding, a free evening or two for a take-home, and talking a design through out loud for system design. If the answer is 'a technical conversation', ask whether you will be writing code in it.
Which languages and systems does the team actually use day to day?
Why ask it
Job posts tend to list everything anyone at the company touches. A recruiter who has spoken to the hiring manager can name the two or three that matter. If your main language is not one of them, ask how the team has treated that in past hires.
What's the range budgeted for this level?
Why ask it
Ask on the first call, because the recruiter is often the only person in the process who will say a number. Some places have pay transparency rules that require a range, and those differ by state and country. If you are asked for your number first, you can say you would like to hear the budget for the level before naming one.
Why is this role open: new headcount, or a backfill?
Why ask it
New headcount usually means a growing team and a job you can partly shape. A backfill comes with a follow-up, which is whether the last person moved up, moved teams or quit. Either answer tells you what the first year is likely to be made of: a new product line, a delivery crunch, or someone else's half-finished work.
Do you work for the company itself, or for an agency it has hired?
Why ask it
Someone in-house sits near the hiring manager and the pay bands, while an agency recruiter may be working from a one-page brief and is paid when you are placed. With an agency, get the company's name before your resume goes anywhere.
How closely have you worked with the hiring manager on this search?
Why ask it
A recruiter who sat in on the kickoff meeting can tell you what the manager disliked about the last ten resumes. One who was handed a requisition number can only read the posting back. Their answer sets how much weight to give everything else you hear on this call.
What level would I come in at, and how does that map to your internal ladder?
Why ask it
'Senior' at a small startup and 'senior' at a large company can be different jobs on different pay. Get the internal level's name or number, because the level is what sets the band. It also gives you something to compare when two companies use the same title.
How is the role set up for location: office days, hybrid, or fully remote?
Why ask it
Get the specifics: which days, whether the team or the company sets them, and whether the arrangement is written into the offer. Ask too whether a change to the policy is being discussed, since that is better heard now than three months in.
Role and company
How long has the role been open?
Why ask it
A few weeks is ordinary. Several months points to a very high bar, a pay range candidates keep turning down, or a budget that was paused and restarted, and you can ask which. A long search can also work in your favor, because a team that has waited that long may be ready to move quickly on someone it likes.
Which team is this for, and what does that team own?
Why ask it
Large companies post one job for several teams, and 'platform engineer' on payments is a different job from the same title on internal tools. A product or service name also gives you something to look up, or to try out, before the next call.
Who would I report to, and how many engineers are on the team?
Why ask it
A name lets you read up on the manager before you meet. One who still writes code tends to run a team differently from one who came up through project management, and on a team of three you would touch everything where a team of twenty gives you one slice.
What would I be expected to own or ship in the first six months?
Why ask it
A recruiter who has been briefed can name a project: the checkout rewrite, the move off the old data pipeline. If all they have is 'get familiar with the codebase', write the question down for the hiring manager, because nobody has told the recruiter what the hire is for.
Which of the listed requirements are firm, and which are a wish list?
Why ask it
Engineering posts often ask for eight technologies when the manager would settle for two and a record of picking up the rest. Find out which ones get a resume turned down, especially if you are missing one, and lead with the firm ones in the technical rounds.
What kind of engineer does the hiring manager have in mind for this?
Why ask it
A posting lists skills, and the manager usually has a person in mind: someone who has scaled a service before, someone patient enough for a codebase nobody fully understands, a steady senior for a young team. If the description fits you, that is the story to tell in the manager round.
Is this a hands-on coding role, or does it come with lead or management duties?
Why ask it
Senior and staff titles hide a wide spread, from writing code all week to spending most of it in planning and reviews. Ask roughly what share of the week the last person at this level spent coding, because month two is a bad time to find out.
How experienced is the rest of the team?
Why ask it
On a team of mostly senior people you learn fast and compete for the interesting work. Where you would be the most experienced engineer, expect to do the mentoring, set the standards and have nobody to check your designs against. Decide which of those you want before you hear the answer.
How long do engineers tend to stay on this team?
Why ask it
If the recruiter has hired for this team before, they know how often its seats come open. Steady tenure, with people promoted from within, is a good sign. If the team has turned over more than once in a couple of years, ask where people went: to other teams in the company, or out the door.
Is this a permanent role, a contract, or contract-to-hire?
Why ask it
Technical recruiters at staffing firms fill all three, and the listing does not always say which. For a contract, ask who the end client is, how long it runs, and how often contractors there have been extended or converted. How a contractor is paid and taxed depends on the country and the arrangement, so ask how it works on this one before you compare rates.
Does the company sponsor work visas for this role?
Why ask it
Raise it early if it applies to you, because it is a yes or no that no interview performance changes. Policies differ by company, by level and sometimes by team, so ask about this role specifically. For anything about your own status, ask who at the company handles immigration, since the recruiter is not the person to advise you.
For remote hires, where does the company need me to live, and what hours does the team overlap?
Why ask it
'Remote' usually means remote within a list of states or countries where the company is set up to employ people. Check that yours is on it before you go further. Then ask whose time zone the meetings follow, since a remote job pinned to mornings eight time zones away is a different schedule.
Has engineering had layoffs or a hiring freeze in the past year?
Why ask it
A fair question, and recruiters expect it. Listen for how plainly it gets answered and whether this team was affected. If there were cuts, ask whether this role replaces someone who was let go, which says a lot about how settled the plan is.
What stage is the company at: still venture funded, profitable, or public?
Why ask it
It decides how to read the rest of the offer. At a funded startup, ask when the last round closed and how long the money is expected to last, since the hiring plan can change with the next raise and the value of the equity depends on how the company does from here. At a profitable or public company, the better question is how this team's budget has held up.
Engineering
Would I work across the whole stack, or mostly in one layer?
Why ask it
'Full stack' in a posting can mean a backend engineer who occasionally fixes a button, or someone who owns features from database to browser. If your strength is on one side, find out how much of the other you would be doing, and whether the interviews test both.
What's the split between new development and maintaining what exists?
Why ask it
Building from scratch and keeping a ten-year-old system running suit different temperaments, and postings blur the two. A rough answer is enough, such as 'mostly new features' or 'half of every sprint is bugs and upgrades'. Mostly maintenance is a fine job if you like it and a bad surprise if you were sold a rebuild.
Who decides what the engineers build: product managers, the engineers themselves, or a client?
Why ask it
You are finding out how much say you would have. On some teams engineers are handed finished tickets, and on others they are in the room when the problem is first described. Hiring managers tend to tell recruiters which kind of person they want, so this is one a recruiter can often answer.
How often does the team ship, and what does a change go through before it goes live?
Why ask it
Several releases a day and one release a quarter are different working lives. A recruiter may only know the outline, and the outline is enough: code review, automated tests and a staging step mean there is a process.
Is a rewrite or a migration under way, and how far along is it?
Why ask it
Many engineering hires are made to finish something: a move to the cloud, off a monolith, onto a new framework. Joining at the start means design decisions, and joining near the end means the hard cases everyone else skipped. Ask what the role becomes once the migration is done.
Does the team use AI coding tools, and is there a policy on them?
Why ask it
Companies differ widely here, from tools provided and expected to tools banned for security reasons. If you lean on one every day, a ban is worth knowing about before you accept. So is a team that will expect you to work that way from the first week.
Is there an on-call rotation, and how often does it page?
Why ask it
One week in eight with a quiet pager is a small tax, and one week in three with pages most nights is a second job. Ask how many people share the rotation and whether new hires join it straight away. Extra pay or time off for on-call varies by employer and country, so ask how it is handled here.
What does a normal week look like for hours, and how often does a deadline stretch it?
Why ask it
This asks about crunch without using the word. A busy two weeks before each release is a real answer, and 'we work hard and play hard' is not one. If the team spans time zones, check whether early or late calls are part of the normal week.
What does onboarding look like for a new engineer, and how soon do people ship their first change?
Why ask it
Some teams have a new hire deploying a small fix in the first week, with a named buddy and a setup guide that works. Others hand over a laptop and a wiki. How long the last hire took to get a change into production is a fair measure of the tooling and the documentation.
How would you describe the engineering culture there?
Why ask it
Asked bare, this gets you the careers page. Follow it with something that can be checked: whether engineers review each other's code, whether any days are kept free of meetings, what happened the last time a release went wrong. A recruiter who has placed people on the team has usually heard how they talk about it a few months in.
Interviews
Who would I meet at each stage, and what is each of them assessing?
Why ask it
An in-house recruiter usually knows the panel by name and what each round is scored on: coding, design, how you work with other people. With the names you can look up what each interviewer works on. With the scoring you know which examples to save for which hour.
Is there a prep guide, or topics you would tell me to review?
Why ask it
Many companies have a document for candidates and only send it when asked. Even without one, a recruiter has watched a lot of people go through this loop and knows whether it leans on algorithms, practical debugging or design. Two sentences from them can save you a week of practicing the wrong thing.
Can I do the coding rounds in the language I know best?
Why ask it
Many companies let you choose, but some insist on the language the team uses, and the odd round is tied to a framework. Find out now, because the week before is too late to get fluent. If the choice is free, pick the one you can write without looking anything up.
What are the ground rules for the coding round: my own editor, documentation, AI assistants?
Why ask it
Rules differ from company to company and sometimes from round to round. Some want your normal setup, tools included, and others want a bare shared editor and treat any outside help as cheating. Get the answer in writing if you can, so nobody has to rule on it in the middle of an interview.
If there is a take-home, how long is it meant to take and who reviews it?
Why ask it
Ask for the intended hours, not the deadline, because a 'weekend project' can mean three hours or twenty. The better versions end with an engineer going through your solution with you, and you will want to know that in advance since you will be defending your choices. It is fair to ask whether a long one is paid.
How much weight is on system design at this level, compared with coding?
Why ask it
The balance shifts with seniority: junior loops are often mostly coding, and a senior one can be decided by the design round. Ask what a strong design answer looks like here, since some companies want a sketch of a familiar product and others want you to go deep on something you built yourself.
Is there a behavioral or values round, and what is it built around?
Why ask it
Engineers tend to prepare for the technical rounds and improvise this one, and that is how a strong coder ends up without an offer. If the company has published values or principles, the questions are usually built on them. Find out which ones interviewers keep coming back to, and have a true story ready for each.
Which round do candidates most often stumble on?
Why ask it
Recruiters read the feedback after every loop, so they know whether people tend to fall at the timed coding screen, the design round or the conversation with the manager. That is where your preparation hours should go. What the people who got through it did differently is worth a second question, and is as close to coaching as the process allows.
Are the final rounds on one day, and are they remote or on site?
Why ask it
Four or five hours of interviews in a row is a stamina test as much as a technical one. A remote loop can often be split over two days if you ask before it is scheduled. If it is on site, find out who books and pays for travel.
Am I interviewing for this one team, or for a general pool with team matching afterwards?
Why ask it
With a specific team, the people you meet are the people you would work with. With a pool, you can pass every round and then wait weeks for a team to pick you, or be matched somewhere you did not expect. The two things to pin down are how long matching has been taking lately and whether you get a say in it.
Can the interviews move me up or down a level from the one I applied for?
Why ask it
At many companies the loop decides the level, and an offer one rung down is a common way for it to end. Knowing that in advance lets you say now what you would and would not accept. The rounds that carry the leveling decision are where your preparation should go, so find out which they are.
Who makes the decision after the final round?
Why ask it
It might be the hiring manager alone, a debrief where every interviewer votes, or a committee that never met you and reads written feedback. The last kind takes longer and rewards answers you explained out loud, because your reasoning has to survive being written down by someone else.
If one round goes badly, is that the end, or is the loop judged as a whole?
Why ask it
Some companies need a yes from every interviewer and others weigh the full set. If the whole loop counts, a rough hour is worth shaking off before the next one starts. Recruiters also know whether an extra round is ever offered to settle a split result.
If I don't get an offer, will I get feedback, and how long before I can apply again?
Why ask it
Easier to ask now, while everyone is friendly, than after a rejection email. Many companies set a waiting period before you can interview again, and feedback policies run from a detailed call to nothing at all. Neither is standard, so find out how this company handles each.
Pay and level
What's the compensation mix: base, bonus, and equity?
Why ask it
A large total can be mostly equity in a private company. Ask what type of equity it is, how it vests, and what the last valuation was, because a headline figure without that is not comparable to anything.
What would put me at the top of the range instead of the middle?
Why ask it
It turns the range from a number you are told into one you can argue for. The answer is usually specific: a competing offer, experience with a particular system, coming in at the upper end of the level. Whatever they name, bring it up again when the offer is being put together.
Are there equity refreshers after the first grant?
Why ask it
If the first grant vests over a few years and nothing is added, your pay drops when it runs out. Ask whether refreshers are routine or reserved for top ratings, and how they compare in size with the initial grant. At a private company, also ask what happens to vested options if you leave.
Has the bonus paid out at target in recent years?
Why ask it
A bonus is quoted as a target percentage, and the target is the optimistic number. Ask what actually paid out over the last couple of years and whether it depends on company results, your own rating, or both.
Is there a sign-on bonus or relocation help at this level?
Why ask it
These are often available and rarely offered unprompted, because they tend to come from a different budget than salary. A sign-on can cover a bonus or unvested stock you would leave behind, so mention what you would be walking away from. Either may have to be repaid if you leave within a set time, so check the terms before you count on it.
Does the pay band change with where I live?
Why ask it
Many companies with remote engineers pay by location tier, so the range you were quoted may assume the head office city. Find out which tier your address falls in and what happens to your pay if you move later.
Is there a written engineering ladder, and does it go past senior without managing people?
Why ask it
A written ladder means promotions are argued against stated criteria and not only a manager's impression. Ask whether staff and principal roles exist on this team in practice, with people holding them. If the only way up is into management, that matters when you would rather keep building.
What is in the package besides pay: health cover, retirement contributions, a learning budget?
Why ask it
Benefits vary so much by country and employer that the only useful version is the written summary, so ask the recruiter to send it. Read it for the items with real money attached and for when each one starts. Conference time and a training budget are small, but they show whether the company expects its engineers to keep learning.
Next steps
What timeline is the team working to, and is there a start date in mind?
Why ask it
A team hiring against a start date next month will schedule your rounds this week and decide fast. An open-ended search can go quiet for two weeks without it meaning anything. Knowing which one you are in also tells you how much notice you could realistically give your current employer.
Where are other candidates in the process?
Why ask it
If someone is already at final rounds, you are catching up, so ask whether your loop can be compressed. If you are among the first, expect the team to want a few more people to compare you with before it decides.
I'm speaking with other companies: can this process move faster if an offer comes in elsewhere?
Why ask it
Only say it if it is true, and say it early so it lands as information and not as a threat. Many recruiters can compress a loop when there is a real deadline, and they would much rather have a week's warning than a day's. The useful detail is how much notice they need.
Looking at my resume, where do you expect the hiring manager to hesitate?
Why ask it
Direct and slightly uncomfortable, which is why it works. A recruiter who names the gap, whether it is no experience at this scale, a short stint or a missing language, has handed you the thing to address in the next round. Arrive with a specific answer to it, not a defense.
What do you need from me before the next round: a code sample, references, proof that I can work here?
Why ask it
Getting the paperwork in early keeps a slow week from being your fault. If they want a code sample or links to past work, ask what the reviewers look at, since a small project you can explain line by line serves you better than a large one you half remember.
What happens after this call, and when should I expect to hear from you?
Why ask it
Get a day, not 'soon'. With a date agreed, a short message the morning after it passes is ordinary and not pushy, and a quiet week stops reading as a rejection. Check whether they prefer email, a text or a call when scheduling stalls.
If this role isn't the right fit, would you consider me for others?
Why ask it
Recruiters carry several open roles at once, and agency recruiters carry several clients. Say which kinds of team or stack you would want to hear about, so your name comes up for the right ones and you are not sent every opening.
Working with a Technical Recruiter
Practical guidance for the conversation itself
Know Which Kind of Recruiter You Have
In-house recruiter
Works for the company, sits near the hiring manager, and can usually answer questions about level, range and who is on the panel. They are often the person who carries your offer through approval, so what you tell them about your expectations travels.
Agency or contingency recruiter
Paid by the company when a candidate is placed, and often working for several clients at once. They may know less about the team and more about what the market pays. Ask which company the role is with before sharing your resume.
Sourcer
A sourcer finds candidates and hands them on, so their part often ends once you agree to a call with the recruiter. Cover the basics with them, and save detailed questions about the codebase or the team for the next conversation.
Order the Call Sensibly
- 1Confirm the basics first: company, level, location expectations, and range. If any of these rule the role out, you both save an hour.
- 2Then ask about the work itself: the stack, the split between building and maintaining, and why the role exists.
- 3Then the process: rounds, format, panel, and timeline.
- 4Close with two questions: where the hiring manager might hesitate over your background, and what happens next and when you will hear.
- 5Do not try to cover the whole list in one sitting. The Essentials group fits a first screen. Keep the Interviews group for the call where the loop gets scheduled, and Pay and level for when an offer is close.
What a Technical Recruiter Will Ask You
Do recruiters ask technical questions?
Usually light ones. A recruiter screen is mostly about whether your experience matches the brief and whether the logistics work. Some companies give their recruiters a short scripted set of technical questions with the expected answers, and a recruiter who used to be an engineer may go further. When the call is booked, ask whether it includes any technical questions, and the surprise goes away.
What they nearly always ask
A two-minute account of your recent work, which technologies you have used in production and for how long, why you are looking, what pay you are aiming for, where you can work and whether you need sponsorship, your notice period, and where you stand with other companies. Have a plain answer ready for each before you pick up.
How they listen
Most tech recruiters are matching what you say against a list the hiring manager gave them. Use the names of the technologies in the posting when they are true of you, and give years and scale in place of adjectives: 'three years of Go on a payments service' travels better than 'strong backend skills'. It makes you easy to pass along accurately.
Common Mistakes
Naming your current salary
You are usually not required to, and in some places an employer is not allowed to ask. The rules differ by country and state, so check the ones where you live. Giving the range you are targeting for this level answers the question well enough.
Saving all questions for the hiring manager
The recruiter is usually the person best placed to talk about process, panel and money. Many hiring managers will send you back to the recruiter for all three.
Treating the screen as one-way
The recruiter is deciding whether to spend the panel's time on you. Preparing a short, specific reason you are interested in this company does more than a long list of skills.