Written first
Proposals are written and read before they are built. Meetings are for disagreement, not for status.
Small team, remote, deliberately slow hiring. You will own a surface rather than a ticket queue, and you will talk to the people using it.
Proposals are written and read before they are built. Meetings are for disagreement, not for status.
We would rather ship one surface that holds under load than four that need a caveat in the docs.
Everyone who ships to production is in the rotation, compensated, with a hard expectation that pages become fixes.
You will own the scheduling and failover layer: how requests find capacity across providers, how we decide a route is unhealthy, and how we keep tail latency flat while replicas move underneath. Experience running GPU capacity in anger matters more than a specific language.
Build the promotion gates and environment isolation that let fintech and healthcare teams move a model from sandbox to production without a manual compliance scramble. You should be comfortable with both the infrastructure side (isolation, audit logging) and talking to compliance teams about what a gate actually needs to check.
Design the consoles our users live in: rollout screens, quota editors, review queues. This is dense, state-heavy interface work for people who are often under time pressure. Portfolio of shipped operational tools preferred over marketing sites.
Sit with prospective customers during evaluations, map their environment, and get a first endpoint or first scoring integration live. Half engineering, half translation.
We keep a short list of people we would hire when the role opens. Tell us what you would want to own.