we cover >the future of work_

about
back to feed

11 comments

0sarozarena·1w
Great analysis. As more execution gets automated, the scarce skills become judgment, taste, trust, coordination, and knowing what is worth building in the first place. The next wave of engineering may be less about writing every line of code and more about orchestrating humans and AI systems toward better outcomes.
0omarKhaled·1w
Matches what I'm seeing on our side. We cut two contractor roles last quarter because three of our staff engineers now ship features with Claude that used to need a five-person pod.
0diego.rivas·1w
Cut my planned engineering hires from 4 to 1 this year after rebuilding our internal tooling around a Claude Opus + custom eval harness I wrote myself over six weekends. The one hire we're making is someone who can read agent traces and write evals, not someone who ships features.
0MiaJ·1w
mid-level backend roles around me are basically rfp wars now
0diego.rivas·1w
The "junior dev market is dead" framing in the post misses that I've hired two juniors this year specifically because they can drive Claude Code and Cursor harder than my seniors who keep fighting the tools. The bottleneck isn't experience anymore, it's taste plus willingness to babysit eight parallel agent runs without losing the plot. Pipeline's fine if you stop screening for the 2019 job description.
0laylahaddad·1w
Cut our tier-1 ticket queue by 60% after wiring up an agent that drafts replies and pulls order context from Shopify before a human ever sees it. Went from 14 reps to 7 over nine months, and the remaining team mostly handles edge cases and angry escalations now.
0AishaKapoor·6d
Four clients right now, all SaaS shops between 8 and 30 engineers. Three of them hired me specifically to clean up agent-generated code their juniors shipped last year, mostly Cursor output that nobody reviewed properly. My rate went from $140 to $185 since January and I'm still turning work away. The weird part is two of these clients laid off mid-levels in 2025 and are now paying me more per month than those salaries cost them, because nobody internal wants to own the cleanup.
0raj.patel·5d
Hiring senior people who can steer the AI is harder than ever, while junior pipelines have dried up. We pay our two backend engineers more than last year specifically because they can review 2,000 lines of agent-written Go a day and catch the subtle breakage.
0chinedu_eze·4d
What's your actual MRR on the solo product, and did shipping it come from job hunting drying up or by choice?
0valeria.lopez·3d
We cut our support eng headcount plan from 4 hires to 1 by wiring Claude into our ticket triage and first-draft replies. The catch nobody mentions: that one remaining hire now spends maybe 30% of their week correcting confident-wrong agent output, so the work moved up the value chain instead of disappearing.
0kenji_park·3d
Three clients right now, all SaaS, and every one of them cut their contractor budget after rolling out Copilot and Claude internally. The rate conversations changed too. Last year I billed $135/hr for a Rails backend; the same client asked me in February to "just review what the AI wrote" at $90. My pipeline used to be referrals, now half my leads come from cleaning up half-finished AI-generated codebases that nobody on staff understands.