TixelJobs
O
Omadahealthvia Greenhouse

Senior IT Engineer, AI Enablement

REMOTE$143K - $178K/yrPosted 1d ago
OtherSeniorFull-time

Not sure if you're a good fit?

Upload your resume and TixelJobs AI will compare it against Senior IT Engineer, AI Enablement at Omadahealth. Get a match score, missing keywords, and improvement tips before you apply.

Free preview · Your resume stays private

About the Role

Omada Health is on a mission to inspire and engage people in lifelong health, one step at a time. The Omada IT department builds and operates resilient, scalable services that empower everyone at Omada. Increasingly, that means putting the right AI capabilities in the right people's hands.

Job Overview:

The Senior IT Engineer, AI Enablement is a senior individual contributor who builds and expands 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. You are the bridge between what AI can do and what Omada's teams actually need it to do.

You will work directly with department champions across the company to understand their workflows, surface opportunities for AI-driven automation, and turn those opportunities into real, working integrations. Your daily question is: what new capability did I unlock for the company today?

This role sits on a small, high-impact team within IT that owns business process automation and agentic/AI-driven automation. You'll partner with Senior IT Engineers, Automation and work under the Senior Manager, IT Automation. We're hiring two people for this role.

You'll use Omada's MCP control plane, not as a system to babysit, but as the platform that lets you move fast and ship integrations safely. You build with security and governance in mind from the start because it's the right way to build, not because someone else is watching the dashboards.

And you’ll document and socialize as you go, so the entire IT org understands this emergent technology and can multiply your impact throughout the organization.

Responsibilities:

AI Enablement & Adoption

  • 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.
  • 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.
  • 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.
  • Build lightweight documentation, reference examples, and enablement materials that help non-technical stakeholders understand what's possible and how to request new capabilities.
  • Represent the needs of end users and champions when making integration decisions; you are their voice in the build process.

MCP Integration & Build

  • 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.
  • Write skills that expose the right actions and data to AI agents in a clear, composable way.
  • Compose skills and tools into role-appropriate bundles, scoped to what each team and function actually needs, not everything at once.
  • Deploy tool bundles to ABAC groups, managing access so the right people get the right capabilities without overprovisioning.
  • Partner with the Senior IT Engineers, Automation on integrations that span MCP and workflow automation, ensuring handoffs and shared patterns are consistent.
  • Participate in design reviews for new MCP integrations to catch potential issues early and keep the ecosystem coherent.
  • Teach and mentor IT team members as you go. Be the SMEs that help us understand and internalize this tech.

Governance & Responsible Building

  • Build MCP servers and skills that follow least-privilege principles from day one, scoping access to what an integration actually needs, and nothing more.
  • 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.
  • 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.
  • Maintain audit-friendly integration configurations so that security and compliance teams have the visibility they need without heroic effort on their part.
  • Collaborate with Security on risk assessment for high-sensitivity integrations, and translate security requirements into practical implementation decisions.

Platform Craft

  • Maintain a working knowledge of the MCP control plane configuration and capabilities so you can ship integrations efficiently and troubleshoot confidently.
  • 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.
  • Contribute to reusable patterns, shared templates, and internal documentation that raise the quality bar for everyone building on the platform.
  • Stay current on the MCP ecosystem, agentic frameworks, and adjacent tooling. Bring relevant innovations back to the team.

What Great Looks Like:

  • Ships new MCP integrations and skill bundles regularly, moves from "teams want this capability" to "teams are using this capability" with speed and confidence.
  • Earns trust with department champions by listening carefully, delivering on commitments, and iterating when something isn't quite right.
  • 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.
  • Operates autonomously but communicates proactively: stakeholders always know what's in progress, what's blocked, and what's comi
Share