InterviewsVector
AdvancedPrincipalReliability, Resilience & Recovery65 minutesPro answer

SDV-023

Set dependency failure budgets across teams with different incentives

Allocate reliability expectations through a dependency graph without pretending service-level SLOs compose automatically or using budgets as blame.

Error BudgetsSloOrganizational DesignReliability

Interview prompt

Problem context

A critical journey calls twelve internal services. Every service reports meeting 99.9%, yet the customer journey misses its 99.9% target. Teams dispute whose roadmap should fund reliability and whether optional dependencies should count. Define technical policy, measurement, and governance.

Skills being evaluated

SLO compositiondependency policyincentive designreliability governance

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

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.

Distinguished · 75 min

Degrade a dependency graph under severe overload without guessing

Turn business priority and dependency criticality into coordinated admission, brownout, and recovery policies across a large service graph.

Staff · 55 min

Define architecture principles that autonomous teams will actually use

Create testable principles, paved roads, exception evidence, and feedback loops instead of aspirational slogans or a central approval bottleneck.

Senior · 50 min

Contain cascading failures across services that share hidden dependencies

Find common pools and retry amplification, then design bulkheads, deadlines, admission, and recovery that contain a dependency slowdown.