By Lee Flanagan
Introduction
Collaboration isn’t friendliness. It’s not even “working well with others” in the abstract sense. It’s the ability to deliver an outcome—a project, a decision, a strategic pivot—when that outcome requires resources, authority, or priorities you don’t control. It’s whether someone can navigate competing stakeholder interests, influence peers without line authority, and maintain relationships while pushing for what needs to happen. The best collaborators don’t shy from conflict; they navigate it. They know the difference between agreeing and aligning.
Most interviewers assess this badly, and predictably so. They ask candidates to describe themselves as team players and accept “we achieved X” as evidence, without ever pressing: What did you specifically do? Where did you and the team disagree? Whose budget were you pulling from? What would the other stakeholder say about your approach? They reward candidates who make everything sound frictionless and mistake agreeableness for actual cross-functional delivery. They rarely surface the moments where collaboration actually matters—when priorities clash, when you need someone else’s department to move fast, when the relationship has to survive the negotiation.
This page covers 22 interview questions across 5 dimensions: Cross-functional Delivery, Disagreement & Tension Management, Coalition Building, Influence & Persuasion (without authority) and Relationship Building (long-term trust). All questions are behavioural, all designed to surface how candidates actually handle real friction and competing interests. We’ve drawn on structured interview research and our own patterns across 10,000+ candidate assessments to isolate the questions that expose real capability.
Cross-functional Delivery
What good looks like
A strong collaborator delivers outcomes that depend on people and resources they don’t control, navigating competing priorities across functions to land something concrete. They keep accountability with themselves rather than diffusing it across the group, and they can point to specific shipped results that required other teams’ active cooperation.
Behavioural questions
- Tell me about a piece of work you owned that you couldn’t deliver without another team’s resources.
- Which team was it, and what specifically did you need from them?
- What state was the relationship in when you started — were they expecting this ask, or did you arrive cold?
- What did you do to get their priority shifted onto your work? Walk me through the specific moves.
- What got shipped in the end, and how long did it take from first conversation to delivery?
- Describe a cross-functional project where the other team’s priorities were in direct conflict with yours.
- Whose roadmap was in the way, and what were they protecting?
- How did you frame the trade-off when you raised it with them?
- What did you concede, and what did you hold the line on?
- Where did it land — did you get what you needed, partially, or did you have to escalate?
- Walk me through the last time you had to deliver something on a deadline that depended on three or more functions.
- Who were the functions, and what was each accountable for?
- How were you tracking whether everyone was on pace? Be specific about the mechanism.
- Where did it nearly come unstuck, and what did you do at that point?
- What was the outcome against the original deadline?
Situational scenario
You’re leading a launch that’s promised to a major customer for the end of the quarter. Engineering tells you in week three that they’re going to miss their build slot by two weeks because a higher-priority security issue has pulled their senior people. Marketing has already committed launch spend. You don’t manage either team.
Walk me through what you do from the moment engineering gives you that news.
Then introduce a constraint: “The engineering lead is the one who escalated the security issue and they're not going to back down on it. Your VP is on holiday for the next week. What now?”
What to listen for
whether they go to the people directly or escalate first, whether they reshape the commitment with the customer or try to hold the original line, and whether they treat marketing spend as sunk or actively try to recover it.
Disagreement & Tension Management
What good looks like
A strong collaborator surfaces disagreement rather than smoothing it over, holds their position when they have evidence, and changes it when they don’t. They can name specific instances where they were in real conflict with a colleague and describe how the working relationship survived or didn’t.
Behavioural questions
- Tell me about a working disagreement with a peer that you couldn’t resolve in one conversation.
- Who was the peer and what were you actually disagreeing about?
- What was their position, in their own words, as best you can reconstruct it?
- What did you do between the first conversation and the resolution?
- How did it land, and where is the relationship now?
- Describe a time you held an unpopular position in a room of more senior people.
- What was the position, and who in the room was pushing back hardest?
- What evidence were you working from?
- How did you keep the conversation going when the pressure to fold was high?
- What did the room decide, and what happened next?
- Tell me about a time you realised mid-disagreement that you were wrong.
- What was the moment the penny dropped?
- Whose argument made you reconsider, and what specifically did they say?
- What did you do in the room once you’d realised it?
- How did you reset with the person you’d been pushing back against?
Situational scenario
A senior peer in another function has been making decisions that affect your team without consulting you. The last one is going to cost you two weeks of rework. You’ve raised it informally twice and nothing changed. Your manager has told you to “sort it out between you.”
Walk me through how you handle the next conversation with this peer.
Then introduce a constraint: “Mid-conversation, they tell you they didn't consult you because they thought you'd block the decision and they had to move fast. Does that change how the rest of the conversation goes?”
What to listen for
whether they make the cost concrete or stay at the level of feelings, whether they go after the pattern or just the latest incident, and whether they leave the conversation with a specific changed behaviour or a vague "let's communicate better."
Coalition Building
What good looks like
A strong collaborator assembles support across functions before a decision is made, not after. They can name the specific people whose backing they sequenced to get a piece of work approved, funded, or prioritised, and explain why they went to each person in the order they did.
Behavioural questions
- Tell me about a decision you needed approved that required support from people outside your reporting line.
- What was the decision and who held the formal approval?
- Who else’s backing did you need, and why specifically those people?
- What order did you go to them in, and why that order?
- What did the approval meeting actually look like by the time you got there?
- Describe a piece of work that wouldn’t have happened without you pulling a coalition together.
- Why hadn’t it happened before — what was the blocker?
- Who were the three or four people you most needed, and what was in it for each of them?
- What did you offer or concede to bring them on board?
- What got built or shipped, and over what time period?
- Walk me through a time a coalition you were building fell apart partway through.
- Who pulled their support, and at what stage?
- What did you find out about why?
- What did you try to recover it?
- Where did the work end up — did it die, get reshaped, or proceed without them?
Situational scenario
You believe your company should sunset a product line that’s eating engineering time and generating little revenue. The product line was championed by a VP who’s still at the company. Two of your peers benefit from features on that product line for their own customers. The CFO is sympathetic but won’t lead the conversation.
Walk me through how you build support for this over the next six weeks.
Then introduce a constraint: “The VP who championed it gets wind of what you're doing and asks you directly what you're up to. What do you say?”
What to listen for
whether they sequence private conversations before public ones, whether they actually address the VP's interests or just route around them, and whether they're building a coalition or just collecting signatures.
Influence & Persuasion (without authority)
What good looks like
A strong collaborator changes the mind of someone who doesn’t have to listen to them. They can describe a specific person whose position they shifted, what that person actually said before and after, and what argument or evidence did the work. This is not about being well-liked; it’s about moving the room when you don’t have the title to mandate it.
Behavioural questions
- Tell me about a time you changed someone senior’s mind on a decision they’d already made.
- Who was the person, and what was the decision they’d made?
- What was their stated reasoning?
- What did you say or show them that did the work?
- What did they decide instead, and how do you know your argument was what moved them?
- Describe a time you needed a peer to drop a priority they cared about to make room for yours.
- What was their priority, and why did it matter to them?
- What did you understand about their incentives before you went into the conversation?
- What was the actual exchange — what did you offer, what did they push back on?
- What did they end up doing, and what was the cost to you?
- Walk me through a time you tried to influence a decision and failed.
- Whose mind were you trying to change, and on what?
- What argument did you make?
- Where do you think the argument didn’t land?
- What did you do differently the next time you needed to influence that person?
- Tell me about a piece of work that only got funded because you sold it internally.
- Who held the budget, and what were they spending it on instead?
- What was the version of the pitch that worked, after the ones that didn’t?
- Who else did you need to bring along before the budget holder would say yes?
- What got built, and did it deliver against the case you made?
Situational scenario
You’re convinced the company should invest in a new market segment based on customer signals you’ve been seeing. Your CEO is sceptical and has said publicly she wants the team to focus, not expand. You have ninety days before the next planning cycle and no formal authority to commission research or pull people onto a working group.
Walk me through how you use that ninety days.
Then introduce a constraint: “Your direct manager tells you they think the CEO is right and you should drop it. Does that change what you do?”
What to listen for
whether they go after the CEO's actual objection or just build a louder version of their own case, whether they recruit one or two credible voices before they re-enter the conversation, and whether they reshape the proposal in response to what they learn or keep pushing the original.
Relationship Building (long-term trust)
What good looks like
A strong collaborator invests in working relationships before they need anything from them, and can point to specific people they’ve stayed connected to over years across role changes and company changes. They can describe a moment when an early investment paid back, and the payback is concrete — a hire, an introduction, a fast answer on something that would otherwise have taken weeks.
Behavioural questions
- Tell me about a working relationship you’ve maintained for more than three years across role or company changes.
- Who is the person, and how did the relationship start?
- What have you done to keep it going when you weren’t actively working together?
- When was the last time you spoke, and what was the conversation about?
- Has there been a moment that relationship paid back for either of you? Be specific.
- Describe a colleague you invested in early who later became important to a piece of work.
- Who were they when you first started investing — junior, peer, in a different function?
- What did the investment look like in practice? What did you actually do?
- How much time passed between the early investment and the moment it mattered?
- What did they do for you or the work that wouldn’t have happened otherwise?
- Walk me through how you stayed in touch with someone after one of you left the company.
- Who was the person and why was the relationship worth keeping?
- What’s the rhythm — how often do you actually speak, and who initiates?
- What’s the most recent thing one of you did for the other?
- Has there been a relationship like this you let lapse, and what happened?
- Tell me about a time you called in a favour from someone you’d built a relationship with years earlier.
- Who was it and what did you need?
- What had the relationship looked like in the years before you needed something?
- How did you make the ask, given the gap?
- What happened, and what did you do afterwards to keep the relationship even?
Situational scenario
You’re starting a new role in three months. You’ve got a quiet stretch in your current role before you leave. You know from experience that the people you’ll most need in your first year at the new place are usually not the ones you’d predict on day one.
Walk me through how you spend the next three months on relationships, given you don’t yet know which ones will matter.
Then introduce a constraint: “Your current manager finds out you're investing time in external conversations and asks you to focus on finishing your current work. How do you handle that?”
What to listen for
whether they treat this as networking or as something more deliberate, whether they have a view on who's worth investing in absent a specific ask, and whether they can describe what "investing in a relationship" actually consists of in practice rather than as a concept.
How to Use These Questions in a Structured Interview
These questions only work if you probe. The first answer is rarely the full answer. Plan to dig into 2–3 of these per interview, rather than rushing through all 26. For each question, listen for specifics: What exactly happened? Who specifically resisted, and what was their reasoning? What would they say about how you handled it? If a candidate gives you a polished answer with no tension, no setback, no moment where they actually had to choose—follow up harder.
Use a 1/3/5 rubric as you score. A candidate who describes collaboration as conflict-free, who can’t articulate what they gave up or where relationships were tested, scores 1. One who describes real cross-functional work with genuine friction, who can explain both their own role and the other person’s perspective, scores 3–5. Calibrate across your interview panel; one interviewer’s “strong collaborator” is another’s “people-pleaser.” See how Interview Intelligence solves this → by capturing how different interviewers frame the same behaviour, so you catch those blind spots before they cost you.
Also sanity-check your questions themselves. Check your interview questions for biased language →, because collaborative questions can accidentally reward people who talk a certain way or come from backgrounds where networking is easier, rather than those who actually get cross-functional outcomes.
Frequently asked questions
How is Collaboration different from Communication?
Communication is about clarity and how you convey information. Collaboration is about what you *do* with other people to achieve an outcome, especially when there's friction or competing priorities. A candidate can communicate brilliantly but fail to actually move collaborators. These questions are about the moving part—the behaviour change, the outcome that required someone else.
Isn't Relationship Building just networking?
No. Networking is transactional and often short-term. Relationship building is investing in people before you need them, staying consistent, and maintaining trust when there's no immediate payoff. The distinction shows up in the questions: we're asking about people they've helped without a return, or relationships they've maintained over time—not about how many connections they've made.
What if a candidate can't think of a time they had conflict with a collaborator?
That's a flag. Real cross-functional work involves friction. If someone tells you they've never disagreed with a collaborator, they either haven't collaborated much, or they're not being honest about it. Press: *Tell me about a time you wanted to do something a certain way but someone else pushed for a different approach. What happened?* If they still can't produce an example, their collaboration experience is either shallow or their self-awareness is.
Should I ask hypothetical questions like "What would you do if...?"
No. Candidates can imagine any version of themselves they want. Behavioural questions—*tell me about a time*—force them to describe what actually happened. If you ask hypotheticals, you're testing their ability to imagine themselves under pressure, not their actual behaviour under pressure.
How should I score if someone collaborated successfully but the outcome was mediocre?
Separately. Collaboration and results are not the same thing. A candidate can collaborate brilliantly and still miss the mark, or deliver results by steamrolling people. Score the collaboration skills independently: Did they navigate competing priorities without breaking relationships? Did they genuinely shift someone's perspective? Did they maintain trust? The outcome quality is a separate assessment.