Are Software Engineers Cooked? Pt. 2 | Autonomous Agents, The 30% Rule & What Skills Actually Matter

About This Episode

Software engineers thought the AI wave would pass. It didn't. In Part 2, we go deeper, breaking down how autonomous agent loops are already handling CI/CD, why SWE roles are shifting from coding to QA and verification, and what the "30% Rule" means for who stays employed. We also get into the two most bullish areas in tech right now, why human accountability is the one thing AI can never replace, and the exact playbook for engineers who want to stay ahead — pivoting, joining startups, and building with equity. If you're a software engineer/in Computer Science trying to figure out your next move, this one's for you. Chapters 0:00 – Intro 1:19 – Recap: Who Is Cooked in Tech & Why We're Back 2:07 – The Optimistic Take — Is SWE Actually the Last Job to Go? 3:27 – Claude & OpenAI Agent Loops — The Next Level of Automation 4:43 – Claude Code Loop: Agents Handling CI/CD Without You 5:27 – SWE Roles Shifting from Coding to QA & Verification 6:19 – Autonomous Agents Working for Days Without Human Input 7:35 – Software Engineers Pivoting to GTM, Marketing & Consulting 8:59 – Fewer SWE Roles, Higher Competition — The New Reality 10:03 – The 30% Rule: Only the Top Tier Will Stay Employed 11:51 – What Skills Actually Matter Now: Architecture & Business 12:27 – Two Bullish Areas: HCI & Human Trust in AI Systems 13:35 – Why Humans Stay Relevant — Accountability Agents Can't Have 14:55 – Connection & Taste — The Last Human Competitive Advantages 17:11 – Historical Precedent: 10-Year Tech Adoption Cycles vs AI 18:27 – Trust Barriers Slowing Agent Adoption — But Not for Long 19:19 – Only 0.3% of Humans Directly Pay for AI — We're Very Early 20:43 – The Playbook: Pivot, Join Startups, Build with Equity 21:43 – AI Research Roles — The Best Position to Be In Right Now 22:51 – Apply AI in Your Field Before Your Competition Does