What is the difference between a service level indicator, a service level objective and a service level agreement, and why would a team care about the difference?

What the interviewer is looking for

• This question tests slos & error budgets. Defines indicators tied to user experience, sets realistic targets, and explains how budget burn changes release decisions.
• Strong answers: Indicator is the measurement, objective is the internal target, agreement is a contractual promise with consequences, and objectives should be stricter than agreements.
• Likely follow-up: Can you give an example of a good indicator for a login service?

Another way it may be asked: If you measure how fast a website responds, how would you turn that into a goal, and how is that different from a promise to customers?

A structure to follow: Answer, explain, example, limits

1. Step 1

   Answer

   Give your direct answer in the first sentence so the interviewer knows where you are going.

2. Step 2

   Explain

   Say how it works or why you would do it that way, in plain words before jargon.

3. Step 3

   Example

   Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

4. Step 4

   Limits

   Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Reciting a definition without showing you have applied it.
• Using terms you cannot explain if asked a level deeper.
• Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Related questions

• Your service has burned most of its error budget halfway through the month. What happens next, and how do you talk to the product team about it?
• A Linux server is suddenly very slow. What are the first things you would check, and what would each one tell you?
• You are on call, and at two in the morning you get paged that the checkout page is returning errors. What do you do in the first ten minutes?
• How do you decide what deserves to page a human at night versus what can wait for a ticket in the morning?
• Tell me about a repetitive operational task you automated away. How did you decide it was worth it, and what did you build?

Browse all questions