Questions to Ask During Recruitment
Questions for a candidate working through a hiring process, aimed at the hiring manager, future peers and the offer conversation. The goal is to learn what the job is really like before you accept it.
The questions
Open any question for the note
What would I be doing in my first month?
Why ask it
A manager who has thought about the hire can name the first two pieces of work. A vague answer about ramping up and meeting people usually means nothing is waiting for you, and you will spend a quarter inventing the role.
Why is this role open?
Why ask it
Growth, a resignation, a reorganisation and a role that has been open twice all lead to different jobs. If the answer skips past a departure without explaining it, come back to that later in the process.
Who would I work with most closely, and what do they do?
Why ask it
This tells you whether the job is done alone or through other people. Naming three or four colleagues also gives you people to ask about in later rounds.
What does the person in this role spend the most time on that isn't in the posting?
Why ask it
Job descriptions list the interesting quarter of the work. The unlisted three quarters is often reporting, coordination or maintenance of something old, and it is where people get worn down.
How does work reach the team: does it get picked up, assigned, or negotiated?
Why ask it
The mechanism tells you how much autonomy the role has. A team that is handed a fixed backlog has a different daily texture from one that decides its own priorities, whatever the job title says.
What has the team already tried on this problem that didn't work?
Why ask it
Every long-standing problem has failed attempts behind it. Hearing them stops you from proposing the thing that was rejected last year and reveals whether the obstacle is technical or political.
How are decisions made when the team disagrees?
Why ask it
Listen for whether anyone can actually decide. Consensus cultures move slowly, single-decider cultures move fast and unevenly, and "we just talk it through" often means the loudest person wins.
What would a good first six months look like, in things I would have shipped or changed?
Why ask it
Asking for artefacts rather than adjectives makes the answer checkable. If the concrete list is impossible in six months, you have found the expectation gap before you signed rather than at your first review.
How is performance reviewed, and when is the next cycle?
Why ask it
The timing matters as much as the method. Joining two months before a cycle you are not eligible for can mean eighteen months before your first real pay conversation.
What is the band for this role, and where in it would I land?
Why ask it
Sitting at the bottom of a band means limited room to rise without a promotion. Sitting at the top means the same, from the other direction, and both are worth knowing before you negotiate.
How much has this team's plan changed in the last year?
Why ask it
Frequent reorganisation or strategy shifts predict that the role you accept is not the role you will hold. Ask what the team was working on twelve months ago and compare it to now.
What are the expectations around on-call, travel and working outside normal hours?
Why ask it
Ask for the last month rather than the policy: how many nights someone was paged, how many trips they took. Averages hide the weeks that make people quit.
Who has left this team in the past year, and what did they go on to do?
Why ask it
Where people go is a sharper signal than why they left. Leaving for a step up elsewhere in the company reads very differently from a group of exits to competitors in the same quarter.
What is the promotion path, and who was promoted most recently?
Why ask it
A named recent promotion proves the path exists. If nobody can think of one, the ladder described in the handbook is theoretical for this team.
What do people here complain about?
Why ask it
Asked directly, this gets a surprisingly honest answer, usually about tooling, meetings or a slow approval process. An interviewer who cannot name a single complaint is managing you rather than talking to you.
What would make you conclude, six months in, that this hire hadn't worked?
Why ask it
This flushes out the failure mode they have seen before. The answer often describes the last person in the seat, which is more useful than any list of required skills.
Could I talk to someone who would be my peer, without a manager in the room?
Why ask it
The willingness matters as much as the conversation. A team that refuses, or only offers a hand-picked advocate with a manager present, is telling you how much candour to expect later.
How does this team's work make or save the company money?
Why ask it
Teams that cannot draw a line to revenue or cost are the first cut when budgets tighten. If nobody can explain the connection in a sentence, that is the answer.
What is the company's financial position, and how long is the current funding or budget secured for?
Why ask it
Fair to ask at offer stage, and the reaction is informative in itself. Look for a specific answer about profitability, runway or an approved budget rather than reassurance about momentum.
What are the next steps, and when will you decide?
Why ask it
Ending with this gives you a date to work against and lets you manage competing processes. If the timeline slips twice without explanation, treat that as data about how the company runs.
Working a hiring process from the candidate side
Practical guidance for the conversation itself
Match the question to the interviewer
Recruiter
Band, level, process, timeline, hard requirements. They can also tell you what the hiring manager asked for during the intake call.
Hiring manager
First month, failure modes, how decisions get made, how work is assigned, what the last person struggled with. This is the only person who can describe the job as it will actually run.
Future peers
What the week really looks like, what the tooling is like, what people complain about. Ask them what surprised them in their own first month.
Senior leader or skip level
Where the team sits in the plan, whether the budget is secure, what they expect this function to look like in two years.
Reading the answers you get
Ask for last month, not policy
Policies describe intent, recent history describes practice. Convert every question you can into "what happened in the last four weeks".
Compare answers across rounds
Ask two or three people the same question about priorities or the first month. Divergent answers mean the role is not settled, which is worth knowing before you negotiate.
Write down the exact wording
At offer stage you will want the specifics you were told about scope, remote working and review timing. Vague memories are hard to raise later without sounding accusatory.
What tends to go wrong
Saving every hard question for the offer
By then you have sunk twenty hours into the process and are motivated to hear good news. Ask about hours, on-call and scope while you are still comfortable walking away.
Accepting adjectives
Fast-paced, collaborative and flat are descriptions of nothing. Follow each one with a request for an example from the past month and see whether it arrives.
Skipping the peer conversation
Managers describe the job as designed, peers describe it as lived. If the process does not include a peer, ask for one.