How do you manage performance and disagreements?

Behavioral prompts for managers

Respond to these as a people manager (or manager-level tech lead). Where possible, draw on actual examples.

1. Scope and ownership: What does your team own? How do you connect that scope to organizational goals, and which metrics are you accountable for?
2. Managing a poor performer: How do you spot performance problems, give feedback, and carry out an improvement plan while still shielding the rest of the team?
3. Disagreement with your manager: Tell about a time you disagreed with your manager. What did you do, and how did it turn out?
4. Disagreement with cross-functional partners (PM/DS/Eng): Describe a conflict with XFN partners and how you worked through it (tradeoffs, decision process, and communication).

Overview: This question assesses leadership and people-management skills: defining team scope and ownership, tying metrics to organizational goals, recognizing and correcting poor performance, and resolving disagreements with managers and cross-functional partners.

Solution

How to structure behavioral answers for managers

Use a consistent structure so you stay concise and believable.

Suggested template (STAR + leadership layer)

• Situation: background, stakes, and the people involved.
• Task: what you were responsible for and what a successful outcome looked like.
• Actions: what you did, including sequence, decision points, and communication.
• Result: measurable outcomes plus what you learned.

Add a manager-specific layer:

• How you set expectations, tracked progress, coached, and managed alignment.

---

1) Team scope / org goals / metrics ownership

What interviewers are looking for

• You can turn strategy into execution.
• You take ownership of outcomes through measurable metrics.

Elements of a strong answer

1. Define the scope in one or two sentences
   • Product area, customers, and boundaries (what you do and what you do not do).
2. Link it to organizational goals
   • For example, growth, retention, cost, reliability, compliance.
3. Metrics you own (leading and lagging)
   • Lagging metrics: revenue, conversion, retention, SLA.
   • Leading metrics: latency, error rate, funnel step drop-offs, experiment win rate.
4. Operating rhythm
   • Weekly reviews of metrics, roadmap, and incidents.

Example metric framing

• North Star metric: checkout conversion rate.
• Supporting metrics: cart load latency p95, checkout failure rate, pricing mismatch rate, SEV incidents, on-call load.

---

2) Managing a poor performer

What interviewers are looking for

• You identify root causes (skill vs will vs context).
• You act directly, fairly, and with documentation.
• You can keep team delivery on track while supporting the person.

Step-by-step method

1. Catch problems early using specific signals
   • Deadlines missed, weak review quality, recurring incidents, poor collaboration.
2. Make expectations clear
   • What good performance looks like (quality bar, autonomy, communication).
3. Provide timely, specific feedback
   • Apply the SBI model (Situation–Behavior–Impact).
4. Identify the root cause
   • Skill gaps (training), role mismatch (reassignment), personal issues (support), unclear requirements (process).
5. Put together an improvement plan
   • A 30/60/90 day plan with concrete milestones.
   • Weekly check-ins and a written recap.
6. Offer support
   • Mentoring, pairing, smaller work assignments, clear success criteria.
7. Protect the team
   • Risk management: rebalance critical-path work and ensure coverage.
8. Escalate if necessary (PIP / performance process)
   • Involve HR early and document objectively.

Mistakes to avoid

• Delaying action.
• Giving vague feedback such as “be more proactive.”
• Allowing performance issues to surface as a surprise during reviews.

---

3) Disagreement with your manager

What interviewers are looking for

• You can voice disagreement and still commit.
• You can influence upward using data and empathy.

A practical playbook

1. Align on goals: confirm you are optimizing the same objective.
2. Bring data and options:
   • Present two or three alternatives with tradeoffs (time, risk, cost).
3. Surface risks explicitly:
   • “If we choose A, the risk is X; the mitigation is Y.”
4. Decide and commit:
   • If your manager decides differently, commit publicly and execute.
5. Retrospect:
   • After the results are in, review what happened without assigning blame.

Signals of a strong result

• Faster decisions.
• Stronger alignment.
• A better plan because risks were surfaced.

---

4) Disagreement with XFN (PM/DS/Eng)

What interviewers are looking for

• You can manage ambiguity and competing incentives.
• You avoid thrash by defining decision mechanisms.

A framework

1. Make incentives explicit
   • PM: user value and the roadmap.
   • DS: measurement validity and experimentation.
   • Eng: feasibility, reliability, and cost.
2. Define decision owner and DACI/RACI
   • Who decides versus who advises.
3. Agree on success metrics and guardrails
   • For example, ship a growth experiment with reliability SLO guardrails.
4. Run structured tradeoff discussion
   • Options, impact sizing, risks, and reversibility.
5. Document and communicate
   • A one-pager plus a decision log.

Edge cases worth mentioning

• Conflicting metrics (short-term conversion versus long-term retention).
• Disputes over data quality (instrumentation gaps).
• Launch versus reliability (requiring phased rollout, feature flags, canarying).

---

Quick preparation tips

• Prepare two or three stories that can be reused across prompts:
  1. A performance/coaching story
  2. A strategic alignment story
  3. An XFN conflict story
• For each story, write out in advance:
  • Stakes, your role, the hardest moment, the decision, and measurable outcomes.
• Keep answers to about 2–3 minutes, then go deeper when prompted.