VOLOVLOAutomation risk & transition, task by task
AskOccupationsMajorsBusinessFoundersChangesNotesMethod
Search occupations, majors…
EN
  • English
  • 简体中文
  • 日本語
  • Español
  • Português
  • Français
VLO
VOLO

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

AskOccupationsMajorsBusinessFoundersChangesNotesMethodAboutRole diagnosisPrivacyTerms
© 2026 VOLO
Since 2 August 2026… — impact on machine learning engineers | 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›Machine learning engineer›2026-08-02
ConstraintCognitive automation2026-08-02

Since 2 August 2026 the EU AI Act requires the data behind a high-risk AI system to be examined for bias and documented as fit for its intended purpose (Article 10)

Machine learning engineeroccupation page →
Event date / reported
2026-08-02
Evidence stage
ConstraintFailure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
Tasks this bears on
Answering for what it does to people
Explaining a decision the system made about someone, showing the inputs were fit for the purpose, and being the named person when it is challenged.
New task✓ Evidence-backed
Where this applies
The EU market, and only for high-risk systems under Article 6 that are trained on data — the duty falls on the provider, which is the organisation, not the individual engineer. It is recorded against answering for what the system does to people rather than against the data-preparation task itself: Article 10 governs how that data work must be done, but says nothing about how much of it a machine now does, and attaching it to the direction of that task would claim more than the text supports. What it does establish is that being able to show the data was suitable for the purpose, examined for bias and gap-checked has moved from professional practice to a documented legal duty. The article says nothing about how many teams already work this way, what it costs, or what applies outside the EU.
What this means
A constraint record on being answerable for what the system does to people: from 2 August 2026, showing that the training, validation and testing data was suitable for the intended purpose, examined for bias and checked for gaps is a documented legal duty for the provider of a high-risk system, not a matter of professional practice.
What it does not yet show
The duty falls on the provider organisation, not on a named engineer. The article does not say how many teams already work this way, how much of the data work a machine now does, what any of it costs, or what applies outside the EU.
What you can check
Take one model your team ships into a decision that touches people and ask where the written answer to 'why was this data suitable for this purpose' lives. Article 10(2)(h) also asks for the gaps to be identified, so look for what the document says is missing — a data note with no absences listed is usually a data note nobody stress-tested.
Does it change the assessment?
No. The impact index is never moved by a single event. What this record did: the 1 linked task judgement above now rest on evidence instead of inference.
Source
Regulation (EU) 2024/1689 (Artificial Intelligence Act), Article 10 — EUR-Lex, the Official Journal's own portal · verified 2026-09-15 · Claude Opus 5 (agent) · interpreted 2026-09-15 · Claude Opus 5 (agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
All changes for Machine learning engineer →All recent changes →How events become evidence →