You are getting urgent, conflicting priorities from two different managers. Walk me through a time that happened and how you resolved it.
What they are really testing: They are testing whether you escalate cleanly or become the battleground. A mid engineer who quietly tries to serve both and fails both is a real risk to a matrixed org.
A real interview question
You are getting urgent, conflicting priorities from two different managers. Walk me through a time that happened and how you resolved it.
What most people say
drag me
“I tried to do both. I worked on the platform migration during the day and the reporting dashboard in the evenings so nobody was disappointed.”
Serving both means committing to a schedule nobody agreed to, and it usually ends with two half done things and one burnt out engineer. It also removes the information the managers needed to make a real call about their own priorities.
The follow-ups they ask next
What if the two managers refuse to agree and both keep pushing?
Then it goes up one level, calmly and in writing. Say you will proceed on your best guess and name it explicitly, so silence becomes a decision they can veto.
Did this damage your relationship with the manager who lost?
Say what you did to protect it, you kept the deferred item visible and finished it, and you gave him a date rather than a shrug.
How do you decide the priority if nobody will make a call at all?
Fall back on blast radius and external commitments, a public launch date or a security exposure beats internal tidiness, and you state your reasoning out loud.
What the interviewer is listening for
- Put both stakeholders in one thread instead of managing the conflict privately
- Attached honest capacity and cost figures to each option rather than vibes
- Proposed a default so the decision could be made in minutes, not days
What sinks the answer
- Quietly picking the louder or more senior manager and hoping the other forgets
- Attempting both by working nights, with no shared record of the trade off
- Complaining about the org structure instead of describing a resolution
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“I have not been shared across two managers, but here is how I would reason about it. I would get both asks into one message with my real capacity and the cost of deferring each, propose a default order, and ask them to correct it rather than deciding silently myself.”
Keep going with behavioural
Foundation
Tell me about a time you had to learn a new technology quickly. How did you go about it?
Foundation
So, why cloud? You have not worked in cloud before, so walk me through what actually pulled you here.
Foundation
Why are you leaving your current job?
Foundation
Tell me about a time you noticed something was broken, wasteful or risky, and nobody seemed to own it. What did you actually do?
Junior
You join a team and inherit a service with no documentation and the original author has left. Walk me through your first week.
Junior
Describe a time you were blocked and there was genuinely nobody available to ask. What did you do?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free