About Buildkite

Buildkite’s CI platform is trusted by the world’s leading engineering teams, shipping software to over 1,000,000,000 daily users.

Job Overview

We’re looking for a Dev Events & Enablement Lead to run the field surface area of our strategy; events, community meetups, workshops that turn Buildkite’s PoV into lived moments; then convert those moments into repeatable pipeline, adoption, and advocacy through clear enablement for GTM to translate.

We see events and community as a proof engine for our brand. You’ll execute programs that engineers actually want to attend, capture the right proof while you’re there, and ensure Sales can follow through with clarity and confidence afterwards.

We’re only interested in candidates who can do both sides of the job; build dev-first event experiences with taste, and run enablement like an operating system.

🚀 What You’ll Do

Build a field program developers respect

• Design and run dev-first events: community meetups, workshops, dinners, roundtables and co-sponsored nights
• Create a coherent program strategy aligned to our 2026 pillars and journey stages (awareness→consideration→adoption)
• Build a repeatable community system presence in the Bay Area; what we run, why it works and what gets better every iteration

Turn moments into proof

• Capture high-signal proof on-site
• Partner with teams and on-site coll to convert raw event reality into durable assets
• Ensure every event produces reusable artifacts

Own enablement as a system

• Build and maintain enablement that gets used effectively
• Create a clean operating model for enablement intake
• Run enablement like product: versioned, maintained and measurable, with explicit quality gates

Ship stage plays that move deals forward

• Translate community learnings + funnel friction into stage plays across the customer journey
• Equip Sales to run credible, technically honest conversations
• Tighten loop with GTM programs so outbound/inbound follow-up is sharp and consistent

Make the funnel legible

• Define what good looks like per event type
• Build simple tracking that connects: event→signal→meeting→pipeline→revenue
• Report with honesty; what worked, what didn’t and what we evolve next cycle

Run an OS that compounds

You’ll operate with a cadence that scales beyond any single person:

• Program loop; plan→run→debrief→iterate→scale
• Proof loop; capture→validate→package→publish→reuse
• Enablement loop; objections→assets→usage→feedback→refresh
• Pipeline loop; signals→routing→follow-up plays→outcomes→learnings
• Quality loop; standards→review gates→sampling→retire/replace
• Partner loop; align with Brand/GTM/Dev Voice→ship together→reduce narrative drift

What You Bring

This role only works with field instincts and operational rigor.

• Proven experience running dev events and community programs that engineers actually like
• You’ve shipped systems that improved conversion quality and rep confidence
• Devtools/technical marketing fluency, where you can hold your own in CI/CD conversations
• You know the difference between “content” and “proof,” and you avoid hollow claims
• You can run calendars, vendors, budgets, logistics plus ship the actual work without chaos
• You understand how deals move, why they stall, what objections sound like in the real world
• You can turn messy feedback into simple stage plays and reusable assets that don’t rot
• You partner tightly with GTM while owning outcomes end-to-end
• Comfort working async in a high-trust environment where you own problems start-to-finish

Nice-to-haves

• Experience in CI/CD, DevOps, infra or adjacent technical domains
• Familiarity with intent/ABM systems
• Strong network in relevant dev communities and event ecosystems
• Comfort collaborating on technical demos and proof artifacts with engineering

How We Work

• Autonomously, with agency; you'll join a small team of high-performing ICs, with the ability to drive and influence business impact from the start
• Async by default, with focused sync for decisions, pairing, and unblock moments
• We ship iteratively; small releases, tight feedback loops, measurable improvements
• We document and work in the open; decisions, risks, tradeoffs, fails, the lot
• We aim for craft and delight, but we don’t worship polish over progress