Full Stack Engineer
Build the product and platform surfaces that make Direct Inference feel like one dependable endpoint, from API workflows to dashboard tools used by production teams.
You will build across the customer-facing product and the platform systems that make production AI feel straightforward.
About Direct Inference
Direct Inference is the endpoint that does everything frontier models can do. Customers bring the SDK and model id they already use; Direct Inference handles capability, quality, cost, latency, failover, and provider churn behind the scenes.
The important product constraint is zero-knowledge: customers never see which model, provider, or version served a request. That lets them build on a stable surface while the model market keeps moving underneath it.
What you'll own
- Ship full-stack product flows across onboarding, API keys, billing controls, traces, analytics, docs, and playground workflows.
- Build frontend and backend features that make customer usage understandable without exposing private serving internals.
- Work with design, reliability, and inference engineering to turn platform capability into practical product surfaces.
- Improve type safety, tests, and developer experience in the marketing and portal codebases.
- Talk through customer workflows and translate product friction into shippable improvements.
Projects you might ship
- Build a better first-run flow that gets a developer from signup to a successful Direct Inference request with less uncertainty.
- Improve a traces or analytics workflow so teams can understand usage, spend, and request types without seeing private serving internals.
- Ship a cross-stack feature that connects API behavior, stored usage, and portal presentation end to end.
What we're looking for
- You have shipped production web products with meaningful backend/API work.
- You are comfortable in TypeScript, React, backend services, data models, and product analytics.
- You care about UI polish, performance, and clear user flows.
- You can balance quick iteration with maintainable system boundaries.
- You enjoy product ownership and can make sensible decisions with incomplete information.
Nice to have
- Experience with developer tools, billing systems, observability products, AI products, or API-first SaaS.
- Comfort moving between Go, TypeScript, SQL, Next.js, and product copy.
- A track record of making complex technical systems feel approachable to builders.
Your first 90 days
- Ship a customer-facing improvement to the portal or onboarding flow.
- Own one cross-stack feature from product shape through backend implementation.
- Identify a repeated customer support or adoption issue and remove it from the product.
Benefits & support
Built for people doing serious work in a small team.
Interview process
A direct loop with the people doing the work.
Intro
A focused conversation about your background, what you want to build, and where this role should create leverage.
Technical
A practical working session around the kind of problem this role owns. We prefer realistic systems over puzzle interviews.
Team
Meet the people you would work with across product, engineering, reliability, and customer-facing work.
Offer
We align on scope, compensation, start timing, and the first problems you would take on.
Application
Apply for Full Stack Engineer.
Share the practical context we should know before the first conversation. We read applications for ownership, clarity, and evidence of shipped work.
More openings
Other ways to build Direct Inference.
Forward Deployed Engineer
Engineering · Remote / San Francisco, CA
Work directly with high-intent customers to get production AI workloads running on Direct Inference, then bring the sharp edges back into the product and serving engine.
Senior Inference Engineer
Engineering · Remote / San Francisco
Own and extend the serving engine: the quality, latency, health, and price signals that decide how every request is served.
Platform Reliability Engineer (SRE)
Infrastructure · Remote
Keep one endpoint dependable across a churning set of upstream providers: failover, rate-limit absorption, and the spend caps that fail closed.