Fetching from the wire…
Top 5 · 2026-06-27 · source-backed
Farhan Thawar, VP and Head of Engineering at Shopify, just put the orchestration thesis on record in a way you can't un-hear. The clip pulled from a 26-minute talk has roughly 654K views and 2.5K likes, and the line that's doing the work is blunt: AI authors the code, AI reviews the code, and the engineer's job is to build the loops around it. (X/Twitter)
I've been saying a version of this for a year, so I'm biased. But hearing it from someone responsible for ~3,000 engineers at a company that processes a meaningful slice of global commerce is different from hearing it from a solo builder on Bluesky. This isn't a hot take. It's a hiring doctrine. Shopify's 2026 "agentic harness" framing, corroborated by Pragmatic Engineer and Bessemer coverage, treats toilsome coding as delegable and reserves the human for direction and evaluation. That maps exactly to how I work in my personal projects. I don't write the function. I write the test, the constraint, the verification gate, and the loop that runs the agent until those hold.
Here's the part that should reset your career planning. A June 24 TechCrunch analysis found engineering roles fell only ~11% in 2025 against a 25% drop in total tech hiring, and engineers made up 55% of all new hires at large firms. (TechCrunch) The cuts landed on non-engineering, entry-level, and back-office roles. GitLab trimmed ~14% citing AI. ServiceNow trimmed too. So the headline "AI kills engineering jobs" is wrong, but the comforting version is also wrong. The demand isn't for people who type code. It's for people who run the loops, evaluate output for craft, and own the ML infrastructure, evals, and applied research that are still in acute shortage.
What to do about it: stop measuring yourself by lines shipped. Measure yourself by harnesses built. If you can't describe your workflow as "agent does X, my gate checks Y, the loop repeats until Z," you're still doing the part that's getting automated. Build the loop. Then build the thing that grades the loop. That's the job now.
Each link below shares sources, entities, or timing with this story.
Claude Code supports GitLab / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code supports GitLab); both cover Build, TechCrunch; reported by the same outlet (techcrunch.com).
Claude Code supports GitLab / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (Claude Code supports GitLab); both cover Shopify, Then; overlapping topics (agent, harness).
Vercel partners with Shopify / Shared entity: Build / Shared topic / What happened next
Linked by a graph relationship (Vercel partners with Shopify); both cover Build; overlapping topics (agent, around, engineer, engineering, harness).
GitLab partners with Anthropic / Shared entities / Same source domain / Earlier coverage / Tension
Linked by a graph relationship (GitLab partners with Anthropic); both cover Build, TechCrunch; reported by the same outlet (techcrunch.com).
Shopify uses Claude Opus / Shared entity: TechCrunch / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Shopify uses Claude Opus); both cover TechCrunch; reported by the same outlet (techcrunch.com).
Claude Code supports GitLab / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code supports GitLab); both cover Build, Shopify; overlapping topics (agent, code, shopify).
Mikhail Parakhin works at Shopify / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Mikhail Parakhin works at Shopify); both cover Shopify, Then; overlapping topics (agent, code, shopify).
Claude Code supports GitLab / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Claude Code supports GitLab); both cover Build, Then; overlapping topics (agent, code).