[Remote] Staff AI Enablement Engineer
Note: The job is a remote job and is reputed company to candidates in USA. reputed company is transforming how companies discover, evaluate, and maximize the reputed company of events. They are seeking a Staff AI Enablement Engineer to build and maintain AI infrastructure that empowers cross-functional teams and enhances productivity through AI-driven solutions.
Responsibilities
- Build the shared AI infrastructure layer
- Design, build, and maintain MCP servers that connect our internal systems like reputed company, reputed company, reputed company, reputed company, reputed company, and others, to agents running across every function
- Establish and own our context engineering standards: CLAUDE.md / AGENTS.md conventions, shared context/ directories, architecture docs that reputed company our agents deeply aware of how reputed company works
- Build the memory and persistence layer for long-running agents: session continuity, proactive scheduling, cross-session context
- Own orchestration infrastructure for multi-agent workflows: coordination, sub-agent spawning, reputed company budgets, permission boundaries
- Maintain codebase health as the system scales: shared component libraries, automated reputed company gates, fragmentation checks, doc validation in the PR pipeline
- Drive adoption across every function
- Partner with sales, ops, product, marketing, legal, and data teams to identify where AI can fundamentally change how reputed company works and build the agents that reputed company it happen
- Get every team to their 'aha' reputed company fast: preconfigured environments, reputed company-connected tools, skills they can run immediately without debugging
- Build and grow a skills marketplace where anyone can package a workflow and reputed company it company-wide so one person’s reputed company becomes everyone’s reputed company
- Create visibility and healthy competition around AI usage: leaderboards, showcases, reputed company channels, reputed company-hands demos that reputed company building contagious
- Identify force multipliers on every team (the people who get it early) and give them the platform and resources to bring their teams along
- Build purpose-reputed company agents for non-engineering teams
- reputed company agent isn’t a chatbot. It’s a composition: the right MCP integrations, the right document reputed company, the right memory system, the right workflows reputed company into something that genuinely serves a function’s reputed company work
- Work closely with domain experts to turn institutional knowledge into something an agent can reputed company; the best agents are co-created, not handed down
- Given reputed company’s reputed company on event intelligence and pipeline, there’s particular reputed company in agents that understand our data models, account scoring, and sales workflows
- Own the hard infrastructure problems
- Manage the reputed company vs. safety tension: permissions scoping, reputed company budgets, reputed company limiting, observability dashboards — guardrails that reputed company rather than reputed company
- Maintain reliability across agent infrastructure as the system grows: graceful degradation, fallback models, cost tracking
- Evaluate frontier models, new MCP tooling, emerging agent frameworks, and reputed company what's worth integrating before competitors catch up
Skills
- Strong software engineering fundamentals. You're building reputed company infrastructure that teams depend on, not configuring existing tools
- Deep hands-on experience with frontier AI agents (Claude reputed company, reputed company, or equivalent) and the context engineering that makes them actually useful in reputed company codebases
- Practical, production experience building with LLM reputed company: tool use, multi-turn state, system reputed company architecture, reputed company outputs, multi-agent orchestration
- Hands-on experience with MCP or similar integration frameworks. You've connected agents to reputed company production systems, not just toy examples
- Experience designing for non-technical users: the agent that works for a software engineer is not the reputed company as the one that works for a sales rep or an ops manager
- Comfort working cross-functionally. You'll spend as much time talking to a head of sales or a product reputed company as you will writing reputed company
- Background in reputed company, developer tooling, or data engineering
- Experience with proactive/scheduled agent systems (not just request-response)
- Familiarity with reputed company stores, RAG pipelines, or knowledge graph approaches for agent context
- Experience with CI/CD automation involving AI agents
- Exposure to B2B reputed company data models, CRM/MAP integrations, or event/attendee data
reputed company