Prep by Company
Software Dev Engineer SDE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Solutions Architect SA ML Engineer MLE Technical PM TPM
Guides About Get Your Playbook →
The Bar Raiser's Debrief · Meta Product Manager

"Tell me about a time you proposed or drove a product bet that required conviction against resistance"

Be Bold Product Manager 5–7 min
Why candidates fail: Candidates describe a decision that was eventually validated by consensus rather than showing they maintained conviction against sustained, credible resistance — and they omit the specific data or reasoning that made their bet defensible when most people disagreed.
Two voices. One question. The insider reaction you don't usually see.
Also on YouTube 5–7 min 2026
"Tell me about a time you proposed or drove a product bet that required conviction against resistance"
Competency tested
Be Bold
Who asks it
Bar Raiser · HM · Peer
What they're really asking
Why were you right when credible people disagreed?
The answer that fails — and why
Candidate answer Does not raise the bar — Be Bold

At my last company, I pushed to invest in a creator monetisation feature when the leadership team was focused on growth. A lot of people thought it was too early and would distract us. I believed creators were churning because they couldn't earn, so I put together a proposal, got buy-in from the CPO, and we shipped a tipping feature. Six months later, creator retention improved and leadership came around. It was a risk, but the team eventually saw what I saw from the beginning.

Bar Raiser evaluation
Resistance described as vague hesitation — no credible opposing argument surfaced
No data or reasoning anchoring the bet at decision time
Outcome framed as validation by consensus — not conviction held under pressure
Prefer to hear it? Watch the video for the two-voice delivery with live reaction commentary.
Meta debrief · PM loop · Bar Raiser evaluation Below Bar
Meta Value: Be Bold
Does not demonstrate Be Bold.
Resistance unnamed — no credible stakeholder position or data-backed counterargument presented
Bet rationale absent — candidate states belief but offers no specific evidence held at the time
Conviction not demonstrated — story resolves through CPO buy-in, not sustained independent judgment
Outcome framed as retrospective consensus — 'they came around' signals the candidate waited for validation
interview101.com · Be Bold · Meta PM · Bar Raiser debrief reference
Now here's what a strong answer actually sounds like
The answer that works — in full
Strong answer Raises the bar — Be Bold

We were seeing 22% monthly creator churn on our platform. Leadership's position was that monetisation was a year-two problem — their specific argument was that adding payments infrastructure would slow our growth roadmap by a quarter. I disagreed, and here is why I was confident at the time: our exit survey data showed 61% of churning creators cited inability to earn as their primary reason, not product quality. That meant growth without monetisation was a leaky bucket. I built a lightweight tipping MVP scoped to six weeks, held the line through two roadmap reviews where it was nearly cut, and shipped it without delaying the growth sprint. Creator 30-day retention moved from 41% to 58% in the cohort that used it. The resistance was reasonable given the engineering cost framing — but it was wrong because it misread the churn driver.

Bar Raiser evaluation
Opposing argument named precisely — engineering cost versus growth roadmap trade-off
Bet grounded in specific data held at decision time — 61% exit survey signal
Conviction demonstrated under repeated pressure — survived two roadmap reviews
Candidate explains why resistance was wrong then, not just in hindsight
Meta debrief · PM loop · Bar Raiser evaluation Raises Bar
Meta Value: Be Bold
Strong signal. Raises the bar.
Opposing argument articulated precisely — not dismissed, engaged on its own terms
Conviction anchored in specific pre-decision data — exit survey signal named and quantified
Sustained resistance demonstrated — two roadmap review cutpoints named explicitly
Candidate distinguishes why resistance was wrong at the time, not post-hoc rationalisation
interview101.com · Be Bold · Meta PM · Bar Raiser debrief reference
Run your story through these three questions
1
Can you name the strongest argument against your bet — in the resister's own terms?
If not, the Bar Raiser hears confidence, not conviction — they are not the same thing.
2
What specific data or reasoning made you right at the time — before the outcome?
Without a pre-decision signal, your story sounds like luck dressed up as boldness.
3
Did you hold the position after the first pushback, or did someone senior unlock it for you?
If a CPO or VP approved it, you drove buy-in — you did not demonstrate Be Bold.
Get your personalized report
How do your real stories score?
Get a personalized report scored against the interview rubric Meta uses for your role.
Get your Meta Product Manager report →
Other questions from the same loop
Each video covers a different competency tested in the Meta Product Manager loop
Explore the full Meta Product Manager prep hub