Skip to content
Interview rounds

Observability · Design under changing requirements

Thirteen months at full resolution

How do you design hot, warm and cold retention for cost versus usefulness?

Platform-SRESenior10 min
Interview-style scenarioLast reviewed: Checked against official documentation

Quarterly cost review · observabilityIllustrative scenario, not a real incident

Telemetry storage is the fastest-growing line on the infrastructure bill for the third quarter running

Metrics, logs and traces are all kept for thirteen months at the resolution they arrived in, on fast disks. The policy was set when the company was a tenth of its size.

Finance wants the cost halved. The capacity team needs a year of trends, compliance needs audit logs for a year, and incident reviews reach back about two weeks.

What the dashboards and logs show

Retention today
13 months, raw, for every signal
Where it is kept
fast disks for everything
Target
half of today's cost

Clarify · optional · scored under "Hypothesis before change"

Ask the interviewer

0 of 3 asked

Each question reveals a fact. What you ask before you act is part of your score.

First move · scored under "Mitigate before root cause"

The redesign needs a month of analysis, and the bill keeps growing meanwhile. What do you do first?

Your rubric score, the model answer, the follow-up questions and the related lessons appear once you have answered the last step.