Jobs

Vibe Coding Jobs

Checked 2026-10-31

Loading poll...

Vibe coding jobs are roles where you build software mainly by directing an AI agent or app builder, and take responsibility for the result. They rarely carry that title. We list no jobs yet and quote no market figures. This page explains what the work involves, what employers can test, and how to post a role when listings open. Checked 31 October 2026.

What is listed here

Nothing yet. The jobs hub at /jobs/ uses the Job listing type of our directory engine. Each posting will be a listing with a salary field, a job type field and an apply link, and it will carry JobPosting structured data. We will not name employers or roles on this page unless we verify each from its own page the same day, and any we name will be examples, not a ranking.

We will not publish figures for how many roles exist or what they pay until we can source them.

What the work looks like

"Vibe coding" describes building by prompting and reviewing, not writing every line. The job titles around it vary, and the tasks cluster into a few shapes.

Shape of work

What you do

What the employer checks

Building prototypes and internal tools

Turn a brief into a working app with an agent or builder

A live example and how you tested it

Agent-assisted development on a codebase

Use a coding agent like Claude Code or Cursor inside a real repository

Pull requests, tests, review quality

Building agents and automations

Wire an agent to tools and data

See how to create an AI agent

Rescue and cleanup

Fix an app that works but is fragile

Security, structure, tests; see vibe code rescue services

Content and operations with agents

Run repeatable workflows

Reliability, not novelty

These are descriptions of work, not claims about hiring volume.

What employers can actually test

Prompting is easy to demonstrate and hard to value. The skills that separate a good hire are the ones around it.

  1. Reading generated code. Can they say what it does and find what is wrong?
  2. Testing. Do they try empty forms, bad input and two accounts?
  3. Data safety. Do they keep keys out of the browser and check access rules? See securing a vibe-coded app.
  4. Version control. Do they commit in small steps and roll back?
  5. Deploying. Can they publish and explain what the plan limits are? See deploying.
  6. Scoping. Do they cut a big idea down?
  7. Cost sense. Can they estimate credits or tokens for a task before they run it?

A fair test is a small paid task: take a brief, ship something, explain how it was checked.

If you are looking for work

  • Show live work. A link that loads for strangers beats a certificate. You can launch a project here to give it a credited page.
  • Show your process. A short note on how you tested it.
  • Show the stack. Which agent, model and add-ons.
  • Learn the safety basics. It is where most generated apps fail.
  • Read the posting for what it asks. "Ship fast with AI" with no mention of review is a warning.

For learning paths, see courses and books.

If you are hiring

A posting that gets good applicants says:

Include

Why

What you want built or maintained

So people can judge fit

Which tools you use

Agents and builders differ a lot

How the work is reviewed

Shows you value checking

Pay or rate, and the job type

Listora has fields for both

Remote, hybrid or on site

Saves time on both sides

An apply link

One clear route

Avoid vague titles, income promises and requirements that mix a decade of experience with a tool that is newer than that.

How to list a job

When the Job type opens, use the listings form at /listings/submit/. A listing needs a title, description, pay or rate and job type, and an apply link. We check that the link works and that the role is real, and we hold anything that looks like spam. Imports and submissions arrive as drafts and are approved by an editor before they show. Paid tiers, if offered for jobs, will be labelled and will not change editorial order. See advertise and how we make money.

Related

Questions

Are there vibe coding jobs?

Roles that use AI agents and app builders exist under many titles. We do not list jobs yet, and we publish no counts of openings.

What skills matter most?

Testing, reading what an agent produced, data safety, version control and deploying. Prompting alone is not enough.

How do employers list a job?

Through the listings form once the Job type opens. A listing needs a clear role, an apply link and the pay or type fields.

Loading poll...

Sources

  1. docs.lovable.dev/introduction/welcome
  2. bolt.new/

Part of the Wbcom Designs family

The all-in-one WordPress community stack

Also ours: wbcomdesigns.comvapvarun.combrndle.com