Skip to content
Français
Account: not signed in, sync available My learning
Select theme
Français

Career path

Site Reliability Engineer

Make sure production services meet their reliability, availability and performance objectives, by measuring what users experience, automating repetitive work and turning every incident into a lasting improvement.

Aim for this jobWhat this job does

  • 7 responsibilities
  • 14 missions
  • 44 skills
  • 217 hours of work an estimate, starting from zero

The job

What a Site Reliability Engineer does

Seven responsibilities. Each one is carried out through concrete missions, which require skills.

Solve recurring problems at their root cause

Design and improve 1 mission · 2 skills

Missions that make it up

Manage incidents

Do on your own 3 missions · 9 skills

Missions that make it up

Ensure continuity and resilience

Do on your own 2 missions · 4 skills

Missions that make it up

Reduce repetitive work through automation

Do on your own 2 missions · 8 skills

Missions that make it up

Observe and measure the service delivered

Do on your own 2 missions · 7 skills

Missions that make it up

Also required, outside missions

Change and deploy without putting the service at risk

Do on your own 3 missions · 12 skills

Guarantee service reliability and performance

Do on your own 1 mission · 5 skills

Missions that make it up

The means

With which tools?

Choose your tools: the choice changes the lessons to read, never the responsibilities.

GitOps tool

Automation language

Going further

Specialisations

Optional, measured apart from the job.

What the site does not cover yet

Signal correlation and distributed tracing: taught as concepts (optional module of the Observability training), with no published hands-on content (Tempo distributed tracing and correlation labs still in draft), with no active skill. Instrumenting a service (traces emitted and checked) and tracing an LLM application's calls into Tempo are practised and recommended; correlating signals and following a distributed trace across services remain concepts.

Non-functional testing (SFIA NFTS): covered by sizing and scaling. Controlled fault injection is being prepared (draft ops.fault.inject); the mission "Test a service's reliability with an induced failure" will join the role once it is taught. Load testing is not taught yet.

Problem management (SFIA PBMG level 4): the responsibility is only carried today by repairing an incident; the level 4 gesture (incident trends, root cause, lasting fix) is being prepared (draft ops.problem.resolve).

Data analytics (SFIA DAAN): limited to reading service measurements, level 2.

Is this project useful to you?

The guides, courses, quizzes and labs stay free. If you use them regularly, you can contribute to their upkeep and development.

Become a supporting member (new tab) One-time support (new tab) Learn more

Follow the project on LinkedIn