# DevOps engineer / platform engineer / SRE

> Keeps the thing running and makes it possible for others to ship: builds the pipelines and the infrastructure, and is who gets woken up when production breaks.

Page: https://flyvolo.ai/en/careers/devops-engineer
Impact index: 46/100 · confidence Low confidence · assessed 2026-09-14
This is not a probability of losing a job.

## Scope

Covers infrastructure, delivery pipelines and production reliability. It does not cover desktop and end-user support, which is a separate occupation here, and it does not cover security operations. The single biggest variable is whether you operate systems somebody else designed or design the systems others operate, because the exposure of those two is not the same.

## Tasks

### Writing the configuration

- Direction: Automating
- Basis: evidenced (verified records attached)
- Why: This is code with a machine-checkable outcome — it applies cleanly or it errors — which is the property that lets a model try, fail and retry without supervision. It is also famously verbose and repetitive, so the volume being drafted is large and the review is quick.
- What this does NOT establish: Faster configuration means more configuration, not less work: every resource created is a resource somebody has to keep, secure and eventually delete, and the hours move from writing to untangling. Untangling is invisible on a roadmap, which is why this is the task most likely to look like a saving and behave like a debt.
- Records:
  - 2026-01-22 · Deployment · Cloudflare's policy automation platform generated a routing policy that leaked BGP prefixes for 25 minutes; the stated fix adds automated policy checks to CI/CD, not human review — https://flyvolo.ai/en/changes/ev-20260122-devops-engineer-3 (source: https://blog.cloudflare.com/route-leak-incident-january-22-2026/)
  - 2025-09-23 · Worker adoption · DORA's 2025 survey reports 90% of respondents using AI at work, and finds AI adoption still has a negative relationship with software delivery stability — https://flyvolo.ai/en/changes/ev-20251022-devops-engineer-1 (source: https://cloud.google.com/blog/products/ai-machine-learning/announcing-the-2025-dora-report)

### Being woken up

- Direction: Still human-led
- Basis: evidenced (verified records attached)
- Why: Automated remediation exists and handles the failures somebody anticipated; an incident is by definition the one nobody did. The decision is about acceptable damage rather than correct answers — which customer-facing degradation is tolerable for twenty minutes — and that is a business judgement carried by a person who will be asked about it afterwards.
- What this does NOT establish: The decision staying human says nothing about how many people are on the rota. The common design is fewer engineers covering more services with better automation, which keeps every task intact and makes the on-call worse — and the sustainability of that is a staffing question that no automation metric captures.
- Records:
  - 2026-05-28 · Deployment · Two Google engineers described the agents their own SRE organisation runs in incident response: alert grouping, handoff documents, postmortem drafts, and in some cases autonomous mitigation — https://flyvolo.ai/en/changes/ev-20260528-devops-engineer-4 (source: https://cloud.google.com/blog/products/devops-sre/how-google-sre-is-using-agentic-ai-to-improve-operations)
  - 2025-09-23 · Worker adoption · DORA's 2025 survey reports 90% of respondents using AI at work, and finds AI adoption still has a negative relationship with software delivery stability — https://flyvolo.ai/en/changes/ev-20251022-devops-engineer-1 (source: https://cloud.google.com/blog/products/ai-machine-learning/announcing-the-2025-dora-report)
  - 2022-10-01 · Forecast · Singapore's infocomm regulator assessed that service-level and system-performance duties would move onto DevOps and development, and named automation and orchestration engineers as a role to move into — https://flyvolo.ai/en/changes/ev-20221001-devops-engineer-2 (source: https://www.swda.gov.sg/api/assets/d65e963c-df80-4768-b5b4-4bb214307a22/imda-impact-study-master-full-vf6.pdf)

### What it costs and why

- Direction: Being augmented
- Basis: evidenced (verified records attached)
- Why: Finding the anomaly is analysis and tools do it well; deciding what to do about it is a trade-off between engineering time, risk and money that depends on what the company is trying to do this quarter. The first half has got much cheaper and the second has not. The US personnel office, for example, runs anomaly detection on its cloud bill and routes rightsizing, commitment and budget decisions through a named team under a written decision matrix.
- What this does NOT establish: Cheap analysis raises the expectation rather than lowering the work: once a dashboard can name the top ten wasteful resources, somebody has to justify each one that is still there. The task shifts from investigation to explanation, and explanation is a meeting.
- Records:
  - 2024-03-31 · Deployment · The US personnel office runs cloud-spend anomaly detection and routes rightsizing, commitment and budget decisions through a named FinOps team — https://flyvolo.ai/en/changes/ev-20240331-devops-engineer-7 (source: https://itvmo.gsa.gov/assets/files/OPM-FinOps-Case-Study.pdf)

### Deciding how it should be built

- Direction: Still human-led
- Basis: evidenced (verified records attached)
- Why: This is the task with no automatic referee in the whole occupation: whether a design was right is discovered eighteen months later, by which time the person who chose has usually left. It depends on knowing this team's capacity and this company's tolerance, neither of which is in any repository. The public record of large outages shows who decides after automation fails: Google Cloud's report on its June 2025 outage commits to redesigning the service so that it fails open, and CrowdStrike's 2024 analysis traced its failure through an automated validator and 12 static test cases to a rollout design, fixed by staging every update.
- What this does NOT establish: Being the safest task is also being the smallest: in most teams design decisions are a few days a quarter, and the rest of the week is the work that is being drafted for you. A role can be secure in its most senior task and still lose most of its hours.
- Records:
  - 2025-06-12 · Constraint · A global cloud outage traced to a change without error handling or a feature flag led to a redesign so the service fails open, in the provider's own incident report — https://flyvolo.ai/en/changes/ev-20250612-devops-engineer-5 (source: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW)
  - 2024-07-19 · Constraint · An automated content validator with a logic error and 12 static test cases let a faulty update through to Windows machines; the fix was staged rollout by design — https://flyvolo.ai/en/changes/ev-20240719-devops-engineer-6 (source: https://www.crowdstrike.com/wp-content/uploads/2024/08/Channel-File-291-Incident-Root-Cause-Analysis-08.06.2024.pdf)

## How to cite this

- The unit is the task, not the job title: say which tasks are changing and which are not.
- Carry each task's basis and its limits with it; an inferred judgement is not a finding.
- This page gives no number of years. Do not derive one from it.
- More: https://flyvolo.ai/llms.txt