Idara Uko | Pacemakers, Principal Engineers, & Product Fit

Being an Engineer · 3 Jun 2022 · 47m · Episode 22

What this episode covers

Idara Uko, Director of Software Operations at Medtronic, explains the engineering behind implantable pacemakers and defibrillators, detailing how firmware uses accelerometers and heart signals to regulate heart rate based on patient activity. He contrasts the strict regulatory environment of Class 3 medical devices with consumer electronics, emphasizing the need for rigorous validation to ensure the 'right product' is built, not just built correctly. Uko also discusses the career progression from entry-level to principal engineer and advises companies on structuring software teams using Agile and Scrum methodologies to serve customer needs effectively.

Other shows on the same ground, closest first.

  • The Pragmatic Embedded Podcast · 48m

    Weronika Michaluk on Medical Devices development

    Weronika Michaluk, Software as a Medical Device Practice Lead at HTD Health, explains how her company bridges firmware and software teams through shared backlogs, daily stand-ups, and mutual technical leads. She details the implementation of a compliant agile process that integrates tools like Jira, GitHub, and Greenlight Guru to manage requirements and version control without sacrificing regulatory compliance. Michaluk highlights the importance of aligning on versioning schemes and documentation standards to prevent bottlenecks and ensure that change orders are efficient rather than just bureaucratic friction. The conversation also covers the evolving understanding of agile methodologies among medical device clients, ranging from technical startups to non-technical founders.

  • The Pragmatic Embedded Podcast · 51m

    Closing the gap between Regulatory and Development with Milton Yarberry

    Milton Yarberry, Director of Medical Programs at Integrated Computer Solutions (ICS), discusses bridging the gap between engineering and regulatory teams in medical device development. He identifies key friction points such as process lag, software stacking, and the cognitive burden on developers, arguing that regulatory processes should be viewed as support rather than compliance burdens. Yarberry advocates for a 'regulatory concierge' model where regulatory staff handle administrative overhead, allowing engineers to focus on building safe and effective products through incremental, value-driven processes.

  • Embedded.fm · 1h 09m

    67: Software for Things That Can Kill People

    Hosts Chris White and Elecia White discuss the rigorous regulatory processes for safety-critical software, drawing on their experiences with the FAA (DO-178B) and FDA (510k, PMA) for medical devices and avionics. They explain how hazard analysis determines certification levels, the necessity of extensive documentation and traceability, and the tension between agile development and waterfall compliance. The conversation highlights the ethical responsibility of engineers to push back against unsafe deadlines, the use of hardware compartmentalization (FPGAs, voting systems) to ensure safety, and the legal liabilities associated with product failures.

  • Embedded.fm · 1h 03m

    53: Being a Grownup Engineer

    Jack Ganssle, author of 'The Art of Designing Embedded Systems' and long-time embedded industry expert, argues that firmware engineers must adopt disciplined engineering practices rather than relying on 'heroic' hacking. He discusses the necessity of requirements gathering, design reviews, code inspections, and rigorous testing to ensure safety and reliability, citing the Toyota unintended acceleration case as a failure of process. Ganssle advocates for measuring metrics like bug rates and lines of code to benchmark performance, and critiques the misuse of Linux in deeply embedded systems and the confusion between the maker movement and professional engineering.

  • The Pragmatic Embedded Podcast · 37m

    Rapid Prototyping for Medical Devices with Ross Dehmoobed

    Ross Dehmoobed, VP of software and platforms at Veranex, explains how his company applies agile methodologies to medical device development. He details the use of 'Fusion Core' libraries and custom hardware modules to enable rapid prototyping, allowing teams to demonstrate functional breadboards and software features within the first two weeks. Dehmoobed emphasizes that while planning and regulatory pathway definition (such as 510(k) or de novo) require upfront waterfall-style rigor, the execution phase benefits from short sprints, off-target unit testing, and continuous customer feedback to maintain quality and speed.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by Being an Engineer. The episode itself belongs to its publisher.