Interview frameworks

Interview frameworks:a shape for any question

An interview framework is a fixed sequence of steps you say out loud, so your answer has a shape before you know how it ends. They come in two families. Five are story frameworks, for a question about your past: STAR, CARL, SOAR, CAR and PAR, which differ only in how they cut one event up. Six work a problem you are meeting in the room: CIRCLES for product design, AARRR for growth, HEART for metrics, RICE for prioritization, MEDDPICC for enterprise sales qualification, and a root-cause tree for anything that broke.

11

frameworks, each mapped to the question shape it answers

37,092

questions in our interview bank that one of these frameworks structures

JobMentis interview corpus, 2026

2,202

companies whose interview loops we have catalogued

JobMentis interview corpus, 2026

The frameworks in 30 seconds

Which answer shapes companies actually ask for, counted across the whole bank.

STAR-shaped questions are asked at more than 88% of the 2,000+ companies in the JobMentis bank. Seven frameworks (STAR, CIRCLES, HEART, Root Cause, RICE, MEDDPICC, AARRR) answer 1 in 3 of 108,000+ interview questions. Learn the shape, not the script. Measured, not surveyed. Source: the JobMentis interview corpus, 2026-10-04.

Which framework does your question want?

Pick by the phrasing the interviewer used, not by the framework you know best. First decide which family the prompt is in, because that is the only choice you can get badly wrong, then let the opening words point at the row.

Tell me about a time

Five ways to cut one past event. They ask for the same story and differ only in which box you have to fill, so pick the one whose boxes you can actually answer.

Work the problem

Six ways to think out loud about a problem you are meeting for the first time. Here the framework is the reasoning itself, not the narration of it.

How to actually use one in the room

Use the framework as scaffolding, not as a script. Interviewers grade structure, not vocabulary, and announcing "I will use CIRCLES now" reads as recital rather than thinking. Three rules separate a framework that helps from one that gets in the way.

  1. Never name it out loud

    Clarify, segment, prioritize, recommend. The interviewer reads the structure in the moves you make. Saying the acronym adds nothing and costs you a beat of credibility.

  2. Skip the steps that do not apply

    A framework is a checklist for you, not a contract with the interviewer. If the prompt already names the customer, do not spend ninety seconds segmenting. Say what you are skipping and why.

  3. Land the recommendation

    Most answers die in the middle: well structured, never concluded. Reserve the last thirty seconds for one recommendation, the metric that proves it, and the risk you accept.

Interview frameworks: frequently asked questions

What is the difference between STAR, CARL, SOAR, CAR and PAR?

They are five cuts of one story. STAR has four boxes: Situation, Task, Action, Result. SOAR swaps Task for Obstacle, asking what stood in your way instead of what you owned. CARL merges Situation and Task into one Context and adds Learning. CAR and PAR drop to three boxes by merging the setup, and differ only in vocabulary: CAR says Challenge and suits cover letters, PAR says Problem and suits CV bullets. Pick by the box you can actually fill.

Which interview framework should I learn first?

STAR, if you have a behavioral round coming up. It is the one framework almost every role shares, and in our interview bank it structures more questions than every other framework combined. Learn CARL, SOAR, CAR or PAR next, since each is STAR with one box swapped, and add CIRCLES if you are prepping product-sense rounds.

Do interviewers care which framework I use?

They care that you are structured, not that you name-drop. Use the framework as scaffolding for your thinking and never announce it. Clarify, segment, prioritize, and recommend, and the structure will be visible without you labeling it.

Are these frameworks only for product management?

No, and our own numbers say otherwise. STAR-shaped questions land most often on sales candidates, AARRR-shaped ones on marketing, and root-cause questions on software engineers. MEDDPICC is sales-only. CIRCLES, HEART and RICE skew product, but the logic transfers to any role that has to defend a decision.

Can I combine two frameworks in one answer?

Yes, and it is often the strongest move. Use STAR as the narrative spine of a behavioral case and a MECE tree to organize the Action section, or open a growth question with AARRR and switch to root-cause once you know which stage broke. Just do not let it read as a checklist.