Describe feedback, change, and conflict
Company: Meta
Role: Data Scientist
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Technical Screen
In the behavioral portion of the onsite, answer the following leadership questions using concrete examples from your work:
1. Tell me about a time you gave constructive feedback to a teammate or cross-functional partner.
2. Tell me about a time you had to pivot quickly because priorities, data, or business conditions changed.
3. Tell me about a time you had conflict with a stakeholder and how you resolved it.
For each story, explain the context, your specific role, the trade-offs you considered, how you communicated, and the measurable outcome.
Quick Answer: This question evaluates a data scientist's leadership, communication, stakeholder management, adaptability, and conflict-resolution competencies through concrete workplace examples.
Solution
Use a tight STAR structure for each story: **Situation, Task, Action, Result**. For senior interviewers, add a short reflection at the end: what you learned and what you would repeat or change.
**1. Constructive feedback**
A strong answer shows empathy, specificity, and follow-through.
- Pick a real example where the feedback mattered to team outcomes.
- Describe the behavior, not the person's character.
- Explain how you prepared: concrete examples, desired outcome, private setting.
- Show two-way communication: you listened, asked questions, and adapted.
- End with a measurable or visible improvement, such as faster review cycles, fewer incidents, or better stakeholder trust.
Good signal: you improved the working relationship while still addressing a performance or collaboration issue.
Bad signal: you sound accusatory or focus on being right.
**2. Pivoting during change**
Interviewers want evidence that you can update your plan when new information arrives.
- Choose a case where the original plan was reasonable, but new data changed the decision.
- Explain what signal triggered the pivot: experiment results, leadership reprioritization, market event, or technical blocker.
- Describe how you re-scoped work, communicated trade-offs, and protected the most important deliverables.
- Quantify the result when possible: saved launch time, reduced wasted effort, or improved metric outcomes.
Good signal: you were decisive but data-driven.
Bad signal: the story sounds chaotic, or you changed direction without a clear rationale.
**3. Conflict resolution**
Pick a real disagreement with stakes, ideally cross-functional.
- Frame the conflict as a difference in goals, incentives, or interpretation, not a personality clash.
- Show how you clarified decision criteria and aligned on shared goals.
- Use evidence: data, user research, experiment design, or clear success metrics.
- If needed, propose a reversible experiment rather than forcing a debate to be won verbally.
- End with both the outcome and the relationship impact.
Good signal: you can disagree without becoming defensive, and you know when to escalate.
Bad signal: you blame others, avoid the conflict entirely, or never explain the resolution.
**Practical template for each answer**
- Situation: 2 to 3 sentences
- Task: what you owned
- Action: 3 to 5 concrete steps you took
- Result: business outcome plus interpersonal lesson
**Common mistakes**
- too much background and not enough action
- vague claims without measurable outcomes
- stories where you were not the primary actor
- conflict stories that are actually minor misunderstandings
- feedback stories with no evidence that the other person improved
A strong final sentence is reflective, for example: you now standardize expectation-setting earlier, document decision criteria, or create feedback loops before tension builds.