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.