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›Junior software developer›2025-07-25
PilotCognitive automation2025-07-25

At an IT consulting firm, LLM-drafted requirements saved an analyst 10–15% of drafting time but missed user stories whose knowledge was tacit, and could not replace the analyst

Junior software developeroccupation page →
Event date / reported
2025-07-25
Evidence stage
PilotSmall-scale trial in a real setting. Tells us the deployment conditions are being tested, not that they hold — so one pilot is never enough on its own; two independent ones are.
Tasks this bears on
Turning a vague request into a spec
Asking the questions that reveal what should actually be built.
Still human-led≈ Platform inference
Where this applies
A university study of language models drafting requirements specifications on one project at an IT consulting company, assessed by the company's expert analyst. A subset of user stories stayed unaddressed across all models because the knowledge analysts hold can be tacit and not written in the elicitation documents; the analyst estimated drafting time savings of 10% to 15%, and the authors conclude the models can help early documentation but cannot replace human intervention. It is one project with one expert, and the role studied is requirements analyst rather than developer.
What this means
Drafting a specification can start from a machine draft, but what makes a request buildable — the knowledge nobody wrote down — stays with the person who asks the questions.
What it does not yet show
One project and one analyst; it does not show how juniors work on requirements or anything about hiring.
What you can check
Open arXiv:2507.19113 and find "Overall, LLMs can enhance productivity in the early phases of documentation and definition of requirements but cannot replace human intervention".
Does it change the assessment?
No. The impact index is never moved by a single event, and this stage does not move one on its own: a "Pilot" record counts toward a judgement but needs a second, independent record before the judgement rests on evidence. This one is counted; on its own it changed nothing.
Source
Pasquale, Ragone et al. (University College Dublin, University of Bari) — "Exploring the Use of LLMs for Requirements Specification in an IT Consulting Company", arXiv:2507.19113 (25 July 2025) · 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 Junior software developer →All recent changes →How events become evidence →
At an IT consulting… — impact on junior software developers | VOLO