Responsibilities

• Build the motion: design the Enterprise Developer Advocacy program from pilot to repeatable practice, including session formats, account selection criteria, readouts, and measurement
• Run sessions inside target accounts: deliver education-first technical sessions (agents and AgentControl, safe rollouts, experimentation, runtime control) tailored to each account's stack and use cases
• Build champions with the field: partner with AEs, SEs, and CS to identify accounts, find and develop internal champions, and hand off what surfaces cleanly to the teams who should own it
• Keep it credible: protect the non-promotional, education-first nature of the sessions; this motion works because it isn't a sales pitch
• Prove it with evidence: instrument the pilot, produce session readouts, debrief with reps, and make the scale, adjust, or stop recommendation based on what the data shows
• Shape what comes next: as the motion proves out, define how it scales, including the playbook future advocates would run

Requirements

• A background spanning at least two of: developer advocacy, solutions engineering, developer education, technical marketing
• Comfortable in enterprise rooms: you can teach a technical session to fifty engineers and handle hardball questions from a skeptical principal architect
• Hands-on technical credibility: you build, demo, and teach, and senior engineers take you seriously
• Strong operational instincts: you can run a repeatable program, prioritize incoming demand, and keep commitments to the field
• Typically requires a minimum of 12 years of related experience.
• Ability to travel approximately 25% of the time

Preferred

• (Bonus) Experience with feature management, experimentation, observability, or agent orchestration tooling
• (Bonus) You've built a customer-facing technical program (workshops, DevDays, office hours) from scratch
• (Bonus) Deep enterprise software background: you understand how large engineering organizations make platform decisions