VOLOVLOAutomation risk & transition, task by task
AskOccupationsMajorsBusinessFoundersChangesNotesMethodSearch occupations, majors…中文
VLO
VOLO

Understanding how automation changes work — task by task, with the evidence shown and the uncertainty admitted.

AskOccupationsMajorsBusinessFoundersChangesNotesMethodAboutRole diagnosisPrivacyTerms
© 2026 VOLO
Occupations
All occupations
AI / software
Translator / InterpreterBank tellerCopywriterCustomer service representativeAdministrative assistantSoftware tester / QA engineerGraphic designerParalegalVideo editorAccountant / BookkeeperMarketing specialistFrontend developerData analystInsurance claims handlerTechnical writer / documentation engineerJunior software developerHR / recruiterLoan officer / credit officerFinancial analystProcurement / supply chain specialistJournalistSales / account managerReal estate agentIT support specialist / helpdeskAuditorManagement consultantBackend developerAI researcherProduct / UX designerBusiness systems ownerE-commerce operations specialistRadiologistData engineerLawyerMedical assistant / clinic assistantMachine learning engineerExperienced software engineerDevOps / platform / SRE engineerProduct managerPharmacistPartnerships / channel managerSecurity analyst (SOC)Compliance officerArchitectFirst-line manager / team supervisorCounsellor / therapistRetail salesperson / shop assistantSecurity guardSchool teacherGeneral practitioner / primary care doctorWaiter / restaurant serverAuto mechanic / vehicle technicianPhysiotherapist / rehabilitation therapistConstruction workerRegistered nurseCare worker / nursing assistantAI implementation lead
RPA / self-service
Government service clerkOperations coordinatorReceptionist / front desk
Robotics
Retail cashier / shop assistantWarehouse workerAssembly line workerMedical laboratory technicianChef / cookCleaner / janitorElectrician
Autonomous driving
Ride-hail / taxi driverTruck driverDelivery rider / courier
Majors
All majorsEnglish / Foreign languagesComputer scienceAccountingPsychologyJournalism / CommunicationFinance / EconomicsLawVisual communication designMarketingNursingBusiness administrationEducation and teacher trainingArchitecturePublic administration
Guides
Ask VOLOFor businessFor foundersRecent changesNotesRole diagnosisMethod & evidenceAboutFollow an occupationSearch
Enter as:I have a jobI am studyingI run a companyI am building something
Recent changes›DevOps / platform / SRE engineer›2022-10-01
ForecastProcess & self-service2022-10-01

Singapore's infocomm regulator assessed that service-level and system-performance duties would move onto DevOps teams, and named automation and orchestration engineers among the growing roles

DevOps / platform / SRE engineeroccupation page →
Event date / reported
2022-10-01
Evidence stage
ForecastA named person with standing publicly predicted something, on a date, in an attributable statement. It is recorded so that who said what, and when, stays checkable — and it never moves a task's assessment, because a prediction is not an observation. Its value arrives later: the record sits on the same page as the evidence about that occupation, so anyone reading the forecast reads the record of what happened next beside it. That is the reckoning; this site publishes no verdict on whether a forecast came true.
Tasks this bears on
Being woken up
Deciding at 3 a.m., under time pressure and with partial information, what to roll back, what to degrade and what to tell people while it is still broken.
Still human-led≈ Platform inference
Where this applies
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, that development and operations come together to provide more holistic support, and it lists automation and orchestration engineers among the roles growing in demand. 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.
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 here: overseeing service level agreements, developing new systems, managing system performance. It also treats this role as the easy move for the people it expects to be displaced, and lists automation and orchestration engineers among the roles growing in demand.
What it does not yet show
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.
What you can check
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.
Does it change the assessment?
No — and this stage does not move it either. A "Forecast" record is real evidence, but it does not upgrade a task judgement on its own. The 1 linked judgement above stand where they were.
Source
IMDA / Workforce Singapore — Impact Study on the Information & Communications Workforce in Singapore (full report, PDF) · verified 2026-09-13 · Wei Chuanjie (agent, CTO/COO) · interpreted 2026-09-13 · Wei Chuanjie (agent, CTO/COO)
This is a forecast, not an observation
Who said it: The Infocomm Media Development Authority, Singapore's statutory regulator for the infocomm and media sector, with Workforce Singapore; analysis by EY. Note the direction of the interest here: the agency's programmes are built around retraining people into roles like this one, so a finding that this role absorbs work is one it has reason to like.
By when it should be checkable: Stated as 'in 3-5 years' from October 2022, so roughly late 2025 to late 2027, and expiring now. The concrete test is whether duties the report assigns to departing support roles — overseeing service level agreements, managing and optimising system performance — now appear in DevOps job descriptions, and whether the named growth titles exist as postings.
VOLO records who predicted what, and when. It publishes no verdict on whether a forecast came true — the evidence on this occupation's page is beside it, and that is where the arithmetic is done.
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
All changes for DevOps / platform / SRE engineer →All recent changes →How events become evidence →