Questions to Ask in a Peer Interview
For the peer round of an interview, when you are talking to the coworkers you would have rather than to a boss. These are questions to ask a potential colleague about the things they know better than anyone, starting with the ordinary shape of the job: how work gets assigned, how many hours go to meetings, which tools you would live inside and what happens when something breaks late in the day. Then come the team, the manager and what joining was like, down to how long it took them to feel useful. The Deciding group is for weighing whether to accept: who has left in the past year, what happened to the last person in the role, and whether they would join again. The last group is for a nursing peer interview, where the colleagues in the room are staff nurses from the unit: patient loads, floating, breaks and what happens when someone calls out.
The questions
Each question, and why to ask it
The job
What were you working on last week?
Why ask it
A concrete week beats a job description. Peers will describe the meetings, interruptions and cleanup work that never appear in a posting.
What surprised you in your first month here?
Why ask it
Surprises are exactly where the written culture and the real one diverge. If two peers name the same surprise, treat it as a fact about the team.
How does work actually get assigned on this team?
Why ask it
Ask whether people pick items up, get handed projects, or negotiate for them. This is the biggest difference between teams that look identical on paper.
What is the team stuck on at the moment?
Why ask it
Peers answer this more honestly than managers do. If nobody can name anything, either they are not being told much or they are being careful with a candidate.
Who would I be working with most closely day to day?
Why ask it
Names and roles show you where the dependencies sit. If the answer is a team in another time zone, ask how many hours of overlap there actually are.
What does the first hour of your day look like?
Why ask it
The opening hour is the most habitual part of any job and the least likely to be dressed up. A stand-up, a queue of overnight alerts and an empty calendar until ten are three very different working lives.
How much of your week goes to meetings?
Why ask it
Ask for a number, then ask which meeting they would drop. The second answer tells you more about the team than the first.
Which tools do you spend the most time in?
Why ask it
The daily tool is where the friction lives. A specific ticketing or spreadsheet workflow tells you the actual texture of the job better than the tech stack on the posting.
Walk me through how a piece of work goes from starting it to being finished.
Why ask it
Forces out the real process rather than the documented one, including reviews, approvals and whoever has to sign off. Long answers with many handoffs are a map of where your week will actually go.
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.
How much of your week goes to things that are not the actual job: reporting, process, tooling?
Why ask it
This is where enthusiasm quietly leaks away in otherwise good jobs. A precise answer, such as Monday mornings and Thursday afternoons, is more trustworthy than a shrug.
How much of the work is done together, and how much on your own?
Why ask it
Ask for a rough split. Someone who needs long uninterrupted stretches will struggle on a team that pairs most of the day, and someone who thinks out loud will be lonely on a team that works in silence.
Does the team mostly work in calls, in writing, or in person?
Why ask it
This determines whether your best working mode is an advantage or a constant friction. Ask what happens to someone in a different time zone, since the answer reveals whether writing things down is a real habit here.
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 much of your time goes to other teams, and which ones are hardest to work with?
Why ask it
The second half is the part people answer honestly, and it maps the friction you would inherit. A team with no difficult dependencies is either unusually lucky or unusually isolated.
How much contact does the team have with the people who use what you build?
Why ask it
Distance from users shapes both how decisions get made and how satisfying the work feels. Ask when the team last spoke to one directly.
Who decides what this team works on next, and how much say do you get?
Why ask it
This separates teams that shape their roadmap from teams that receive it. Both can be fine jobs, but only one will let you propose the work you actually want to do.
How often do priorities change, and who changes them?
Why ask it
Frequent reversals from a single executive is a very different job from quarterly planning that holds. Peers will usually describe this accurately because it is what frustrates them most.
What did the team stop doing this year, and was that a choice?
Why ask it
Work that quietly got dropped shows where a team ran out of capacity or standing. A deliberate decision to narrow the scope reads very differently from things that simply fell over, and peers will tell you which it was.
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.
When something breaks late in the day, what happens?
Why ask it
This exposes on-call reality, escalation habits and whether staying late is routine. Ask them to describe the most recent time it happened.
How flexible are hours and location in practice rather than in policy?
Why ask it
The written policy and the observed behavior often differ. Ask when people are typically online and whether anyone actually takes the flexibility they are offered.
When was the last time you worked a weekend, and why?
Why ask it
This turns the work-life balance question into something checkable. One release weekend a year is a different job from a quarter-end that always spills, and the reason matters as much as the frequency.
Do people here answer messages in the evening?
Why ask it
A plain factual question that no policy document will answer. Peers usually tell the truth because they are describing their own habits, and hesitation before the answer is itself informative.
The team
How long have you been on this team, and what were you doing before?
Why ask it
An easy opener that also dates everything else they say. Someone three months in describes the team as advertised; someone three years in describes what it turned into, and you want to know which you are hearing.
What is this team good at that you would not know from the outside?
Why ask it
An easy question to answer, which is why it works early, and the specific claim they choose, code review, handling incidents, writing things down, can be checked against everything else you hear that day.
What kind of person does well on this team, and who has struggled?
Why ask it
The second half is the useful half. Peers often describe the mismatch far more precisely than they can describe the fit.
How does the team settle a disagreement about a technical or creative call?
Why ask it
Listen for whether anyone actually decides. Teams that say they reach consensus sometimes mean that whoever argues longest wins.
How does work get reviewed here, and how direct is the feedback?
Why ask it
Ask so they can answer either way without insulting anyone. People who say feedback is always positive are often describing a team where problems get discussed only after someone leaves.
What happens here when someone makes a real mistake?
Why ask it
Ask for an instance. A team that can walk through a failure without naming a villain is unusual, and worth valuing when you find it.
What happens here when someone says they do not understand something?
Why ask it
You are finding out whether questions are cheap. On teams where admitting confusion carries a cost, people guess quietly instead of asking, which is slower and far more expensive than anyone involved tends to notice.
Does everyone get heard in meetings? How do you know?
Why ask it
The second half is what makes the question work. General reassurance is easy. A concrete practice, written proposals circulated before discussion, going round the room deliberately, is not, and only one of those answers is evidence.
Who do people go to when they are stuck, and is that person overloaded?
Why ask it
Every team has one, and whether that person is protected or quietly burning out tells you a lot about how the team is run. If the answer is that nobody knows, expect long stretches of solo debugging.
When something goes well, who tends to get the credit?
Why ask it
Listen for the names in the success story. If the manager appears in every good outcome and never in a bad one, you have learned exactly how this team is described to the rest of the company.
What is the last thing this team pushed back on and won?
Why ask it
This tests whether the team has any real standing. If nobody can think of an example, the team's input is advisory, which matters if you are joining to change how something is done.
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.
Was there a genuinely hard stretch in the past year? What made it hard?
Why ask it
Every team has had one. The honest version shows you what happens under strain: whether people covered for each other, whether anyone stepped in, or whether everyone went quiet and worked longer alone.
What has changed on this team in the past year?
Why ask it
Reorganizations, new managers and shifting priorities all show up in this answer. Frequent change is not disqualifying, but it should be priced in.
The manager
How often do you talk to your manager, and what do those conversations cover?
Why ask it
Frequency plus subject matter beats any description of management style. Weekly conversations about blockers and career are a different job from a monthly status check that gets cancelled.
What is your manager good at, and what do you have to work around?
Why ask it
The two-part framing makes the second half answerable without disloyalty. Most people will name something, and what they name tells you what your own experience of being managed would be.
What was the last time you disagreed with the manager, and what happened?
Why ask it
Whether they can produce any example at all is the real answer. A long hesitation before a small, safe story tells you more about how much dissent this team can absorb than the story itself does.
What does the review cycle feel like from your side?
Why ask it
Ask whether people knew their rating before the meeting. Surprises at review time mean feedback is not happening in between.
What does this team get recognized for, and by whom?
Why ask it
Tells you what the organization actually values, which is often not what the job description emphasizes. A team whose good work is invisible to the rest of the company is a hard place to build a case for promotion.
Has anyone moved up out of this role recently, and what did that take?
Why ask it
A named example with a timeline is evidence; a statement that growth is available is not. If nobody has been promoted from this seat, ask where people go instead.
Joining
If I joined, what would my first project probably be?
Why ask it
You are checking whether the role has actual defined work waiting or is a hope. Hesitation here often means the team has a budget line and a general sense of need, and the scope will be invented after you sign.
What was your onboarding like, and what would you change about it?
Why ask it
Recent hires remember this vividly. A team that has improved onboarding since the last person joined pays attention to its own problems, which usually generalizes.
How long did it take you to feel useful here, and what helped?
Why ask it
The answer measures onboarding honestly. Six months with no documentation and a lot of asking around means you should plan your own ramp, and it tells you whether the team has capacity to support a new person right now.
What do new people usually underestimate about this work?
Why ask it
This surfaces the hidden difficulty, whether that is a legacy system, one demanding stakeholder, or the sheer volume of coordination.
If I joined, what should I be careful about in the first few weeks?
Why ask it
Positions them as an ally rather than an evaluator, and the advice tends to be practical: a person to avoid annoying, a system nobody understands, a meeting that matters more than it looks.
What are you hoping the next person brings to the team?
Why ask it
Peers answer this differently from managers, usually naming a gap they feel weekly rather than a skill on the requisition. It also tells you what you would be measured against informally.
Deciding
What happened to the last person in this role?
Why ask it
Promoted, transferred internally, left the company or the role is new are four very different situations. If they do not know, ask whether the role has been open a long time, and why they think that is.
Who has left in the past year, and do you know why?
Why ask it
Peers usually know and will often tell you more than they intend to. Several departures in the same direction, or a pattern of people leaving from one manager, is the most useful signal available in a peer round.
What is the last thing that made you think about leaving, and why did you stay?
Why ask it
A direct question that most people answer honestly because it lets them show loyalty and candour at once. What they weighed on each side is the closest you will get to seeing the job from inside.
What is one thing you would change if you could?
Why ask it
Almost everyone has an answer. Someone who insists there is nothing is either guarding the company line or has stopped noticing, and both are worth knowing.
If I take this job, what is likely to frustrate me by month three?
Why ask it
The specific frustration is the point: slow approvals, unclear ownership, a tool nobody will replace. A peer who says nothing comes to mind either has not been there long or is being careful.
What do you wish someone had told you before you joined?
Why ask it
Usually the most candid moment in the conversation, because it is framed as advice rather than criticism. Whatever comes out here should be checked against what the hiring manager told you.
Is there anything you would want to know if you were in my position?
Why ask it
This lets a peer volunteer the thing nobody asked about, which is often the single most useful sentence of the conversation.
Knowing what you know now, would you join again?
Why ask it
The best closing question in a peer round because the pause before the answer carries as much information as the answer. A qualified yes with a reason is the most useful outcome; enthusiasm with no detail is the least.
Nursing peer interview
What kinds of patients does this unit see most, and which are the hardest to care for?
Why ask it
The posting names a specialty; the nurses name the real mix, including patients who are boarded there for want of a bed elsewhere. What they call hard tells you what you would need to learn first.
How many patients did you have on your last shift?
Why ask it
Asking a staff nurse about one real shift gets a number instead of a target. Staffing rules differ by state and by hospital, so ask how the ratio is set here and what happens when the unit goes over it.
What happens to your assignment when someone calls out?
Why ask it
A float pool, a resource nurse and a heavier load for everyone already there are three different units. Whoever answers has lived the most recent version.
How often are you floated to another unit, and where do you get sent?
Why ask it
Floating is rare on some units and weekly on others. If it is common, find out whether nurses are sent only to areas they have been oriented to, and how the turn is decided.
How long was your orientation here, and did you keep the same preceptor?
Why ask it
A nurse hired in the past year can tell you how many weeks they really got, which may not match what the recruiter described. One preceptor who knows what you have already done is a different start from a new face each shift.
Do you usually get your meal break, and who watches your patients while you take it?
Why ask it
Break coverage with a name attached, a charge nurse or a break buddy, is coverage that happens. If the room laughs, you have your answer.
Does the charge nurse take a patient assignment on this unit?
Why ask it
A charge nurse carrying a full load has little slack to help when an admission and a discharge land together. Ask too how soon newer nurses are expected to take charge.
When you are worried about a patient who is getting worse, who comes and how fast?
Why ask it
Have them tell you about the last time. Whether it was a rapid response team, the charge nurse or a long wait on the phone shows how alone a newer nurse would be at three in the morning.
How do the nurses and the physicians on this unit work together?
Why ask it
What you are listening for is whether a nurse can question an order and be heard. A single story about a disagreement on rounds says more than general praise for the doctors.
How is the schedule made, and how are weekends and holidays shared out?
Why ask it
Self-scheduling, a fixed rotation and picks by seniority make for very different years. Find out how far ahead the schedule is posted and how easy it is to trade a shift.
How much overtime or on-call do you end up working, and is any of it mandatory?
Why ask it
Rules on mandatory overtime depend on the state and on any union contract, so ask how it works at this hospital. Staff nurses can say how often the phone rings on a day off.
What is report like at shift change, and do you usually leave on time?
Why ask it
Bedside handoff, a recorded report and a hurried summary at the desk each set up the next twelve hours differently. If staying late to finish charting is common, ask how that time is handled here.
Using a Peer Interview Well
Practical guidance for the conversation itself
What Peers Can Tell You That Managers Cannot
The texture of an ordinary week
Managers describe the role; peers describe Tuesday. Ask about last week specifically, including the parts that went badly, and you get the version of the job you would actually be doing.
Whether the stated process is followed
Every team has a documented way of working and a real one. Peers will usually tell you where the two come apart if you ask about a specific recent decision rather than about process in general.
Who is difficult to work with
Nobody will answer this directly, but asking who you would depend on most, and watching which names come with a pause, gets you close enough.
In a nursing peer interview
The peers are usually staff nurses from the unit, and what they know best is their last shift. Ask how many patients they had, whether they got a break and who helped when it got heavy, then set that beside the staffing plan the nurse manager described.
How to Ask So You Get a Real Answer
- Ask about the last time something happened, not about how things generally happen
- Ask the same two or three questions of every peer, then compare the answers
- Follow a positive answer with a request for an example, once, without pressing further
- Leave silence after a question rather than filling it with a softer version
- Remember that peers are usually scoring you too, so keep the tone curious rather than investigative
Warning Signs
Every peer gives the same polished answer
Identical phrasing across three interviewers usually means they were briefed. Ask something the brief would not have covered, such as what they were working on last week.
Nobody can name a recent decision the team made
It suggests decisions are made elsewhere and handed down. That may be fine at a junior level and frustrating at a senior one, so weigh it against the role.
Peers do not know what the role is for
If your future teammates cannot say why the position was opened, the scope is probably still unsettled and the ambiguity will land on you.
Complaints with no sense of what would fix them
Venting about a broken process is normal. Nobody having a view on how it should work usually means attempts to fix it went nowhere.