A B2B SaaS product at $40M ARR has slowed from 30% to 5% annual growth, net revenue retention is 96%, and you have three squads for the next 24 months; what strategy do you choose and what do you do first?

I would spend six weeks separating a retention problem from market saturation, then fund one core recovery bet and one tightly gated adjacency rather than spread three squads across ideas. - I would split growth by acquisition cohort, segment, expansion, and churn; 96% net retention makes fixing the core value leak the first priority unless one small segment is masking strong retention elsewhere. - Two squads would target the largest verified retention driver, with a six-month goal of lifting net retention from 96% to 102%, while the third runs paid tests in one adjacent segment. - The adjacency earns more funding only after 10 paid pilots show at least 60% activation and a credible path to a $10M serviceable market. - At months 6 and 12, I would shift capacity toward the bet beating its threshold and stop any bet missing two consecutive checkpoints.

The company vision is to become the operating system for independent retailers, the board wants 25% ARR growth within 12 months, and four squads have proposed 18 unrelated features; what product strategy do you set?

I would turn the broad vision into a 12-month choice to win multi-location retailers through faster setup and daily inventory workflows, not approve an 18-feature roadmap. - I would select one ideal customer profile, such as retailers with 3 to 20 stores, after confirming its retention and revenue pool can support the 25% growth target. - Two squads would cut onboarding from 14 days to 3, one would deepen the inventory workflow used weekly, and one would improve the integration layer that removes adoption blockers. - I would reject custom enterprise reporting and single-store edge cases for this cycle because neither strengthens the chosen path to win. - The strategy would carry quarterly targets of 60% activation, 4% monthly logo churn, and $5M in qualified segment pipeline so the board can judge the choices, not feature output.

You have 20 engineers for 18 months: segment A produces $8M ARR with 92% retention and 5% growth, segment B produces $2M ARR with 40% growth but 78% retention, and segment C has a $4M pipeline but requires a 12-month compliance build; which segment do you deprioritize?

I would deprioritize segment C, stabilize A as the economic base, and give B a small retention test before treating its growth as strategic. - A already pays for the portfolio, so 14 engineers would address its biggest churn causes with a target of moving retention from 92% to 96% within two renewal cycles. - B gets six engineers for a 90-day cohort test; I would expand only if new customers retain above 88% and acquisition payback stays under 12 months. - C's $4M pipeline is not revenue, and a 12-month compliance build would consume most of the horizon before proving repeatable demand. - I would tell sales that C is excluded for 18 months and require at least $10M of qualified, multi-customer demand before reopening the decision.

An enterprise strategy needs six months of engineering and revenue will lag by 18 months, but after 90 days only 8 design partners have tested the prototype; what evidence would make you continue, pivot, or stop?

I would continue only if the 90-day evidence clears pre-agreed adoption, buyer, and delivery gates; otherwise I would pivot once or stop before the six-month build. - At least 6 of 8 partners must complete the target workflow weekly for four weeks and cut a measured task by 30%, not merely praise the prototype. - At least 4 buyers must sign a paid pilot or letter with price and procurement timing, giving evidence beyond user enthusiasm. - Engineering must confirm that the production version fits the six-month estimate within a 20% range and does not hide an unstaffed compliance dependency. - If one gate misses, I would run one 30-day correction; if two miss or the same gate misses twice, I would stop and return the team to the core roadmap.

The CEO needs $5M more EBITDA in the next 12 months, while your proposed API platform costs $3M now and is forecast to unlock $8M ARR in year two; with five squads available, how do you resolve the conflict?

I would not ask the company to choose between the goals blindly; I would stage the API bet behind a 90-day proof while keeping most capacity on the 12-month EBITDA commitment. - Finance and I would rebuild the $8M forecast from named use cases, expected attach rate, price, and sales timing, then show the downside case alongside the $3M cost. - One squad and no more than $750,000 would deliver the narrowest API used by three committed customers, with paid contracts or $1M qualified pipeline as the next funding gate. - Three squads would pursue margin and retention work tied directly to the $5M target, while one squad protects reliability so the portfolio does not borrow EBITDA from future incidents. - After 90 days, I would fund the platform only if the evidence preserves a credible year-two return above 2x; otherwise I would stop it and move the squad to the company goal.

A legacy add-on generates $6M ARR at 20% gross margin, migration to a new platform will lose an estimated $1.2M in year one but can reach 75% margin and add $4M ARR in year two, and the company has 18 months of runway; do you migrate now?

I would start a phased migration now only if the downside cash model keeps runway above 12 months and early cohorts prove the year-two economics. - I would migrate the lowest-risk 10% of customers first and require at least 85% conversion with support cost per account falling 40% within 90 days. - Existing customers would receive a 12-month price bridge and assisted migration, limiting avoidable churn while preserving a clear end date for the legacy add-on. - Finance would track the $1.2M revenue loss, cash burn, gross margin, and expansion separately so a margin improvement cannot conceal failed demand. - If two cohorts miss 85% conversion or runway falls below 12 months, I would pause migration; if they pass, I would retire the legacy product within 15 months.

Your SMB analytics product has $25M ARR, and an enterprise compliance adjacency appears to offer a $500M TAM, but it needs 12 engineers for nine months, sales cycles rise from one to nine months, and only 3 of 20 interviews show willingness to pay; do you enter?

I would not fund a full enterprise entry from this evidence; I would run a 90-day paid wedge test with four people and preserve the SMB roadmap. - I would replace the $500M top-down TAM with a bottom-up market of reachable accounts, expected contract value, win rate, and nine-month sales capacity. - The wedge would solve one compliance job using our existing analytics advantage, rather than build the complete enterprise control suite. - Entry requires three paid design partners, at least $300,000 in contracted value, and 8 of the next 15 buyer interviews confirming the same urgent job. - If those gates fail after 90 days, I would stop; if they pass, I would fund the remaining eight engineers in stages against implementation and renewal evidence.

Competitors copy your visible features within three months, and you can spend $4M over 18 months on only two of these options: 50 integrations, proprietary benchmark data, a 30% price cut, or a deeper approval workflow; which two do you choose?

I would invest in proprietary benchmark data and the deeper approval workflow because they can compound into a defensible system, while a price cut and a long undifferentiated integration list cannot. - Benchmark data becomes more useful as participation grows, so I would seek 1,000 contributing accounts and prove that insights improve a customer outcome by at least 10%. - The approval workflow raises switching cost only if it becomes embedded across roles, so I would target 60% weekly use among accounts with five or more approvers. - I would build only the 10 integrations required by those workflows, not spend the budget on 50 connectors competitors can match. - I would reject the 30% price cut unless win-loss data shows price causes more than half of losses, because it sacrifices margin without creating an advantage.

A 120-person product organization with six squads must lift gross retention from 84% to 90% in 12 months, but the current roadmap contains 40 initiatives; what strategy do you communicate in the first 30 days, and what do you cut?

I would replace the 40-item roadmap with one retention strategy, three measurable choices, and an explicit rejection list that every squad can use without asking me. - I would publish the diagnosis and metric tree, naming the two churn moments that explain at least 70% of lost ARR and setting quarterly retention targets of 86%, 88%, and 90%. - Four squads would own those churn moments, one would protect reliability, and one would test the next largest cause rather than keep six unrelated backlogs. - Any initiative unable to show a plausible effect on activation, recurring value, or renewal within two quarters would be cut, including executive requests under the same rule. - After 30 days, I would ask a sample of 20 people to explain the choices and run a monthly review of outcomes, stopped work, and new evidence.

A competitor cuts price by 40% and ships an AI feature in one quarter; your product has $30M ARR, 70% gross margin, 8% annual churn, 55% of users depend on a unique integration, and three squads are fixed for the next two quarters; what do you decide within two weeks?

I would not match the 40% cut broadly; I would defend the integration-led segment, test whether AI changes buying behavior, and set a two-quarter trigger for a larger pivot. - Within two weeks, I would segment renewals and 30 recent win-loss calls by price sensitivity, AI demand, and integration use to identify which assumption actually changed. - One squad would deepen the unique integration for the 55% who use it, while a second ships the smallest AI workflow that 10 committed customers agree to test. - The third squad would address exposed renewals with targeted packaging, capped at a 15% concession, instead of destroying margin for customers who are not at risk. - If AI drives over 25% of qualified losses or test users improve the target task by 20%, I would reallocate next-quarter capacity; otherwise I would keep the differentiated course.

You have one squad for 10 weeks and three roadmap options: an onboarding redesign estimated to add $600k ARR at 40% confidence, an enterprise audit log worth $350k ARR at 80% confidence, and a retention fix expected to prevent $500k churn at 60% confidence. Each takes the full 10 weeks. Which do you choose?

I would choose the retention fix because its confidence-adjusted value is highest at $300k and it protects revenue we already earned. - The onboarding redesign scores $240k after confidence adjustment, while the audit log scores $280k and the retention fix scores $300k. - I would verify that the $500k churn estimate is incremental and that the affected customers are actually saveable before locking the squad for 10 weeks. - The trade-off is delaying the audit log despite its 80% confidence, so I would ask sales whether a two-week manual export can protect the most time-sensitive $350k pipeline. - I would set a week-four checkpoint on the retention leading indicator and switch to the audit log if the expected churn reduction is not tracking toward at least $300k.

Two initiatives compete for six engineers next quarter: A has impact 9/10, effort 24 engineer-weeks, and 50% confidence; B has impact 6/10, effort 12 engineer-weeks, and 90% confidence. You cannot split the team. Which enters the roadmap?

I would put B on the roadmap because its confidence-adjusted impact per engineer-week is 0.45 versus 0.19 for A. - I calculate A as 9 x 0.50 / 24 = 0.19 and B as 6 x 0.90 / 12 = 0.45, so B returns about 2.4 times more expected impact per unit of capacity. - B uses only half the available 24 engineer-weeks, leaving 12 weeks for reliability work or a follow-on bet instead of consuming the whole quarter. - I would spend at most two engineer-weeks testing A's riskiest assumption; if confidence rises from 50% to above 80%, its score reaches 0.30 but still does not beat B. - The trade-off is passing on A's larger upside, and I would state that explicitly rather than presenting the score as objective truth.

A customer representing 18% of ARR will renew a $1.8M contract only if you deliver a custom approval workflow in eight weeks; the same squad is scheduled to ship a roadmap capability requested by 35 customers and forecast to add $1.2M ARR. What do you choose?

I would protect the renewal only if we can turn the approval workflow into a configurable capability for the target segment, not a permanent one-customer fork. - Losing $1.8M now outweighs the forecast $1.2M, but an account at 18% of ARR is already a concentration risk that should not dictate the product indefinitely. - I would give discovery one week to test whether at least 8 of the 35 roadmap customers share the approval need and whether a configurable version still fits the eight-week deadline. - If it generalizes, I would ship a narrow version in seven development weeks and move the $1.2M capability back one cycle with a named revenue cost. - If it requires customer-specific branching, I would decline the feature and offer services or an integration, accepting the renewal risk rather than adding an estimated 20% maintenance burden to every future release.

A shared billing platform needs two squads for 12 weeks and should cut delivery effort for four product teams by 30% from next quarter; alternatively, those squads can ship two visible features forecast to generate $450k this year. The company must reach break-even in nine months. Which investment do you make?

I would fund the platform only if the recovered capacity is worth more than $450k within the nine-month break-even window; otherwise I would ship the revenue features now. - Assuming six engineers per squad, four teams each spending 20 engineer-weeks per quarter on billing would save 24 engineer-weeks per quarter at 30%, which repays the platform's 144 engineer-weeks only after six quarters and is too slow for this constraint. - On those numbers I would choose the two features, book the $450k forecast, and reserve one engineer per squad to remove the highest-cost billing bottlenecks incrementally. - I would reconsider if billing work is actually 60 engineer-weeks per team per quarter, because 72 saved weeks per quarter would repay the investment in two quarters. - The trade-off is continued duplication and slower delivery next year, and I would show that debt in the roadmap rather than letting the platform case disappear.

You control four squads for a 12-week quarter: Checkout needs two squads to pursue a projected $2M conversion gain, Compliance needs one squad to meet a fixed deadline, and Search asks for two squads to address $900k annual churn. How do you allocate the squads?

I would assign one squad to Compliance, two to Checkout, and one to the highest-churn slice of Search rather than pretending all three programs can run at full scope. - Compliance gets one squad because missing the fixed deadline is not a deferrable revenue trade-off; I would confirm the minimum scope with legal before planning anything else. - Checkout keeps two squads because the $2M upside is the largest discretionary outcome and splitting its tightly coupled work could erase the 12-week delivery window. - Search receives one squad to target the segment responsible for at least 60% of the $900k churn, with the rest of the search redesign deferred by one quarter. - The cost is slower Search recovery, so I would cap Checkout discovery at two weeks and reassign one squad if its projected gain falls below $1M after validation.

At week five of a 12-week cycle, a new partner opportunity worth $1.5M requires one squad for six weeks; your three squads are 60% through initiatives worth $800k, $700k, and $300k respectively, and switching costs one week. Do you reallocate?

I would pause the $300k initiative and reallocate that squad because the partner opportunity still has positive incremental value after the switching cost. - The squad has about 4.8 weeks of planned work left, so finishing the $300k item plus six partner weeks does not fit in the seven weeks remaining. - Switching immediately consumes one week and leaves six execution weeks, matching the partner deadline while preserving the $800k and $700k initiatives. - I would require a signed commercial commitment or at least 80% deal confidence, making the adjusted partner value $1.2M rather than moving a team for an unqualified pipeline claim. - We forfeit the near-term $300k and strand some completed work, so I would preserve a releasable slice only if it takes no more than three engineer-days.

Your three squads provide 72 engineer-weeks per quarter. Reliability incidents consumed 18 weeks last quarter, core growth asks for 45 weeks, and a new-market experiment needs 18 weeks. What capacity plan do you approve?

I would approve 18 weeks for reliability, 39 for core growth, and 15 for a narrower new-market experiment, keeping the total at 72. - Reliability receives the full 18 weeks because treating last quarter's incident load as unplanned would overstate available product capacity by 25%. - Core growth loses 6 of its requested 45 weeks, so I would cut the lowest-confidence feature rather than spread a 13% reduction across every initiative. - The experiment gets 15 weeks only if that is enough to test demand and willingness to pay; it should not build the full 18-week solution before evidence exists. - I would revisit the allocation monthly, and every 6 weeks saved through fewer incidents would move to growth rather than silently expanding the experiment.

One squad can either build an enterprise integration expected to close $900k ARR at 70% confidence in 12 weeks or improve self-serve activation for a projected $500k annual gain at 90% confidence in six weeks. What is the opportunity cost of your choice, and which option wins?

I would choose the self-serve activation work and use the remaining six weeks for a second comparable bet because its expected value per week is higher. - The integration's confidence-adjusted value is $630k, or $52.5k per week; activation is $450k, or $75k per week. - If the next six-week item can produce more than $180k of adjusted value, activation plus that item beats the integration's $630k total. - The opportunity cost of choosing the integration is the $450k activation gain plus the best use of the remaining six weeks, not merely its 12-week engineering cost. - I would choose the integration instead if the contract is signed contingent on delivery, raising confidence near 100% and making its strategic enterprise reference value material.

Sales wants five roadmap integrations, each worth about $250k pipeline and four engineer-weeks, while product data shows a 10-week onboarding change could improve retained ARR by $1.1M at 65% confidence. You have one squad with 20 engineer-weeks. What do you commit to?

I would commit to the onboarding change and the two integrations with the strongest commercial evidence, exactly filling the 20 engineer-weeks. - Onboarding has $715k confidence-adjusted value, while all five integrations represent $1.25M of pipeline but not necessarily closed ARR. - I would rank integrations by signed commitment, probability to close, reuse across accounts, and maintenance cost, then fund only the top two at four weeks each. - I would reserve two weeks for onboarding instrumentation and rollout, so its total commitment remains 12 weeks and the plan does not rely on zero delivery overhead. - The trade-off is leaving roughly $750k of nominal pipeline unsupported, and sales would see the exact three deals deferred rather than an ambiguous integrations bucket.

A six-month roadmap assumes 240 engineer-weeks, but hiring slips and you now have 180. A contractual launch consumes 60 weeks, reliability needs at least 36, and the remaining initiatives are Growth A at $1.4M impact for 60 weeks at 75% confidence, Growth B at $900k for 36 weeks at 90%, and Platform C saving 30 weeks per half-year for 48 weeks at 80%. What stays?

I would keep the contractual launch, reliability minimum, Growth A, and 24 weeks of a reduced Growth B, while removing Platform C from this half-year. - The fixed commitments consume 96 of 180 weeks, leaving 84; Growth A uses 60 with $1.05M confidence-adjusted impact. - Full Growth B would exceed capacity by 12 weeks, so I would fund a 24-week slice only if it can capture at least two-thirds of the $810k adjusted value. - Platform C saves 30 weeks per half-year but costs 48 now, so it does not repay within this constrained period and would force out nearer-term growth. - The trade-off is carrying platform drag into the next half, so I would schedule C first then unless reliability exceeds 36 weeks again.

Product Manager interview questions

100 real questions with model answers and explanations for Senior Product Manager candidates.

See a Product Manager resume example →

Practice with flashcards

Spaced repetition · Hunter Pass

Questions

retentioncloud

I would spend six weeks separating a retention problem from market saturation, then fund one core recovery bet and one tightly gated adjacency rather than spread three squads across ideas.

I would split growth by acquisition cohort, segment, expansion, and churn; 96% net retention makes fixing the core value leak the first priority unless one small segment is masking strong retention elsewhere.
Two squads would target the largest verified retention driver, with a six-month goal of lifting net retention from 96% to 102%, while the third runs paid tests in one adjacent segment.
The adjacency earns more funding only after 10 paid pilots show at least 60% activation and a credible path to a $10M serviceable market.
At months 6 and 12, I would shift capacity toward the bet beating its threshold and stop any bet missing two consecutive checkpoints.

Why interviewers ask this: The interviewer is testing whether the candidate can diagnose a plateau, concentrate scarce capacity, and attach stop or scale gates to a multi-year strategy.

product-strategysystem-design

I would turn the broad vision into a 12-month choice to win multi-location retailers through faster setup and daily inventory workflows, not approve an 18-feature roadmap.

I would select one ideal customer profile, such as retailers with 3 to 20 stores, after confirming its retention and revenue pool can support the 25% growth target.
Two squads would cut onboarding from 14 days to 3, one would deepen the inventory workflow used weekly, and one would improve the integration layer that removes adoption blockers.
I would reject custom enterprise reporting and single-store edge cases for this cycle because neither strengthens the chosen path to win.
The strategy would carry quarterly targets of 60% activation, 4% monthly logo churn, and $5M in qualified segment pipeline so the board can judge the choices, not feature output.

Why interviewers ask this: A strong answer distinguishes an enduring vision from a time-bound set of choices that allocates teams and supports a measurable company goal.

retentionci-cd

I would deprioritize segment C, stabilize A as the economic base, and give B a small retention test before treating its growth as strategic.

A already pays for the portfolio, so 14 engineers would address its biggest churn causes with a target of moving retention from 92% to 96% within two renewal cycles.
B gets six engineers for a 90-day cohort test; I would expand only if new customers retain above 88% and acquisition payback stays under 12 months.
C's $4M pipeline is not revenue, and a 12-month compliance build would consume most of the horizon before proving repeatable demand.
I would tell sales that C is excluded for 18 months and require at least $10M of qualified, multi-customer demand before reopening the decision.

Why interviewers ask this: The interviewer wants to see explicit portfolio focus based on retained economics, proof quality, opportunity cost, and a condition for revisiting a rejected segment.

designprototypes

I would continue only if the 90-day evidence clears pre-agreed adoption, buyer, and delivery gates; otherwise I would pivot once or stop before the six-month build.

At least 6 of 8 partners must complete the target workflow weekly for four weeks and cut a measured task by 30%, not merely praise the prototype.
At least 4 buyers must sign a paid pilot or letter with price and procurement timing, giving evidence beyond user enthusiasm.
Engineering must confirm that the production version fits the six-month estimate within a 20% range and does not hide an unstaffed compliance dependency.
If one gate misses, I would run one 30-day correction; if two miss or the same gate misses twice, I would stop and return the team to the core roadmap.

Why interviewers ask this: This tests whether the candidate converts a long-lag strategy into falsifiable leading indicators and acts on thresholds instead of defending sunk work.

api

I would not ask the company to choose between the goals blindly; I would stage the API bet behind a 90-day proof while keeping most capacity on the 12-month EBITDA commitment.

Finance and I would rebuild the $8M forecast from named use cases, expected attach rate, price, and sales timing, then show the downside case alongside the $3M cost.
One squad and no more than $750,000 would deliver the narrowest API used by three committed customers, with paid contracts or $1M qualified pipeline as the next funding gate.
Three squads would pursue margin and retention work tied directly to the $5M target, while one squad protects reliability so the portfolio does not borrow EBITDA from future incidents.
After 90 days, I would fund the platform only if the evidence preserves a credible year-two return above 2x; otherwise I would stop it and move the squad to the company goal.

Why interviewers ask this: The interviewer is evaluating whether the candidate can surface a real company-level trade-off, tranche a long-term bet, and make the funding decision financially accountable.

estimationmigrationscss

I would start a phased migration now only if the downside cash model keeps runway above 12 months and early cohorts prove the year-two economics.

I would migrate the lowest-risk 10% of customers first and require at least 85% conversion with support cost per account falling 40% within 90 days.
Existing customers would receive a 12-month price bridge and assisted migration, limiting avoidable churn while preserving a clear end date for the legacy add-on.
Finance would track the $1.2M revenue loss, cash burn, gross margin, and expansion separately so a margin improvement cannot conceal failed demand.
If two cohorts miss 85% conversion or runway falls below 12 months, I would pause migration; if they pass, I would retire the legacy product within 15 months.

Why interviewers ask this: A strong answer balances runway, cohort risk, customer transition, and unit economics rather than choosing long-term margin on an unsupported forecast.

pricing

I would not fund a full enterprise entry from this evidence; I would run a 90-day paid wedge test with four people and preserve the SMB roadmap.

I would replace the $500M top-down TAM with a bottom-up market of reachable accounts, expected contract value, win rate, and nine-month sales capacity.
The wedge would solve one compliance job using our existing analytics advantage, rather than build the complete enterprise control suite.
Entry requires three paid design partners, at least $300,000 in contracted value, and 8 of the next 15 buyer interviews confirming the same urgent job.
If those gates fail after 90 days, I would stop; if they pass, I would fund the remaining eight engineers in stages against implementation and renewal evidence.

Why interviewers ask this: The interviewer is testing whether the candidate discounts headline TAM, examines transferable advantage and distribution cost, and buys evidence before committing a full team.

I would invest in proprietary benchmark data and the deeper approval workflow because they can compound into a defensible system, while a price cut and a long undifferentiated integration list cannot.

Benchmark data becomes more useful as participation grows, so I would seek 1,000 contributing accounts and prove that insights improve a customer outcome by at least 10%.
The approval workflow raises switching cost only if it becomes embedded across roles, so I would target 60% weekly use among accounts with five or more approvers.
I would build only the 10 integrations required by those workflows, not spend the budget on 50 connectors competitors can match.
I would reject the 30% price cut unless win-loss data shows price causes more than half of losses, because it sacrifices margin without creating an advantage.

Why interviewers ask this: This checks whether the candidate chooses advantages that deepen with data and workflow adoption and ties each proposed moat to evidence rather than labels.

retentioncommunicationroadmap

I would replace the 40-item roadmap with one retention strategy, three measurable choices, and an explicit rejection list that every squad can use without asking me.

I would publish the diagnosis and metric tree, naming the two churn moments that explain at least 70% of lost ARR and setting quarterly retention targets of 86%, 88%, and 90%.
Four squads would own those churn moments, one would protect reliability, and one would test the next largest cause rather than keep six unrelated backlogs.
Any initiative unable to show a plausible effect on activation, recurring value, or renewal within two quarters would be cut, including executive requests under the same rule.
After 30 days, I would ask a sample of 20 people to explain the choices and run a monthly review of outcomes, stopped work, and new evidence.

Why interviewers ask this: The interviewer wants evidence that the candidate can make strategy operational through diagnosis, capacity allocation, refusal rules, and checks that a large organization understood it.

churncss

I would not match the 40% cut broadly; I would defend the integration-led segment, test whether AI changes buying behavior, and set a two-quarter trigger for a larger pivot.

Within two weeks, I would segment renewals and 30 recent win-loss calls by price sensitivity, AI demand, and integration use to identify which assumption actually changed.
One squad would deepen the unique integration for the 55% who use it, while a second ships the smallest AI workflow that 10 committed customers agree to test.
The third squad would address exposed renewals with targeted packaging, capped at a 15% concession, instead of destroying margin for customers who are not at risk.
If AI drives over 25% of qualified losses or test users improve the target task by 20%, I would reallocate next-quarter capacity; otherwise I would keep the differentiated course.

Why interviewers ask this: A strong answer isolates the damaged assumption, avoids a reflexive price war, protects an existing advantage, and defines evidence that would justify changing course.

retentionchurnonboarding

I would choose the retention fix because its confidence-adjusted value is highest at $300k and it protects revenue we already earned.

The onboarding redesign scores $240k after confidence adjustment, while the audit log scores $280k and the retention fix scores $300k.
I would verify that the $500k churn estimate is incremental and that the affected customers are actually saveable before locking the squad for 10 weeks.
The trade-off is delaying the audit log despite its 80% confidence, so I would ask sales whether a two-week manual export can protect the most time-sensitive $350k pipeline.
I would set a week-four checkpoint on the retention leading indicator and switch to the audit log if the expected churn reduction is not tracking toward at least $300k.

Why interviewers ask this: The interviewer is testing whether the candidate can make a numerical choice, challenge the inputs, and preserve an option to change course.

roadmap

I would put B on the roadmap because its confidence-adjusted impact per engineer-week is 0.45 versus 0.19 for A.

I calculate A as 9 x 0.50 / 24 = 0.19 and B as 6 x 0.90 / 12 = 0.45, so B returns about 2.4 times more expected impact per unit of capacity.
B uses only half the available 24 engineer-weeks, leaving 12 weeks for reliability work or a follow-on bet instead of consuming the whole quarter.
I would spend at most two engineer-weeks testing A's riskiest assumption; if confidence rises from 50% to above 80%, its score reaches 0.30 but still does not beat B.
The trade-off is passing on A's larger upside, and I would state that explicitly rather than presenting the score as objective truth.

Why interviewers ask this: A strong answer uses the supplied impact, effort, and confidence figures while recognizing that scoring supports rather than replaces judgment.

roadmap

I would protect the renewal only if we can turn the approval workflow into a configurable capability for the target segment, not a permanent one-customer fork.

Losing $1.8M now outweighs the forecast $1.2M, but an account at 18% of ARR is already a concentration risk that should not dictate the product indefinitely.
I would give discovery one week to test whether at least 8 of the 35 roadmap customers share the approval need and whether a configurable version still fits the eight-week deadline.
If it generalizes, I would ship a narrow version in seven development weeks and move the $1.2M capability back one cycle with a named revenue cost.
If it requires customer-specific branching, I would decline the feature and offer services or an integration, accepting the renewal risk rather than adding an estimated 20% maintenance burden to every future release.

Why interviewers ask this: The interviewer wants a candidate who weighs immediate revenue against concentration, reuse, maintenance cost, and roadmap displacement.

I would fund the platform only if the recovered capacity is worth more than $450k within the nine-month break-even window; otherwise I would ship the revenue features now.

Assuming six engineers per squad, four teams each spending 20 engineer-weeks per quarter on billing would save 24 engineer-weeks per quarter at 30%, which repays the platform's 144 engineer-weeks only after six quarters and is too slow for this constraint.
On those numbers I would choose the two features, book the $450k forecast, and reserve one engineer per squad to remove the highest-cost billing bottlenecks incrementally.
I would reconsider if billing work is actually 60 engineer-weeks per team per quarter, because 72 saved weeks per quarter would repay the investment in two quarters.
The trade-off is continued duplication and slower delivery next year, and I would show that debt in the roadmap rather than letting the platform case disappear.

Why interviewers ask this: The interviewer is assessing whether the candidate can translate platform leverage into a payback period and honor the company's financial horizon.

churnestimation

I would assign one squad to Compliance, two to Checkout, and one to the highest-churn slice of Search rather than pretending all three programs can run at full scope.

Compliance gets one squad because missing the fixed deadline is not a deferrable revenue trade-off; I would confirm the minimum scope with legal before planning anything else.
Checkout keeps two squads because the $2M upside is the largest discretionary outcome and splitting its tightly coupled work could erase the 12-week delivery window.
Search receives one squad to target the segment responsible for at least 60% of the $900k churn, with the rest of the search redesign deferred by one quarter.
The cost is slower Search recovery, so I would cap Checkout discovery at two weeks and reassign one squad if its projected gain falls below $1M after validation.

Why interviewers ask this: The interviewer checks whether the candidate can allocate whole squads around fixed obligations, value, dependencies, and explicit cuts.

I would pause the $300k initiative and reallocate that squad because the partner opportunity still has positive incremental value after the switching cost.

The squad has about 4.8 weeks of planned work left, so finishing the $300k item plus six partner weeks does not fit in the seven weeks remaining.
Switching immediately consumes one week and leaves six execution weeks, matching the partner deadline while preserving the $800k and $700k initiatives.
I would require a signed commercial commitment or at least 80% deal confidence, making the adjusted partner value $1.2M rather than moving a team for an unqualified pipeline claim.
We forfeit the near-term $300k and strand some completed work, so I would preserve a releasable slice only if it takes no more than three engineer-days.

Why interviewers ask this: A strong answer quantifies the switch, demands evidence for the new opportunity, and names both displaced value and sunk work.

experimentsincidentscapacity

I would approve 18 weeks for reliability, 39 for core growth, and 15 for a narrower new-market experiment, keeping the total at 72.

Reliability receives the full 18 weeks because treating last quarter's incident load as unplanned would overstate available product capacity by 25%.
Core growth loses 6 of its requested 45 weeks, so I would cut the lowest-confidence feature rather than spread a 13% reduction across every initiative.
The experiment gets 15 weeks only if that is enough to test demand and willingness to pay; it should not build the full 18-week solution before evidence exists.
I would revisit the allocation monthly, and every 6 weeks saved through fewer incidents would move to growth rather than silently expanding the experiment.

Why interviewers ask this: The interviewer is evaluating whether the candidate plans from real capacity, protects reliability, and reduces scope instead of overcommitting.

activation

I would choose the self-serve activation work and use the remaining six weeks for a second comparable bet because its expected value per week is higher.

The integration's confidence-adjusted value is $630k, or $52.5k per week; activation is $450k, or $75k per week.
If the next six-week item can produce more than $180k of adjusted value, activation plus that item beats the integration's $630k total.
The opportunity cost of choosing the integration is the $450k activation gain plus the best use of the remaining six weeks, not merely its 12-week engineering cost.
I would choose the integration instead if the contract is signed contingent on delivery, raising confidence near 100% and making its strategic enterprise reference value material.

Why interviewers ask this: The interviewer wants the candidate to compare the best displaced alternative, normalize value by time, and identify what new evidence would reverse the choice.

roadmaponboardingci-cd

I would commit to the onboarding change and the two integrations with the strongest commercial evidence, exactly filling the 20 engineer-weeks.

Onboarding has $715k confidence-adjusted value, while all five integrations represent $1.25M of pipeline but not necessarily closed ARR.
I would rank integrations by signed commitment, probability to close, reuse across accounts, and maintenance cost, then fund only the top two at four weeks each.
I would reserve two weeks for onboarding instrumentation and rollout, so its total commitment remains 12 weeks and the plan does not rely on zero delivery overhead.
The trade-off is leaving roughly $750k of nominal pipeline unsupported, and sales would see the exact three deals deferred rather than an ambiguous integrations bucket.

Why interviewers ask this: This tests whether the candidate distinguishes pipeline from retained revenue and turns a crowded request list into a capacity-feasible commitment.

roadmap

I would keep the contractual launch, reliability minimum, Growth A, and 24 weeks of a reduced Growth B, while removing Platform C from this half-year.

The fixed commitments consume 96 of 180 weeks, leaving 84; Growth A uses 60 with $1.05M confidence-adjusted impact.
Full Growth B would exceed capacity by 12 weeks, so I would fund a 24-week slice only if it can capture at least two-thirds of the $810k adjusted value.
Platform C saves 30 weeks per half-year but costs 48 now, so it does not repay within this constrained period and would force out nearer-term growth.
The trade-off is carrying platform drag into the next half, so I would schedule C first then unless reliability exceeds 36 weeks again.

Why interviewers ask this: The interviewer is testing whether the candidate can rebuild a roadmap against hard capacity, sequence payback, and cut scope without hiding the opportunity cost.

Locked questions

21
Checkout conversion is 38% overall, 31% on mobile web and 46% on desktop; leadership wants 45% overall within eight weeks. How would you define the North Star and guardrails so the mobile team cannot hit the target by increasing accidental purchases?
north-starguardrails
22
A B2B collaboration product has 42% workspace activation, 68% 90-day logo retention, and $12 million ARR; enterprise retention is 84% while SMB retention is 61%. Build a metric tree for raising ARR to $15 million over the next 12 months, including leading and lagging indicators.
retentionactivationleading-lagging
23
A new invoicing product has no historical baseline, a six-week beta with 2,000 invited freelancers and 300 small agencies, and a goal of proving enough value to fund a six-month build. What metrics and numeric decision thresholds would you set before the beta starts?
monitoring
24
DAU for a consumer app fell from 800,000 to 680,000 over three days after holding near 800,000 for six weeks; the product serves iOS, Android, and web across the US, Brazil, and Germany. Walk through the first two hours of diagnosis and the cuts you would request.
active-users
25
Paid signup conversion dropped from 6.2% to 4.8% in the 48 hours after a pricing-page release; desktop stayed at 6.1%, mobile fell from 5.7% to 2.9%, and the decline appears in the US and UK but not Canada. How would you diagnose and contain the issue today?
pricing
26
Eight-week retention fell from 34% for January signup cohorts to 25% for March cohorts; enterprise users remain at 52%, SMB users fell from 31% to 20%, and the decline began two weeks after onboarding changed. How would you determine whether onboarding caused the drop?
retentioncohortsonboarding
27
Amplitude reports 1.10 million DAU while BigQuery reports 980,000, a 12% gap that appeared five days after an Android timestamp migration; iOS differs by only 1% and Android users in India show the largest gap. How would you resolve the data-quality incident and decide which number to publish this week?
migrationsbigqueryincidents
28
A Snowflake dashboard says 30-day trial-to-paid conversion rose from 14% in Q1 to 18% in Q2, but Finance sees only 15%; self-serve appears at 21% and sales-assisted at 11%. What SQL and warehouse checks would you ask for before claiming a win?
sqlwarehousesnowflake
29
Onboarding completion rose from 52% to 64% over six weeks, but 90-day retention stayed at 28%; the lift is 16 points for paid-social users and 5 points for organic users, with no retention change in either segment. Would you keep onboarding completion as a leading metric for the next quarter?
retentiononboardingmonitoring
30
Weekly active teams grew from 120,000 to 150,000 in one quarter, yet net revenue retention fell from 108% to 99%; free teams grew 40%, paid teams grew 3%, and paid teams with more than 50 seats contracted 9%. How would you revise the North Star and operating review for the next two quarters?
north-starretentionzero-to-one
31
Checkout converts at 8.0%, you have 120,000 eligible users per week, and a 0.4 percentage-point lift is the smallest win worth shipping; at 80% power and alpha 0.05, what sample and runtime would you choose?
32
Trial-to-paid conversion is 1.5% across 40,000 eligible users per month, and Finance cares about a 0.1 percentage-point lift; with 80% power and a two-sided alpha of 0.05, do you run the test if Marketing suggests alpha 0.10 to make it faster?
33
A B2B onboarding test reaches its planned 60,000 exposures in five days, but the primary metric is 7-day activation and Monday cohorts activate at 42% versus 32% on Friday; do you call the result on day five, and what runtime do you use?
cohortsactivationonboarding
34
An AI drafting feature raises documents per user from 4.0 to 5.2 in week one but only to 4.3 by week four, while 30-day retention moves from 61% to 60% and compute cost rises by $1.80 per user on a $12 gross margin; do you launch it broadly?
retentioncss
35
A test was planned for 28 days and 200,000 users, but on day six at 44,000 users it shows a 6% lift with p = 0.03; the CEO wants to stop and ship, so what do you do?
36
Your primary metric is flat, but after checking 12 secondary metrics across four segments you find three results below p = 0.05, led by a 9% lift for Android users in Germany; do you ship or personalize to that segment?
discoverymonitoring
37
A search-ranking test lifts search-to-purchase conversion by 4%, worth an estimated $350,000 annually, but returns rise from 6.0% to 7.4% against a pre-set 6.5% guardrail and support contacts rise 11%; do you launch?
guardrailsestimation
38
In a ride marketplace with 10,000 shared drivers, a 50/50 rider-randomized priority-dispatch test cuts treatment wait time by 8% but raises control wait time by 6%, while total cancellations stay flat; do you trust the lift, and how do you retest?
designresilience
39
An enterprise audit-log feature would cost four engineer-months; a transparent fake-door shown to 2,000 admins gets 160 clicks, 18 booked calls, and four nonbinding commitments at $12,000 ARR each, while your funding hurdle is 15 paid design partners or $180,000 ARR; do you build it?
design
40
A concierge procurement workflow serves 20 customers: 14 use it weekly, eight say they will pay $2,000 per month, but delivery takes six staff-hours per customer per week at a loaded $50 per hour versus a 70% gross-margin target; do you fund a nine-month product build?
procurementcss
41
A SaaS product has 10,000 customers at $50 per month, 2% monthly logo churn, and no price change in three years; finance proposes a 20% increase and expects 8% immediate churn. Would you approve it, and how would you roll it out?
churncloud
42
A collaboration tool gets 100,000 sign-ups per month, 35% activate within three days, has no network effect, and each non-paying sign-up costs $0.30 in its first month; freemium converts 3% of sign-ups at $30 per month, while a 14-day trial converts 12% of activated users. Which model would you choose?
pricing
43
A B2B product has 8,000 accounts on one $39 monthly plan; research shows 58% need only the core workflow, 30% need automation, and 12% also require SSO, audit logs, and priority support. How would you package and price the product?
44
A compliance platform charges $20 per seat; ten-seat customers run 100,000 checks monthly, while 100-seat customers run only 20,000, and customer interviews say value comes from checks completed rather than collaboration. What value metric would you choose and how would you migrate pricing?
discoverymonitoringpricing
45
Before launching a new analytics add-on, a 300-person survey suggests $89, but equal 10,000-visitor checkout tests produce 800 purchases at $49, 700 at $69, and 400 at $89. What price would you set and what research would you do next?
testing
46
A free export feature is used by 24,000 of 60,000 monthly active users; exporters refer a new user at 25% per month versus 8% for non-exporters, and finance wants a hard $19 paywall expected to convert 5% of exporters. What would you ship?
47
A self-serve SaaS has 4,000 accounts at $99 per month, 2% monthly churn, and $300 CAC; sales has 20 enterprise leads at $60,000 ACV with a 25% expected win rate, but enterprise work would consume two squads for six months at a $600,000 opportunity cost. How would you allocate the roadmap?
churncloudroadmap
48
A subscription product charges $40 per month, has 75% gross margin, 4% monthly logo churn, and $600 CAC; growth wants to double paid acquisition because top-line revenue is rising 10% monthly. Do you approve the spend?
churncss
49
A $12 million ARR SaaS has 86% GRR and 22% expansion, giving 108% NRR; new packaging is forecast to lower GRR to 82% but raise expansion to 30%, while doubling annual SMB logo churn from 10% to 20%. Would you launch it?
churncloud
50
A $50 monthly plan has 3% monthly churn; finance proposes a $480 annual plan, a 20% discount, to improve cash flow, and 1,000 new customers arrive each month. How aggressively would you promote annual billing?
churn
51
You planned for a new self-serve setup wizard to lift 14-day activation from 48% to 60%, but 10 days after launch activation is 29%, median setup time rose from 12 to 21 minutes, and 2,000 accounts have entered the flow; do you fix forward or roll back within the next 24 hours?
activationrollback
52
An enterprise workflow launched to 60 licensed accounts with a week-six target of 35 weekly active accounts, but only 11 are active and $2.4M of renewals arrives in 90 days; customer success says role setup blocks 70% of inactive accounts, so what do you decide by Friday: fix adoption, pivot the workflow, or stop investing?
decision-making
53
A scheduled-payout feature reached 30% of 20,000 merchants at 09:00, and by 09:25 it has created three duplicate payouts totaling $75,000 while the launch campaign is already live; what decision do you make in the next 30 minutes and how do you handle the first 24 hours?
soft-skills
54
A new analytics package was launched with a 45-day goal of $3M in qualified pipeline, but it produced $900,000, 70% of leads are below the target company size, and lost deals cite a missing data-warehouse connector; Marketing wants another $400,000 next month, so do you continue, pivot, or stop within five days?
missing-datawarehouseci-cd
55
An AI support assistant was launched to cut average handle time from 14 to 10 minutes within eight weeks, but handle time is 13.5 minutes, agents correct factual errors in 9% of drafts, and the tool costs $120,000 per month with an annual renewal due in 21 days; do you fix, pivot, or stop?
56
A partner integration was supposed to connect 300 merchants in its first four weeks, but only 52 are live because partner approval takes nine days instead of the promised 24 hours, and $1.2M of quarter-end pipeline depends on it with six weeks left; do you keep selling, build a workaround, or pause the launch within seven days?
ci-cdpromises
57
A marketplace city launch targeted 1,500 completed orders per week by week eight, but it now completes 320 of 1,100 requests, median wait time is 27 minutes, and $180,000 of a $250,000 subsidy budget is already spent; do you double subsidies, narrow the launch, or leave the city in the next 48 hours?
58
An internal billing platform was meant to migrate eight product teams in 12 weeks, but only two have moved, the legacy system costs $140,000 per month, and its shutdown is scheduled in six weeks; do you force migration, extend the deadline, or abandon the platform at Monday's review?
estimationmigrationssystem-design
59
A document-sharing rollout reached 25% of 400 enterprise accounts, and 40 minutes later you learn that 17 files were visible to the wrong tenant for 11 minutes across six customers; contracts require incident notice within 72 hours, so what do you decide in the next 30 minutes?
incidents
60
A fraud-control launch promised to reduce chargebacks from 1.8% to 1.2% within 60 days, but chargebacks are still 1.7%, checkout conversion has fallen from 42% to 39.6%, and Finance estimates $900,000 in lost monthly revenue; do you fix forward, roll back, or stop the approach within 48 hours?
estimationpromisesrollback
61
Marketing prepaid a $600,000 campaign that starts in nine days, Design wants the new checkout included, Engineering estimates 36 engineer-days with only 18 available, and an accessibility review found four blockers affecting 8% of keyboard-only users; what ships, who has the final call, and what do you tell each team?
communicationestimationdesign
62
Growth wants contact import enabled by default for a campaign launching in 12 days and forecasting $1.1M in annual revenue, while the team has 24 engineer-days, Legal estimates a 20% chance that the consent flow is invalid, and 75,000 business accounts would be affected; what do you ship and how do you communicate the conflict?
communicationestimation
63
A payments launch is due in 10 days and supports $3.6M of first-year revenue, but a penetration test found a high-severity flaw with a 15% estimated abuse risk, the only squad has 50 engineer-days, and 260 accounts would share the vulnerable flow; do you launch, what do you cut, and what do you say?
estimationvulnerabilitiesseverity-priority
64
Your reporting release is due in six weeks and unlocks $1.8M of expansion revenue across 90 accounts, your squad has 60 engineer-days, but it also needs 25 engineer-days from the Data Platform team that can provide only eight, leaving a 45% deadline risk; what do you decide and how do you handle the peer-team conflict?
soft-skillsestimation
65
The CEO asks for an AI account summary in 21 days for a conference tied to $5M of pipeline, the squad has 36 engineer-days already committed and production work needs another 28, and a rushed release carries a 25% risk of showing incorrect data across 1,200 accounts; what do you offer and what do you communicate upward and to the team?
communicationci-cd
66
The CRO wants 300 accounts launched in four weeks to protect $4.2M in renewals, while the COO wants an eight-week delay because support can absorb only 120 accounts and estimates a 35% risk of more than 400 tickets; the product team has 70 engineer-days, so what do you recommend, who decides, and what does each group hear?
estimation
67
An account executive promised EU data residency within 30 days for a $1.6M renewal, but the platform team has 45 engineer-days against an 80-day estimate, an accelerated migration has a 20% cross-region exposure risk, and the shared architecture covers 14 regulated accounts; what do you decide and how do you address the customer promise?
estimationmigrationsarchitecture
68
A billing migration is due in 72 hours with $700,000 of monthly revenue at risk, three teams together have 30 engineer-days available, nobody owns the final cutover, and an untested switch has a 40% risk of corrupting invoices for 2,800 accounts; what do you do in the first hour and how do you communicate ownership?
communicationownershipmigrations
69
A government launch must happen in 15 business days to recognize $7M in revenue, the team has 90 engineer-days, Compliance says 12 missing controls create a 40% audit-failure risk, and the rollout covers 600 accounts; what ships, who can block it, and what do you communicate?
communication
70
The CTO wants to shut a legacy API in six weeks to avoid an $800,000 hosting renewal, while the CRO says 160 accounts representing $5.5M ARR were promised 12 months to migrate; only 48 engineer-days are available against 70 days of migration tooling, and shutdown creates a 35% renewal risk, so what do you recommend and how do you resolve and communicate the C-level conflict?
communicationapimigrations
71
Seven days after a 20% price increase for renewing customers, paid churn is 11% versus a 4% baseline and billing contacts have tripled; the CFO wants the change left in place to protect this quarter's target. What do you do in the next 48 hours?
churn
72
A hard paywall launched two weeks ago raised checkout conversion by 18%, but day-14 retention fell from 43% to 34% and refunds rose from 3.1% to 8.7%; the CEO plans to cite the conversion win at a board meeting in five days. How do you respond?
retention
73
A workflow automation feature has 41% weekly adoption among enterprise accounts, but after a full rollout SMB support tickets rose 68% and SMB churn increased 2.6 percentage points; sales has a campaign featuring it scheduled in six days. Do you roll back, fix, segment, or kill it?
churndecision-makingrollback
74
Six hours after changing new profiles to public by default, sharing rises 24% but 2% of created profiles expose personal details and support receives 38 privacy complaints; marketing wants to wait until tomorrow's campaign ends. What do you do before the next hour is over?
discovery
75
At 25% rollout, a new recommendation service pushes checkout p99 latency from 400 ms to 3.8 seconds and error rate from 0.3% to 6.2% while about $120,000 in GMV passes through checkout each hour; marketing's launch event is already live. What is your call?
latency
76
A collaborative map championed by the founder is used by only 1.7% of monthly active users, consumes 22% of one squad's capacity, and caused three Sev-2 incidents last quarter; the founder asks for another six months before any decision. How do you handle it?
soft-skillsincidentscapacity
77
API v1 must be retired because its authentication model blocks a compliance renewal in 90 days, but 47 live consumers remain, eight have no known owner, and customer contracts promise 180 days' notice; sales insists no account can be disrupted. What deprecation plan do you own?
authapipromises
78
A one-click data import released 10 days ago lifted activation by 9%, but it has corrupted records in 1.4% of imports, doubled support volume, and generated $92,000 in refunds; growth wants three more weeks to patch it in place. What do you do?
activation
79
Three days before a keynote, you learn that an AI assistant used conversations from 600 enterprise accounts for model improvement without the opt-in promised in contracts; two customers demand answers within 48 hours and the launch team argues that deleting the data will delay the release by a month. What do you do?
promises
80
A mandatory identity check rolled out globally five days ago cuts fraud losses by 35%, but legitimate activation falls 18%, support has a four-day backlog, and only 12 of 46 countries legally require the check; compliance wants one global rule by Friday. What do you change?
activationbacklog
81
After a reorg, three squads become one 18-person group, an executive-promised launch is eight weeks away, and ownership is unclear across 12 open workstreams; what do you decide in the first 48 hours?
program-managementpromisesownership
82
Layoffs reduce your product team from 14 people to seven overnight; a workflow tied to a $2 million renewal is due in six weeks, a mobile redesign is 40% complete, and severe defects arrive weekly. How do you reset the team?
defects
83
A seasonal mobile launch is five days away, Marketing has spent $800,000, crash-free sessions are 94% against a 99.5% release gate, six critical Android crashes affect a platform carrying 62% of traffic, and you have four engineers; do you ship?
sessions
84
Checkout has suffered three incidents in 30 days, causing nine hours of downtime and $420,000 in failed orders, while leadership still expects a major launch in five weeks from the same 12 engineers. How do you allocate the team?
incidents
85
An AI recommendation feature is scheduled for a 50,000-user public launch in ten days, but review shows 86% correct outputs and 4% harmful outputs against a 1% safety limit; marketing has already spent $250,000. Do you launch?
86
The CEO wants enterprise SSO for a signed $1.5 million contract in six weeks, the CRO wants a pricing rebuild forecast to add $800,000 this quarter in four weeks, and you have one eight-person squad. Which urgent bet gets the team?
pricing
87
At week seven of a 13-week quarter, activation has moved from 38% to 40% against a 50% OKR, and your nine-person team is split across referrals, dashboard personalization, and onboarding; data shows 62% of failed activations stop at integration setup. What do you do?
activationonboardingdiscovery
88
Seventy-two hours before a board meeting, Finance reports $18.2 million ARR, the CRM reports $21.4 million contracted ARR, and the product dashboard reports $20.1 million active ARR; you have four analysts and no agreed definition. What number do you publish and how do you resolve the conflict?
89
A marketplace loses 35% of active suppliers overnight across six of its 20 regions, fill rate falls from 92% to 61%, cancellations rise from 9% to 24%, and you have a 12-person product and operations team. What do you do for the next 48 hours?
resilience
90
The board orders a 25% operating-cost reduction within 30 days while the CEO protects a launch in seven weeks tied to $4 million of renewals; your 16-person team also supports a secondary product used by 8% of customers and a vendor costing $600,000 annually. What do you cut?
procurement
91
A PM has slipped 2 launches by 3 weeks in the same quarter because dependencies surfaced after the committed date; how do you coach them before an 8-week launch starts?
dependencies
92
A technically strong PM has interrupted a designer and dismissed sales evidence in 3 planning meetings, and 2 teammates now send concerns privately instead of speaking; what do you do over the next 30 days?
design
93
A PM presents activation as rising from 41% to 49%, but you discover they excluded the weakest channel and changed the activation definition after seeing the result; how do you handle it this week?
activationsoft-skills
94
In one month a PM has promised sales four custom features totaling 14 engineer-weeks without team review, and says they cannot tell sales no; how do you coach them before the next deal cycle?
promises
95
A junior PM asks for promotion in 2 months after shipping 3 features, but their manager still rewrites most decision memos and leads difficult stakeholder meetings; how do you assess readiness?
stakeholder-managementcommunicationhealth-checks
96
A PM has missed four of six milestones, and incomplete requirements caused 12 engineer-days of rework in the last quarter; design a 60-day underperformance plan.
milestonesdesign
97
A hiring panel is split two to two on a senior PM: the candidate aced analytics but failed to win support in a 45-minute stakeholder exercise; how do you resolve the calibration disagreement within 48 hours?
conflictcommunicationstakeholder-management
98
A reorganization merges 2 product areas, the VP will not name permanent owners for 3 weeks, and 3 PMs have already sent conflicting messages to the same customers; what do you do in the next 5 days?
99
Ten days before launch, a senior PM is personally holding 17 open decisions while a junior PM waits for approval on every customer message; how do you improve delegation without risking the launch?
discoverydelegation
100
A PM has sent a designer through 3 redesigns in 2 weeks using feedback such as make it cleaner, and the designer now waits for the PM's taste instead of testing users; how do you improve this team practice?
feedbackdesigntesting

Questions

1A B2B SaaS product at $40M ARR has slowed from 30% to 5% annual growth, net revenue retention is 96%, and you have three squads for the next 24 months; what strategy do you choose and what do you do first?

2The company vision is to become the operating system for independent retailers, the board wants 25% ARR growth within 12 months, and four squads have proposed 18 unrelated features; what product strategy do you set?

3You have 20 engineers for 18 months: segment A produces $8M ARR with 92% retention and 5% growth, segment B produces $2M ARR with 40% growth but 78% retention, and segment C has a $4M pipeline but requires a 12-month compliance build; which segment do you deprioritize?

4An enterprise strategy needs six months of engineering and revenue will lag by 18 months, but after 90 days only 8 design partners have tested the prototype; what evidence would make you continue, pivot, or stop?

5The CEO needs $5M more EBITDA in the next 12 months, while your proposed API platform costs $3M now and is forecast to unlock $8M ARR in year two; with five squads available, how do you resolve the conflict?

6A legacy add-on generates $6M ARR at 20% gross margin, migration to a new platform will lose an estimated $1.2M in year one but can reach 75% margin and add $4M ARR in year two, and the company has 18 months of runway; do you migrate now?

7Your SMB analytics product has $25M ARR, and an enterprise compliance adjacency appears to offer a $500M TAM, but it needs 12 engineers for nine months, sales cycles rise from one to nine months, and only 3 of 20 interviews show willingness to pay; do you enter?

8Competitors copy your visible features within three months, and you can spend $4M over 18 months on only two of these options: 50 integrations, proprietary benchmark data, a 30% price cut, or a deeper approval workflow; which two do you choose?

9A 120-person product organization with six squads must lift gross retention from 84% to 90% in 12 months, but the current roadmap contains 40 initiatives; what strategy do you communicate in the first 30 days, and what do you cut?

10A competitor cuts price by 40% and ships an AI feature in one quarter; your product has $30M ARR, 70% gross margin, 8% annual churn, 55% of users depend on a unique integration, and three squads are fixed for the next two quarters; what do you decide within two weeks?

12Two initiatives compete for six engineers next quarter: A has impact 9/10, effort 24 engineer-weeks, and 50% confidence; B has impact 6/10, effort 12 engineer-weeks, and 90% confidence. You cannot split the team. Which enters the roadmap?

13A customer representing 18% of ARR will renew a $1.8M contract only if you deliver a custom approval workflow in eight weeks; the same squad is scheduled to ship a roadmap capability requested by 35 customers and forecast to add $1.2M ARR. What do you choose?

15You control four squads for a 12-week quarter: Checkout needs two squads to pursue a projected $2M conversion gain, Compliance needs one squad to meet a fixed deadline, and Search asks for two squads to address $900k annual churn. How do you allocate the squads?

16At week five of a 12-week cycle, a new partner opportunity worth $1.5M requires one squad for six weeks; your three squads are 60% through initiatives worth $800k, $700k, and $300k respectively, and switching costs one week. Do you reallocate?

17Your three squads provide 72 engineer-weeks per quarter. Reliability incidents consumed 18 weeks last quarter, core growth asks for 45 weeks, and a new-market experiment needs 18 weeks. What capacity plan do you approve?

18One squad can either build an enterprise integration expected to close $900k ARR at 70% confidence in 12 weeks or improve self-serve activation for a projected $500k annual gain at 90% confidence in six weeks. What is the opportunity cost of your choice, and which option wins?

19Sales wants five roadmap integrations, each worth about $250k pipeline and four engineer-weeks, while product data shows a 10-week onboarding change could improve retained ARR by $1.1M at 65% confidence. You have one squad with 20 engineer-weeks. What do you commit to?

Locked questions