The rise of the professional vibe coder (a new AI-era job) | Lazar Jovanovic (Professional Vibe Coder)

The professional vibe coder who never writes code

Vibe coding is a real job, and the skill it rewards is clarity rather than code. Lazar Jovanovic, Lovable's first official vibe coding engineer, has never written a line of code and treats the agent as an obedient, agreeable collaborator that will claim to have fixed what it has not. Because AI hands everyone the ability to produce, the gap between good enough and world-class has widened, and taste closes it.

Takeaways

• AI tools reward clarity over coding skill. Lazar says the tools solve clarity rather than coding, and he spends 80% of his time planning and chatting with the agent and 20% executing. An unclear request makes the tool read the whole codebase, burning 80% of the token budget on reading.
• A non-technical background is an advantage. Lazar has never written a line of code and says that is why he does not know what should be impossible, which is how he built a Chrome extension. He advises arriving with the delusion that everything is possible until proven wrong.
• Agents claim fixes they never made. Lazar describes the tools as obedient and agreeable, happy to say they fixed something they did not. He says 90%, really 100%, of failures are the user's fault, so the first move is to look at your own prompt.
• Everyone can reach good enough now. Because AI hands everyone the ability to produce, the gap between good enough and world-class has widened, and taste is what closes it. Product managers win today for bringing clarity, designers win next, and elite engineering stays essential for maintenance and scaling.
• Ship apps instead of sending resumes. Companies including some in the S&P 500 are hiring full-time vibe coders and moving code bases onto Lovable. Lazar got his own role by building in public, advises people to hire themselves first, and says vibe coding is simply coding within 12 months.

Lazar's parallel project workflow

1. Run a first project as a brain dump prompt, holding nothing back.
2. Open a second with more clarity and a reference screenshot from Mobbin or Dribbble.
3. Seed a third with code snippets, then compare the concepts side by side and pick a winner.
4. Spend up to a day on PRDs covering the master plan, implementation plan, design guidelines and user journeys.
5. Feed them into tasks.md and rules.md or agents.md so prompts become 'proceed with the next task'.

The four by four debugging framework

1. Press the tool's own try-to-fix button, which appears in orange when the agent labels its mistake.
2. Add console logs so the agent becomes aware of what is actually happening.