Remote work – not AI – is killing job prospects for the youth(theregister.com)

Blaming remote work ignores that my district cut two paraprofessional roles last year specifically because Khanmigo and MagicSchool handle the small-group reteaching a 22-year-old aide used to do. The entry rung wasn't shipped to someone's spare bedroom, it got absorbed by a chatbot the principal pays $15 a seat for. Remote work didn't write those lesson plans at 2am, GPT did.

Cut my lab's in-person onboarding from 6 weeks to 2 after we lost 3 RAs in a row who'd never met anyone on the team and ghosted by month four. Now first-year RAs are required on-site Tues-Thurs and pair-shadow a senior student for the first month, and retention's back up.

The post frames remote as the cause, but my team went hybrid two days a week last September and the seniors still spend those days in back-to-back Zooms with the other office. Proximity does not equal mentorship if nobody has slack in their calendar to actually teach. Fix the workload before blaming the location.

Agreed, the casual osmosis of watching a senior pitch a client or rework copy at 4pm is gone, and Slack threads don't replicate it. When I onboarded two juniors last year for a brand AI rollout, the ones who came into my home office twice a week were billing solo within four months while the fully remote hire was still asking permission to send drafts.

Cut our junior intake from 6 to 2 last year and the official reason was "AI makes seniors more productive," but the actual reason was nobody wanted to mentor over Zoom anymore. The two we kept happen to live within 40 minutes of the office, which tells you everything about what's actually being measured.

What ratio of remote-to-office days did your team land on before junior associates started picking up procedural nuance again?

Remote work didn't kill juniors, the agents we're shipping did. My team replaced two junior tickets a sprint with a Claude loop that opens PRs against a scoped repo, and the senior reviewers prefer it because the bot takes feedback without ego. Blame the office calendar all you want, the headcount math changed when one staff engineer started merging six agents worth of work.

Cut 3 junior hires from this year's plan because our remote-first setup means nobody's around to shoulder-surf during incident response, and pairing over Zoom for an 8-hour debugging session just doesn't stick the same way. Switched to contracting a senior consultant for the same budget, which solves my staffing problem but leaves zero entry points for grads trying to break into data engineering.