Skip to content
tezvyn:

Monitoring & SRE

Observability, incident response, reliability, SLOs

137 bites

Test yourself: Top 30 intermediate Monitoring & SRE interview questionsMultiple choice, with the correct answer and why it is correct on every question. Free, no sign-in.

Intermediate everything in Monitoring & SRE

intermediate2 min read

Federating reliability ownership to product teams

Build a self-service reliability platform (golden paths, paved roads), train teams and embed SLO/on-call practices, and govern with standards plus error budget…

intermediate2 min read

Capacity planning for a distributed cache

Track hit ratio, memory and eviction rate, throughput/latency, and connections; correlate with growth to forecast when to add capacity before the hit ratio or evictions…

intermediate2 min read

Capacity planning for distributed stateful systems

Account for replication and cross-region network, IOPS and disk throughput, connection limits, partition/shard balance, and N+1 region failover headroom; validate with load and chaos…

intermediate2 min read

Designing a feature flagging service

Control plane (UI, store, targeting), SDKs that cache flags locally for zero-latency evaluation, streaming/CDN delivery for near-real-time updates, and stale-flag lifecycle tooling.

intermediate2 min read

Managing a risky release with feature flags

Deploy code dark behind an off flag, enable for internal then small percentage, monitor metrics, ramp gradually, then remove the flag.

intermediate1 min read

Automating actions on error budget burn

Use multi-window burn-rate alerts; on fast burn, auto-trigger actions like halting deploys, rolling back, or scaling, with escalating tiers.

intermediate2 min read

Safeguards for automated remediation runbooks

Add rate limits and circuit breakers on restarts, escalate to humans after N attempts, log all actions, and check for cascading failure before acting.

intermediate1 min read

Breaking tunnel vision during an incident

Call out the assumption, ask for disconfirming evidence, list parallel hypotheses, split responders to investigate them, and anchor on what changed and the data.

intermediate1 min read

Key roles in incident response

Incident Commander coordinates and decides but does not fix; Communications Lead handles stakeholders; Operations/SMEs do hands-on diagnosis and remediation.

intermediate2 min read

OpenTelemetry agent and gateway architecture

Agents run per-node for local collection and host enrichment; gateways are central, horizontally scaled pools for batching, tail sampling, and routing.

intermediate1 min read

First-SRE 90-day plan at a startup

Listen and measure first, pick one high-impact service, define SLIs/SLOs and basic alerting, then show reduced toil or incidents to leadership.

intermediate2 min read

Designing shallow vs deep health checks

Shallow checks confirm the process is alive; deep checks verify dependencies; use shallow for liveness/load-balancer routing and deep sparingly to avoid…

intermediate1 min read

Rolling update vs blue-green deployment

Rolling replaces instances gradually with minimal extra capacity but mixes versions; blue-green runs two full environments for instant switch and rollback at double the cost.

intermediate1 min read

Writing high-quality postmortem action items

Good action items are specific, assigned to an owner, prioritized, tracked to completion, and ideally prevent recurrence rather than just detect faster.

intermediate1 min read

Calculating downtime for a 99.9% SLO

0.1% of 30 days is roughly 43 minutes of allowed downtime; healthy budget enables faster shipping while depletion slows or freezes deploys.

intermediate1 min read

Keeping a postmortem blameless after an admission

Acknowledge the courage, redirect from who to why the system allowed it, ask what guardrails were missing.

intermediate1 min read

Conducting a Production Readiness Review

Assess monitoring and alerting, capacity and load testing, failure modes and dependencies, on-call and runbooks, and rollback or release safety.

intermediate1 min read

Embedded vs consulting SRE engagement models

Embedded SREs sit inside one team for deep impact but limited reach; consulting SREs advise many teams broadly but shallowly.

intermediate2 min read

A team keeps blowing its error budget. First steps?

Analyze where the budget is burning via SLIs and postmortems, validate the SLO and SLIs are sound, then partner blamelessly on the top fixes.

intermediate2 min read

Automating chaos in CI/CD for continuous verification?

Run codified experiments against staging or canary with pass/fail on steady-state SLIs; prerequisites are observability, automated abort, and isolation.

We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.

See open roles