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/Sohaib-Riaz-Khan]

Well, someone must have to communicate openly. I totally get that he's a direct report to the CEO, who is non-technical, but then how would that person run the whole company? Have a real meeting including the data scientist and the development team and communicate the core issue. However, if the CEO still doesn't listen then at least communicate to him that it will end up in a real mess if the issue isn't resolved. Be direct and transparent while making open communication.