
What Zep AI does
Zep assembles the right context from chat history, business data, and user behavior so agents are personalized, accurate, and fast. Our open source project Graphiti hit 20k GitHub stars in under 12 months. Sub-200ms retrieval, SOC 2 Type 2/HIPAA certified, used by teams from startups to Fortune 500s.
2 open roles
What the role involves
Zep is the memory and context layer for AI agents. As a Senior Applied Research Engineer, you'll explore novel approaches to memory, context, and context generation, then own those ideas all the way to production. This is a research role with a hard applied bent. We're not hiring ML researchers chasing publications. We're hiring engineers who can run rigorous experiments, train and evaluate models, and ship the result as production code our customers depend on. How we work We're a small, distributed team that works closely together. We pair on hard problems, review each other's designs, and treat learning as part of the job rather than something that happens after hours. We ask a lot of questions: of customers, of teammates, of our own assumptions. When we find pain, we go fix it. We expect the same back: ask questions early, push back when you disagree, and care about the people on the other end of the API. What you'll do Explore novel approaches to memory, context, and context generation. Define the problem, run the experiments, ship the result. Own research to production end-to-end: dataset creation and curation, experiment design, evaluation, training and finetuning, and production deployment. Train, finetune, and evaluate models on Zep's domain. Build the eval harnesses that catch regressions before they ship. Work with our model serving stack to operate inference at low latency and reasonable cost on AWS. What we're looking for 6+ years of production engineering with a strong backend systems background. You've shipped services with real throughput and latency requirements. Master's in Computer Science or equivalent. Strong research skills: methodology, dataset creation and curation, experiment design, and evaluation. You can frame an open problem and design experiments that actually answer the question. Hands-on experience with model finetuning. Working familiarity with transformer architectures, training and finetuning workflows, and evaluation. PyTorch and OpenAI Triton for experimentation. Working experience with model serving technologies: vLLM, SGLang, or Triton Inference Server. You've operated inference in production. Python, plus high proficiency in one of Rust, C++, or Go. You can work in critical-path code and on performance. Python-only is not enough. Hands-on AWS experience in production: deployments, monitoring, scaling, cost and reliability tradeoffs. Nice to have Published or open-source work in retrieval, memory systems, or LLM evaluation. Tech stack: Python, Rust/C++/Go, PyTorch, vLLM/SGLang, AWS. This role is probably NOT a fit if: You're an ML researcher or model trainer who hasn't shipped research to production. Your background is primarily Python application work without lower-level systems experience. You haven't operated production backend systems with real latency or throughput requirements.
What the role involves
Zep is the memory and context layer for AI agents. As a Senior AI Engineer, you'll build low-latency backend systems, operate them in production on AWS, and ship LLM-powered capabilities our customers depend on. You'll have the opportunity to work on Graphiti (25K+ GitHub stars), Zep’s popular open-source context graph framework. This is a senior backend role centered on running LLM workloads at significant scale. We're not hiring ML researchers or data scientists. We're hiring engineers who have already lived through the messy reality of taking an LLM application from demo to production. How we work We're a small, distributed team that works closely together. We pair on hard problems, review each other's designs, and treat learning as part of the job rather than something that happens after hours. We ask a lot of questions: of customers, of teammates, of our own assumptions. When we find pain, we go fix it. We expect the same back: ask questions early, push back when you disagree, and care about the people on the other end of the API. What you'll do Ship product features end-to-end across backend services, APIs, data flows, and the supporting UI where it makes sense. Build and operate LLM-powered systems: extraction pipelines, evaluation harnesses, and reliability improvements running at scale. Contribute to system design for new components. Write the code, document the decisions, iterate. Improve production quality across performance, observability, and operational runbooks on AWS. What we're looking for 6+ years of production engineering with a strong backend systems background. You've shipped services with real throughput and latency requirements. Master's in Computer Science or equivalent. Go and Python experience in real systems. You can work in critical-path code and on performance. Hands-on AI agent and LLM application experience. You've shipped a non-trivial agentic system to production. Not a prototype, not a thin wrapper over a chat-completion API. We expect concrete examples: multi-turn agent loops with tool calling, retrieval and context pipelines you tuned against real failures, eval harnesses you built to catch regressions, or production memory and state systems for agents. Working familiarity with the agent ecosystem: at least one of LangGraph, Google ADK, Mastra, or other agent SDKs, vector stores, and eval tooling. Extremely comfortable with spec-driven agent coding, coding harnesses, and guiding agents to build complex product. Hands-on AWS experience in production: deployments, monitoring, scaling, cost and reliability tradeoffs. Nice to have TypeScript experience for frontend or SDK work. Tech stack: Go, Python, TypeScript, AWS. This role is probably NOT a fit if: Your LLM experience is single-turn chat completions or RAG-as-a-feature. Your background is primarily in ML research or model training rather than shipping agent systems in production. You haven't operated production backend systems with real latency or throughput requirements.
Roles are as last read from the company’s own listings. Openings close without notice — check the date on the listing before you spend an evening on the application.
Check the company’s own careers page — linked at the top — before a job board. A role appears there first, sometimes weeks before it is syndicated anywhere else.
Questions and experiences
Nobody has asked anything about Zep AI yet. If you have interviewed here, what you know is worth more to the next person than anything on the rest of this page.
Company facts compiled from public sources and last refreshed 9 September 2026. Details change; treat the company’s own site as the authority.