Principal Software Engineer

About the role
We're hiring a Principal Engineer for our New York office, which opened this summer. You'll work alongside our other principals to set technical direction for the company.

We're defining what AI-first product development looks like in practice: the UI/UX, the capabilities, the data models, and the systems underneath them. It's a wide open problem space, and you'll be one of the people deciding which problems matter most and how we solve them.

In practice, that means you'll:

Set technical direction. Own the architecture for major parts of our product and make the calls that shape the platform for years to come — then write the code to back them up.

Take on our hardest problems. The ambiguous, high-stakes, cross-cutting work: reliability at millions-of-tickets scale, evaluation and quality systems for AI agents, and the foundations other engineers build on.

Define how we build with AI. Coding agents are a core part of our workflow. You'll design the tooling, guardrails, and feedback loops that make them effective across the team — and bring the judgment to know when output is ready to ship and when it isn't.

This is a hands-on role. You'll spend most of your time building, and you'll lead through the quality of your thinking and your work rather than through a reporting line.

Our stack is TypeScript, React/Remix, PrismaORM, NestJS, and some Python. Knowledge of the stack is nice; we know great engineers pick things up fast.

We'd love to talk if you
Have 10+ years of experience shipping software, including time as a staff- or principal-level engineer at a company with high engineering standards

Have set the technical direction for a product or platform and lived with the consequences — you can tell us what you'd do differently

Have led ambiguous, high-stakes projects from blank page to production, across the stack

Make other engineers better through design reviews, mentorship, and the example you set in your own code

Use coding agents as a core part of how you build — not just as autocomplete, but as a real development workflow — and have opinions on how teams should use them

Want to be early: real scope, real ownership, and real upside at a fast-moving company