Meta Behavioral Interview: What Gets Scored
- Know what Meta's behavioral round scores and how a weak hour here can sink a strong coder
- Name Meta's six current values from memory, and avoid the two dead Facebook-era ones that flag you as under-prepared
- Tell a first-person STAR story (situation, task, action, result) scoped to your target level
Most Meta loops have exactly one behavioral round. Forty-five minutes, one interviewer, five or six "tell me about a time" questions, and follow-ups that keep digging until your story runs out of detail. The interviewer is doing one thing the whole time: working out who you are once the whiteboard is gone.
Coding and design are what get you hired at Meta, and a good behavioral hour won't rescue a loop where you solved one problem out of two. So people file this round under "soft skills" and wing it. That's the mistake. A weak behavioral sinks strong coders all the time, and it's often where the down-level happens: you came in for E5, the stories came out junior, the offer comes back at E4. Lighter than Amazon's, where the leadership principles are the entire show. Still a gate. This lesson covers how it's scored and how to answer; the next is the question bank.
Meta's six values (get these exactly right)
Meta rewrote its values in February 2022, the same week the company stopped being Facebook. The round grades against the new set, so your stories should land on them without you ever saying their names. There are six.
Move Fast
Ship and learn at speed. Bias toward action over a perfect plan, and treat shipping something testable as the way you find the right answer.
Focus on Long-Term Impact
Optimize for the multi-year win even when it costs you this quarter's metric. Take on the harder bet when the payoff is bigger and further out.
Build Awesome Things
Raise the bar on what you ship. Inspiring, polished work that users can feel in their hands, rather than something that merely passes review.
Live in the Future
Work as if the future Meta is building has already arrived, and design for where the product is going instead of where it sits today.
Be Direct and Respect Your Colleagues
Say the hard thing plainly, and do it with respect. Candid feedback given kindly, the trait the conflict questions probe hardest.
Meta, Metamates, Me
A sense of stewardship. The company first, your teammates ("Metamates") second, yourself last, looking after the mission and each other.
The Meta angleThe eight things the interviewer scores
Below the values sit the traits an interviewer actually marks you on. You'll see them written up as eight focus areas. Meta's internal scorecard collapses them into fewer named competencies (conflict, driving results, ambiguity, growth, communication), so don't memorize the number. Every question is a door into one or two of these. See which trait a question is hunting for and you know which story to reach for.
Motivation and drive
What truly pushes you. The proudest-project and "what gets you out of bed" questions live here.
Proactivity
Whether you act on a problem outside your lane without being told, instead of waiting for the ticket.
Comfort with ambiguity
Making progress when the spec is vague and no one has mapped the path. At Meta you ship into fog often.
Perseverance
Pushing a hard, long problem to a finish when the easy move was to drop it.
Conflict resolution
How you handle a real disagreement with a peer or with management, and whether you resolve it through influence.
Empathy
Reading what a teammate or user really needs underneath what they say, and acting on it rather than just hearing it.
Growth and self-awareness
Owning a mistake, absorbing hard feedback, and naming what you changed afterward.
Communication and storytelling
Whether you can tell a tight, clear story. The delivery gets scored alongside the events themselves.
Conflict and failure aren't on that list, and that's deliberate. They're the situations Meta uses to test several traits at once. One good conflict story shows communication, empathy, and "Be Direct" in a single answer. The next lesson sorts its question bank by these situations, so you build one story per cluster instead of one per question.
Your stories set your level
Meta's ladder runs E3 (new grad), E4 (mid), E5 (senior), E6 (staff), and this round is one of the places your rung gets set. The lever is scope. Two people can show identical skill, and the one whose work reached more people reads as more senior. So while you tell your conflict story, the interviewer is quietly counting: how many people, how many teams, were in the room with you.
E4, team level
Your stories live inside one team. You drove a feature, unblocked a teammate, owned a component. The impact is real but bounded to the people you sit with.
E5, cross-team
Senior. Your stories pull in three or more collaborators and reach beyond your immediate team. You aligned another team's roadmap, drove a decision that touched a partner group, led without a title across team lines.
E6, org wide
Staff. Your stories move two or more teams or shift an org-level direction. You set a technical strategy others built on, or resolved a conflict that ran between whole teams rather than two individuals.
The Meta angleAnswering with STAR
Structure every answer as STAR: Situation, Task, Action, Result. What decides the answer is the time split. Most people burn two minutes setting the scene and then rush the part that actually gets scored. Flip it. Two sentences of setup, and the rest on what you did and what happened. Call it 80 percent of your words living in Action and Result.
Situation
The context in about two sentences. Where you were, what was at stake. Do not narrate the org chart for a full minute.
Task
The specific problem that landed on you. What were you on the hook to solve?
Action
What you did, step by step, in the first person. This is the part that scores, so it gets most of the clock.
Result
How it turned out, with a number wherever one exists. "Cut p99 latency from 800ms to 300ms." "Shipped two weeks early." "Lifted retention four points." A vague result is forgettable; a number sticks.
The Meta angleSame story, two tellings. One earns a No-Hire; the other gets you leveled at E5.
Weak: vague and all "we"
- "We had a disagreement with the data team about the schema, so we talked it through and eventually we got the migration done."
- All "we," no specific action, no number, no real tension on the page. The interviewer cannot tell what you personally did or how big the problem was.
- Scope is invisible, so it defaults to the lowest reading. This sounds like an E4 story even if the work was senior.
Strong: specific, "I", cross-team
- Situation & task: "Our payments rollout stalled two weeks out because the data team's schema would not support our event model. I owned our side of the integration across both teams."
- Action: "I set up a working session with their tech lead, mapped the exact point where our models conflicted, and proposed a shared event table neither team had considered. I wrote the migration plan and ran it past both on-calls."
- Result: "We shipped four days early with zero downtime, and the shared table is now used by a third team."
- Learning: "I now pull in dependent teams during design, not at integration time."
The strong version names the tension, stays in the first person, lands two numbers, and reaches across teams. That's what E5 sounds like. And it won't stop there. Expect the digging: "What did their tech lead think of your table?" "What would you have done if they'd said no?" The follow-ups mine the same story for a layer you didn't volunteer, so have that layer ready before you open your mouth.
Prepare about five reusable stories
You don't write a story per question. You bring a small set of strong ones and re-aim them on the fly. Five projects, each rich enough to answer several prompts, covers the whole round. The ones that work have texture: the same project gives you a conflict told one way and a proud win told another. Thin projects can't flex like that, so pick the messy, high-stakes ones over the clean little wins.
Stories that travel
- A project with real friction, where the same events give you a conflict from one angle and a win from another
- At least one story with cross-team scope if you are targeting E5 or above
- A genuine failure you own cleanly, with the change you made afterward
- Concrete numbers attached before you walk in, so the result beat is ready
Stories that stall
- Five separate thin anecdotes, one per question, with no depth for the follow-up questions to mine
- A "failure" that is secretly a humblebrag ("I worked too hard")
- A win where the whole story is "we," with no first-person action to point at
- Badmouthing a past manager or team, which the interviewer marks against the "Be Direct and Respect" value
Tag your five stories to the focus areas before you walk in. One project might cover drive told one way and conflict told another. When the question lands, you don't want to be flipping through your memory; you want to already know which story you're reaching for and which beat opens it. Five well-tagged stories beat twenty half-remembered ones.
Key Takeaways
- ✓The behavioral round is lighter than Amazon's, but it is a real gate: a weak hour can sink a strong coder and it weighs on E5-versus-E4 leveling.
- ✓Meta has six current values (Move Fast; Focus on Long-Term Impact; Build Awesome Things; Live in the Future; Be Direct and Respect Your Colleagues; Meta, Metamates, Me). "Be Bold" and "Be Open" are dead Facebook-era values, so never recite them.
- ✓Your level is set by story scope: E4 is team-level, E5 reaches across three or more collaborators and other teams, E6 moves the whole org.
- ✓Answer in STAR with ~80 percent on Action and Result, say "I" not "we", quantify the outcome, and prep about five rich stories tagged to the focus areas.
Meta interview guideKnow what Meta asks before you walk in.
28 coding · 5 system design · 28 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.