Integrations Engineer

Building a world-class company

At Vitalize, we’re building toward a future where hospital operations are safe, autonomous, fair, and cost-effective. Today, hospitals still run their most critical workflows (staffing, labor planning, capacity management) on spreadsheets, paper, and gut instinct. This creates massive waste, burnout, and poor patient outcomes. Vitalize replaces this with an intelligent operating system for the hospital workforce. We bring real-time decision support to clinical leaders, eliminate manual work, reduce unnecessary labor spend, and unlock patient capacity across health systems.

About the role

Hospitals run on a patchwork of systems — medical records, time-and-attendance platforms, payroll engines, scheduling tools — none of which were designed to talk to each other. Vitalize sits at the center of that data and turns it into workforce intelligence that clinical leaders use to staff smarter, catch problems earlier, and stop making decisions blind.

As an Integration Engineer, you'll build and own the data pipelines, transformation logic, and synchronization infrastructure that connect Vitalize to the systems health systems already run on. Without what you’ll be building, the product doesn't exist.

Every staffing decision, scheduling recommendation, and real-time visibility into who's working and where depends entirely on the integrations you build. You'll write the code that makes enterprise-wide rollouts production-ready from day one.

Problems you'll work on

• Integrating with EHR platforms (Epic and others) via our integration middleware — configuring and extending proven connectors, not hand-rolling HL7 from scratch

• Engineering direct integrations with workforce management systems — UKG, Workday, Kronos, and others — that are reliable under load, resilient to chaotic upstream data, and built to scale with the largest health systems in the country — without sacrificing the platform stability.

• Reconciling shift, staff, and ADT data arriving from multiple source systems that are inconsistent by design — handling conflicts, gaps, and contradictions at the transform layer before they reach the product.

• Maintaining data accuracy under live conditions — detecting when systems have drifted apart, recovering cleanly when something goes wrong mid-flight, and ensuring inconsistency never surfaces to the product or the user.

What you bring

You know what it feels like to own integrations in production — not just ship them. When an upstream system changes without warning, when a sync is silently wrong, when an enterprise rollout exposes an edge case that didn't exist in UAT. That experience is the baseline.

On the technical side:

• You've built and operated queue-based worker systems in production — you've scaled clusters under real load and you understand the business cost of getting it wrong.

• You know when a full sync is a liability and how to design incremental sync pipelines that stay correct under failure, retry, and partial delivery.

• You design systems where failures are visible by default. You use schema contracts, typed error channels, and structured observability to make silent failures impossible

• You've built workflows and cron-driven pipelines that are durable across restarts, retries, and partial failures. You know the difference between a job that ran and a job that succeeded.

• You instrument before you ship. When something goes wrong in production you can move fast to trace an anomaly from symptom to source and narrow the blast radius

• You communicate clearly across technical and non-technical audiences expectations and limitations of the integration

You might not be the right fit if:

• You're not ready to operate at the pace and ambiguity of a Series A company

• You work better alone than in close collaboration with customers, fellow engineers, and deployment teams

• You're not comfortable owning high-risk actions — building the guardrails upfront, and having a clear plan for when things go wrong anyway

• You see integrations as a support function. We view them as a core part of how customers realize value from our platform.

Nice to have:

• Experience with healthcare systems — EHR platforms (Epic, Cerner), workforce management systems (UKG, Workday, Kronos), or adjacent healthcare data pipelines

• Experience with healthcare systems

• Experience working with Effect

If these problems resonate, we want to hear from you — regardless of how cleanly your background maps to what's above.