When an interviewer asks how you handle working for more than one manager, the honest subtext is usually: “This job has two bosses, and they will sometimes want different things from you on the same day.” They are checking whether you will make priorities visible and get the managers to agree, or whether you will quietly pick a favourite, overcommit, and let something slip.
The best answers share one move. When requests conflict, you do not decide alone what gets dropped and you do not hide the clash. You lay out the work, the deadlines and the trade-off, and you ask the people with authority to settle it, ideally together. Then you keep both informed.
Below are five annotated examples, from weak to strong, followed by a reusable structure and the follow-up questions to prepare for.
Where this question comes from
Many organisations use a matrix structure, where you report to a line or functional manager for your profession and to one or more project or product leads for day-to-day work. Shared-service roles (an assistant supporting three directors, a designer serving several product teams, a nurse taking direction from a ward manager and a specialist lead) create the same situation.
The tension is well documented. A paper presented at a Project Management Institute research conference notes that project team members “work for more than one boss”, that project managers often have “total responsibility and total accountability but limited authority”, and that the functional manager “usually has the most influence over the resource”. It also observes that people tend to focus their effort depending on who has the main influence on their performance evaluation. Interviewers know this. They want someone who will not be pulled in that direction without saying so.
Five answers, annotated
All examples are illustrative.
Example 1: the non-answer
“I’m very flexible, so I just do whatever each manager asks. I work long hours if needed to get it all done.”
Annotation: This describes a plan to burn out. It also signals that, when time truly runs out, the candidate will decide privately which manager to disappoint. No example, no method.
Example 2: the loyalty answer
“I always prioritise my line manager, because they do my appraisal. The project lead understands that.”
Annotation: At least it is honest, and it shows awareness of reporting lines. But it is exactly the bias the PMI paper describes, and a project lead on the panel will hear “your work comes second”. It also assumes rather than confirms what the project lead understands.
Example 3: the process answer without proof
“I keep a shared task list so both managers can see what I’m working on, and if there’s a clash I ask them to agree the priority.”
Annotation: The right instinct and a good tool. It is still a description of intentions. The interviewer will immediately ask, “Tell me about a time that happened.” Lead with the example instead.
Example 4: a strong office answer
“In my last role I was an executive assistant to the finance director and the operations director. Both kept separate calendars and both assumed I was theirs on Monday mornings, when board papers and the weekly site report were due. One week both asked for urgent work due the same day. I didn’t pick one. I sent them a short joint message listing the two tasks, how long each would take and that I could finish one by noon and the other by 4pm, and asked which should go first. They agreed between them in about ten minutes. Afterwards I suggested a shared request tracker and a fixed Monday priority call, which they both adopted. Clashes didn’t disappear, but they were settled early instead of at 11am on deadline day.”
Annotation:
- Context in two sentences: who the managers were and why clashes happened.
- The key move: one message to both, with time estimates and a concrete choice. The candidate makes the trade-off visible and lets the people with authority decide.
- Neutral tone: no blame on either director.
- Lasting fix: a tracker and a regular check-in, which shows the candidate improved the system rather than just surviving one bad Monday.
Example 5: a strong matrix or project answer
“As a data analyst I reported to the head of analytics, but most of my time was allocated to a pricing project led by a product manager. Midway through, my line manager asked me to rebuild a reporting dashboard that would take about a week, which would have pushed the pricing model past its launch date. Rather than accept both, I booked fifteen minutes with each of them separately to understand the reason behind the request, then proposed a three-way call. I brought a one-page plan showing two options: delay the dashboard by a fortnight, or deliver a simpler version in two days and the full rebuild after launch. They chose the second. The pricing model shipped on time and the simplified dashboard covered the immediate need. I also started sharing a weekly status note with both, so neither had to ask me what I was working on.”
Annotation:
- Understands the structure: names the line manager and the project lead and how time was allocated.
- Finds the underlying need: asking why each request mattered is what made the simplified dashboard option possible.
- Options, not complaints: two workable choices with consequences, presented together.
- Result and habit: a measurable outcome (on-time launch) plus a weekly note that prevents the next clash.
The structure behind the strong answers
Use the STAR format (situation, task, action, result). The UK National Careers Service advises keeping examples “short and to the point” and being ready for follow-up questions. Within the action part, the strong examples above follow the same four beats:
- Make the work visible. A shared list, tracker or status note so both managers see the same picture.
- Spot the clash early. Raise it when you see it coming, not when a deadline has already been missed.
- Bring options with consequences. “If A first, B lands Thursday; if B first, A slips to Monday.”
- Let the decision-makers decide, then confirm in writing. A short follow-up message prevents “I never agreed to that” later.
Public-sector frameworks describe the same behaviours in general terms. The Scottish Government’s success profiles candidate guide defines “Working Together” as forming effective partnerships while “sharing information, resources and support”, and “Communicating and Influencing” as including respecting “the needs, responses and opinions of others”. If the job advert uses these behaviour names, echo them.
Adjusting for the role
| Situation | What to emphasise |
|---|---|
| Assistant or coordinator supporting several executives | Shared calendars, a single request channel, and a regular joint priority check. |
| Specialist in a matrix (analyst, engineer, designer) | Understanding the line manager versus project lead split, and resolving clashes with options. |
| Clinical or shift-based roles | Following the agreed chain of command for patient or operational safety, and escalating to the person in charge of the shift when instructions conflict. |
| Applying for your first job | Use a part-time job with two supervisors, or a university project with two module leads. The structure is the same. |
Mistakes that cost points
- Criticising a former manager, even if one really was unreasonable.
- Claiming you never had a clash. With two bosses, that is not believable.
- Playing managers off against each other, for example using one’s request as an excuse to avoid the other’s.
- Escalating to a third person first without trying to settle it with the two managers concerned.
Follow-up questions to prepare
- “What if both managers insist their work comes first?” Say you would ask them to agree together, and if they cannot, ask who has the final say under the reporting arrangement.
- “How do you keep both informed without drowning them in updates?” Describe a short weekly note or a shared tracker.
- “Have you ever got it wrong?” Have a brief, honest example of a time you overcommitted and what you changed.
If you have handled matrix reporting well, it is worth showing on paper as well as in the interview. A CV line such as “Supported two directors; introduced a shared request tracker” signals the skill before you are asked. The resumebuilder.ae/ resume builder includes layouts for this, and you can check how a draft reads to screening software with the ATS resume score checker.
Frequently asked questions
Is it disloyal to tell one manager that the other’s work clashes with theirs?
No. Being open about workload is what both managers need. Keep it factual: tasks, time estimates and options, without commenting on either person.
Should I mention which manager I preferred?
No. Interviewers listen for even-handedness. Describe both managers neutrally.
What does matrix reporting mean?
It usually means you have a line manager for your discipline and also take day-to-day direction from one or more project or product leads.
Can I use an example where I had to escalate?
Yes, if you first tried to settle it with both managers and then escalated to whoever the arrangement says has the final say. Show that escalation was a last step, not the first.
Sources
- Using performance evaluations to raise individual accountability on project teams, Project Management Institute
- Success profiles: candidate guide (behaviour definitions), Scottish Government
- The STAR method, National Careers Service (UK)