Ask HN: Would you hire a "vibe coder"?

Absolutely not. Vibe code is barely sufficient for an unskilled would-be founder to throw out a trash proof of concept in hopes of attracting VC money. The results are not production-quality for an ongoing business, the code is a sloppy average for code hoovered indiscriminately from places ike StackOverflow, reddit, and even Quora. The tools have no concept of performance, security, consistency, maintainability, or fitness-for-purpose.

And before you say, "OK but they will improve, right?", let me give you an analogy.

We can build ladders to climb to the moon, we just need better ladder technology. Today, we can build very tall self-supporting ladders. We cannot yet build one tall enough to reach the moon, but by next year, or 2028 at the latest, we'll have ladders to the moon, or failing that, ladder technology that, in principle, will be sufficient to reach the moon.

Now replace "ladders to the moon" with "LLMs to AGI".

https://cendyne.dev/posts/2025-03-19-vibe-coding-vs-reality....

From my limited experience with AI coding I wouldn't hire a "bive coder". I'd be less concerned about specific language experience though as long as the team already had a strong foundation in the language they were using and the new hire had experience with similar languages and domains. I have a strong background in Java, decent background in Go, and virtually no background in Python. I've been using AI to help me write Python and I feel my prior programming experience has allowed me to have a pretty good understanding of what the generated code does and where it's incorrect even with out being an expert in Python. If I were hiring and we made use of AI tools during development I'd have no concerns about hiring a DotNet developer for a Java position if there fundamentals were solid. I wouldn't want to hire a Java developer for imbedded systems work in C since even if the languages have syntactic similarities the domains are incredibly different.

No, I would not hire a vibe coder. I think vibe coding will make cowboy coding look rigorous and make debugging next to impossible.

It is already the case where I interview less experienced people who ultimately have no ability to code. Vibe coding will make that problem worse. It will not make it harder for someone who actually can code get a job. IMHO

Relatedly, there is a YC company right now that states on is web site that it will ONLY hire "vibe" coders.

And you're expected to work 16 hour days. And weekends. And for about half the pay of a regular coder.

I don't know how they wrote that job listing with a straight face.

I see worse and worse software being produced in the future. Vibe coders won't understand half the code an LLM spits out.

I would, if they're a great dev when they aren't "vibe coding". That they called themselves that would certainly make me more cautious about them, though.

1. I would see that a red flag.

2. Any standard education in CS or SWE, AI hasn't changed anything about it IMHO. Only people hyping ChatGPT believe that the world has changed.

2b. It doesn't change anything since "vibe coding" (aka "code vomit") has no value to me. I want to work with juniors eager to learn, and vibe coders are not part of that group.

I already had bad experiences with "vibe coders" who can't explain or debug their code. They are like "pigeon CEOs" and only add problems without bringing solutions.

I would, under my understanding of what vibe coding is, provided that the prompt and vibe check processes aren’t overly limited.

My understanding of vibe coding is that you prompt, the LLM does something, and if it passes the vibe check you go with it, and if not, you do something to revert it, and afterward you try another prompt. Reverting after it doesn’t pass a vibe check could be actual reverting or a forward fix.

If you read stuff and do research and spend time thinking when prompting or doing a vibe check, I think this is a valuable activity.