Director, Developer Marketing

Redis•San Francisco, CA

About The Position

Software is being rebuilt around AI agents, and the systems those agents rely on for memory and real-time data are some of the most important infrastructure of the next decade. Redis sits at the center of that shift. Developers are the people who decide what gets built, and increasingly their agents are too: both learn from the guides, demo apps, docs, and community answers that exist in the world. Developer Marketing is the team that earns developer love for Redis in the AI era and makes Redis the natural choice when a developer (and their agent) reaches for memory and real-time data. It wins the long game: building the audience, the credibility, and the content corpus that compound over time. This is a standalone function, and you are the leader who builds it.

Requirements

A builder who has run or scaled a developer relations, developer marketing, or community function, ideally at a developer-tools or infrastructure company.
Technical credibility with developers. You do not have to ship production code, but you understand what an engineer building a production AI agent actually needs, and you earn respect in that room.
A track record of producing or commissioning developer content that developers (and now their agents) actually use: guides, demo apps, reference implementations.
Fluency with leading indicators (sign-ups, sentiment, third-party validation, agent recommendation) and how to grow them.
A point of view on the AI-builder ecosystem and where it is heading, plus a network in it.
Operator instincts: a focused team, a bias toward shipping, and the judgment to know what matters most.

Responsibilities

Advocacy in the field. In the room with developers: events, hackathons, speaking, workshops. Your advocates are the human face of Redis and a center of gravity for the developer community, the people the AI-builder world gathers around, learns from, and trusts. Credibility you cannot buy.
Content engineering. How-to guides, demo apps, reference implementations, and writing on where developers are heading. Proof that the product works, written so a developer (and their agent) can copy, paste, and ship.
Community. Active where developers already live: Reddit, Stack Overflow, Discord, Slack. Answer questions, remove friction, surface what you hear to Product, and turn participants into advocates.
Agent recommendation. Whether agents reach for Redis by default when a developer builds. This is the signal the whole function is built to move.
Developer sign-ups. New developers the team brings to the door. Top of funnel, fully ours to drive.
Developer sentiment. How the community feels about Redis, tracked across the channels we work.
Third-party validation. External advocates and content vouching for Redis. The signal that matters most, and the one that compounds.