Interview framework

RICE

Prioritization questions - which feature, project, or bet to do first

When to reach for it

Any 'how would you prioritize' or roadmap-tradeoff question in a PM or growth interview.

1,529 questions of this shape, across 1,085 of the 1,887 companies in our interview bank.

What is the RICE framework?

RICE scores competing items so a roadmap decision is defensible rather than political. Score = (Reach x Impact x Confidence) / Effort. Reach is how many users or events are affected in a set period, Impact is a relative score per user, Confidence is a percentage that discounts hand-wavy estimates, and Effort in person-months is the denominator.

Watch the RICE breakdown

Three minutes: the same weak answer rewritten into a strong one, and the corpus numbers behind who actually gets asked this.

RICE scores competing items so a roadmap decision is defensible rather than political. Seventy-seven percent of the RICE-shaped questions in our bank go to product managers. Counted across 98,000+ real interview questions from 1,800+ companies, by question type. Measured, not surveyed. Source: the JobMentis interview corpus. Chapters: 0:00 A real RICE interview question 0:19 Who actually gets asked this 0:43 Score competing projects with RICE 1:13 A weak answer 1:36 The same answer, rewritten 2:38 What flattens a RICE answer 2:55 Where this prioritization framework gets asked 3:09 Get the full guide

The RICE steps

Each step is one move, and the order is the point. Skipping ahead is what makes an answer feel unstructured even when the content is good.

  1. R

    Reach

    How many users or events does this affect in a set period? Use a real number, not a guess.

  2. I

    Impact

    How much does it move the goal per user? Score it on a simple scale (e.g. 3 = massive, 1 = low).

  3. C

    Confidence

    How sure are you about Reach and Impact? Express as a percentage and discount hand-wavy estimates.

  4. E

    Effort

    Total person-months to ship. The denominator: score = (Reach x Impact x Confidence) / Effort.

A weak RICE answer, rewritten

The acronym is on every interview blog. The graded contrast is not, so this is the part worth reading twice.

Question

“You have three features and one quarter of engineering time. How do you decide what to build?”

Weak answer

I would talk to stakeholders and see what is most important to the business, then check what engineering thinks is feasible. Probably I would start with the one that has the biggest impact on revenue, since that is what the company cares about most this year.

Strong answer

I would score all three on RICE. Checkout retry: reach is 40,000 monthly checkout sessions, impact 2 because it removes a hard failure, confidence 90% because we have the funnel data, effort 1.5 person-months. That scores about 48,000. Referral widget: reach 6,000, impact 3, confidence 50% since we have never shipped referral here, effort 3. That scores 3,000. Admin bulk editor: reach 300 internal users, impact 3, confidence 100%, effort 0.5. That scores 1,800. Checkout retry ships first, by an order of magnitude. I would also flag that the referral score is dominated by that 50% confidence, so a two-week fake-door test buys more than another debate would.

Why the strong version wins: The strong answer treats Impact as a relative score and Confidence as a real discount, so a high-reach guess cannot outrank a sure thing, and it closes by naming what would change the ranking. The weak answer picks the winner first and reasons backwards to justify it.

What flattens a RICE answer

The moves that turn a good framework into a forgettable answer.

  • Treating Impact as a precise number instead of a relative score.

  • Ignoring Confidence, so a high-reach guess outranks a sure thing.

  • Forgetting Effort is the denominator - a small, certain win often beats a big, risky one.

Who actually gets asked RICE questions

Counted across every question in our interview bank, not estimated. RICE-shaped questions are not spread evenly, and these are the roles and industries whose loops lean on them hardest.

Roles

Industries

Practice RICE out loud, not in your head

Try it on this prompt

“You have three features and one quarter of engineering time. How do you decide what to build?”

Reading a framework builds false confidence. The voice simulator asks a RICE-shaped question, listens to the whole answer, and scores the structure, the signal and the length, so you find out where your story drifts before an interviewer does.

Start a mock interview

RICE: frequently asked questions

What does RICE stand for?

RICE stands for Reach, Impact, Confidence, and Effort. The score is (Reach x Impact x Confidence) divided by Effort. Reach and Effort are real numbers, Impact is a relative score on a fixed scale, and Confidence is a percentage that discounts estimates you cannot back up.

What is the most common RICE mistake?

Treating Impact as a precise number rather than a relative score, and quietly ignoring Confidence, which lets a high-reach guess outrank a sure thing. The third is forgetting that Effort is the denominator, so a small certain win often beats a big risky one.

How do I score Impact and Confidence without real data?

Use a fixed scale and say it out loud: for example 3 for massive, 2 for high, 1 for low. For Confidence, state the evidence behind the number. 100% means you have shipped this before and have the data, 50% means it is an informed guess. The score is only as honest as the Confidence you attach to it.

Is RICE only used by product managers?

It is PM-dominated in our interview bank, but supply-chain candidates are the second-largest group asked prioritization-shaped questions, ahead of software engineers. Any role that allocates a constrained resource across competing bets can be asked to defend a ranking method.

The other five frameworks

RICE is one of six. If the question you are preparing for does not have this shape, one of these does.