Design Anomaly Detection

Hard45 min
1 / 30
understanding6 min read

Problem Statement & Context

How Problem Statement & Context shapes architecture and interviewer follow-ups for Design Anomaly Detection.

Problem Statement & Context

You are designing multi-tenant observability anomaly detection — the pipeline Datadog, Dynatrace, and AWS DevOps Guru run over metrics, logs, and traces. This section focuses on mission, personas, and why anomaly detection is not threshold alerts. Interviewers expect you to separate streaming ingest (durable, partitioned) from detection (seasonality-aware, low false positives) and alert delivery (SLO-aware, deduplicated).

  • 1.1: detect abnormal metric/log/trace behavior per tenant
  • 1.2: minimize alert fatigue while catching real incidents
  • 1.3: support SRE, security, and product analytics personas

Mechanism

Customers ship telemetry via agents and OpenTelemetry. The platform maintains per-series baselines (STL, Holt-Winters, or learned encoders), scores recent windows, and emits incidents with severity, context graphs, and runbook links. Security teams want UEBA-style spikes; SRE wants saturation before paging.

Interview phrasing

Open with scale: 40K tenants, 12M active series, 8M points/sec peak. State detection SLO 60s for infra metrics vs 5m for business KPIs.

Failure mode to volunteer

Static thresholds on elastic workloads—Kubernetes CPU at 80% is normal during batch, catastrophic on API tier.

SignalTarget
Peak ingest8M pts/s
Active series12M
Detect SLO60s
Noise reduction70%
javaOne Dark Pro
1public record TenantContext(String orgId, String env, String service) {}
pythonOne Dark Pro
1def is_multi_tenant(org_id: str) -> bool:
2 return bool(org_id)
typescriptOne Dark Pro
1export interface TenantContext { orgId: string; env: string; service: string; }

Why interviewers care

Anomaly Detection interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

Interview checkpoint

Name one failure story for Problem Statement & Context that proves you understand real outages, not happy-path diagrams.

Key Highlights

  • Problem Statement & Context: mission, personas, and why anomaly detection is not threshold alerts
  • Ops angle: support SRE, security, and product analytics personas
  • Metric anchor: 8M pts/s / 60s
Interviewer signal
Volunteer Static thresholds on elastic workloads—Kubernetes CPU at 80% is normal during batch, catastrophic on API tier.
Avoid
Static thresholds on elastic workloads—Kubernetes CPU at 80% is normal during batch, catastrophic on API tier.
Strong move
Open with scale: 40K tenants, 12M active series, 8M points/sec peak. State detection SLO 60s for infra metrics vs 5m for

Section Rescue Kit

Buzzwords to use:

Seasonality bandIncident group

Safe statements:

  • "For Problem Statement & Context, I anchor on 8M points/sec and 60s detection SLO."
  • "I separate ingest durability from detector freshness and alert routing budgets."
Design Anomaly Detection - System Design | WinJob | WinJob