0Tell Me About a Time You Gave Direct Feedback That Was Hard to Hear - Meta Core Values
Proactively gave direct, hard feedback with measurable impact.
Be Open at Meta means candidly sharing honest feedback, even when it is difficult to hear, to accelerate learning and improve outcomes. The core test is whether the candidate proactively gave direct, constructive feedback without waiting for permission or perfect conditions.
Meta values speed and impact; being open means candidly surfacing issues early to prevent costly delays or defects, not waiting for perfect data or consensus.
- Avoiding difficult conversations to keep peace
- Waiting for manager approval before giving feedback
- Giving vague or sugar-coated feedback to avoid discomfort
- Only providing feedback when asked or in formal reviews
- Confusing openness with oversharing irrelevant personal opinions
Shows proactive awareness and ownership to identify issues without prompting.
Demonstrates courage and commitment to truth over politeness, core to Be Open.
Shows emotional intelligence and skill in delivering hard truths effectively.
Meta prioritizes impact; showing measurable benefit elevates the story.
Shows initiative and ownership beyond assigned scope, critical at Meta.
Demonstrates growth mindset and self-awareness, valued at Meta.
Spend about 50 seconds total on Situation and Task combined, then devote 70% of your answer time to Action steps showing how you gave direct feedback, and finish with a clear Result including impact metrics.
- Tell me about a time you gave direct feedback that was hard to hear.
- Describe a situation where you had to be candid with a teammate despite discomfort.
- Give an example of when you challenged someone’s idea openly.
- Have you ever had to deliver difficult feedback quickly to avoid impact?
- Tell me about a time you helped improve a process or product.
- Describe a situation where you noticed a problem no one else raised.
- Give an example of when you influenced a team decision.
- Have you ever had to speak up when others stayed silent?
Keywords: direct feedback, candid, hard to hear, challenge, speak up, uncomfortable conversation, impact, unblock, prevent delay.
I just told them what I thought without much preparation.
Appears impulsive and insensitive, risking relationship damage.
I considered their perspective and framed feedback around impact, using specific examples to keep it constructive.
They got defensive and I dropped the topic.
Shows inability to persist or manage conflict productively.
They were initially defensive, so I listened actively and clarified my intent, which helped us align and improve.
I gave feedback and assumed they would fix it.
Shows lack of follow-through and accountability.
I checked in after a week, offered help to implement changes, and tracked progress until resolved.
No, I think I handled it perfectly.
Appears closed to feedback or reflection.
Next time, I would prepare more by anticipating reactions and framing feedback even more collaboratively.
Amazon expects candidates to fix root causes and take full ownership end-to-end, not just give feedback.
Name the trade-offs you made: 'I delayed my sprint tasks by two days to fix the root cause, because the cost of inaction was $8K/week. I also proposed a monitoring alert to prevent future issues.' This shows long-term thinking and ownership beyond feedback.
Google values open, respectful communication that challenges ideas but preserves psychological safety.
Explain how you balanced candor with empathy: 'I used data to support my points and invited their perspective, which led to a productive discussion and better solution.'
Meta prioritizes speed and impact; being open means candidly surfacing issues early to prevent costly delays or defects, not waiting for perfect data or consensus.
Lead with how you balanced speed and candor: 'I had 70% of the info and chose to give direct feedback quickly rather than wait for full certainty, managing risk by framing it as a hypothesis. This prevented a 3-day delay affecting 10K users.'
Legacy Facebook combined rapid iteration with radical candor; feedback was expected to be blunt but constructive to accelerate product cycles.
Highlight how your direct feedback shortened the feedback loop and prevented wasted effort: 'I told the PM directly that the design was unscalable, which led to a pivot saving 2 weeks of development.'
Gives direct feedback on a problem or behavior within own team or immediate scope; shows individual contribution and some impact; no cross-team complexity required.
Gives candid feedback that influences multiple stakeholders or teams; demonstrates thoughtful framing to avoid defensiveness; quantifies impact on delivery or quality.
Proactively identifies systemic issues beyond own team and gives direct feedback that leads to process or product improvements; manages complex interpersonal dynamics; drives measurable impact across teams.
Leads culture change by modeling radical candor at scale; coaches others on giving and receiving hard feedback; influences leadership decisions through open, data-driven communication; drives long-term organizational impact.
Shows initiative beyond own team, courage to speak up, and impact by preventing costly delays.
Demonstrates technical insight, courage to give hard feedback, and impact on product stability.
Shows upward candor and impact on team efficiency or culture.
- Effort Without Initiative - Staying late or working hard on assigned tasks is execution, not being open or proactive feedback.
- Feedback Only in Formal Reviews - Waiting for scheduled reviews lacks speed and candor; Meta expects timely, direct feedback.