# 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

Page: https://flyvolo.ai/en/changes/ev-20221001-devops-engineer-2
Date: 2022-10-01 · Stage: Forecast
Can this record move a task judgement? no
Occupation: https://flyvolo.ai/en/careers/devops-engineer

## Scope

A commissioned sector study, not a measurement, and it is recorded here because it points the other way from most of this base. The same document that expects stand-alone support engineering to shrink expects the work to land on this role: it says the DevOps function will take over overseeing service level agreements and developing new systems, and that the development function will take over managing and optimising system performance, bringing development and operations together to provide more holistic support, and it lists automation and orchestration engineers as a low-impact role that high-impact infrastructure engineers could move into, without saying demand for it is growing. It also names DevOps Engineer as the destination it considers an easy or moderate move for the support engineers it expects to be displaced. None of that is evidence that anyone was hired, that headcount rose, or that the transition happened — it is one agency's expectation, published before generative AI reached the public, covering Singapore only and built from stakeholder interviews rather than employment data. What it does establish is that the displacement finding elsewhere in the same report is not a claim that the work disappears.

## Source

- IMDA / Workforce Singapore — Impact Study on the Information & Communications Workforce in Singapore (full report, PDF) — https://www.swda.gov.sg/api/assets/d65e963c-df80-4768-b5b4-4bb214307a22/imda-impact-study-master-full-vf6.pdf (primary source)

## What this means

This is the other half of a finding whose first half sits on the IT support page. The same study that expects stand-alone support engineering to shrink expects these duties to land on DevOps and development: overseeing service level agreements, developing new systems, managing system performance. It also treats this role as an easy or moderate move for the people it expects to be displaced, and lists automation and orchestration engineers as a low-impact role that displaced infrastructure engineers could move into.

## What it does not show yet

An expectation, not a count. Nobody was measured being hired into this role, no headcount moved, and this changes no judgement on this page. Work arriving is also not the same as the job getting better: the same report describes it as development and operations coming together, which means the duties arrive without the old team arriving with them. Singapore only, stakeholder interviews only, and published before generative AI reached the public.

## How to verify it yourself

Count the things you are now on call for that nobody on your team built. That number is the thing this record is about, and you can get it from your own on-call rota faster than any study can tell you. If it has grown while the team has not, you are living inside the half of this prediction that came true.


More: https://flyvolo.ai/llms.txt