Managing Up¶

Theme: Judgement & Influence | Seniority: Senior → Staff

Why This Question Gets Asked¶

Managing up is a different skill from peer influence — there's a real power differential, and your manager controls your ratings, your projects, and often your promotion. Interviewers want to know:

• Can you disagree with someone who evaluates you, without either caving or becoming a problem to manage?
• Do you surface bad news early, or let it surface itself later, worse?
• Can you negotiate scope or timeline instead of silently absorbing an unrealistic ask?
• Do you know the difference between "managing up" and "managing around" (going over their head unnecessarily)?

STAR + Reflection Framework¶

flowchart LR
    S[Situation\nthe call, the stakes] --> T[Task\nyour position,\nwhy you disagreed]
    T --> A[Action\nhow you raised it,\nwhat you proposed instead]
    A --> R[Result\nwhat changed, quantified]
    R --> Ref[Reflection\nhow the relationship held]
    style A fill:#1b5e20,color:#fff
    style R fill:#e65100,color:#fff
    style Ref fill:#37474f,color:#fff

Seniority Differentiation¶

Surfacing Risk Early¶

The core mechanic of "managing up" well is timing: bad news gets cheaper the earlier it surfaces and more expensive every day it's held back hoping it resolves itself.

flowchart LR
    A[Risk identified] --> B{Can I still\nchange the plan?}
    B -->|Yes, cheaply| C[Surface immediately,\nwith options attached]
    B -->|Getting expensive| D[Surface now anyway —\ncost only grows]
    B -->|Already committed| E[Surface + propose\nmitigation, not blame]

When Surfacing It Early Backfired¶

Surfacing risk early doesn't always land well, and it's worth having a story where it didn't. Early in a project, I flagged in a planning meeting — in front of the wider team, not privately first — that I thought our proposed three-week estimate for a data-migration project was closer to six, based on a similar migration I'd done two years earlier. I was right about the estimate, but the way I raised it read as undermining my manager's plan in front of the people he'd just committed it to, and he told me afterward, fairly, that it put him in a position of either overruling me publicly or looking like he hadn't done his homework. The estimate was later revised to five weeks anyway, so I was directionally correct — but the relationship cost was real, and it took a few weeks of deliberately routing concerns to him privately first to rebuild the trust that I wasn't going to contradict him in front of the team again. I learned that being right about the risk doesn't excuse getting the forum wrong; the two are scored separately, by the room and by the manager.

Negotiating Scope vs. Timeline¶

Managers and skip-levels usually don't actually want an impossible date — they want a number they can commit externally, and they often don't know the internal cost of the scope they've implicitly assumed. Your job is to make the trade-off visible, not to simply refuse.

Template: "I can hit [date] if we cut [specific thing]. I can hit [full scope] if we move to [later date] or add [specific resource]. Which trade-off do you want?"

This works because it replaces "no" — which a manager under their own pressure may not be able to accept — with a choice they can actually make.

Disagreeing Without Burning Trust¶

• Raise it privately first, not in a group setting where they have to defend a position publicly.
• Bring the alternative, not just the objection — "here's what I'd do instead" is a different conversation than "this is wrong."
• After the decision is made, commit fully, even if it went the other way — and say so out loud rather than passive-aggressively executing a plan you disagree with.
• If you were overruled and turned out to be right, don't collect the win publicly — the trust cost of "I told you so" outweighs being seen as correct once.

Common Interview Questions¶

1. "Tell me about a time you disagreed with your manager's technical decision."
2. "Describe a time you had to deliver bad news to your manager."
3. "How do you negotiate scope when a deadline is fixed?"
4. "Tell me about a time your manager was wrong — what did you do?"
5. "How do you handle being overruled by someone senior to you?"

Staff-Level Extensions¶

Red Flags in Answers¶

Self-Assessment¶

• [ ] Do I have a story where I surfaced risk early enough that it was still cheap to fix?
• [ ] Did I offer explicit trade-offs, not just an objection?
• [ ] Do I have a story where I was overruled and committed fully anyway?
• [ ] Can I describe how the relationship or process changed afterward?
• [ ] For Staff roles: can I describe managing a two-level relationship without going around anyone?