Stand out for this role — generate a tailored resume and cover letter in about a minute.
Sage AI Labs in San Francisco is seeking an experienced backend engineer to own production systems and infra that power AI agents transacting on the open web. You will design, deploy, monitor, and on-call for systems that operate 24/7, collaborating with the CTO and platform team.
You'll own the ingestion and processing pipelines, scale ingestion from hundreds of sources to thousands, and build resilient, self-monitoring infrastructure with reliable search and ranking across a dynamic catalog.
Sage AI Labs is building the infrastructure that lets AI agents transact on the open web. It is one of the few genuinely unsolved problems left in commerce, and whoever solves it sets the defaults everyone else builds on top of.
Sage AI Labs
Sage AI Labs is building the infrastructure that lets AI agents transact on the open web. It is one of the few genuinely unsolved problems left in commerce, and whoever solves it sets the defaults everyone else builds on top of.
The company was founded by Sebastian Thrun (founder of Google X and Waymo, Udacity) and is backed by leading venture and strategic investors.
We build agents that shop for you. They find products across the open web and complete the purchase end to end. Real carts, real payments, and real systems built to stop them.
You would own that. Architecture, code, deploys, monitoring, and on-call for systems that transact around the clock, working directly with our CTO.
What you'll own
Our checkout agents. Frontier-model computer-use agents driving live checkouts at scale, plus the machinery that keeps them standing when the ground moves. Every retailer breaks differently and they change without warning. Your job is to make failure rare and recovery automatic.
Ingestion at scale. Take product ingestion from hundreds of sources to thousands. The answer is not more hand-written code. It is infrastructure that generates, validates, and monitors itself.
Search and ranking. Embedding-based retrieval, LLM query understanding, reranking, and caching, across a catalog that never stops changing.
Why this role
Very few engineers get to own a category-defining system while the category is still being defined. This is one of those seats, at the point where it still counts as early. A year from now this problem will have a standard answer and someone will have written it. We intend for that to be us.