Senior Product Engineer

About the Role

Nomad runs a lean, AI-native engineering team by design — small, high-ownership, and built to force-multiply with the best tools available rather than scale headcount. As a Senior Product Engineer, you don't just own your own tickets end to end — you set the pattern for how the whole team does it. You turn vague, cross-cutting problems into work other engineers can pick up, you own the AI and agentic conventions the rest of the team inherits, and the standard you set is still being followed you've moved on to the next thing.

This role is ideal for someone who thrives in a startup environment, is comfortable operating with minimal process, and has experience building and scaling SaaS products.

What You'll Own

The full workflow, not just the ticket: turning an ambiguous problem into a shipped, monitored outcome, using AI and agentic tools as the default way that work gets scoped, built, and verified.
The pattern other engineers follow — a service's quality bar, its AI/agent conventions, and the review standard — not just your own code.
A domain you can hand off. When you're heads-down elsewhere, the area you own stays healthy without you.
The judgment call on what AI should and shouldn't touch in your area, and why — and the accountability when that call is wrong.

What You'll Do

Take a vague problem statement — from a customer, from Ops or Sales, from a metric that looks wrong — and turn it into a validated ticket, then own it through design, build, ship, and monitor: you watch the number it was meant to move, and you are the first to know when it is wrong.
Talk to the person who hit the problem before you design the fix — a customer call, an Ops shadow session, a Sales thread — not only when Support escalates it.
Treat any figure that reaches an invoice, a payout, or a reconciliation report as needing a named source and a second, independent way to check it — when a change touches money, the before-and-after numbers are part of the pull request, not a follow-up.
Decompose a large, ambiguous change into small, reviewable pull requests instead of landing it big-bang and share at 70% for feedback rather than polishing to 100% in private.
Use coding agents as your default way of writing code and read every line before it merges — your name on the pull request means you understand what it does and would own the incident it causes.
Own the agent setup for a repo or service — the instructions, skills, and conventions other engineers inherit — and design the workflows, verification gates and failure paths that other people actually use, not just ones that work for you.
Review work across services you don't own, and treat “changes requested” as a normal, expected outcome — not a rare escalation.

What We're Looking For

4–7 years shipping production software, with real, demonstrable ownership of a domain — not just tickets assigned to you.
Startup and SaaS experience required, with experience operating effectively in fast-paced, high-ownership environments with minimal process, and building, maintaining, or scaling SaaS products or platforms.
Fluency with modern AI-assisted and agentic development tools, with evidence you've built something with them that other people now rely on — a shared prompt, a skill, a workflow, a convention.
A track record of taking ambiguity and turning it into work other people can execute, including work you don't do yourself.
Comfort reviewing and being accountable for code and systems outside your own immediate area.
Strong judgment about trade-offs — including the judgment to say no to a shortcut that trades long-term health for short-term speed.
Experience operating with minimal process in a small team, where your call is usually the only call.