🌏 中文版
Today's Focus
Behavioral interviews get mistaken for "just prepare a few inspiring stories," but what interviewers are actually listening for is the decision structure inside the story: how you read the situation, who you were accountable to, what your actions actually chose to do, and whether the result can be checked. That's why Meta's Leadership and Drive round stacks 4–5 follow-ups on the same story — by the third layer, it's clear whether you were the one actually making the call. Today also closes out the week, so after one influence/conflict question, this post ties together all six topics from Product Sense through Technical PM.
Framework Cheat Sheet
STAR sets the story's skeleton, SBI zooms into the key interaction. The two frameworks do different jobs.
| Framework | Breakdown | What it solves |
|---|---|---|
| STAR | Situation → Task (your responsibility) → Action (what you actually did) → Result (a checkable outcome) | Keeps the story from turning into a timeline dump, so the interviewer can grab "what you owned and what you did" in 60–90 seconds |
| SBI | Situation → Behavior (a concrete action, not a personality judgment) → Impact (what that action actually caused) | Replaces vague claims like "I showed leadership" with checkable detail: "he interrupted me twice in the meeting, so I proposed we each list our priorities first and compare" |
Stack them this way: use STAR to lay down the story's four beats, then zoom into the Action beat with SBI to spell out the moment the conflict or influence actually happened — that's exactly where follow-ups usually dig in.
Today's Practice Question
The Question
"Tell me about a time you had to influence a peer with a different priority."
(Source: Meta PM Leadership and Drive interview, documented in Aced/Exponent's interview guide as a recently reported real question)
Breaking It Down
- Clarify: this question names a "peer," not a manager or a senior cross-functional stakeholder — the interviewer wants to see persuasion that works purely on argument and relationship, with no title gap to lean on. Lock onto a story that's genuinely a peer relationship instead of repurposing a "convincing my boss" story.
- Define the roles: state who the other person was, what their priority was, and why it differed from yours — usually because they were reading the same data differently, or accountable to a different metric. Skip this and the "influence" part later just sounds like you won an argument.
- Structure the analysis: lay down the STAR skeleton, then use SBI inside the Action beat — name the specific thing the other person said or did in that discussion (Behavior) and what it actually caused (Impact), then what you did in response.
- Propose a solution: your persuasion method needs to be specific enough to repeat — reframing the problem around data both sides accept? Running a small-scope test and letting the result speak? Finding a higher-level goal both of you actually care about? Avoid "we talked a lot and he eventually agreed."
- Define success: the outcome needs a checkable metric or behavior change (the priority actually shifted, or how you work together afterward changed), and add an honest line about what you'd do earlier next time — that self-awareness is usually the next follow-up anyway, so naming it first lands better.
Sample Answer (how you'd actually say this in an interview)
Start with the situation and why priorities diverged. We had to decide what to build next quarter, and I was pushing for a retention-focused change while a peer on the growth side insisted on something that would drive new signups fast, because his OKR that quarter was tied directly to new-user count. This wasn't a personality clash — we were two people accountable to two different metrics, so whoever argued louder wasn't going to settle it.
Then I'd describe the actual moment and how I responded. In a planning meeting he said flatly, "the retention change won't show results fast enough for me to report to my manager." I didn't push back immediately — I proposed we each write up our expected impact on the same table, using the same historical data to estimate each option's contribution to the company's north-star metric over three months, instead of arguing from gut feeling. The point wasn't whose plan would win — it was moving the conversation from "your metric versus mine" to "which one actually helps the company more."
Finally, the result and what I'd change. The estimate showed the retention change paying off faster within that three-month window, but it also surfaced that his new-signup change compounded more over six months — so we didn't pick one and kill the other; we shipped a small version of the retention change and scheduled his for the following quarter. If I did it again, I'd walk through that table with him privately before the meeting instead of laying it out live — the conflict would have been much smaller.
Self-Check List
Use this table to check your answer for gaps:
| Check item | Covered? |
|---|---|
| Clearly named that the other person was a "peer," and why your priorities differed | |
| Described the conflict moment with a concrete behavior and its actual impact (SBI), not just "we disagreed" | |
| Named a specific persuasion method — reframing with shared data, a small test, a common goal — not "we talked it through" | |
| Included a checkable result or a real behavior change afterward | |
| Added an honest self-check: what you'd do earlier next time | |
| Bonus: the outcome wasn't a one-sided win — both sides got part of what they wanted |
Today's Case
Airbnb's May 2020 layoff memo: a transparency template inside the worst kind of news
On May 5, 2020, Airbnb co-founder and CEO Brian Chesky sent an internal memo announcing that the company — hit hard by the pandemic's collapse of global travel — would cut roughly 1,900 of its 7,500 employees, about 25% of the workforce. The memo has since been cited repeatedly in media and HR circles as a template for staying respectful and transparent inside the worst news a leader can deliver, not because the writing was elegant, but because the structure was clear: first, how the decision was reached (revenue forecast cut in half, prior steps already taken like cost cuts and a $2B raise, and why those still weren't enough); then, the more focused direction the company would take (pausing Transportation and Airbnb Studios, scaling back Hotels and Lux); and finally, exactly what departing employees would receive (severance, accelerated equity vesting, extended healthcare, job-search support). The memo never dodged the fact that it was a layoff, and it didn't end the explanation at "the external environment did this to us" — it worked through decision logic and concrete impact on the people affected, section by section, so every recipient could follow the structure and know what would happen next.
Interview angle: use this case to answer "give an example of a difficult decision communicated well" or "what does staying transparent under pressure actually look like." The point isn't "Chesky is a good writer" — it's the three-part structure (decision logic → new direction → concrete impact and compensation), which is exactly what today's STAR framework needs inside the Action beat: let the listener see how you thought, not just what you chose.
This Week's Review
| Day | Topic | Practice Question | Self-rating |
|---|---|---|---|
| Mon | Product Sense | Instacart's 35–44 family-subscriber behavior signals are strong, but the app has no matching design — what do you do | ☐ Done ☐ Needs review |
| Tue | Metrics & Analytics | Netflix wants to raise average session length — is that even the right north star | ☐ Done ☐ Needs review |
| Wed | Strategy & Execution | As Zoom's CPO, facing intense competition from Google Meet, what do you do | ☐ Done ☐ Needs review |
| Thu | AI Product Design | A computer-use agent saves time but makes mistakes in 5–10% of sessions — how do you define quality thresholds for launch | ☐ Done ☐ Needs review |
| Fri | Growth & Experimentation | Only 18% of Suno's new creators make a second song within 7 days — how do you break down the funnel and find the key metric | ☐ Done ☐ Needs review |
| Sat | Technical PM | Design a system to detect review abuse on Amazon | ☐ Done ☐ Needs review |
| Sun | Behavioral & Weekly Review | Tell me about a time you had to influence a peer with a different priority | ☐ Done ☐ Needs review |
Next Week's Preview
Next week (10/19–10/25) follows the regular rotation: Mon Product Sense, Tue Metrics & Analytics, Wed Strategy & Execution, Thu AI Product Design, Fri Growth & Experimentation, Sat Technical PM, and back to Behavioral on Sunday. This week practiced "lay out the decision logic before the decision" repeatedly — the Zoom-vs-Google-Meet strategy question, the Amazon review-abuse system design, and today's Airbnb case. Carry that same habit into next week's concrete feature-design questions in Product Sense and Growth.
Further Reading
- Meta Product Manager (PM) Interview Guide — Aced — a full breakdown of Meta's six PM interview rounds; the Leadership and Drive section lists recently reported real questions, and today's practice question comes from here
- STAR Method Examples: 20 Behavioral Answers for 2026 — OphyAI — 20 STAR examples covering leadership, conflict, and failure stories, useful for building out your own story bank
- Microsoft Behavioral & Leadership Questions — PracHub — another big-tech company's behavioral question taxonomy, useful for practicing the same story under a different framing
References
- Meta Product Manager (PM) Interview Guide — Aced — source of today's practice question and what the Leadership and Drive round evaluates
- A Message from Co-Founder and CEO Brian Chesky — Airbnb Newsroom — the original memo in full, published May 5, 2020
- STAR Method Examples: 20 Behavioral Answers for 2026 — OphyAI — source of today's STAR framework structure and examples