You understand how developers behave online.
You’ve built an audience, community, engagement program, developer program, or similar function, and can point to outcomes you changed.
You have strong judgment about when a company should join a conversation and when it shouldn’t.
You are naturally curious. If developers suddenly start discussing something relevant to Datadog, your instinct is to understand why, find the thread, and figure out whether we should participate.
You think in systems. If ten people are manually forwarding Reddit posts into Slack, you want to build something better.
You’re comfortable with tooling, automation, monitoring platforms, APIs, AI, and lightweight workflows. You don’t necessarily need to be an engineer, but you should be comfortable working closely with engineers and technical products.
You can create structure where none exists: monitoring rules, triage processes, response playbooks, escalation paths, reporting, and measurement.
You know how to earn participation from internal experts rather than simply assigning them another marketing task.
You move quickly, have strong judgment, and know what can ship immediately versus what needs another set of eyes.
You have opinions about developer culture, platforms, formats, and internet behavior — and you update those opinions when the evidence changes.
Your background
You may come from Growth,Developer Marketing, Audience Development, Product, Media, Social, Technical Communications, or somewhere entirely different.
What matters most is that you can show us how you’ve built participation around an audience, created systems that scale engagement, and turned what people were saying into action.
Experience working with a technical or enthusiast audience is especially valuable.