You're the engineering anchor of an initiative — working as part of a tight team with your PM and designer, and alongside engineering peers on adjacent initiatives.
You have a hand in the full lifecycle: shaping the problem, deciding the technical approach, directing AI agents to implement much of the code, shipping to production, and — with your team — owning the outcome.
You're measured by impact, not by lines of code merged.
When an agent can ship something safely, your job is to make sure it's done right and the metric moves.
When the work calls for careful, hand-written code in a sensitive area, you write it yourself.

AI-native. Claude Code, Cursor, Codex, or equivalent are how you ship today — daily, on production work.
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."
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.
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.

Staff Software Engineer, Product

Key skills