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 dataOntologyVOLO ProPrivacyTerms
© 2026 VOLO
Guides
Ask VOLOFor businessFor foundersRecent changesNotesRole diagnosisFirst AI experimentVOLO ProMethod & 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 developerInsurance underwriterHR / 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 engineerProject managerLawyerMedical assistant / clinic assistantQuantity surveyorMachine 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 officerSonographerAir 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›Machine learning engineer›2025-11-21
DeploymentCognitive automation2025-11-21

Instacart replaced separately trained query-understanding models with one fine-tuned LLM serving millions of weekly searches, moving its engineers' core challenge away from feature engineering

Machine learning engineeroccupation page →
Event date / reported
2025-11-21
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
Building a model for the problem
Picking an architecture, training it on your data, tuning it until the numbers move.
Automating✓ Evidence-backed
Hand-crafting the inputs
Designing the derived signals a model learns from, by hand, from domain knowledge.
Automating✓ Evidence-backed
Where this applies
Five named Instacart engineers describing their own search system. They say Instacart historically trained and maintained multiple independent models for individual query-understanding tasks, each bespoke solution with its own data pipeline, training and serving architecture; that replacing these specialised models with a single LLM handling multiple language tasks removes the complexity of maintaining separate models; that the system is now live, serving millions of cold-start queries weekly; and that it has shifted their core challenge from feature engineering to productionising these backbones while managing latency and cost. One company and one system, described by the team that built it; it says nothing about how many ML engineers Instacart employs or whether their number changed.
What this means
At one large marketplace, the bespoke models an ML engineer used to build and tune for each search task were folded into one fine-tuned foundation model, and the hand-designed features went with them. The work moved to getting that model into production cheaply and fast.
What it does not yet show
It is one company's own account of one system; it gives no figures on engineering staff and does not show the same shift elsewhere.
What you can check
Open Instacart's post "Building The Intent Engine" and find "It has shifted our core challenge from feature engineering to productionizing these powerful backbones".
Does it change the assessment?
No. The impact index is never moved by a single event. What this record did: the 2 linked task judgements above now rest on evidence instead of inference.
Source
Instacart — "Building The Intent Engine: How Instacart is Revamping Query Understanding with LLMs" (Nov 21, 2025), by five Instacart engineers · verified 2026-09-27 · Claude (VOLO agent) · interpreted 2026-09-27 · Claude (VOLO 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 →