Staff Product Engineer

What You'll Own

• The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make most calls yourself and bring significant architectural decisions to architect review; you document them, and revisit if the data says you were wrong
• Implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code. Most lines will be agent-authored, and you're accountable for them — held to the same standard as the rest of the team working in a shared codebase
• Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and designer (UX decisions, in-tool prototyping), regular collaboration with engineering peers, and weekly check-ins with your EM
• The initiative outcome — the metric the initiative was set up to move. With your PM, you present results 2-4 weeks post-launch and share the "did it work" answer
• A high bar for what ships — production correctness, security, performance, observability, and the experience for customers and pros. Agents accelerate you; they don't lower the bar

Requirements

Who You Are

• AI-native. Claude Code, Cursor, Codex, or equivalent are how you ship today — daily, on production work. You have real opinions about prompts, evals, agent loops, and review workflows, and you know when to let the agent run versus write it yourself
• Operating at a lead level. Whatever your current title, you've been the person making the call, shipping the hard thing, and standing behind whether it worked
• Outcome-driven. You measure your week in "did the metric move" and "did the experience get better." You read the post-launch dashboard and own the answer
• A strong horizontal partner. You hold your own with a strong PM and designer, and you collaborate well with engineering peers in a shared codebase. You bring engineering judgment to product calls and product judgment to engineering calls
• Decisive and documented. You make architecture, data-model, and rollout calls, write them down, get fast input, and move
• A force multiplier. Your impact compounds beyond your own initiative because you leave reusable artifacts behind — agent workflows, evals, runbooks, post-launch reviews
• Customer- and pro-minded. This is a real marketplace with real people on both sides, and you care about the outcomes for both

Good to Know

• An individual-contributor role with room to grow. People management sits with the EM — but the path into management is an open door for those who want it
• A product-engineering role, end-to-end. You ship features that move metrics; platform and architecture work happen inside the initiative when the outcome needs them
• Hands-on, with a high quality bar. Agents handle much of the implementation; you bring the judgment, design, safety, and accountability. The bar is high
• Shipping to a live marketplace. With $100M+ in bookings, customers and pros use what you ship within the same week