When the AI writes the code and you spend your day reviewing it for correctness, security, and architectural coherence, you've become QA. This happened to everyone who adopted vibe coding. Congratulations on the role transition.
Here's the thing: this isn't inherently a downgrade. QA is underrated, underpaid, and more cognitively demanding than most of the code it reviews. The problem is that most developers are bad at QA — because we were never trained for it, it wasn't in the job description, and the culture says shipping is more important than verifying.
Vibe coding at scale requires reviewers who understand what good looks like. Who can spot the hallucinated function call. Who know enough about the system to catch the context the LLM didn't have. That's a senior engineering skill, not a junior one.
What vibe coding actually did: it made the senior/junior gap larger. The junior who can't review AI output is less useful than before. The senior who can is more valuable than ever.
Congrats on the new job title. Hope you were already good at it.
Read the full piece on Medium →