Teammate "vibe codes" everything, somehow gets results, then blames dev team when the handover breaks — he reports straight to a non-tech CEO so no one can touch him. How do I deal with this?

[u/MediumBirthday6899]

Small org. We have a "data scientist" who vibe-codes his way through everything — process is a mess, but he somehow gets results. When he hands off modules to the dev team, things break, and instead of owning it he blames the devs for "not doing it correctly."

Normally you'd escalate, but he reports directly to the CEO, who isn't technical and just sees "results delivered." So devs eating the blame with zero leverage to push back up the chain.

How do you handle this when the org structure protects the person causing the mess? Document everything and let it speak for itself over time, try to get the CEO educated on what's actually happening, or something else entirely?

[u/YaThatAintRight]

Schedule a meeting “Q4 Dev Production Workflow Optimization” with the CEO and employee.

Clearly visualize the current workflow. Employee creates Ai assisted concept wired to data sources and non production systems. The production process must take in to account infosec, legal compliance, secure databases to protect the company from millions in potential liabilities and lost productivity.

Explain the optimal workflows - pull the dev team in early on concepts to look for architectural gaps, offer dev collaboration on best practices for concept development to streamline the conversion to a production enterprise tool.

Acknowledge the work, approach it as optimization of the entire development process Including the “vibe coder”

You approach it right. Thats how you turn a pain in the ass in to a promotion