Principal Systems Engineer; CAS

We anticipate the application window for this opening will close on - 13 Nov 2026 Careers that change lives start here. Medtronic is a global leader in healthcare technology with a Mission to alleviate pain, restore health, and extend life. Our 95,000 employees work across more than 150 countries to put patients first — developing innovative medical technologies that improve the lives of 72+ million patients each year.

Your unique talents will help shape the future of healthcare while building a career grounded in purpose, growth, and impact.

The Cardiac Ablation Solutions business develops cardiac mapping and ablation technologies used to treat patients with abnormal heart rhythms. The Principal Systems Engineer will serve as a recognized technical leader, connecting customer and clinical needs with disciplined systems engineering across capital equipment, software, disposables, catheters, sheaths, accessories, and their interfaces. This role operates across the full product lifecycle, from early concept and architecture through design transfer, commercialization, post-market support, and product evolution.

The engineer will influence cross-functional decisions, resolve ambiguous system-level challenges, mentor technical teams, and strengthen systems engineering practices across CAS.

At Medtronic, we bring bold ideas forward with speed and decisiveness to put patients first in everything we do.

In-person exchanges are invaluable to our work.

We are working onsite 4 days per week as part of our commitment to fostering a culture of professional growth and cross-functional collaboration as we work together to engineer the extraordinary.

This role will require less than 10% of travel to enhance collaboration and ensure successful completion of projects.

This position will be located in Mounds View, MN.

• Lead systems engineering activities for complex, multidisciplinary medical-device programs and significant product changes.

• Partner with Marketing, Clinical, Human Factors, Medical Safety, and field-facing teams to translate stakeholder needs, use cases, and use environments into clear system-level design inputs.

• Define, evaluate, and maintain system architecture, functional decomposition, interfaces, operating modes, performance budgets, and key design trade-offs across hardware, software, firmware, disposables, and accessories.

• Lead development, review, allocation, and lifecycle management of stakeholder, system, subsystem, interface, and performance requirements, ensuring clarity, testability, consistency, and end-to-end traceability.

• Integrate product safety, usability, reliability, cybersecurity, and software risk considerations into system design; ensure risk controls are appropriately implemented, traced, and verified.

• Establish system verification and validation strategies, including methods, acceptance criteria, test architecture, evidence plans, and resolution of system-level anomalies.

• Plan and lead architecture reviews, requirements reviews, design reviews, trade studies, and technical decision forums. Communicate conclusions, residual risks, and recommendations to project and functional leadership.

• Lead cross-functional root-cause investigations and system-level troubleshooting for complex design, integration, field, manufacturing, supplier, and product-performance issues.

• Support design changes, component obsolescence, CAPA and corrective actions, regulatory commitments, supplier changes, product enhancements, and continuity-of-supply initiatives.

• Serve as a technical authority who influences without direct authority, aligns global teams, and helps programs make balanced decisions across patient safety, quality, performance, cost, schedule, manufacturability, and serviceability.

• Mentor systems engineers and partner disciplines; create reusable methods, templates, models, and lessons learned that improve predictability and technical excellence.

• Engage suppliers, consultants, laboratories, clinicians, and other external partners when specialized capabilities or system evidence are required.

• Stakeholder and system requirements, interface requirements, and traceability evidence
• System context, architecture, functional…