Would you hire a VibeCoder to work on your product?
by•
I've been pretty impressed at the amount of products people (including myself) have been able to create which got me curious... do vibe coders or AI-primary builders have a place in a company or team?
My thinking is the more technically adept would work on the core-focus while vibecoders can assist with other tasks that shouldn't be the main devs focus...like a potential feature add, minor changes, or even exploring different ways of modifying the existing product.
I'm curious what you all think, would you hire a vibe coder?
3.1K views
Replies
VibeTalent
Great question. i think the framing of "vibe coder vs real dev" is a false binary, what matters is proof of work.
The problem with hiring any builder (vibe coder or not) is signal. Resumes are noisy, portfolios can be fabricated, and a quick interview doesn't tell you if someone can actually ship consistently.
What I'd look for: shipping streaks (are they building every day?), live projects you can actually use, peer endorsements from other builders, and verified GitHub activity. If someone has been shipping daily for 30+ days with real deployed projects, that tells me more than a resume ever could.
That's actually why I built VibeTalent, it's a marketplace that ranks builders by consistency (coding streaks), shipped projects, and community endorsements rather than credentials. The idea is that proof of work > proof of pedigree.
To answer your question: yes, I'd hire a vibe coder — but only one who can prove they ship. The tooling doesn't matter as long as the output is real.