Site Reliability Engineer assigned to your roadmap.
A Site Reliability Engineer treats uptime as something engineered rather than hoped for, with measurable targets and a plan for when they are missed.
Assigned under one service agreement with a minimum monthly capacity in hours, run by a service delivery manager in Chiang Mai, Thailand — five hours ahead of Northern Europe.
This role is delivered as part of our cloud and DevOps services. Take the role on its own, or the whole discipline as one delivery team.
What a Site Reliability Engineer does on a managed DevOps team.
Skills and scope are agreed before delivery starts, so the first sprint is productive rather than a ramp-up month. The work runs to the same backlog, the same repositories and the same definition of done as your own team's.
Site Reliability Engineer skills and technology we assign for
-
Defining service level objectives and error budgets that product and engineering both accept.
-
Building observability so an incident is diagnosed from data rather than guesswork.
-
Incident response, on-call process and blameless postmortems that change something.
-
Capacity planning against growth so scaling is a decision rather than an emergency.
-
Running game days to test whether the runbooks actually work under pressure.
Seniority levels we assign.
Senior and principal. SRE is a judgement role, and junior SRE tends to produce dashboards rather than reliability. Seniority is one of the inputs behind the committed monthly capacity written into your agreement.
When a Site Reliability Engineer is the right assignment.
Makes sense once downtime has a measurable commercial cost. On an ongoing roadmap this role is most often assigned alongside a DevOps Engineer or a Cloud Engineer. All 4 roles in this service line can sit on the same agreement, and capacity moves between them at the monthly cycle rather than requiring a new contract. This capacity is assigned under DevOps as a service rather than sold as a separate engagement.
Questions about assigning a Site Reliability Engineer.
Do we need an SRE if we already have DevOps?
Not always. SRE makes sense once downtime has a measurable commercial cost and someone needs to own that number.
Will the SRE take on-call?
Within agreed hours, yes. Thai working hours cover a European afternoon, and the arrangement is set out in the agreement.
Add site reliability engineer capacity to your roadmap.
Tell us the scope and the stack. We come back with the profile, the capacity and what the first month looks like, or you can talk to a service delivery manager first.
Assign a Site Reliability Engineer to your roadmap.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.