A cross-functional interview round looks like a formality. You have already convinced the hiring manager, and now a few people from other departments want "a quick chat". Then the finance lead asks how you would cut spend, and an hour later the head of sales asks how you would get discounts approved faster. Each of them is hiring a slightly different person, and you are the only candidate for all of those jobs.
The hard part here has nothing to do with facing several people in one room. The rounds are separate, the agendas conflict, and everyone compares notes afterwards.
Why other departments read the same role differently
A job description is a compromise document. By the time it is published, someone has sanded it down until no department objects to it, which is why it tells you so little about what each of them expects. The expectations did not go away. They moved into the interview loop.
Take a product manager hired to own pricing and billing at a software company. Sales wants someone who will say yes to custom deals without a two-week review. Finance wants someone who will stop custom deals, because every exception makes revenue harder to forecast and invoices harder to reconcile. Support wants fewer plans, since each new one generates tickets. All of these are reasonable. They cannot all be fully satisfied by the same person in the same quarter.
Each interviewer from another function also holds an informal veto. They rarely get to choose the hire, but a firm "I could not work with this person" from finance is usually enough to stall an offer. So the conversation tests your skill less than it tests one risk: whether you will be a problem for their team.
Find out what each function needs before the round
Most candidates prepare by reading the interviewer's profile and stopping there. The profile tells you who the person is. You need to know what their department loses if this hire goes badly.
Start with the recruiter, who is the one person paid to make the loop go smoothly. Ask plainly:
- "How does each of these teams work with this role day to day?"
- "What did the last person in the job do that each team liked or struggled with?"
Then read the posting again with one function in mind at a time. A line such as "partner with finance on revenue recognition" suggests finance has been burned before. "Enable the sales team" in a product role suggests sales asked for this hire, or at least lobbied for it.
Finally, write one sentence per department: what they want from this role, and what they fear from it. If you cannot write the sentence, that is your first question in the room.
Each interviewer also skims your CV for proof from their own world. If you build it from your LinkedIn profile, with Postulit for example, check that at least one line speaks to each function.
One question, different emphasis, the same story
Every interviewer will ask some version of "how do you handle a request you cannot fulfil?". The temptation is to tell sales you are flexible and tell finance you are strict. That works until the debrief, when two people read their notes aloud and describe two different candidates. Inconsistency is the one thing a debrief reliably catches.
The fix is to keep one position and change which part of it you show first. Settle it before the loop begins.
Here is the pricing manager answering the head of sales:
"When a rep brings me a deal that needs non-standard terms, my first job is to get them an answer fast, ideally the same day. I keep a short list of exceptions I can approve on my own, so most requests never wait. Anything outside that list goes to finance with a recommendation from me, not just a forwarded email."
And the same person answering the finance lead:
"I keep a short, written list of pre-approved exceptions, agreed with your team in advance, so nothing reaches a contract that you have not already seen the shape of. Anything outside it comes to you with the numbers and my recommendation. Sales gets a fast answer either way, which is what stops them from improvising."
Read side by side, those are the same policy: a pre-agreed list, quick decisions inside it, escalation outside it. Sales heard speed. Finance heard control. If the two interviewers compare notes, they find a candidate who told both of them the truth.
A simple test before each round: would you be comfortable if this interviewer heard your answer to the previous one? If not, you have two positions, and one of them has to go.
When two interviewers want incompatible things
Sometimes there is no framing that satisfies both. Operations wants the product frozen for six months so they can stabilise delivery. Sales wants three new features by the next trade show. You will be asked, more or less directly, which side you are on.
Do not pick a side to please the person in front of you, and do not retreat into "I would align the stakeholders". Both are heard as evasion. Name the trade-off out loud and then describe how you would decide.
Something like this:
"These two goals pull against each other, and I do not think I can make that disappear. What I would do in the first month is put a cost on each option: what a freeze does to the pipeline, and what three launches do to delivery times. Then I would take that to whoever owns the budget for both teams and ask for a decision on the ratio. If the decision is mine to make, I would protect delivery first and release one feature, the one tied to the most signed revenue."
That answer contains a method, a named decision-maker and a default. The interviewer may disagree with your default. Fine. People forgive a candidate who would decide differently much more easily than one who refuses to decide.
One caution. You are an outsider with an hour of context, so state your default as a starting position that the numbers could change.
Questions that surface the disagreement
You are allowed to investigate. The rounds with other departments are the best chance you will get to see how the organisation argues with itself, and a few questions do most of the work.
- "If this hire goes well, what changes for your team in six months?" Ask it of every interviewer and compare the answers afterwards.
- "Where does your team's priority most often collide with the team I would be joining?"
- "When that happens today, who makes the call?"
The last question matters most. If two interviewers give the same name, there is a working arbitration route, and the job is manageable. If they name different people, or laugh, you have learned that the disagreement currently has no owner. It may be about to get one: you.
What a visible disagreement tells you about the job
Conflicting priorities between departments are normal. A company where sales and finance want identical things is either very small or not paying attention. So the disagreement on its own is not a warning.
What matters is how it shows up. When interviewers describe the tension openly and agree on who settles it, you are looking at a healthy company with a hard job on offer. When each one describes the role as if the others did not exist, the job description is hiding an unresolved fight, and the new hire inherits it without the authority to end it. When one interviewer criticises another department to a candidate they met forty minutes ago, believe what you are seeing.
None of this has to mean turning the offer down. It changes what you negotiate. If nobody owns the trade-off, ask before you sign who you would escalate to and how success gets measured when two teams score you differently. Get the answer from the hiring manager, in writing if you can.
Before the loop, write one line per department: what they want from this role and what they fear from it. After the loop, rewrite those lines from what you heard. The gap between the two versions is the real job description.
Keep that second version. It is the first document you will want in week one.