
Member of Technical Staff - Product Engineer (Console/API)
San Francisco, CA · HybridFull-timePosted 1 day agoStill listed · checked in the last 2 days
See where you stand before you apply. No sign-up to start.
You apply on the posting's application page, with no Olive account needed.
Watch jobs like this. New roles like this one near San Francisco, CA, by email.
Don't just apply. Show up ready.
Olive works from this exact posting.
At a glance
Olive focuses on jobs in the United States, including remote roles you can work from there.
Job overview
Liquid AI is seeking a product engineer to build and operate the distributed services behind its public inference API and improve the Liquid Console. The role spans API reliability, developer onboarding, usage, credits, billing, and account management. The engineer will work with inference engineers, go-to-market teammates, and customers to prioritize improvements and carry them from discovery through production.
Skills & qualifications
Skills
Benefits
Full job description
About Liquid AI Spun out of MIT CSAIL, we build general-purpose AI systems that run efficiently across deployment targets, from data center accelerators to on-device hardware, ensuring low latency, minimal memory usage, privacy, and reliability. We partner with enterprises across consumer electronics, automotive, life sciences, and financial services. We are scaling rapidly and need exceptional people to help us get there.
The Opportunity Liquid Console and our API let developers use Liquid’s models in their own applications. We’re looking for a product engineer to make our hosted inference API more reliable under production load and easier to adopt, from a developer’s first successful request to running a critical workflow. You’ll build and operate the distributed services behind the API and ship improvements to the Console across onboarding, usage, credits, and billing. You’ll work with inference engineers, go-to-market teammates, and customers to decide what to fix first and take those improvements from discovery through production.
What We're Looking For We need someone who:
-
You turn ambiguity into action. You can start with a customer problem, identify the constraints that matter, and deliver without waiting for a fully specified ticket.
-
You care about the whole product. You think beyond whether a feature works in isolation to how developers discover it, integrate it, and rely on it when something goes wrong.
-
You know what to fix first. You use production data and customer feedback to distinguish urgent problems from nice-to-haves. You ship iteratively and know when a system needs a more durable fix.
The Work
-
Build, scale, and operate the distributed services behind Liquid’s public inference API. Improve observability, investigate production issues, and make tradeoffs across reliability, latency, and cost.
-
Make it easier for developers to get from sign-up to a successful API request. Improve onboarding, API access, and how the product explains errors and limits.
-
Build self-serve Console features for usage, credits, billing, and account management, with clear interfaces backed by dependable services.
-
Work with inference engineers to diagnose issues that span the API and model-serving stack. Use customer feedback and production data to prioritize fixes and verify that they worked.
Desired Experience What you'll need:
-
Hands-on experience building and operating a distributed, customer-facing API or service in production, including instrumenting it, debugging failures, and scaling it under load.
-
Familiarity with AI model APIs or inference, and the developer workflows around integrating them.
-
Experience owning a project end to end, from an ambiguous problem through rollout and iteration, with the ability to work across backend services and customer-facing interfaces.
-
Sound product judgment and clear communication. You can explain what you chose to build, what you deferred, and why.
Helpful, not required:
-
Experience building developer platforms, public APIs, or self-serve products.
-
Familiarity with model serving, GPU inference, or the workflows developers use to integrate model APIs.
-
Experience working on a small team or an early-stage product where priorities evolve quickly.
What Success Looks Like (Year One)
-
You own a critical part of the inference API in production, from shipping changes to diagnosing issues under real customer traffic.
-
You’ve measurably improved a reliability or operability problem, such as reducing timeouts or making incidents faster to diagnose.
-
You’ve shipped a Console improvement that removes a recurring obstacle to adoption, and you can show how it made a developer workflow better.
What We Offer
-
Direct product impact: Help shape the Console and API that connect customers to Liquid’s models, with ownership from the first customer conversation through production.
-
Compensation & Equity: Competitive base salary plus equity, so you share in what we build. Final offers reflect skills, experience, and location.
-
Time Off: Unlimited PTO, plus company-wide Refill Days, long weekends when the whole company rests together.
-
Health & Wellbeing: Comprehensive health coverage, with details varying by location.
-
Paid Leave: Paid leave for pregnancy, parenting, medical needs, and caring for family.
How this job compares
Set against the 1,496 open Product Engineer jobs on Olive Jobs, counted November 20, 2026.
- Pay
- This postingNot listed
- California median$155–249K/yr348 salary ranges
- US median$43–50/hr29 hourly ranges
- Openings
- Olive Jobs lists 455 open Product Engineer jobs in California and 1,496 across the US. 5% of them nationwide are listed as remote or flexible.
- Experience
- Product Engineer postings that state a minimum ask for 5 years of experience at the median; the middle half ask for 3 to 7 years (1,212 postings).
- Education
- 466 of the 1,496 open Product Engineer jobs (31%) ask for a bachelor's degree or higher.
Pay, requirements and demand for Software Engineer jobs
Counted across the open, public US postings on Olive Jobs on November 20, 2026. Figures based on too few postings are left out.
Prepare for this role
You've read the whole posting — now see how you match it.


