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.

AskOccupationsMajorsBusinessFoundersChangesNotesMethodWill AI replace my job?AboutRole diagnosisOpen dataOntologyPro MCPPrivacyTerms
© 2026 VOLO
Guides
Ask VOLOFor businessFor foundersRecent changesNotesRole diagnosisFirst AI experimentMethod & evidenceAboutFollow an occupationSearch
Occupations
All occupations
AI / software
Translator / InterpreterBank tellerCopywriterContent moderatorCustomer service representativeAdministrative assistantSoftware tester / QA engineerGraphic designerParalegalVideo editorAccountant / BookkeeperMarketing specialistFrontend developerTax preparer / tax agentVoice actorMedical coderData 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 specialistActuaryRadiologistData engineerLawyerMedical assistant / clinic assistantMachine learning engineerExperienced software engineerDevOps / platform / SRE engineerProduct managerPharmacistPartnerships / channel managerSecurity analyst (SOC)Financial adviser / financial plannerCompliance officerLibrarianArchitectFirst-line manager / team supervisorCounsellor / therapistRetail salesperson / shop assistantCivil / structural engineerSecurity guardBus driverInsurance agentSchool teacherGeneral practitioner / primary care doctorAirline pilotWaiter / restaurant serverRadiographer / radiologic technologistAuto mechanic / vehicle technicianPolice officerAir traffic controllerVeterinarianPhysiotherapist / rehabilitation therapistDentistConstruction workerSocial workerRegistered nurseCare worker / nursing assistantPlumberAI implementation lead
RPA / self-service
Government service clerkOperations coordinatorMetro train driverReceptionist / front desk
Robotics
Retail cashier / shop assistantContainer port workerWarehouse workerAssembly line workerMedical laboratory technicianWelderChef / cookCleaner / janitorFarmerFirefighterCabin crewElectrician
Autonomous driving
Ride-hail / taxi driverTruck driverDelivery rider / courier
Majors
All majorsEnglish / Foreign languagesComputer scienceAccountingPsychologyJournalism / CommunicationFinanceLawVisual communication designMarketingNursingBusiness administrationEducation and teacher trainingArchitecturePublic administrationMedicineHospitality and tourism managementEconomicsInformation systems
Enter as:I have a jobI am studyingI run a companyI am building something
Recent changes›Backend developer›2024-10-29
DeploymentCognitive automation2024-10-29

Alphabet's CEO said on the Q3 2024 earnings call that more than a quarter of all new code at Google is generated by AI, then reviewed and accepted by engineers

Backend developeroccupation page →
Event date / reported
2024-10-29
Evidence stage
DeploymentAn employer has put it into production. Can move the baseline — weighted by scale and how similar the setting is.
Tasks this bears on
Endpoints and the plumbing between them
CRUD, validation, serialisation, calling one service from another, and the tests for all of it.
Automating✓ Evidence-backed
Where this applies
One large technology company, company-reported, with no definition of how 'generated' is measured (autocomplete versus whole functions). The figure covers all new code at Google without saying what kind; it attaches to this task because writing routine service code — handlers, validation, calls between services and their tests — is what this task is, not because the statement singles out backend work. It says nothing about hiring, and the review step stayed with engineers.
What this means
Code generation at production scale in one of the largest engineering organisations, with engineers reviewing and accepting what is generated. For a backend developer this is the routine layer — handlers, validation, serialisation, calls between services — running through generation, with the review staying with people.
What it does not yet show
'More than a quarter' is a CEO's remark with no definition of 'generated' — a completed line and a whole function count the same — and it does not say which code: services, front ends, tests or infrastructure. It describes one company's pipeline, not backend work in general, and says nothing about headcount.
What you can check
Open Google's transcript of the CEO's remarks for the Q3 2024 earnings call and find the sentence on the share of new code generated by AI; note that it covers all new code at Google and that engineers review and accept it.
Does it change the assessment?
No. The impact index is never moved by a single event. Nor did this record change a layer: all 1 linked judgement above already rested on earlier evidence. This one adds to them.
Source
Google — CEO remarks, Alphabet Q3 2024 earnings call · verified 2026-09-26 · Claude (VOLO agent) · interpreted 2026-09-26 · Claude (VOLO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
All changes for Backend developer →All recent changes →How events become evidence →