Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
Get started

Define HelloFresh North Star Metric

EasyMetrics00:00
Practice interviewer
In session
5 left
00:00

Your question is Define HelloFresh North Star Metric. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Business Context

HelloFresh is a subscription meal-kit product that acquires customers through paid channels and retains them through recurring weekly orders. Leadership wants a single North Star Metric (NSM) that reflects long-term customer value rather than just short-term signups.

Metric Scenario

In the last quarter, HelloFresh added 420,000 new subscribers, but only 58% placed a second box order within 30 days and 41% were still active after 90 days. Average order value was $67, average gross margin per delivered box was $19, and weekly order skip rate rose from 18% to 24%. Marketing is optimizing to trial starts, while operations is optimizing on-time delivery rate (94.5%), and product is focused on app engagement. The Chief Product Officer asks you to define the best North Star Metric for HelloFresh and explain why it should be preferred over alternatives such as total subscribers, revenue, or app DAU.

Requirements

  1. Propose one primary North Star Metric for HelloFresh and define it precisely.
  2. Explain why it best captures customer value creation and business health.
  3. Show how you would calculate it using the available data.
  4. Identify leading indicators and guardrail metrics that should accompany it.
  5. Describe how you would decompose the metric to diagnose changes over time.

Data Available

Data SourceDescription
subscriptionscustomer_id, signup_date, plan_type, acquisition_channel, status, cancel_date
ordersorder_id, customer_id, scheduled_week, delivered_at, box_price, discount_amount, items_count
skips_pausescustomer_id, week, skip_flag, pause_flag, reason_code
delivery_opsorder_id, on_time_flag, missing_item_flag, refund_amount
app_eventscustomer_id, event_time, event_name, recipe_views, add_on_clicks
support_ticketscustomer_id, created_at, ticket_type, resolution_time

Constraints

  • The metric should work at weekly and monthly reporting cadences.
  • It should be understandable to product, growth, finance, and operations teams.
  • It should not be overly distorted by one-time discounts or acquisition spikes.