Skip to content

Vibe coding jobs

By Mari Luukkainen · 6 min read · Last updated

On this page

Vibe coding jobs rarely carry that title. The work appears as product engineer, founding engineer, AI engineer, technical marketer or freelance builder, where you ship software with AI tools. Employers look for shipped projects, the ability to review code and debug, and proof you can finish what you start.

I see this from two sides: I build full time, and through Herizon I work on getting people hired. The data section below separates what has a source from what does not.

Ask AI about this pageChatGPTClaudePerplexityGoogle AI ModeGrok

Which roles use vibe coding?

RoleWhat you do with AIWhat you must still know
Founder or solo builderBuild and run your own productHosting, payments, security basics, customers
Freelance builderDeliver small sites and tools for clientsScoping, testing, handover, maintenance
Product engineer or founding engineerShip features across the stack in a small teamReading code, Git, code review, debugging
Technical marketerFix site issues, build landing pages and toolsSEO basics, analytics, working in a shared repository
Internal tools builderBuild dashboards and automations for a companyData access rules, permissions, who owns the tool

Mine is the technical marketer role. I push pull requests at unicorn sized companies where I am involved as a marketing tech person, with full access to fix things directly. Twelve months before that I did not know what a PR was, and ten years earlier I could not fix a technical SEO issue without waiting for an engineer (post).

What does the hiring data say?

LinkedIn's Jobs on the Rise 2026 list for the US, published 7 January 2026 from data between January 2023 and July 2025, ranks AI engineers first and AI consultants and strategists second (LinkedIn). It is LinkedIn's own data about its platform.

For postings titled vibe coding I found nothing with real numbers. GlobalData said on 1 September 2025 that vibe coding postings had increased and gave no figures (GlobalData). Treat any exact percentage or listing count you see without a named source as unverified.

What do employers ask for?

  • Shipped work. A live URL beats a certificate. Three small apps with real users say more than a course.
  • Evidence you can read and review code. Expect to explain what a file does and why a change is safe.
  • Git and pull requests.
  • Debugging. You will be asked what you do when the AI is wrong twice.
  • Security awareness. See is vibe coding bad for the questions you should be able to answer.

This list is my reading of the work, not a survey of employers.

What does hiring look like from the inside?

Herizon trains people for work and helps them land jobs. The goal I wrote for the employability system is that a skill on someone's profile means they can do that thing for an employer today, backed by evidence the employer can verify. The system optimizes for two numbers: time-to-hire, the days from joining to the first paid placement, and placement durability, the share of placements still active after six months (post).

Evidence the employer can verify is the same thing as a live project with a repository. A claim on a CV is not.

How do you show your work?

  1. Publish three small projects at their own URLs.
  2. Keep each in a public GitHub repository with a README: what it does, how to run it, what you decided and what broke.
  3. Write down the prompts that worked and the failures you fixed. A short note per project is enough.
  4. Put a test or two in each project, and say how you checked the security basics.
  5. Be ready to walk through one project file by file.
README prompt
Write a README.md for this project. Sections: What it does (two sentences), How to run it, Environment variables (names only, no values), How it is tested, Decisions I made and why, Known problems. Base it on the actual code, and mark anything you are unsure about with TODO.

Where do you find the work?

Search job boards for the role names in the table above and for "AI engineer", and read descriptions for the skills they ask for, not the title. For freelance work, small business owners need simple sites and tools, and a published portfolio is how they find you.

My route was building, not applying. I built Pitchkit.net in six days in July 2025 and it made 700 EUR of monthly recurring revenue the following week (post). That is one outcome, not a typical one.

What should you learn alongside the prompts?

  • Git: commit, branch, pull request, revert.
  • How a web request travels: browser, server, database.
  • Environment variables and why secrets stay out of code.
  • Reading error messages. The first project guide lists the common ones.
  • The vocabulary in the glossary.

What interview questions should you prepare for?

Question an interviewer may askWhat a good answer contains
The AI says all tests pass but the page is blank. What do you do?Open the page, read the browser console, run the build, ask the tool to reproduce the problem with a failing test
How do you know a package the AI suggested is real?Look it up on the package registry, check when it was last updated and how many people use it, compare the name to the one in the code
How do you stop one user reading another user's data?Check permissions on the server for every request, test it with two accounts by editing the URL, never trust IDs from the browser
Walk me through your most recent project.What it does, what broke, how you found it, what you would change, with the repository open
When would you not use AI for a task?Anything where you cannot check the result, secrets and credentials, legal or payment logic without review

The questions follow the risks in is vibe coding bad.

Nobody is hiring vibe coders. Sorry · Traversy Media

How do you scope a small client project?

Freelance work goes wrong at the scope. Write the scope as the same four answers used for a first prompt, and send it to the client before you start:

scope prompt
Write a one-page scope for this client project. Sections: Who uses it; The screens and what each does; What the main button does; Out of scope (list at least five things the client might assume are included, such as logins, payments, email sending, a content editor, translations); What I need from the client (texts, images, domain access); How we check it is done (five tests the client can try).
Project description: [paste the description]

The out-of-scope list protects both sides. The "done" tests give the client something to approve against.

Frequently asked questions

Is there data on how many vibe coding jobs exist?

I found none from a credible source. GlobalData reported on 1 September 2025 that postings had increased without giving numbers. LinkedIn's 2026 list ranks AI engineers first among fast-growing US roles, which is a different title.

Should I put vibe coder on my CV or LinkedIn profile?

Use the title of the role you want, such as product engineer, technical marketer or AI engineer, and show vibe coded projects as evidence. The title vibe coder rarely appears in listings.

How do I make employers find my LinkedIn profile?

Herizon's LinkedIn bootcamp has run more than 2,900 people through a monthly program that turns a dead profile into one that gets found. The order is profile first, then content, then networking.

Should I only apply to jobs that are posted?

Not only. I wrote that most jobs get filled before they are ever posted. At Herizon we built a system that reads hiring signals from companies such as Fortum, Neste and Terveystalo to show members who is about to hire before the listing goes public.

Next guideWhat is Lovable? →