Buildkite - Staff Developer Relations Engineer

• Ship a dev-first demand engine • Own campaign execution across priority pillars, from concept→asset plan→launch→iteration • Build programs that serve devs and buyers; credibility up top, clarity in the middle, conversion at the bottom • Create a repeatable cadence that aligns our Labs (Brand Systems + Dev Voice + GTM) into • Be the technical advocate devs trust • Show up in the right places with real, honest and technical insights and answers • Teach CI concepts and Buildkite workflows in formats engineers respect • Build credibility by engaging with reality • Accelerate adoption with education and practical pathways • Design learning paths that reduce time-to-first-value: onboarding guides, implementation walkthroughs, etc • Partner with Product/Support to turn recurring confusion into better docs, better defaults, and better UX • Help teams migrate and modernise safely by demystifying CI and making it clear what good looks like • Partner with customers (large, small and OSS) to share technical war stories and value-first storytelling, both for CI and for deeper orchestration • Turn proof into public artifacts • Co-create with Content Engineering and Content Writing to turn technical reality into distributable proof • Capture and publish dev-grade assets that answer real questions and survive scrutiny • Maintain a high bar for public artifacts • Run signal capture for the whole org • Collect what devs are asking, what objections repeat, what patterns emerge and route it to the right owners • Make signal legible; categorise, quantify, and tell the truth clearly, even if it’s uncomfortable • Close the loop; ensure signal turns into shipped fixes • Build durable advocacy and champion pathways • Identify and nurture champions; power users, repeat contributors, future speakers • Create pathways from curious→capable→confident→advocate, with the assets and moments needed at each step • Partner with Dev Events to turn field moments into ongoing relationships and durable community pull • Run an OS that compounds • You’ll operate with a cadence that scales beyond any single person: • Education loop; teach→observe confusion→update assets→improve onboarding • Education loop; • Proof loop; identify gaps→co-build proof→validate→publish→reuse • Proof loop; • Adoption loop; guides/patterns→activation→support deflection→iteration • Adoption loop; • Advocacy loop; champions→moments→contributions→amplification • Advocacy loop; • Coherence loop; align with Brand/GTM/Dev Voice→reduce drift • Coherence loop;