Working at Zep

Zep is the context engineering platform for AI agents. We solve one of the hardest problems in production AI: getting the right context to agents at the right time. Our platform builds context graphs from conversations and business data, then assembles personalized, token-efficient context with sub-200ms retrieval. Three lines of code to production.

We're a seed-stage company (YC W24) with 50% month-over-month ARR growth, 240+ customers including Fortune 500s, and a well-capitalized balance sheet. Graphiti, our open-source temporal context graph engine, has 24,000+ GitHub stars and is becoming foundational infrastructure for agent memory.

Our buyers are AI engineers and engineering leaders building agent applications. They evaluate us technically, decide fast, and expect the people they talk to to know the stack.

The Role

You'll own the full revenue process: qualify inbound, drive outbound, manage pipeline, run deals through close. Sales at Zep is founder-led and will stay that way. Daniel (founder) sets GTM direction, joins for technical deep-dives and executive alignment, and stays close to the biggest accounts. But you run the day-to-day.

This is not a "figure out if we have product-market fit" role. We have customers, revenue, and a repeatable sales motion taking shape. You'll take what's working and turn it into a machine, while Daniel stays involved in the deals and conversations where he adds the most leverage.

You'll own:

• Inbound pipeline. We get meaningful inbound volume. Leads need fast, thoughtful qualification and follow-up. Today this is a bottleneck.
• Outbound motion. Define target accounts, build sequences, test messaging. We know our ICP. You'll systematize reaching them.
• Full-cycle deal management. From first touch through close. Demos, security reviews, procurement, pricing proposals, contract negotiation. You run the process; Daniel joins for technical depth and executive alignment where it matters.
• Pipeline operations. Maintain the pipeline. Build reporting that tells us what's working. Forecast accurately. Create the operational foundation that lets us hire the next person after you.
• Sales enablement. Work with Daniel to build the collateral that closes deals: demo scripts, competitive positioning docs, reference architectures, security questionnaire templates, pricing proposals. Much of this exists in rough form. You'll make it repeatable.

Your First 90 Days:

• Day 30. You've taken over the inbound queue, learned the product and sales motion, and closed your first $15K+ deal.
• Day 60. You've built and are running a systematized outbound sequence with clear targeting, messaging, and cadence.
• Day 90. You've closed your first $50K+ deal and have a pipeline that you can forecast against.

What We're Looking For

Required:

• 3-5 years of B2B SaaS closing experience with evidence of consistently exceeding targets. We care about trajectory and rate of progression, not just tenure.
• Experience selling technical products to engineers and engineering leaders. You don't need to be an engineer, but you need to be credible in a conversation about APIs, SDKs, and infrastructure architecture. You should be able to run a product demo independently.
• You've built or meaningfully participated in shaping a GTM motion at an early-stage company (Seed to Series B). You know what it's like when there's no playbook, no SDR team, and no product marketing team. You did the work yourself.
• Comfort operating across the full sales cycle: prospecting, qualifying, demoing, negotiating, closing. You don't hand off to someone else because there is no one else.
• Strong written communication. Enterprise sales at our stage is heavily async: email, Slack, security questionnaires, proposals. Your writing needs to be precise, professional, and fast.

Valuable but not required:

• Experience selling AI/ML infrastructure, developer tools, or data platform products.
• Familiarity with the AI agent ecosystem: LangChain, LlamaIndex, CrewAI, Google & AWS products, MCP, etc.
• Experience with enterprise compliance motions: InfoSec questionnaires, SOC 2, DPAs, security reviews.
• You've sold alongside a technical founder and know how to make that dynamic productive rather than chaotic.

Dealbreaker:

• Pure enterprise sales background with no startup building experience. If you've only worked at companies with established territories, SDR teams, and SE support, this isn't the right fit.

Why This Role

Zep is at an inflection point. We have product-market fit in a category (context engineering) that every company building AI agents will need. The open-source traction is real. The enterprise pipeline is growing. The founder is technical, deeply involved in sales, and committed to staying that way. What we need is someone who can carry the weight of running the revenue operation so the business can grow at the rate the market is moving.

You won't be figuring out whether this works. You'll be making it scale.

How to Apply

Include in your application:

1. A short note on why this role interests you and what you'd do in the first 30 days.
2. Anything else that shows how you think about selling technical products (a deal narrative, a cold email you're proud of, a demo recording, whatever).

No cover letter template. No AI-generated boilerplate. We'll know.

Zep is a context engineering platform for AI agents. We help developers build personalized, reliable AI applications by assembling the right context from chat history, business data, and user behavior.

We’re hiring a Forward Deployed Engineer to own technical delivery for strategic customer deployments, from first prototype to stable production. You’ll work directly with customer engineering teams, ship production code, and turn repeatable patterns into improvements to the product and deployment playbook.

Responsibilities

• Own end-to-end delivery for strategic deployments: scope, design, build, rollout, stabilize.  
• Embed with customer engineers to integrate Zep into real systems: data, APIs, auth, infra.  
• Ship production code: integrations, reference implementations, performance and reliability fixes.  
• Help level up the FDE function: coach newer FDEs on execution, review designs/code when useful, and capture repeatable patterns.

Requirements

• Strong production engineering background. You can own architecture plus implementation.  
• Comfortable working across customer stacks and cloud primitives (AWS or GCP, Docker, networking basics).  
• Fast debugging and strong operational instincts in messy, real environments.  
• Can lead by doing: clear communicator who can run customer working sessions and coach junior FDEs in the flow of work.

Salary: $175,000 - $250,000 per year + Stock Options

Benefits: Health, Dental, Vision Insurance; 401K match; Phone Benefits

Zep is a context engineering platform for AI agents, enabling developers to build personalized, reliable, and fast AI applications.

Our open source project, Graphiti, hit 20k GitHub stars in under 12 months. The community skews heavily toward founders and senior engineers building production agent systems.

We're hiring someone to own developer relations end-to-end: engaging directly with users, shaping technical content and examples, supporting the open source community, and feeding real developer input back into product and roadmap.

This role fits someone with a devtool engineering background who works close to the code and close to users. The goal is to define DevRel at an early-stage company, not inherit a playbook.

Responsibilities

• Be the primary interface between Zep and our developer community.
• Work hands-on with Graphiti and Zep to build examples, demos, and reference implementations.
• Produce technical content that reflects how developers actually use the product.
• Support and grow the open source community through issues, discussions, and direct engagement.
• Provide clear feedback to product and engineering based on real developer usage.

Requirements

• Background building developer tools, either as a founder, engineer, or early team member.
• Strong technical depth and comfort reading, writing, and explaining code.
• Clear written and verbal communication with engineers.
• High ownership and comfort operating without a predefined DevRel playbook.
• Interest in agent systems, infrastructure, or developer-facing platforms.