Anyone Can Vibe Code. Did You Build the System?

Episode Summary If AI handles the coding, then being an engineer means planning and reviewing — the work of staff and principal engineers. But that breaks the career ladder: how does anyone become senior when the junior rungs disappear? Dave and Dan dig into where senior engineers come from now, why juniors still add value on top of Claude, builders versus maintainers, and how interviewing changes when anyone can vibe-code. Key Topics The vanishing junior rung — if seniority is "planning and reviewing," how do you climb without junior work to learn from? Adding value on top of Claude — good juniors ship more complete PRs than Claude alone, and compress a 5–10 year career into a couple of years. Builders vs. maintainers — the "commandos and palace guards" framing, reimagined: builders extend the system, maintainers keep the harness healthy. Claude is no longer a junior — with the right harness it plans, tests, lints, simplifies, and reviews like a solid mid-level or senior engineer. Robots ship, humans plan — the autonomous agents do the shipping 24/7; the builder's thrill now comes from queuing tasks, not typing code. Interviewing in the agentic era — show what you built with Claude, then show the system you built to build it. Anyone can vibe-code; the differentiator is the system. Notable Quotes "Right now, as of May 2026, if you're writing code, you shouldn't be. You're doing something wrong." "Anyone can vibe code anything nowadays — but the differentiator is, did you build a system to build it?" "You and I aren't shipping anything. Our autonomous coding robots that live in the cloud and work 24 hours a day, they're the ones actually shipping." About The Velocity Lab Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field. Subscribe: RSS