Would you hire a VibeCoder to work on your product?

Hell yeah I would. Bringing in a vibe coder make so much sense when you think of it form the product and user perspective. They bring a strong focus on what customers actually want. Their superpower or differentiator is knowing, communicating and translating a user's wants/needs into a viable product. "Knowing the vibe" if you will.

They're a new breed of PM.

It's a complimentary role that can elevate the product's overall appeal without pulling resources from dev.

Now would I trust them to do any of the backend, critical systems work? No. But that's why it's a team effort. I wouldn't trust a senior engineer who's focused on security to give me a product that users actually want to use. It takes two to tango!

Yeah, why not? Definitely 😄👍! As long as the Vibecoder has a solid grasp of programming fundamentals 💻. That way, they can maintain, understand, and fix any bugs that come up, especially from AI-generated code.

VibeCoders are the new wildcard, less about code purity, more about directional momentum. For teams iterating fast, they’re perfect for prototyping, vibe-checking UI tweaks, or pressure-testing ideas without slowing down the core loop. I wouldn’t hire one to own infra, but to explore offbeat angles? Absolutely.

good news: I am a competent programmer ( you'd be surprised at how competent I am given ( at the time of writing) I am 18.) I'd gladly take a job, on the sole proviso I am not required to work during times which conflict with school.

I’m planning to gradually scale this up.

Surprisingly, it’s been really useful to delegate repetitive tasks or minor fixes,much more than I expected.

So I’m going to continue expanding through experiments.

I don’t think this needs to be limited to just the early stage of a project either.

That said, one challenge is that code written by people without a technical background often takes a lot of time to clean up or refactor.

I’m still thinking about how to reduce that part.

I was amazed when a “vibe coder” delivered a working prototype in two days, freeing our core team for critical work. They’re perfect for rapid prototyping and minor features. Check out the Rutificador tool for personal and company data

why not

Hring a vibecoder makes a ton of sense if it’s for rapid prototyping, UI tweaks, or side features that need speed and experimentation. They’re great for shipping ideas fast without bogging down your main team.
When it comes to backend, data, or anything super important and could generate a risk factor, I’d still want someone with a strong fundamentals and real experience.

I am planning to consult early stage products as a "vibe coder". I am a senior engineer so I can guide the project but I was very skeptical when I started this journey a couple months back. I have posted about my experiments in multiple places but "proof of the pudding is in the eating".

So I am soon launching a vibe coded micro SaaS, sources available for anyone to learn from. https://github.com/brainless/letsorder and https://letsorder.app. Demo apps are going to be live soon but you can run it locally or check the commits, GitHub issues, etc.

I intentionally setup a Rust backend and TypeScript frontend (2 web apps) to take benefits of their type check systems. Also all API payload (JSON data) types are generated from Rust to TypeScript. These eliminate a lot of potential errors. I do not know any of the code, but I have set the initial instructions to use these technologies.

Honestly, yes! if they bring the right mindset.

A “vibe coder” who can rapidly prototype, experiment, and ship non-core features can be a huge asset. They free up the core team to focus on mission-critical engineering while still exploring creative ideas, small UX tweaks, or integrations that might otherwise sit in the backlog forever.

The key (IMO) is alignment:

• Clear guardrails so their experiments don’t break the product.

• Collaboration with the main devs to ensure hand-offs are smooth if an idea needs to be productionized.

• Curiosity & adaptability — the best vibe coders I’ve seen are basically hackers who love to learn and iterate fast.

AI-primary builders especially shine here. They can whip up prototypes using tools like Vercel/Retool/LLM APIs in a weekend, which can spark new product directions. But you wouldn’t hire them instead of core engineers; you hire them alongside the team as an accelerant.

So yeah, I’d hire one. And that role can absolutely create outsized impact if managed well.

Curious if anyone here has already done this and how it worked out?