Interview framework

HEART

Choosing and defending user-centered metrics (Google's own framework)

When to reach for it

'How do you measure…' or 'What are the top 3 metrics for…'

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

What is the HEART framework?

HEART is Google’s framework for choosing user-centered metrics, across five categories: Happiness, Engagement, Adoption, Retention, and Task success. In an interview it answers "how would you measure success of X?". The grade is not on listing five categories, it is on picking one North Star and saying what you deliberately will not measure.

Watch the HEART breakdown

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

HEART is Google’s framework for choosing user-centered metrics, across five categories: Happiness, Engagement, Adoption, Retention, and Task success. Eighty-one percent of the HEART-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 HEART interview question 0:19 Who actually gets asked this 0:44 How HEART asks you to measure success 1:10 A weak answer 1:33 The same answer, rewritten 2:32 What flattens a HEART answer 2:45 Where this is actually asked 2:57 Get the full guide

The HEART 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. H

    Happiness

    Attitudinal - NPS, CSAT, app-store rating.

  2. E

    Engagement

    Depth of interaction - sessions, time, actions per user.

  3. A

    Adoption

    New users of a feature in a given period.

  4. R

    Retention

    Returning users over time.

  5. T

    Task success

    Can users complete the core job? Completion rate, error rate, time-to-complete.

A weak HEART answer, rewritten

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

Question

“How would you measure success of YouTube Shorts?”

Weak answer

I would look at daily active users, watch time, and the number of Shorts uploaded. If DAU is going up and people are watching more, that means it is working. I would also check the app store rating to see if users are happy.

Strong answer

The goal first: Shorts exists to defend short-form attention, so my North Star is returning short-form viewers per week, which is a Retention metric. Around it: Engagement as Shorts watched per viewer per session, Adoption as the share of monthly viewers who watch their first Short in the period, and Task success as swipe-to-first-frame latency plus completion rate. I would track Happiness only on the creator side, through CSAT, because viewer NPS moves too slowly to steer a feed. I would deliberately not lead on DAU: Shorts can lift DAU by cannibalizing long-form watch time, which would read as success and be a loss.

Why the strong version wins: The strong answer names one North Star, says what each other category is for, and states the metric it refuses and why. The weak answer lists surface numbers with no goal behind them and reaches for DAU, which is the vanity trap HEART exists to avoid.

What flattens a HEART answer

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

  • Listing all five categories without picking a North Star.

  • Picking a vanity metric (DAU) when retention is more honest.

Who actually gets asked HEART questions

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

Roles

Industries

Practice HEART out loud, not in your head

Try it on this prompt

“How would you measure success of YouTube Shorts?”

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

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

HEART: frequently asked questions

What does HEART stand for?

HEART stands for Happiness, Engagement, Adoption, Retention, and Task success. Happiness is attitudinal (NPS, CSAT, app-store rating), Engagement is depth of interaction, Adoption is new users of a feature in a period, Retention is returning users over time, and Task success is whether people can complete the core job.

Who created the HEART framework?

HEART came out of Google’s UX research team, published by Kerry Rodden, Hilary Hutchinson and Xin Fu in their 2010 CHI paper on measuring user experience at scale. That origin is worth knowing: it is a UX-measurement framework first, and a product-interview framework second.

What is the most common HEART mistake?

Listing all five categories without picking a North Star. A metrics answer that gives equal weight to five things has not made a decision. The second mistake is choosing a vanity metric such as DAU when retention would be the more honest read.

Do I need a metric in every HEART category?

No, and forcing one is a tell. Pick the categories the product is actually steered by, name your North Star, and say explicitly which categories you are leaving out and why. Naming the metric you refuse is the strongest move available in this question type.

The other six frameworks

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