Developer Advocate

Your role at Dynatrace

In a world where coding agents write the code that ships to production, the developers steering those agents are the ones who decide what gets merged. But how can they genuinely trust the code their agents are producing? Enter Bluebox.ai, a new product from Dynatrace and a deliberately separate brand. Bluebox is a brand-new product designed to give AI coding agents runtime debugging superpowers, helping developers safely run, track, and ship AI-generated code. As our Developer Advocate, you are the face and voice of Bluebox in the developer community. You will earn credibility the only way it gets earned with developers: by building real things, publishing what you learn, showing up where they already are, and being straight with them about what the product does and does not do yet. You are also the community's voice coming back the other way, carrying real developer friction into the roadmap. We are a new brand in a new category, and the Dynatrace name will not carry this audience. Building brand affinity and developer trust from close to zero is the job. If building things from scratch, learning quickly, and helping define a new market is the kind of work you find meaningful, this may be the role for you.   In This Role, You Will:

Be the public face of Bluebox, under your own name and voice. Developers trust people, not logos. Build community presence on Discord, Hacker News, Reddit, Bluesky, and X. Helpful first, always. Write original technical content: deep dives, use-case walkthroughs, and the kind of post a developer sends to a colleague. Run livestreams, videos, and workshops where you build something real and people leave able to do it themselves. Speak at conferences and meetups, and be the reason developers go try the product. Help users tell their own stories through blogs, videos, and talks. Their version travels further than ours. Find friction in the quickstart, docs, and onboarding, and bring Product and Engineering a clear pattern with evidence. Co-create with influencers and community partners. Contracting and paid placement sit with Marketing. Be measured on sign-ups and real Bluebox usage, not impressions or follower counts.

When Applying Please include links to one or two pieces of your own public work — something you wrote, recorded, or built that taught developers something. Tell us briefly what you were trying to get across, and how you knew whether it landed. Then spend fifteen minutes with the Bluebox quickstart and tell us, in a maximum of 4 bullet points, where you think a developer would give up. We're more interested in what you noticed than whether you're right. Please apply with your resume in English. What will help you succeed

A public body of work. Talks, posts, repos, videos, or streams under your own name that we can go and read, watch, or run. At least 3 years in developer-facing work , including real time as a working developer. You have shipped software, not just talked about it. Hands-on coding. You build your own demos and sample projects and don't need someone else to make them work. Daily use of AI coding agents such as Claude Code, Cursor, GitHub Copilot, or Kiro — as core infrastructure in how you build, not as a novelty you tried once. Production instincts. You've been on call for overnight incidents or debugged something in production, and you know what that feels like. This grounds your authenticity and empathy for the day-to-day reality of our users. Startup or growth-stage experience. You understand the pace, and that a new product's growth story is non-deterministic. What worked last quarter isn't guaranteed to work this one. The willingness to say what isn't working — in public and internally — and the judgment to know how to say it. Comfort being publicly identified with a product nobody has heard of yet , and a genuine interest in changing that. Willingness to travel up to roughly