Discover what vibe coding jobs are, explore examples by role, and learn how to find opportunities in AI-assisted development.
Vibe coding jobs are roles where shipping real artifacts with AI-assisted tools is an explicit expectation — not a nice-to-have.
These roles show up in engineering, but also product, design, ops, and GTM when prototyping and automation are part of the job.
Senior UX Designer role on Amazon’s Applied AI Solutions Healthcare & Life Sciences team, responsible for designing AI-native, trustworthy UX for scientists, clinicians, and healthcare professionals. Lead design strategy, prototyping (including vibe coding and AI-assisted tools), and cross-functional collaboration to deliver regulated, evidence-grounded AI-assisted experiences.
Lead the design vision for Adobe GenStudio to create enterprise-grade generative AI tools for marketing, guiding product experiences, design systems, and prototyping while collaborating with product, engineering, and marketing teams. The role requires hands-on prototyping, mentorship of other designers, and shaping AI-powered creative workflows at scale.
Senior Software Engineer to shape and scale MTech Systems' AI-powered platform for the food production industry by driving architecture decisions, improving system performance, mentoring teammates, and delivering web applications, internal tooling, and shared components. This is a hybrid role based in Dunwoody/Atlanta requiring strong TypeScript expertise and experience with Angular or ASP.NET Core and Azure.
Embedded Systems Engineer role on the Access Point Platform Software team at RUCKUS (Vistance Networks). Design and implement device drivers, board bring-up, bootloader and embedded Linux platform software (U-Boot/OpenWRT) using C/C++, integrate SDKs across vendor platforms, and drive features from prototype to production.
Build and deploy AI-driven applications and autonomous agents to improve Customer Operations at Qualtrics by leveraging Python and modern LLM frameworks. Collaborate with cross-functional teams and use AI-assisted coding tools to design, integrate, and automate solutions that close the loop on model performance.
Lead a Product Development POD to architect and build scalable, event-driven marketing orchestration and real-time customer engagement systems, combining big data engineering and AI-assisted development. Drive architecture, development, and team leadership to deliver high-performance data pipelines and personalized marketing experiences at scale.
Product Manager (temporary-to-hire, remote) to lead strategy, roadmap, and delivery of digital platforms and learning products focused on health equity. The role combines product strategy, human-centered design, data-driven decision making, and vendor coordination to advance HealthBegins’ Learning & Innovation portfolio.
Director role to define and lead the long-term AI and agentic marketing strategy for American Express’ MarTech organization, prioritizing high-impact AI use cases, vendor selection, and cross-functional adoption to drive measurable business value.
The GTM Engineer will design, build, and operate AI-powered agents and automations to support demand generation across Observability, Service Management, and Database products. The role focuses on end-to-end development, governance, integration with GTM systems, and enabling Marketing and Sales with scalable, reliable automation solutions.
Senior Product Marketing Manager to build AI-powered customer experience for enterprise B2B SaaS, owning the full journey from customer insight to positioning, storytelling, and distribution. Use AI-enabled workflows to execute full-stack marketing—research, content and asset creation, sales enablement, and go-to-market strategy—moving fast to ship, learn, and iterate.
More companies are hiring for roles that require AI-assisted prototyping, fast iteration, and agentic workflows. These aren't future trends — they're already in active job descriptions.
The 5 categories of vibe coding jobs, the 7 signals to spot them, and real salary data from $45K to $351K. With examples from Google, Amazon, and startups.
Read article →LLM pair-programming is part of the workflow. The role expects you to build with tools like Cursor, Claude Code, Copilot, or similar—using them deliberately, not as a gimmick.
Speed is an explicit requirement. The posting talks about rapid prototyping, shipping faster, shorter iteration cycles, or “0→1” delivery where throughput matters.
You can turn messy ideas into working software. You’re expected to translate ambiguous requirements into code quickly, iterate with feedback, and keep momentum.
Agentic or LLM-native systems show up (when relevant). Mentions of agents, MCP, RAG, evaluation/evals, tool calling, or automation that’s powered by LLMs—especially if the job involves building or integrating them.
Design-to-code / UI generation is valued. The work includes visual builders, design systems, UI generation, front-end tooling, or workflows that bridge design and implementation.
Devtools / platform / internal tooling is a strong signal. Building developer experience, internal products, pipelines, infra tooling, or systems that make teams ship faster.
AI-first product teams count too. Some roles aren’t titled “engineer”, but prototyping is part of the job (PM, design, solutions, ops) and the posting expects you to build real artifacts with AI tools.
The posting gives concrete signals—not vague “AI buzzwords.” We look for specific workflows, tools, responsibilities, or examples that tie directly to building and shipping.
These are the selection criteria for this board. They're why the list is curated and why jobs here should have a clear, explicit connection to vibe coding.
A vibe coding job is any role where AI-assisted building is part of how work gets done — not a novelty. The common thread is faster iteration: prototyping, shipping, testing ideas, and turning ambiguous inputs into working software. Many of these roles explicitly mention vibe coding or AI pair-programming workflows.
Not always. Some postings name tools like Cursor, Claude Code, or Copilot directly; others describe the workflow (“AI-assisted development”, “ship faster with LLMs”, “agentic automation”). We include roles when the connection to AI-driven building is clear and specific, even if the brand names aren’t listed.
We look for concrete signals in the job description: AI pair-programming workflows, rapid prototyping expectations, agentic systems (MCP/RAG/evals), design-to-code tooling, or devtools/internal tooling where speed matters. Each job includes a short “Why it’s vibe coding” explanation so you can see the reasoning instantly.
No. Remote and hybrid roles are common, but we also include on-site positions when the work is a strong fit for vibe coding workflows. Use filters to narrow by location and work style.
We update continuously as new postings appear and older ones expire. Some roles are added daily, and the “Hot” label typically reflects recent listings.
Titles don’t always describe the real work. Some roles (PM, solutions, ops, design, devrel) still require building prototypes, automations, demos, or internal tools — and they benefit heavily from AI-assisted workflows. The “Why it’s vibe coding” line is there specifically for these cases.
Sometimes, but only when the posting is explicit about AI-assisted building and real hands-on work. Many entry-level roles still avoid specifying these workflows, so they’re less common in the feed. If you’re hiring junior, being explicit about tool expectations helps the role show up.
Because vibe coding turns certain non-engineering roles into builders. PMs (and similar roles) can prototype the product, test workflows with users, and validate direction without waiting on an engineering handoff. A PM who can build becomes faster, more accurate, and harder to outcompete.
AI tools lower the barrier to shipping, but the highest leverage shows up at senior levels: judgment, architecture, reliability, and knowing what not to build. Many companies now expect experienced people to use AI to move faster while still delivering quality. The workflow is “faster”, not “sloppier”.
Focus on prototypes that answer real questions: user flows, pricing pages, onboarding, internal tools, or interactive demos. Use AI tools to build small, testable artifacts quickly, then bring evidence (usage, feedback, metrics) into decisions. In hiring, you can stand out by showing shipped prototypes, not just decks.
No — but they are changing what “good” looks like. Teams still need engineers for systems, performance, security, and long-term maintainability. What’s shifting is the iteration loop: more people can build usable versions faster, and engineering time gets spent on scaling and correctness.
Some postings price in a premium for speed and autonomy: people who can scope well, prototype quickly, and ship without heavy coordination. Roles involving devtools, platform work, or agentic systems can also command higher comp because they multiply productivity across an entire org. And in some cases, the high numbers reflect contract/hourly roles rather than full-time salaries.
Yes! We offer RSS and Atom feeds you can subscribe to in any feed reader — look for the links at the top of the jobs page. You can also subscribe to email alerts to get new listings delivered to your inbox.
