Define the North Star metric for Google Cloud serving commuters
- Metrics
- Hard
- 15 min
Problem Statement Description
Product context: Google is a consumer technology, ads, AI, and cloud company; its products include Search, YouTube, Android, Maps, Gmail, Chrome, Google Play, Workspace, and Google Cloud.
Google Cloud is exploring how to measure success for products and infrastructure that serve commuters through mobility, transit, navigation, workplace commute, and real-time transportation experiences. These experiences may involve enterprise customers, public agencies, app developers, and end commuters who rely on timely, reliable, and personalized information during daily travel.
In this metrics interview, you are asked to define a North Star metric for Google Cloud in this commuter-serving context. The challenge is to identify a metric that reflects durable user value, aligns with Google Cloud’s business role, and can guide product, platform, and ecosystem decisions without collapsing into a narrow infrastructure usage or revenue metric.
Your answer should clarify whose value is being optimized: commuters, transit or mobility partners, enterprise customers, developers building on Google Cloud, or some combination of these stakeholders. You should also distinguish between direct commuter outcomes and the cloud platform capabilities that enable those outcomes at scale.
The experience should consider:
- The primary commuter workflow being supported, such as planning, routing, real-time updates, ticketing, workplace commute coordination, or disruption recovery.
- A clear North Star metric definition, including numerator, denominator, time window, and what user or customer action counts.
- How the metric would be instrumented across Google Cloud services, partner applications, APIs, and downstream commuter experiences.
- Relevant cohorts, such as daily commuters, occasional commuters, enterprise employees, transit-agency users, geographies, transport modes, and partner types.
- Guardrail metrics for reliability, latency, data freshness, privacy, safety, accessibility, cost to serve, and partner satisfaction.
- How to avoid vanity metrics that overemphasize cloud consumption, API calls, or app opens without proving commuter value.
- How the metric would support product decisions, prioritization, partner success, and long-term ecosystem growth.
Your goal is to frame a North Star metric that is measurable, actionable, and strategically appropriate for Google Cloud’s role in enabling commuter experiences, while showing the trade-offs between end-user value, enterprise adoption, platform reliability, and responsible data use.
What this question tests
- Metric Definition
- Instrumentation
- Counter-metrics
- Decision Quality
Practise this question under interview conditions. Answer it out loud against a timer with an AI interviewer that asks follow-ups, then review the scored report.
Related Metrics questions
- Define the North Star metric for Maps serving commutersGoogle · Metrics · Medium
- Create a metric dashboard for the executive team reviewing AndroidGoogle · Metrics · Medium
- Define the North Star metric for Maps serving commutersGoogle · Metrics · Easy
- Create a metric dashboard for the executive team reviewing AndroidGoogle · Metrics · Easy
- What metrics would you use to evaluate a new Photos feature for enterprise adminsGoogle · Metrics · Easy
- How would you detect unhealthy growth in YouTubeGoogle · Metrics · Easy
All Metrics questions · Product manager interview questions by skill area