Why this role exists

Our platform is used by engineers, and engineers judge infrastructure by how fast it stops confusing them.

We have a hard system underneath: graphs, real-time inference, agent behavior in production. Today, understanding it takes a conversation with us. That's a ceiling on how fast we grow. This role exists to remove it, by owning the surface where customers actually meet the product and making it obvious.

The role

You'll own product surface end to end: the interfaces, the APIs behind them, and the data models underneath.

The hard part isn't the CRUD. It's making genuinely complex system behavior legible and fast for the people using it. That takes taste as much as it takes engineering.

The split is roughly [60% frontend and API layer, 40% backend services]. You will not be handed a design file, and you will not be handed a spec. If you want to go deep on distributed systems and never touch a UI, this is the wrong role. If you can't hold your own on the backend either, it's also the wrong role.

We're small and senior. You'll pick the architecture, ship it, watch it in production, and fix what's wrong.

What you'll do

• Ship features across the whole stack. React and TypeScript on top, Python or Go underneath, real data models in between
• Talk to customers directly. Join calls, watch people use what you built, and ship against what you learn
• Sit with platform, data, and ML engineers to figure out what the system can do, then design a product experience around it
• Take things from idea to production, including the testing, deploys, monitoring, and the second version after you learn you got it wrong
• Sharpen the APIs, tooling, and UI patterns so the platform stops needing explanation

What success looks like

• First few weeks: You've shipped something real to production and sat in on a customer call
• First few months: You own a major surface of the product outright, and you're the person who decides how it's built
• Beyond: The platform is noticeably easier to understand than when you arrived, and you're raising the bar on how everyone here ships

What we're looking for

We care about what you've built, not how long you've been building.

• You've shipped production software end to end and can point at something and say "I built that"
• You're strong on the backend (Python, Go, Java, or similar) and can build a real React/TypeScript app without waiting for a designer
• You have opinions about API design and data modeling, and can defend them
• You've operated things in the cloud (AWS, GCP, or Azure) and debugged them at 11pm
• You make pragmatic calls under ambiguity and know which tradeoffs are worth the argument
• You want to be near customers, not shielded from them

Helps, doesn't gate: data-heavy or developer-facing products, distributed systems, ML-adjacent platforms, Kubernetes, observability and performance work, a real interest in AI infrastructure.

Why Join

• Meaningful equity. You're early. The scope and the upside both reflect that.
• The infrastructure layer for agentic AI is being built right now. Very few people get to work on a layer this foundational this early.
• Small, senior team. Your scope is as large as you're willing to make it.
• Real ownership of both architecture and product direction, not a ticket queue.
• Full benefits (medical, dental, vision, 401k). We sponsor H-1B visas and help with immigration.

Apply

Send us (what you've built: a repo, a product, a thing you shipped that you're proud of) at [email protected]. Tell us what was hard about it.

We value builders over résumés. If this role excites you but you don't check every box, apply anyway and show us the work.

We value builders over résumés. If this role excites you but you don't check every box, we still want to hear from you.