Job Opportunities API

The Public Ledger of Openings

← Back to the ledger

Staff AI Platform Engineer

Afresh
CompanyAfresh
CategoryEngineering
LocationSan Francisco
RemoteOn-site (inferred)
EmploymentNot stated
LevelNot stated
SalaryNot stated by the employer
Posted9 Jul 2026
Last verified2 Aug 2026
SourceEmployer ATS (greenhouse)
Applications are handled by the employer, not by us.Apply on the employer's site →
Description
Afresh, the AI platform for grocery, began by tackling the most complex problem in the industry: fresh, and has evolved into the core AI platform for grocers. By leveraging proprietary AI designed for high-volatility environments, we empower partners like Albertsons, Meijer, and Wakefern to drive smarter decisions across their entire enterprise. Following record-breaking 70% revenue growth in 2025, we have scaled to 6 enterprise-grade solutions, with solutions live in over 10% of the U.S. grocery market. Our platform now orchestrates billions of decisions from the store floor to the distribution center and prevented over 200 million pounds of food waste last year alone. If you're looking for a role where your work directly translates into massive scale and social good, and you want to be part of the team that defines how the world eats, there is no better time to join us. About the Role Frontier models are a commodity. The knowledge you feed them is not. As a Staff AI Platform Engineer , you build the AI and data platform that powers Afresh's products: the knowledge and retrieval layer that makes grocery data reliably usable by LLMs, the agent systems built on top of it, and the evaluation and serving infrastructure underneath. Your "customers" are Afresh's own engineers and AI products — your job is to give them a platform that turns raw grocery data into context a model can be trusted with, at production quality. This is senior, 0-to-1 platform work. You'll make foundational choices about how we represent grocery knowledge, ground our models, and measure whether any of it is actually working — in a fast-moving space with no playbook. What You’ll Do Build the knowledge & retrieval layer Design and operate the knowledge graph and ontology that capture how grocery data relates. Build the retrieval systems (vector, graph, and structured) that feed the right context to our models — so grounding is reliable, not lucky. Build and serve the agent platform Build LLM-powered agents (tool-use, multi-step reasoning, orchestration) and the serving infrastructure to run them reliably and cost-effectively. Build the tools, abstractions, and interfaces other engineers depend on — a platform, not one-off features. Own evaluation, quality, and the data foundation Stand up eval sets, LLM-as-judge harnesses, tracing, and observability, plus the metrics (faithfulness, accuracy, hallucination rate, latency, cost) that tell us whether a change helped or hurt. Build the pipelines, data products, and experimentation on Databricks/MLflow that take work from prototype to production — and partner with the engineers deploying our AI in the field to harden what works into reusable capabilities. What Makes You a Good Fit We encourage all highly-qualified candidates to apply, even if they do not fulfill all the listed criteria. 5+ years building production software, data, or ML systems; an excellent engineer with strong systems and API design (Python). Hands-on production experience with LLM systems: retrieval/RAG, agents and tool-use, prompt and context engineering — and, critically, evaluation. You measure quality; you don't eyeball it. Solid data-engineering and data-platform foundations: pipelines, data modeling, and a modern cloud data stack (Databricks/Spark, MLflow, cloud warehouses). Comfort in the messy middle of AI systems — retrieval quality, latency and cost trade-offs, non-determinism — and the instinct to build the guardrails and evals that make them trustworthy. A platform mindset: you build for leverage and clean interfaces, and you thrive in ambiguity in a fast-moving space. Nice to Have Knowledge graphs, ontologies, or semantic layers in production; graph databases. Vector stores (pgvector, Pinecone, Weaviate, etc.) and hybrid search. MCP or similar tool/context protocols; agent frameworks (e.g., LangGraph). MLOps and model serving at
HOUSE ADYou found the opening. Now track it.Tracker, radar and AI drafts in one place.erioun.com →