Senior Engineering Director - IoMT Operations

Job Description Summary

GE HealthCare’s Patient Care Solutions business is building a unified Internet of Medical Things (IoMT) Platform that spans device, edge, and cloud to enable hospitals and caregivers to deliver the best care across the critical care continuum. The IoMT Platform provides secure, scalable connectivity, data and computing solutions that manages mission critical workflows across PCS — from bedside monitors to cloud analytics — into one harmonious solution for customers and developers.

Role Summary
The Director, IoMT Operations is a senior leadership role responsible for platform governance, release management, delivery coordination, and operational excellence across the IoMT Platform organization. The director defines, implements, and continuously improves the operating model that enables a multi‑product platform to deliver predictable, high‑quality releases on a time‑boxed cadence.
This is a high-visibility position that sits at the intersection of engineering, product management, and program management — ensuring the IoMT Platform operates as a mature platform product with transparent prioritization, coordinated releases, and reliable delivery commitments. The role scales through mentoring and enabling experienced managers and does not directly run team-level execution.
This is a unique opportunity to shape the operating model from the ground up. The newly formed IoMT organization is transitioning to a platform operating model, and this director will play a central role in establishing the governance, release, and delivery processes that will define how the platform operates — while ensuring continued delivery of in-flight programs.

Job Description

Key Responsibilities
 

Platform Governance & Release Management
•    Partner with IoMT Product and Program Management to define and champion the portfolio-level governance model that reconciles priorities across multiple consuming PCS product lines into a unified platform roadmap.
•    Set the vision for a single, time-boxed release train that incrementally delivers platform capabilities and maintenance on a regular cadence, independent of any single product’s timeline. The Program & Agile Project Management team manages the day-to-day execution of this cadence.
•    Ensure cross-program prioritization processes are in place that balance shared infrastructure investments with program-specific feature needs, making explicit tradeoff decisions visible to all stakeholders.
•    Co‑establish, with IoMT Engineering leadership, the platform-level capacity allocation model; Program Management maintains operational visibility and reporting.
•    Establish clear decision rights and escalation paths between IoMT Platform ownership and product team ownership, and serve as the senior escalation point for cross-program tradeoff decisions.
•    Ensure release governance, support models, and ownership boundaries reflect the fact that the IoMT Platform is a deployed product installed and operated at customer sites as well as in the cloud.
 

Delivery Coordination & Program Execution
•    Own the process of turning the prioritized platform roadmap into an executable delivery plan across IoMT Platform capability areas.
•    In collaboration with the IoMT Systems Engineering Leader, ensure discovery and definition artifacts (requirements, high-level design, risk management plans, test plans) are planned, timely, and complete for release entry—Systems Engineering owns content; this role owns readiness and schedule integrity.
•    Ensure the organization maintains compliance with NPI program tollgates (concept, definition/planning, development, verification/validation, design transfer, pilot, full release).
•    Support the establishment of the IoMT Platform as an independent product under its own NPI program and dedicated QMS design history file, separate from any individual consuming product.
•    Maintain visibility into current status of development activities, high-level integration points, and key portfolio-level dependencies through the program management team.
•    Lead the Bangalore-based delivery team (systems engineers, product owners, project managers) through a direct-report manager.
 

Build, Release & Verification Engineering
•    Provide strategic direction for build/test/deploy pipelines across both edge and cloud deployment targets. The Platform Build & Release Engineering team owns pipeline implementation and operations, while the Verification & Reliability team owns test strategy and execution.
•    Set quality and reliability standards for platform releases, holding the Verification & Reliability team accountable for platform-level integration testing and release quality assurance.
•    Guide the evolution of CI/CD capabilities toward modern, automated pipelines that reduce manual steps and accelerate delivery — contributing to the organization’s goal of AWS-comparable developer experience.
•    Ensure automated build, test, security scanning, and conformance testing are established as standard release gates.
•    Lead the Build, Release, Verification & Reliability teams through direct-report manager.
 

Installed Base (L4) Support
•    Ensure the Platform Support Engineering team delivers effective L4 engineering support for the IoMT Platform, providing deep technical escalation support for field issues.
•    Hold the team accountable for maintaining operational runbooks and diagnostic capabilities aligned to ownership boundaries.
•    Drive a culture of continuous improvement of platform reliability based on field feedback and incident patterns, ensuring learnings flow back into platform development.
•    Lead the L4 support function through a direct-report manager.
 

AI, Operational Excellence & Continuous Improvement
•    Champion the adoption of AI-assisted workflows across delivery management, release coordination, testing, and operational support to accelerate throughput and reduce manual effort across all three teams.
•    Make AI adoption a competitive advantage — use it to reduce duplication, eliminate process noise, and redeploy engineering capacity toward high-value platform work.
•    Ensure the organization instruments and communicates platform delivery metrics: cycle time, release predictability, defect escape rates, and reliability improvements.
 

Required Qualifications
•    Bachelor’s degree in Engineering, Computer Science, or related technical field; advanced degree preferred.
•    10+ years of experience in software engineering, platform operations, or technical program management, with at least 5 years in a leadership role.
•    Demonstrated experience operating platform organizations that serve multiple product lines with competing priorities and shared infrastructure.
•    Strong track record of establishing and running release governance processes, including time-boxed release trains and portfolio-level prioritization.
•    Experience with Agile methodologies and Agile release trains in a multi-team, multi-product environment.
•    Experience with both edge/on-premise and cloud deployment models, including CI/CD pipeline design and lifecycle management.
•    Familiarity with regulated product development environments (QMS, NPI tollgates, design history files) — medical device or life-critical systems experience strongly preferred.
•    Experience managing L4/L3 engineering support functions and driving operational reliability improvements.
 

Preferred Qualifications
•    Experience in healthcare technology, medical devices, or IoMT/IoT platforms.
•    Knowledge of healthcare interoperability standards (IHE, HL7, SDC, FHIR).
•    Experience with Kubernetes-based edge compute platforms and container orchestration in hybrid (edge + cloud) environments.
•    Familiarity with platform engineering practices: contract-first APIs, SLOs, observability, and operational dashboards.
•    Track record of adopting AI/ML tools to improve engineering productivity and delivery speed.
 

Location & Travel
•    Bangalore, India
•    Occasional travel to PCS engineering sites and key partner locations expected.
 

Strategic Outcomes
•    The IoMT Platform delivers releases on a predictable, time-boxed cadence with clear content commitments honored.
•    Portfolio-level prioritization is transparent — stakeholders across product lines understand what is being delivered, what is deferred, and why.
•    Build and release pipelines are automated, fast, and reliable for both edge and cloud targets.
•    Platform verification catches integration issues before they reach customers.
•    L4 support resolves field escalations efficiently while providing feedback to the organization on how to improve quality and diagnosability in the field.
•    The team is engaged, growing, and retaining talent across a multi-site organization.
•    Managers demonstrably scale capacity and develop successors.
 

Additional Information