InterviewsVector
AdvancedStaffPerformance, Observability & Capacity55 minutesPro answer

SDV-050

Design observability that stays useful under cardinality and cost pressure

Choose metrics, traces, logs, exemplars, retention, and tenant debugging paths without letting unbounded labels bankrupt or disable telemetry.

ObservabilityCloud CostMulti TenancyIncident Response

Interview prompt

Problem context

Teams add user, request, model, and query IDs to metric labels. Costs triple, dashboards time out, and the telemetry backend drops data during incidents. Removing all high-cardinality context would make enterprise debugging impossible. Redesign the telemetry architecture and governance.

Skills being evaluated

telemetry architecturecardinality controlcost governancedebuggability

The full reasoning guide is part of Pro

The scenario and evaluation focus above remain public. Pro unlocks the structured answer, trade-off analysis, follow-up probes, common weak answers, rubric, related reasoning, and any architecture diagram.

Sign in to continue

What the full guide covers

Clarify the decision
Establish scale assumptions
Functional and non-functional requirements
High-level architecture
Data model and flow
Consistency and transaction boundaries
Failure modes and recovery
Security and privacy
Observability and SLOs
Capacity and cost
Alternatives and trade-offs
Evolution and migration
What Staff and Principal candidates should emphasize

Related architecture decisions

Staff · 55 min

Diagnose a p99 regression that every average says does not exist

Localize tail amplification across cohorts, fan-out, queues, pauses, and dependencies while avoiding coordinated omission and misleading percentiles.

Distinguished · 75 min

Detect silent data loss in a multi-stage pipeline before customers do

Design end-to-end completeness signals, invariants, lineage, quarantine, and repair when every component reports healthy while records disappear.

Staff · 55 min

Allocate shared cloud cost to products and tenants without false precision

Design activity-based cost units, shared-capacity allocation, uncertainty, and behavioral feedback that teams trust enough to act on.

Senior · 50 min

Define SLOs and error-budget policy for a product with unequal journeys

Choose customer-centered indicators, windows, targets, and policy actions without averaging away critical tenants or turning SLOs into vanity dashboards.