Questions to Ask Peers in an Interview
Questions for the part of an interview where you are talking to people at your own level rather than to a manager. Focused on the daily shape of the work: meetings, tools, feedback, onboarding, and how the team actually operates when nobody is watching.
The questions
Open any question for the note
What does a typical week look like for you?
Why ask it
Ask for last week specifically if the answer stays general. You are trying to find the ratio of focused work to coordination, which is the single biggest difference between two jobs with the same title.
What do you like about working here?
Why ask it
An easy question with a useful failure mode: someone who reaches only for the people or only for the perks, and cannot name anything about the work, is telling you what the work is like. The speed of the answer matters as much as its content.
What has been the hardest part of your role?
Why ask it
Hardest usually gets a more honest answer than worst. Note whether the difficulty is the work itself, which is often a good sign, or the organization around it, which tends not to improve.
How would you describe this team to someone about to join it?
Why ask it
Framing it as advice to a newcomer produces plainer language than asking about culture. Listen for the adjectives they use twice, and for anything they say the team is not.
How much of your week is meetings, and which ones would I be in?
Why ask it
A number and a list, both checkable against the calendar invite you receive on day one. Recurring meetings are the most stable feature of any job and the hardest to escape once you are in them.
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.
How do people here give each other feedback on work in progress?
Why ask it
Reviews, critique sessions, a quiet word, or nothing at all. A team with no mechanism for this usually discovers problems late, and it also means you will not know whether your work is any good.
How much of your week involves your manager?
Why ask it
A quantity question rather than a style question, so it is easier to answer honestly. Daily involvement and monthly involvement produce very different jobs regardless of how good the manager is.
How do you find out what the current priorities are?
Why ask it
A written plan, a weekly meeting, or overhearing it in chat. If the answer involves guessing or asking around, expect to spend real energy on work that gets abandoned.
Which tools do you use, and which ones get in your way?
Why ask it
The second half is where the information is: a slow build, a ticketing system nobody trusts, three places where documentation might be. These are daily irritations you would inherit in full.
What happens when someone is stuck for more than a day?
Why ask it
Tests whether asking for help is normal or costly. Answers involving a channel, a pairing habit, or a named person are healthy; answers about figuring it out yourself describe a team where people quietly stall.
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 was it before you felt useful?
Why ask it
The number tells you about the complexity of the system and the quality of the support. Six weeks and nine months are both plausible answers, but only one of them matches a role expecting quick impact.
How does hybrid or remote work actually function here, rather than on paper?
Why ask it
Ask where decisions get made, since a team that decides things in the office corridor will leave remote members reconstructing the reasoning afterward. Ask also who is in the office on which days.
When do you switch off, and does anyone message you after that?
Why ask it
More specific than asking about balance, and harder to answer with a policy. What matters is whether messages after hours carry an expectation of a reply, and who sends them.
What kind of person does well here, and what kind struggles?
Why ask it
Who struggles is the useful part, and people answer it more freely than they expect to. If the description sounds like you, take it seriously rather than assuming you would be the exception.
How has the team changed since you joined?
Why ask it
Direction matters more than the current state: growing, shrinking, reorganized twice, moved under a new department. Change described without any explanation of why is worth a follow-up.
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.
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.
What have I not asked that you would want to know if you were me?
Why ask it
A better closing line than asking whether there is anything else, because it puts them in your position. The gap they fill is often the thing they have been hoping you would ask about.
Getting a Straight Answer from Peers
Practical guidance for the conversation itself
What the Peer Conversation Is For
It is the only view of the daily job
A manager describes the role as designed; peers describe it as lived. Meetings, tooling, how long things take, and how much of the week disappears into coordination are things only they can tell you accurately.
Ask about last week, not in general
General questions get general answers. What did you work on last week, how many meetings were on your calendar, and when did you last stay late are all answerable and comparable across companies.
Pick questions to match the person
Someone six months in is your best source on onboarding and surprises. Someone four years in is your best source on how the team has changed and who has left. Asking both the same list wastes half your time.
Say plainly that you want the real version
One sentence about preferring to know the awkward parts now usually shifts the conversation. Peers are generally willing, they just default to a polished answer unless invited not to.
Take notes and compare afterward
The value comes from contradictions: between two peers, or between the peers and the hiring manager. Write down the specifics while they are fresh and raise the gaps before you accept an offer.
Reading the Answers
- Nobody able to name anything they would change about onboarding, in a team that has grown recently. Usually it means there was no onboarding to evaluate.
- Priorities discovered by asking around rather than from a written plan. Expect abandoned work and unclear ownership.
- A long pause on the after-hours question. The pause tends to be more accurate than the sentence that follows it.
- Praise only for the people and never for the work. It can mean a pleasant team doing work nobody finds interesting.
- A description of who struggles here that matches you closely. This is the most actionable warning you will get in the whole loop.
- Answers phrased in company slogans. Peers who talk like the careers page are either very new or working somewhere candor is unwise.
Common Pitfalls
- Bringing compensation, holiday, or notice periods to a peer. They cannot answer and it makes the rest of the conversation stiff.
- Asking only culture questions and leaving without any picture of the work itself.
- Using the time to pitch yourself. You are already being assessed on how you listen, and this is your one chance to gather facts.
- Accepting a friendly non-answer. If a question lands awkwardly, note it and ask the hiring manager the same thing later.
- Interviewing only people the company chose to put in front of you. Where it is appropriate, look for a former employee to speak to as well.
- Forgetting the peers get a say. Ask about their work with real curiosity, because the loop closes with them being asked whether they want you.