<?xml version="1.0" encoding="UTF-8"?>
<source>
  <jobs>
    <job>
      <externalid>16d6fa31-6b8</externalid>
      <Title>Senior IT Engineer, AI Enablement</Title>
      <Description><![CDATA[<p>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&#39;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\n<strong>Responsibilities:</strong>\n\n<em> 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</em> 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&#39;s technically convenient.\n<em> Run a continuous feedback loop: gather usage signals and qualitative input from champions, identify what&#39;s working and what&#39;s falling flat, and iterate accordingly.\n</em> Build lightweight documentation, reference examples, and enablement materials that help non-technical stakeholders understand what&#39;s possible and how to request new capabilities.\n<em> Represent the needs of end users and champions when making integration decisions; you are their voice in the build process.\n\n<strong>MCP Integration &amp; Build:</strong>\n\n</em> Integrate SaaS and internal applications with Omada&#39;s MCP ecosystem by building and configuring MCP servers, adding tools, and handling authentication patterns including OAuth and webhooks.\n<em> Write skills that expose the right actions and data to AI agents in a clear, composable way.\n</em> Compose skills and tools into role-appropriate bundles, scoped to what each team and function actually needs, not everything at once.\n<em> Deploy tool bundles to ABAC groups, managing access so the right people get the right capabilities without overprovisioning.\n</em> Partner with the Senior IT Engineers, Automation on integrations that span MCP and workflow automation, ensuring handoffs and shared patterns are consistent.\n<em> Participate in design reviews for new MCP integrations to catch potential issues early and keep the ecosystem coherent.\n</em> Teach and mentor IT team members as you go. Be the SMEs that help us understand and internalize this tech.\n\n<strong>Governance &amp; Responsible Building:</strong>\n\n<em> 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</em> Contribute to Omada&#39;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<em> Ensure integrations handle data appropriately given Omada&#39;s health data environment. Understand what data flows where, flag concerns early, and work with Security and Compliance when review is warranted.\n</em> Maintain audit-friendly integration configurations so that security and compliance teams have the visibility they need without heroic effort on their part.\n<em> Collaborate with Security on risk assessment for high-sensitivity integrations, and translate security requirements into practical implementation decisions.\n\n<strong>Platform Craft:</strong>\n\n</em> Maintain a working knowledge of the MCP control plane configuration and capabilities so you can ship integrations efficiently and troubleshoot confidently.\n<em> 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</em> Contribute to reusable patterns, shared templates, and internal documentation that raise the quality bar for everyone building on the platform.\n<em> Stay current on the MCP ecosystem, agentic frameworks, and adjacent tooling. Bring relevant innovations back to the team.\n\n<strong>What Great Looks Like:</strong>\n\n</em> Ships new MCP integrations and skill bundles regularly, moves from &quot;teams want this capability&quot; to &quot;teams are using this capability&quot; with speed and confidence.\n<em> Earns trust with department champions by listening carefully, delivering on commitments, and iterating when something isn&#39;t quite right.\n</em> Builds integrations that hold up over time: well-scoped permissions, thoughtful data handling, clear documentation. Don&#39;t just build POCs that work on day one.\n<em> Operates autonomously but communicates proactively: stakeholders always know what&#39;s in progress, what&#39;s blocked, and what&#39;s coming next.\n</em> Thinks about the whole adoption curve, not just the technical implementation. Considers onboarding, training, and feedback from the start.\n<em> Demonstrates strong judgment about when to move fast and when to slow down and involve Security or Compliance.\n</em> Influences how the team builds by contributing ideas, patterns, and standards that make the MCP ecosystem better for everyone who relies on it.\n<em> Measures their own success by whether teams are actually using what was built, and digs in when adoption isn&#39;t happening.\n\n<strong>Candidate Requirements:</strong>\n\n</em> Hands-on experience building with MCP; configuring or authoring MCP servers, connecting tools, writing skills, and working with agentic frameworks.\n<em> Strong SaaS API integration experience: REST, webhooks, OAuth, and the practical realities of connecting enterprise applications reliably.\n</em> Understanding of ABAC, access control, and governance principles for AI/LLM deployments, including how to apply least-privilege in practice.\n<em> Expertise working directly with non-technical stakeholders, understanding their needs, translating them into technical solutions, and maintaining the relationship through iteration.\n</em> Demonstrated track record of driving tool adoption, developer enablement, or similar change; not just building things, but getting people to use them.\n<em> Ability to write and maintain integration code (Python or similar). Comfortable authoring and debugging scripts, not just configuring UIs.\n</em> 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</p>
<p style="margin-top:24px;font-size:13px;color:#666;">XML job scraping automation by <a href="https://yubhub.co">YubHub</a></p>]]></Description>
      <Jobtype>full-time</Jobtype>
      <Experiencelevel>senior</Experiencelevel>
      <Workarrangement>remote</Workarrangement>
      <Salaryrange></Salaryrange>
      <Skills>MCP, SaaS API integration, REST, webhooks, OAuth, ABAC, access control, governance principles, least-privilege, agentic frameworks, Python, integration code, systems integration, developer enablement, internal tooling</Skills>
      <Category>Engineering</Category>
      <Industry>Technology</Industry>
      <Employername>Omada Health</Employername>
      <Employerlogo>https://logos.yubhub.co/omadahealth.com.png</Employerlogo>
      <Employerdescription>Omada Health is a digital health company that provides personalized health coaching and wellness programs to individuals.</Employerdescription>
      <Employerwebsite>https://www.omadahealth.com/</Employerwebsite>
      <Compensationcurrency></Compensationcurrency>
      <Compensationmin></Compensationmin>
      <Compensationmax></Compensationmax>
      <Applyto>https://job-boards.greenhouse.io/omadahealth/jobs/7800365</Applyto>
      <Location>Remote, USA</Location>
      <Country></Country>
      <Postedate>2026-04-17</Postedate>
    </job>
  </jobs>
</source>