AI Adoption Engineer - East

About this role

Traversal seeks an AI Adoption Engineer to guide enterprise customers through post-deployment adoption phases, driving product usage and value realization. You'll own customer portfolios end-to-end, combining technical expertise in distributed systems with executive-level stakeholder management to ensure Traversal becomes the default incident response tool.

What you'll do

• Own four adoption phases (Activation, Scaling, Optimization, Value Realization) for assigned enterprise accounts from deployment through renewal
• Maintain and execute customer-specific 30/60/90 roadmaps, running kickoffs, enablement sessions, QBRs, and executive syncs
• Engineer custom integrations, debug accuracy issues, and conduct prompt engineering for customer-specific use cases
• Instrument accuracy tracking and translate customer failure modes into product roadmap feedback for engineering
• Publish monthly executive updates with usage data and drive service-launch integration across customer platforms
• Synthesize cross-customer insights and contribute to community knowledge-sharing among power users

What they're looking for

• Distributed systems and production incident troubleshooting
• Technical account management and customer success strategy
• Executive and engineer-level communication and relationship building
• Prompt engineering and AI system debugging
• Product adoption and change management
• Data analysis and usage-based performance tracking
• Integration troubleshooting and workflow optimization
• Cross-functional collaboration and roadmap input synthesis

Benefits

• Remote position based in East region
• Work with largest enterprises running mission-critical production systems
• Exposure to cutting-edge AI reasoning and SRE platform technology
• Technical depth valued alongside commercial acumen
• Direct influence on product roadmap through customer feedback

Likely interview questions

• Describe a time you debugged a technical issue at a customer site—how did you balance gathering diagnostic data with maintaining executive credibility?
• How would you approach getting an engineering team reluctant to adopt a new incident response tool to make it their first-call resource?