Platform team metrics versus product team metrics

WHAT THIS TESTS This checks whether you understand the platform mindset: your customers are internal engineers, and success means they build faster and more reliably on top of you. The interviewer wants you to articulate metrics that reflect leverage, not direct user engagement.

A GOOD ANSWER COVERS For a platform team, the headline metric is adoption: how many experience products consume your auth or payments service versus rolling their own. Pair that with reliability expressed as SLOs and error budgets, because a shared service failing takes down every consumer. Measure time-to-integrate, the hours from a new team starting to a working integration, and the self-service ratio, how often teams onboard without filing a ticket to you. Track duplicated work eliminated, the proof your leverage is real. A consumer product engineer instead owns activation, retention, conversion, latency users feel, and feature engagement. The platform succeeds indirectly, by making many products succeed.

COMMON WRONG ANSWERS Reusing DAU, monthly active users, or churn for a platform that has no end users. Measuring only uptime while nobody adopts the service. Optimizing internal elegance with no consumer-facing reliability commitment.

LIKELY FOLLOW-UPS How do you set an SLO when many teams depend on you? How do you measure developer experience? What is an error budget and how does it change your release behavior?

ONE CONCRETE EXAMPLE Your payments platform reports that eight of ten products now use it, integration takes two days down from two weeks, and it holds 99.95 percent availability against a defined SLO. Those numbers prove leverage. A product team next door instead celebrates lifting trial-to-paid conversion from four to six percent, a fundamentally different success definition.