CIRCLES Method: Steps, Examples, Pitfalls

Interview framework

CIRCLES

Open-ended product design / improvement questions

When to reach for it

Any question that starts with Design / Improve / Build a product for…

3,462 questions of this shape, across 1,460 of the 1,964 companies in our interview bank.

What is the CIRCLES framework?

Watch the CIRCLES breakdown

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

CIRCLES answers open-ended product-design questions like "Design a product for X" in seven steps: Comprehend the situation, Identify the customer, Report their needs, Cut through prioritization, List solutions, Evaluate trade-offs, and Summarize. Eighty-one percent of the CIRCLES-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 CIRCLES interview question 0:17 Who actually gets asked this 0:46 Designing a product, step by step 1:20 A weak answer 1:43 The same answer, rewritten 3:03 What flattens a CIRCLES answer 3:21 Where this gets asked 3:35 Get the full guide

The CIRCLES 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.

C
Comprehend the situation
Clarify scope, constraints, goal, and success metric.
I
Identify the customer
Segment users; pick one segment to solve for.
R
Report customer needs
List real jobs-to-be-done, not features.
C
Cut through prioritization
Rank needs by reach × impact × feasibility.
L
List solutions
Brainstorm 3+ distinct solutions, not variations.
E
Evaluate trade-offs
Compare on user value, business value, and cost.
S
Summarize recommendation
Pick one, name the success metric, state the risk.

A weak CIRCLES answer, rewritten

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

Question

“Design a product to help new parents in their first 90 days.”

Weak answer

I would build an app with a feed of parenting tips, a forum to talk to other parents, and reminders for feeding and sleep. New parents are stressed, so an all-in-one app would really help them stay organized.

Strong answer

Comprehend: I will assume we are optimizing for engagement, not revenue, in year one. Identify: new parents split into first-time and experienced, and into solo versus partnered. I will solve for first-time, solo-at-home parents, who feel the most isolated. Report: their top jobs-to-be-done are "is this normal?", "am I doing this right?", and "I need a break". Cut through: I will prioritize reassurance, because it underpins the other two. List: an on-demand video line to a nurse, an AI symptom-checker tuned for newborns, or a peer-match to one vetted parent. Evaluate: the nurse line builds the most trust but is operationally heavy, so I would start with the AI checker and a clear escalation to a human. Summarize: for first-time solo parents, ship an AI newborn-reassurance checker with one-tap escalation to a nurse, measured by weekly active reassurance sessions.

Why the strong version wins: The strong answer clarifies the goal first, picks one segment instead of "all parents", lists real needs before features, prioritizes explicitly, and recommends one solution with a metric. The weak answer jumps to a feature list for everyone, which is exactly what CIRCLES exists to stop.

What flattens a CIRCLES answer

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

Skipping clarification and diving into solutions.
Picking a customer segment then designing for everyone anyway.
Listing features instead of solutions to a specific need.

Who actually gets asked CIRCLES questions

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

Roles

Industries

Practice CIRCLES out loud, not in your head

Try it on this prompt

“Design a product to help new parents in their first 90 days.”

Reading a framework builds false confidence. The voice simulator asks a CIRCLES-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

Companies that ask CIRCLES questions

These companies ask CIRCLES-shaped questions in their loop. Each bank holds the real questions and the rubric we grade against.

CIRCLES: frequently asked questions

What does CIRCLES stand for?

CIRCLES stands for Comprehend the situation, Identify the customer, Report customer needs, Cut through prioritization, List solutions, Evaluate trade-offs, and Summarize. It is the most common structure for product-design and "design a product for X" questions.

When should I use CIRCLES instead of another framework?

Reach for CIRCLES on open-ended product-design or improvement prompts ("Design a product for...", "How would you improve X?"). For behavioral questions use STAR, and for a metric that moved unexpectedly use a root-cause issue tree.

What is the most common CIRCLES mistake?

Skipping clarification and segmentation and jumping straight to features. The other classic error is naming one segment and then designing for everyone anyway. Strong candidates narrow to a single user and solve their top need.

Do I have to run all seven steps?

No. If the prompt already names the customer and the goal, say so and move on rather than segmenting for ninety seconds. What is graded is that you clarified, chose, prioritized and recommended, not that you recited seven letters.

The other six frameworks

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