What is The Four Golden Signals?
The four golden signals, popularized by Google's SRE practice, are latency, traffic, errors, and saturation: the core set of metrics that, monitored together, give a high-level picture of a production service's health and user experience. They are the first dashboard an on-call engineer opens and the first thresholds a performance test should assert against.
No account needed · Scored in under a minute against a senior rubric
What does The Four Golden Signals mean in practice?
When you can only watch a few things about a running service, these four tell you the most. Latency is how long requests take (and crucially, separating the latency of successful versus failed requests, since fast errors can hide problems). Traffic is how much demand the service is handling (requests per second, transactions). Errors is the rate of failing requests (explicit failures and wrong-but-200 responses). Saturation is how full the system is, how close key resources (CPU, memory, I/O, connections) are to their limits, which predicts impending trouble.
Together they cover both symptoms users feel (latency, errors) and causes you can act on (traffic, saturation). They are a foundation of observability and of defining SLIs and SLOs: good service level indicators are often built directly on these signals (for example, an SLO on p99 latency and error rate).
For QA, especially shift-right and reliability-focused testing, the golden signals are how you verify behavior in production and during load and resilience tests. Rather than only asserting functional correctness, you watch latency, errors, and saturation under realistic and stress conditions to confirm the system stays healthy, connecting testing to real operational quality.
Why do interviewers ask about The Four Golden Signals?
The four golden signals come up in SRE-adjacent, reliability, and observability interviews. Naming latency, traffic, errors, and saturation, and connecting them to SLIs/SLOs and to shift-right and load testing, shows you think about quality in production, not just pass/fail before release.
What does The Four Golden Signals look like in a real project?
During a load test, functional checks pass, but watching the golden signals tells the real story: latency climbs steadily, errors spike past a threshold, and CPU saturation hits 95%, revealing the service degrades well below the target throughput. The team fixes the bottleneck before it would have caused a production incident.
How should you talk about The Four Golden Signals in an interview?
List the four golden signals, latency, traffic, errors, and saturation, and briefly define each (with the nuance of separating failed-request latency). Connect them to SLIs/SLOs and to verifying health during load, resilience, and shift-right testing, to show you tie testing to real production quality.
Go Deeper on The Four Golden Signals
Know the term. These are the courses that turn the concept into something you can demonstrate.
Common questions about The Four Golden Signals
What are the four golden signals?
Latency (how long requests take, separating successful from failed), traffic (how much demand the service handles), errors (the rate of failing requests), and saturation (how full key resources are relative to their limits). Together they summarize a service's health and user experience for monitoring.
How do the golden signals relate to SLIs and SLOs?
They are a natural foundation for them. Service level indicators (SLIs) are often built directly on golden signals, such as p99 latency and error rate, and service level objectives (SLOs) set targets on those indicators. Monitoring the golden signals is how you measure whether a service meets its reliability goals.
Which terms relate to The Four Golden Signals?
Explore related glossary terms to deepen your understanding.
Related Resources
Dive deeper with these related interview prep pages.
Free QA career tools, no account needed
Instant and private, everything runs in your browser. Try them before you sign up.
QA Resume Checker
Instant 0-100 score on automation keywords, impact, and ATS formatting.
QA Cover Letter Generator
A tailored 3-paragraph QA cover letter from your resume and a job post.
QA Application Tracker
Drag-and-drop kanban to track every QA application from Applied to Offer.
QA Take-Home Test Generator
A realistic take-home assignment with a scenario, tasks, and a rubric.
QA LinkedIn Headline Generator
A recruiter-searchable headline, About section, and skills list.
QA STAR Story Builder
Structure a QA behavioral answer with the STAR method and instant checks.
QA Bug Report Generator
Build a clean, reproducible bug report for Markdown, Jira, or plain text.
Boundary Value Analysis Generator
Generate boundary value and equivalence partitioning test cases from a range.
QA Metrics Calculator
Calculate DRE, defect leakage, defect density, and pass rate with interpretation.
QA Test Plan Generator
Build a structured test plan (scope, approach, criteria, risks) in Markdown.
QA Salary Calculator
Estimate QA, SDET, and automation tester pay by level, market, and skills.
QA Offer Evaluator
See total comp, a counter range, and a ready-to-send negotiation message.
Ready to Ace Your QA Interview?
Practice explaining the four golden signals and other key concepts with our AI interviewer.
Join 500+ QA engineers already practicing with AssertHired.
A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.
Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.
Rather skip ahead? Create a free account