Sr. Principal Software Engineer, Software Architect & AI-Video Tech Lead
Leading the AI-video software behind Touch Surgeryâ„¢ Aide, Medtronic's real-time AI compute platform for the operating room, where several AI applications run side by side during surgery.
Impact
- Led the AI-video software behind Touch Surgeryâ„¢ Aide, Medtronic's real-time AI compute platform for the operating room.
- Achieved FDA 510(k) clearance for Instrument Exit Point, Aide's first AI app, marking where Hugoâ„¢ instruments exit the view.
- Architected GPU sharing for multiple AI apps with strict medical/non-medical isolation and sub-frame overlay latency.
- Shaped project-wide practices in architecture, versioning, doc generation, integration testing, observability, C++ and CI.
- Acted as the AI-video point of contact between the ML, Systems, DevOps, Cloud, Quality, Regulatory and UI teams.
- Built the C++ runtime (AI manager, scheduler, TensorRT inference, recording) plus IPC, visualization and telemetry libraries.
- Introduced an agentic-AI workspace used daily for development, documentation, compliance audits and FMEA review.
- Mentored 5+ engineers through pairing and design reviews, raising delivery pace and design quality.
Role notes â–¸
I lead the AI-video software behind Touch Surgeryâ„¢ Aide, Medtronic's real-time AI compute platform for the operating room. Earlier Touch Surgeryâ„¢ products mostly analysed surgical video after the operation; Aide runs AI while the procedure is happening. Its first application, Instrument Exit Point, works with the Hugoâ„¢ robotic-assisted surgery system: when an instrument leaves the camera's view, it marks the spot where it was last seen. It has FDA 510(k) clearance.
I took the platform from prototype to release as AI-Video Technical Lead. I'm also one of the software architects on the project, helping shape the decisions that cut across teams and components: software architecture, versioning, generated documentation, automated integration tests, observability (logging and data recording), C++ best practices and CI.
The design comes down to three goals. Isolation: several AI applications run side by side without getting in each other's way. Segregation: regulated medical functions stay cleanly separated from everything else, in line with IEC 62304 (the medical-device software standard). Performance: AI guidance appears live on the surgical video, with latency kept as low as possible so it keeps pace with the surgeon's movements. Getting there meant a modular design where each component has one job, efficient video transport between them, and a layer that coordinates the AI applications, keeps the system within its limits and handles failures gracefully.
The job goes well beyond the runtime: dev containers shared by engineers and CI, a modular build system for feature-gated releases across product variants, shared platform libraries, hardware-in-the-loop testing, and documentation that feeds straight into FDA submissions. Day to day, I'm the technical anchor across ML, Systems, Quality, Regulatory and UI, from the first architecture sketch to regulatory sign-off.
Show, Don't Tell