Interim Chief Information Officer — Medtech Quality Integration

The mandate

Post-acquisition testing found that device history, complaint and field-service records cannot be traced consistently across the two ERP and quality environments, and the selected integration CIO withdrew. The group must integrate operational systems without breaking validated processes or weakening device traceability.

The interim must start within four weeks for a fixed fourteen-month term through design, controlled migration and the first post-cutover quality audit. A permanent CIO search begins after design qualification, with an eight-week transition built into the closing period.

Handover is complete when priority device families have end-to-end record traceability, validated systems pass the post-cutover audit, cyber access is recertified, critical interfaces operate within tolerance for ninety days, and the successor signs the next integration release.

The interim may choose integration sequencing, stop migrations, allocate ₹20 crore within the approved programme and appoint temporary validation specialists. Core ERP replacement, capital above ₹40 crore, permanent executive hires, changes to regulated retention and any cutover with unresolved critical quality risk require board approval.

Product design, manufacturing footprint and commercial distribution integration are outside scope. Technology must enable and evidence approved quality processes without taking over regulatory product accountability.

Why this seat is open

The planned integration leader withdrew just as record incompatibilities became visible. Legacy CIO reports are tied to the systems and migration assumptions they own. An interim executive can arbitrate the validated path and leave the permanent CIO a controlled integration programme.

What you will own

• Define the authoritative record path for device history, complaints, service, corrective action and regulatory reporting.
• Decide migration waves by quality risk, data readiness, operational dependency and reversibility.
• Approve validation plans and reject tests that do not reflect production roles, devices and exception conditions.
• Reconcile migrated master and transaction records to source totals and sampled device-level traceability.
• Remove inherited access conflicts through role redesign, recertification and monitored temporary privileges.
• Pass the first post-cutover quality audit with all critical evidence indexed and reproducible.
• Transfer system decisions, validation artefacts, cyber exceptions, supplier obligations and remaining waves to the permanent CIO.

Candidate qualifications

• Held CIO, enterprise applications chief or technology integration director in medical devices, life sciences or regulated manufacturing.
• Integrated ERP and quality systems while preserving validated process and product traceability.
• Led computer-system validation, data migration and access-control remediation under external audit.
• Made cutover-stop decisions when operational pressure conflicted with quality evidence.
• Directed enterprise technology teams across manufacturing, service and R&D sites.
• Understands device history, complaint, corrective-action and regulated-record requirements.

Non-negotiables

• Available for Pune leadership within four weeks and frequent Chennai site work.
• No current relationship with the ERP integrator or validation assurance provider.
• Will not migrate a regulated record set without reconciled traceability.
• Must have led a live validated-system cutover.

1. 49 words maximum. Confirm availability and disclose any ERP, validation or medtech conflict.
2. 49 words maximum. Describe a validated-system migration you stopped and the missing evidence.
3. 49 words maximum. How would you test device-level traceability after ERP cutover?