Questions to Ask Your Potential Colleagues During a Peer Interview
Questions for the stage of hiring where you meet future teammates rather than the hiring manager: what the days actually contain, how work is assigned, what happens when a deadline slips, who has left recently, and how the job differs from its description.
The questions
Open any question for the note
What did your first month here actually look like?
Why ask it
The concrete version of asking about onboarding. You learn whether new people get a small real task in week one or spend four weeks reading documentation. A long pause usually means nobody has joined the team recently, which is worth noticing on its own.
Walk me through yesterday. What took the most time?
Why ask it
Specifics about a real day are difficult to dress up. If yesterday was five meetings and an unplanned escalation, that is the job, whatever the posting says. Vague answers usually mean the day genuinely has no shape.
Roughly how much of your week goes to meetings?
Why ask it
Ask for a number. Answers that arrive as a figure, about ten hours, roughly half, are usually accurate. Someone who says not too many and then glances at their calendar has just told you something different.
Who would I be working with most closely, day to day?
Why ask it
If they cannot name two or three people, the role is either not defined yet or the team is about to be reorganised. How they say the names is worth as much as the names themselves.
What does this team own outright, and what do you depend on other teams for?
Why ask it
A team that waits on another group for deployments, data access, or sign-off moves at that group's speed, not its own. This is where most hidden frustration sits, and peers describe it far more plainly than a manager will.
How does work actually get assigned here?
Why ask it
The mechanism matters: a queue, a manager handing things out, or whoever asks loudest. You just pick things up can mean real autonomy, or it can mean nobody is prioritising and everything is quietly late.
Which tools do you live in, and which one would you replace tomorrow?
Why ask it
The complaint is the useful half. It shows you where the daily friction is and, more importantly, whether the team has any power to fix its own tooling or has been waiting on someone else for two years.
When two people on the team disagree about an approach, what happens? Can you give me the last example?
Why ask it
Asking for the last real instance stops the generic answer about healthy debate. Functional teams describe a mechanism: someone decides, or it gets written up, or both options get tried. Less functional ones describe who tends to win.
What happens when it becomes clear a deadline is going to be missed?
Why ask it
This is a question about how bad news travels. Teams that renegotiate scope three weeks out behave nothing like teams that work later and later and say nothing until the date arrives.
When did you last work a weekend, and what was it for?
Why ask it
Concrete and hard to deflect. One weekend before a launch is ordinary. A pause, a laugh, then it depends on the quarter, is a complete answer about workload without anyone having to say it.
How much of your job is what the job description said?
Why ask it
Peers will name the parts that quietly attach to the role: on-call rotation, support duty, a legacy system nobody else will touch. That attached work is often what decides whether you like the job a year in.
What has changed on this team in the past year?
Why ask it
You are listening for reorganisations, changes of manager, or a shift in what the team is for. If the answer contains two of those already, expect a third before you finish settling in.
Has anyone left recently, and do you know why?
Why ask it
You will not always get a straight answer, and the discomfort is informative in itself. Several departures in one quarter always have a shared cause, and it is rarely only about pay.
How do you find out you are doing well?
Why ask it
Listen for whether feedback exists at all outside the annual review. If the only signal is that nobody has complained, you will spend a year guessing where you stand, and so will everyone reviewing you.
What kind of person struggles here?
Why ask it
More revealing than asking who succeeds, because the answer describes the environment rather than an ideal. People who need clear direction, people who need quiet, people who dislike being interrupted: hold the description against yourself honestly.
What is the manager like in a bad week?
Why ask it
Anyone can describe the good version. Whether this answer is careful and short or relaxed and specific tells you nearly as much as its content, and you should notice which one you get.
What is the thing everyone here complains about?
Why ask it
Every team has one, and peers know exactly what it is. If nobody can name anything, either the conversation is being closely watched or the person in front of you is very new.
What is the last thing you shipped that you were pleased with, and how long did it take?
Why ask it
You get real cycle time and you find out whether anyone here finishes anything. Difficulty answering sometimes means work gets cancelled before it lands, which is a specific kind of demoralising.
If you could change one thing about how this team works, what would it be?
Why ask it
Peers can name a problem in terms a manager cannot use. When two or three interviewers independently name the same thing, treat that as the actual condition of the team rather than one person's grievance.
Is there anything you wish you had asked before you took this job?
Why ask it
You inherit their hindsight, which is the most useful thing they can hand you and costs them nothing to say. It also tends to produce the one detail no structured question would have surfaced.
How to use a peer interview
Practical guidance for the conversation itself
Understand what the meeting is for
It runs in both directions
In most companies the peers are asked afterwards for a signal on whether to hire you, often a simple yes or no with a sentence of reasoning. Assume you are being assessed on whether people want to work alongside you, and ask your questions inside a normal conversation rather than through a list.
Peers answer differently from managers
A manager describes intent. A peer describes what happened last Thursday. Aim your questions at events and examples, not at policy, because that is the information only this meeting can give you.
Pick six, not twenty
You will realistically get through five or six questions in half an hour if you follow up properly. Choose the ones that would change your decision, and let the rest go.
Asking without seeming to interrogate
- Attach the question to something they said: you mentioned the migration, how did the team decide to take that on?
- Ask about their experience rather than the company's policy. People answer freely about themselves and guardedly about their employer.
- Use the last time framing for anything sensitive. When did you last work a weekend is answerable; is the workload reasonable is not.
- Trade something. Offer a short piece of your own experience before asking about theirs, or the exchange starts to feel like a deposition.
- Ask the same one or two questions of every peer you meet. Divergent answers to the same question are the most reliable signal you will get all day.
Reading what you hear
- Enthusiasm about the work matters more than enthusiasm about the company. Perks are easy to praise; a project is not.
- Note what nobody mentions. If no one names the manager unprompted across three conversations, that absence is data.
- Watch for the corrected answer: a quick response, then a softer restatement. The first version is usually the true one.
- Compare against what the hiring manager told you. Where the two accounts differ, the peers are describing the present and the manager the intention.
Common mistakes
Treating it as a break between the real interviews
Candidates relax here and it costs them. The tone can be friendly and the assessment still counts, so keep the same care about how you talk about previous employers and colleagues.
Asking only about culture
Culture questions produce culture answers, which are almost never useful. Ask about mechanics, who decides, how work arrives, what happens when it slips, and the culture becomes visible on its own.
Not writing anything down afterwards
Write your notes within the hour, while you can still recall the hesitations and the exact phrasing. By the following week, three interviews will have blurred into a single vague impression.
Ignoring a consistent bad sign because you want the job
If two peers separately describe the same problem and neither seems to expect it to change, believe them. That is the condition you would be joining, not a phase you would arrive at the end of.