Answer conflict, ambiguity, feedback, difficult coworker prompts
Company: Meta
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Technical Screen
Prepare behavioral answers for these prompts:
1) Describe a time you had a **conflict with your manager**. How did you resolve it?
2) Describe a project where requirements were **very ambiguous**. How did you drive clarity and deliver?
3) Describe a time you **mentored someone** and gave **constructive feedback**.
4) Describe a time you worked with a **difficult collaborator**. What did you do and what was the outcome?
Overview: This question evaluates a candidate's ability to handle conflict with supervisors, clarify ambiguous requirements, provide constructive feedback and mentorship, and manage difficult collaborators.
Read the full Meta Software Engineer interview experience this question came from
Solution
## How to structure each answer (use STAR+R)
- **S**ituation: context and stakes.
- **T**ask: what you owned (your responsibility).
- **A**ctions: 3–6 specific steps you took.
- **R**esult: measurable impact.
- **Reflection**: what you’d do the same/differently.
Keep it factual, avoid blaming, and show judgment and communication.
---
## 1) Conflict with manager
What interviewers look for: professionalism, aligning on goals, escalating appropriately.
Strong actions to mention:
- Clarify the *actual disagreement* (priority, scope, approach, timeline, quality bar).
- Bring data: tradeoffs, risks, user impact, timeline/cost.
- Propose options (A/B) instead of “I’m right.”
- Align on decision rule (customer impact, OKRs, risk).
- If needed, use a neutral third party (tech lead/PM) or documented RFC.
- Commit after decision; don’t sabotage.
Result examples:
- Decision reached with clear owner + follow-up checkpoints.
- Improved relationship via more frequent 1:1s / written updates.
---
## 2) Handling ambiguous requirements
What interviewers look for: product thinking, execution under uncertainty.
Strong actions:
- Identify stakeholders and users; write a short problem statement.
- Convert ambiguity into questions; define non-goals.
- Define success metrics (latency, adoption, revenue, accuracy, etc.).
- Create a thin MVP + iteration plan.
- Make tradeoffs explicit (speed vs correctness vs scope).
- De-risk early (spikes/prototypes) and communicate frequently.
Result examples:
- Delivered MVP by date; iterated based on metrics.
- Reduced rework by documenting requirements and acceptance criteria.
---
## 3) Mentoring + constructive feedback
What interviewers look for: empathy, coaching, raising team bar.
Strong actions:
- Establish context: their goal, expectations, skill gaps.
- Give feedback that is **specific and behavioral** (not personality):
- “In the design doc, X was missing which caused Y risk…”
- Use SBI model: **Situation–Behavior–Impact**.
- Offer a concrete improvement plan: examples, templates, pairing sessions.
- Follow up and recognize progress.
Result examples:
- Mentee shipped feature independently; improved code quality/communication.
- Team velocity increased; fewer bugs/reviews cycles.
---
## 4) Difficult collaborator
What interviewers look for: conflict resolution, influence without authority.
Strong actions:
- Separate people from problem; assume positive intent initially.
- Diagnose why it’s hard: misaligned incentives, unclear ownership, communication style, time pressure.
- Set working agreements: response times, decision process, meeting cadence.
- Use written artifacts (RFCs, action items) to avoid repeated debates.
- Escalate only after attempting direct resolution, and escalate with evidence + proposed solution.
Result examples:
- Delivered project with clear ownership boundaries.
- Relationship improved; future collaboration smoother.
---
## Tips
- Avoid saying “they were incompetent.” Focus on what you did.
- Include at least one example where you changed your mind after learning new info.
- Quantify outcomes (time saved, incidents reduced, launch date met).