What is Service Level Objective (SLO)?

A Service Level Objective (SLO) is a target value or range for a measured aspect of service reliability, for example "99.9% of requests succeed" or "95% of requests complete under 300ms", that a team commits to meeting over a window.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

SLOs sit in a trio. A Service Level Indicator (SLI) is the actual measurement (the observed success rate or latency). The SLO is the target for that SLI. A Service Level Agreement (SLA) is a contractual promise to a customer, usually looser than the internal SLO, with penalties if breached. So SLI is what you measure, SLO is what you aim for, and SLA is what you promise externally.

SLOs reframe quality from "no bugs" to "reliable enough." A 100% reliability target is neither achievable nor worth the cost; an SLO defines the right amount of reliability and makes trade-offs explicit. The gap between the SLO and 100% is the error budget, the amount of unreliability you can spend on shipping features and taking risks.

For QA and SDET work, SLOs matter because they shape what to test and how hard. Testing protects the journeys tied to your most important SLOs; performance tests assert against latency SLOs; synthetic monitoring and alerting watch SLIs in production. Speaking in SLO terms signals you think about reliability the way modern SRE-influenced teams do.

WHY IT MATTERS

Why interviewers ask about this.

SLOs come up in interviews for SDET, performance, platform, and lead roles. Knowing the SLI/SLO/SLA distinction and tying testing decisions to reliability targets shows you think about quality as managed risk, not perfection.

EXAMPLE

Example scenario.

A checkout service has an SLO of 99.9% availability and 95th-percentile latency under 400ms. The performance suite asserts the latency SLO under load, synthetic checks watch the availability SLI in production, and a release that would push latency over the SLO is held, the objective makes the go/no-go call objective.

TIP

Interview tip.

Cleanly separate SLI (the measurement), SLO (the internal target), and SLA (the external contractual promise). Then connect SLOs to testing: what you protect, what your performance tests assert, and what monitoring watches.

FAQ

Frequently asked questions.

What is the difference between an SLO, an SLI, and an SLA?

An SLI is the actual measurement (observed success rate or latency). An SLO is the internal target for that SLI. An SLA is the external, contractual promise to customers, usually looser than the SLO, with penalties for breach.

Why not aim for 100% reliability?

100% is unachievable and not cost-effective. An SLO defines "reliable enough", and the gap between the SLO and 100% becomes the error budget you can spend on shipping features and taking calculated risks.