The short answer
the term got popularised by Andrej Karpathy earlier this year. the idea: use AI tools: Cursor, Claude Code, v0, Lovable: to generate code through natural language and iteration, rather than writing every line by hand.
The short version
a founder messaged me last month. he'd hired a vibe coder off a freelance platform, paid $2,800, and ended up with a Next.js app that worked perfectly in the demo and crashed the moment three real users hit it at the same time.
that's not a vibe coding problem. that's a hiring problem.
vibe coding is real. the speed is real. i've watched our team at ApexStack take a founder's voice note, literally a voice note, and ship a working MVP in under five weeks. but the gap between someone who can demo a product and someone who can ship one is wider than most founders realise when they're hunting for help online.
if you're about to hire vibe coders for your startup, this is what i wish someone had told me before i learned it the hard way.
what "vibe coding" actually means in a production context
the term got popularised by Andrej Karpathy earlier this year. the idea: use AI tools: Cursor, Claude Code, v0, Lovable: to generate code through natural language and iteration, rather than writing every line by hand.
it sounds like magic. sometimes it feels like magic.
but here's what the hype leaves out: AI generates code that looks right. a skilled vibe coder knows when it's actually right. that judgment, the ability to read AI output, catch the subtle architectural mistake, know when to override the model. That's the skill you're actually hiring for.
any developer can type a prompt into Cursor. far fewer can build something on top of that output that survives real users, scales past your first hundred signups, and doesn't cost you three months of refactoring six weeks later.
when you're hiring vibe coders for your startup, you're not hiring someone who uses AI tools. you're hiring someone who uses AI tools responsibly.
Frequently asked questions
- 1. they optimise for speed of demo, not quality of ship
- i get it. you want to see something fast. a good vibe coder can spin up a working prototype in a day, and that's genuinely impressive.
- 2. they hire based on tool fluency, not product thinking
- every vibe coder's profile lists Cursor, Claude Code, Lovable, Bolt. it's table stakes now. listing tools on a profile tells you almost nothing.
- 3. they skip the brief and pay for it later
- vibe coding thrives on tight inputs. the clearer your spec, the better the output. a vague prompt produces vague code: and at the speed AI moves, vague multiplies fast.
- shipped work, not side projects
- ask for things that are live. not "i built this for fun", things real users have touched. a startup MVP with 200 signups tells you more than a polished portfolio piece with no users.
- how they handle the handoff
- one thing no one talks about: what happens after the build?
- communication that matches your pace
- this sounds soft. it's not.
Talking about product engineering?
A long-running team that owns discovery, delivery and iteration — for products that keep evolving after launch.