Full Stack Engineer

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.

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.

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