Description
Job Title: Senior IT Engineer, AI Enablement\n\nWe are seeking a highly skilled Senior IT Engineer to join our team in enabling AI capabilities across the organization. As a Senior IT Engineer, AI Enablement, you will be responsible for building and expanding Omada's MCP ecosystem, connecting SaaS tools and internal systems via MCP servers, writing skills, composing tool bundles for different teams, and deploying them to the right people.\n\nResponsibilities:\n\n Serve as the primary point of contact for department champions across Omada, working with them to understand their day-to-day workflows and identify where AI-assisted automation creates real leverage.\n Drive AI adoption across the company by deploying tool bundles that are actually useful, making sure integrations fit how teams work rather than asking teams to adapt to what's technically convenient.\n Run a continuous feedback loop: gather usage signals and qualitative input from champions, identify what's working and what's falling flat, and iterate accordingly.\n Build lightweight documentation, reference examples, and enablement materials that help non-technical stakeholders understand what's possible and how to request new capabilities.\n Represent the needs of end users and champions when making integration decisions; you are their voice in the build process.\n\nMCP Integration & Build:\n\n Integrate SaaS and internal applications with Omada's MCP ecosystem by building and configuring MCP servers, adding tools, and handling authentication patterns including OAuth and webhooks.\n Write skills that expose the right actions and data to AI agents in a clear, composable way.\n Compose skills and tools into role-appropriate bundles, scoped to what each team and function actually needs, not everything at once.\n Deploy tool bundles to ABAC groups, managing access so the right people get the right capabilities without overprovisioning.\n Partner with the Senior IT Engineers, Automation on integrations that span MCP and workflow automation, ensuring handoffs and shared patterns are consistent.\n Participate in design reviews for new MCP integrations to catch potential issues early and keep the ecosystem coherent.\n Teach and mentor IT team members as you go. Be the SMEs that help us understand and internalize this tech.\n\nGovernance & Responsible Building:\n\n Build MCP servers and skills that follow least-privilege principles from day one, scoping access to what an integration actually needs, and nothing more.\n Contribute to Omada's standards and policies for MCP server onboarding, skill review, and access governance, as a practitioner who cares about getting it right, not as a compliance gatekeeper.\n Ensure integrations handle data appropriately given Omada's health data environment. Understand what data flows where, flag concerns early, and work with Security and Compliance when review is warranted.\n Maintain audit-friendly integration configurations so that security and compliance teams have the visibility they need without heroic effort on their part.\n Collaborate with Security on risk assessment for high-sensitivity integrations, and translate security requirements into practical implementation decisions.\n\nPlatform Craft:\n\n Maintain a working knowledge of the MCP control plane configuration and capabilities so you can ship integrations efficiently and troubleshoot confidently.\n Identify gaps in the current integration library and propose a prioritized roadmap for new MCP servers and skills, informed by champion feedback and team-level demand.\n Contribute to reusable patterns, shared templates, and internal documentation that raise the quality bar for everyone building on the platform.\n Stay current on the MCP ecosystem, agentic frameworks, and adjacent tooling. Bring relevant innovations back to the team.\n\nWhat Great Looks Like:\n\n Ships new MCP integrations and skill bundles regularly, moves from "teams want this capability" to "teams are using this capability" with speed and confidence.\n Earns trust with department champions by listening carefully, delivering on commitments, and iterating when something isn't quite right.\n Builds integrations that hold up over time: well-scoped permissions, thoughtful data handling, clear documentation. Don't just build POCs that work on day one.\n Operates autonomously but communicates proactively: stakeholders always know what's in progress, what's blocked, and what's coming next.\n Thinks about the whole adoption curve, not just the technical implementation. Considers onboarding, training, and feedback from the start.\n Demonstrates strong judgment about when to move fast and when to slow down and involve Security or Compliance.\n Influences how the team builds by contributing ideas, patterns, and standards that make the MCP ecosystem better for everyone who relies on it.\n Measures their own success by whether teams are actually using what was built, and digs in when adoption isn't happening.\n\nCandidate Requirements:\n\n Hands-on experience building with MCP; configuring or authoring MCP servers, connecting tools, writing skills, and working with agentic frameworks.\n Strong SaaS API integration experience: REST, webhooks, OAuth, and the practical realities of connecting enterprise applications reliably.\n Understanding of ABAC, access control, and governance principles for AI/LLM deployments, including how to apply least-privilege in practice.\n Expertise working directly with non-technical stakeholders, understanding their needs, translating them into technical solutions, and maintaining the relationship through iteration.\n Demonstrated track record of driving tool adoption, developer enablement, or similar change; not just building things, but getting people to use them.\n Ability to write and maintain integration code (Python or similar). Comfortable authoring and debugging scripts, not just configuring UIs.\n 7+ years of experience in a systems integration, developer enablement, internal tooling, or closely related role.\n* Strong communication skills; able to explain technical decisions and trade-offs clearly to audiences ranging from developers to non-technical stakeholders.\n\n