# AI Adoption Engineer
About the role
As an AI Adoption Engineer, you are the person who shows up after the contract is signed and makes adoption real. You design and run hackathons, facilitate Customer Developer Days, build internal champions, and create conditions for engineering teams to shift how they work with AI. This is a post-sales, customer-facing IC role working closely with AI Deployment Managers and Customer Success to identify where adoption is stalling and design high-touch interventions.
What you'll do
- Design, produce, and run internal hackathons within customer organizations: company-specific formats, cohort-based programs, single-day sprints, multi-day builds, and theme-based challenges
- Build and own the Customer Developer Day program: immersive half-day or full-day events for specific accounts or customer segments
- Develop facilitation infrastructure that makes programs repeatable: playbooks, judging rubrics, agenda frameworks, and post-event retrospective templates
- Partner with AI Deployment Managers and Customer Success to identify the right intervention for each account
- Capture outcomes from every engagement and turn them into customer success stories
- Identify patterns across customer engagements and feed them back into Customer Education team design
- Be a credible technical presence in the room with developers: follow codebases, troubleshoot in real time, and demonstrate Cursor capabilities
You may be a fit if
- You have experience running developer events, hackathons, or technical workshops with measurable adoption outcomes
- You are technical enough to be credible with experienced engineers and use Cursor or comparable AI coding tools
- You understand the difference between a great event and a great adoption program
- You are energized by being in the room with customers, not behind a content queue
- You have worked in post-sales or customer success contexts
- You are a strong communicator and facilitator
- You use AI tools as core infrastructure in how you work
Strong candidates may also have
- Prior experience in developer relations, developer advocacy, or technical customer success
- Background in instructional design, facilitation, or learning science
- Experience at developer tools companies
- Familiarity with enterprise engineering environments
- Content creation experience