Founding AI Product Engineer

You’d own a full slice of Standout end-to-end — either the company experience (how hiring managers brief us, see talent, decide) or the talent experience (how the people we represent get found, profiled, and intro’d). UX, UI, and the conversational agent inside it. All of it. From Figma-equivalent to prod.

The job is to make the agent unreasonably helpful. Most “AI products” feel like a chat box stapled to a CRUD app. Ours shouldn’t. The bar is: a hiring manager opens it, types one line, and gets something a senior recruiter would’ve taken a week to put together — and it looks beautiful.

You’re a fit if:

• You ship fast and you ship taste. The product feels right when you build it.
• You’ve spent the last year deep in vibe-coding / Cursor / Claude Code / v0 — not as a curiosity, as your actual workflow.
• You come from one of: a real product or design background, a great builder who fell into code through AI, or an engineering background where the design instinct is just there.
• You care about the small things: empty states, copy, the shape of a button, what the agent says when it has nothing to say.
• You can hold an entire product surface in your head and own it without a PM.

You’re not a fit if:

• You need a spec.
• You want to specialize in “the backend” or “the frontend.”
• You think AI is hype.
• You haven’t shipped something end-to-end in the last six months.

The stack is Next.js 16, React 19, TypeScript, Tailwind, Postgres + Prisma, Anthropic + LangGraph agents, OpenSearch. You’ll touch all of it. We don’t have a frontend team and a backend team — we have product engineers.