AI Enablement Engineer
About the role
- Drive AI adoption and standardization across engineering
- Serve as the primary enablement partner for AI foundations, standards, and framework adoption across the engineering organization.
- Evangelize the AI tooling patterns, standards, and best practices being defined by engineering leaders and working groups.
- Help move the organization toward a standardized AIDLC process by making expected behaviors, workflows, and quality bars explicit and easy to adopt.
- Partner with leaders across platform, engineering, and operations to identify where AI should become part of default engineering practice rather than an optional side project.
- Reinforce practical adoption through examples, short demos, applied workflows, and direct support rather than relying only on broad show-and-tell sessions.
- Own the feedback loop and continuous improvement motion
- Build and maintain a structured feedback loop with the engineering community to understand what is working, where friction exists, and which standards or workflows need refinement.
- Coordinate continuous improvement of AI standards and frameworks, not just their rollout, by channeling field feedback back to the leaders building them.
- Create mechanisms to gather lightweight input from engineers, team leads, and managers on adoption blockers, tooling gaps, and workflow quality.
- Help ensure the AIDLC working group stays connected to real engineering usage patterns, not just policy or infrastructure decisions.
- Translate recurring issues into clear recommendations for updates to playbooks, standards, templates, and training assets.
- Create lightweight, high-frequency enablement content
- Produce bite-size recordings, short snippets, and practical reminders that keep engineers engaged with evolving AI standards and practices.
- Create concise do and do not guides, examples of strong AI-assisted workflows, review checklists, and quick-reference materials that reinforce expected engineering behaviors.
- Use AI tools such as Claude, ChatGPT, Gamma, and similar platforms to rapidly convert notes, strategy docs, working group outputs, meeting recordings, and examples into reusable enablement assets.
- Build repeatable prompt patterns, templates, and content-generation workflows that can be reused by engineering leaders and the broader org.
- Support office hours, hack sessions, team-specific enablement sessions, or time-zone-aware rollouts where hands-on guidance is needed.
- Measure adoption and tell the story of progress
- Partner with engineering leads to define dashboards and metrics that track AIDLC adoption, AI tool usage patterns, and productivity impact over time.
- Contribute to technical storytelling on two tracks: how AI standards and frameworks are evolving, and how the engineering org is trending toward more standardized AIDLC behavior.
- Use metrics to create clear, data-backed narratives about progress, gaps, and opportunities for further adoption.
- Help package adoption metrics and success stories for leadership updates, engineering all-hands, planning discussions, and quarterly reviews.
- Support the visibility of practical wins such as reduced delivery time, stronger code quality guardrails, faster new-hire productivity, and better reuse of AI-assisted workflows.
- Support onboarding and engineering learning where it matters
- Contribute to engineering onboarding by ensuring new engineers are introduced to approved AI tools, standard workflows, and expected usage patterns early in their ramp.
- Create or refresh targeted onboarding assets related to AI tooling, engineering standards, and how teams are expected to work with agents and copilots.
- Support role-specific learning where needed, but keep the primary focus on AI adoption and engineering enablement rather than owning onboarding as the central charter.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
