Technical Advocate

About Dragonfly

Dragonfly is a high-performance, Redis-compatible in-memory data store built for real-time, large-scale, intelligent workloads. Our customers run Dragonfly at the core of ML feature stores, personalization systems, and real-time recommendation engines where latency and scale are non-negotiable.

We're building infrastructure for the next generation of ML and AI systems. The world doesn't need another developer relations person who writes blog posts and attends conferences. We need someone who can cut through the noise in a crowded infrastructure market and make engineers stop scrolling.

Role Overview

The technical enterprise software space is deafening right now. Every database, every cache, every data platform has a blog, a YouTube channel, and a conference talk. The only thing that actually breaks through is creativity paired with genuine technical conviction.

As a Technical Advocate, you'll own how Dragonfly shows up to developers, ML platform teams, and infrastructure engineers. This role sits at the intersection of deep technical expertise, strong opinions, and real go-to-market impact.

You'll have a point of view on where infrastructure is heading and you won't be shy about it. You'll have something to say about why 2015-era caching architectures are a liability in 2026. And you'll find ways to say it that nobody else in the space is saying it.

This role is also an experiment in how much a single, highly leveraged person can do when they build and orchestrate AI agents as co-workers rather than using AI as a spell checker.

What Makes This Role Different

You will build and manage an agent team

This is not "use AI to write faster." You will design, train, and manage a system of AI agents that extend your output across research, content production, community monitoring, competitive intelligence, and distribution. Think of it as building a small production studio where you are the creative director and the agents are the crew.

You'll be expected to architect that system, iterate on it, and own it. The bar for output scales accordingly.

You need a genuine point of view

We don't want someone who explains what Dragonfly does. We want someone who has a thesis about where the ML infrastructure stack is going, where the bodies are buried in legacy architectures, and why the current moment is a real architectural inflection point, not just a marketing cycle.

That point of view should be sharp enough to make some people uncomfortable and credible enough that senior infrastructure engineers take it seriously.

Creativity is a hard requirement

The playbook in this space is: benchmark post, conference talk, integration tutorial, repeat. That playbook is saturated. We need someone who approaches this like a creative problem, not an execution problem. What format hasn't been done? What angle hasn't been taken? What would make an ML platform engineer share something from a database company?

If your portfolio looks like everyone else's, this probably isn't the right fit.

Ownership and Responsibilities

Technical Content and Storytelling

You own Dragonfly's technical voice across every channel. The mandate is quality and originality, not volume for its own sake.

• Technical blog posts with a distinct point of view, not feature announcements dressed up as thought leadership
• Video content: long-form deep dives, short-form for social, live demos that show rather than tell
• Conference talks where you're sharing a real thesis, not a product pitch
• Social content that earns engagement from engineers, not likes from peers

The core narratives you'll develop and push:

• Why Redis-era architectures are a structural liability for teams building real-time ML systems
• How Dragonfly fits into modern AI infrastructure, specifically at the feature serving layer
• Where in-memory data infrastructure is heading and why the next few years look nothing like the last ten

Agent System Design and Management

• Design a content and research agent system from scratch, including tooling choices, prompt architecture, and evaluation loops
• Train agents on Dragonfly's technical voice, competitive landscape, and key narratives
• Build pipelines for competitive monitoring, community signal detection, and content distribution
• Continuously evaluate and improve agent output quality; you are accountable for everything that ships

Documentation and Developer Experience

• Identify friction and gaps in the developer journey, and close them
• Turn real community questions into durable documentation that ranks and helps
• Work directly with engineering to get the technical details right

Community and Field Engagement

• Engage in technical discussions on social platforms, forums, and Discord with genuine substance
• Represent Dragonfly at conferences and meetups, not just as a booth presence but as someone with something to say
• Step in as a technical resource during active sales conversations: demos, deep technical Q&A, deal support

What We're Looking For

Non-negotiables

• Creative instincts: you've produced technical content that doesn't look or sound like everyone else's. You can point to it.
• Strong technical opinions: you have a thesis about where infrastructure is heading. You can defend it in a room full of senior engineers.
• AI-native operator: you don't just use AI tools. You build with them. You've designed systems, written prompts at scale, and thought seriously about output quality and evaluation.
• Technical depth: strong background in distributed systems, databases, ML infrastructure, or adjacent areas. You can go deep with an ML platform team and earn the conversation.
• High bar for quality: you'd rather ship one piece that spreads than five that disappear.

Strong signals

• You've built something in public that got traction with an engineering audience
• You have opinions about the Valkey fork, the future of managed Redis, or the ML feature serving stack
• You've built agent workflows or automated pipelines beyond basic prompt chaining
• You've given a talk that you're genuinely proud of, not just one you completed

KPIs and Success Metrics

• Technical content engagement from the right audience: engineers, ML platform leads, infrastructure decision-makers
• Pipeline impact: shorter sales cycles, higher deal velocity tied to content-driven education
• Agent system output: measurable increase in content quality and reach without proportional increase in manual effort
• Community credibility signals: inbound from engineers, conference invitations, discussion threads you didn't start

Why This Role Matters

Infrastructure is a crowded, noisy, conservative market. The companies that win in it aren't always the ones with the best product. They're the ones that build the clearest, most credible technical narrative and get it in front of the right people first.

This role shapes whether Dragonfly is seen as a credible next-generation infrastructure platform or just another Redis alternative. That distinction is worth a lot.

You'll have real ownership, real visibility, and the opportunity to build something new in terms of how a technical advocacy function can operate at an AI-native company.

Location: SF Bay Area / Remote (North America) To apply: careers@dragonflydb.io