Our kiosks screen 65+ parameters in ten minutes. The firmware you write is what makes the sensors, the printer and the cloud agree on what happened during a session.
What the work looks like
You will own drivers end to end - reading a medical-grade instrument over UART or I2C, handling the failure cases a clinic will actually hit, and getting the reading into the report before the patient stands up.
What you will do
Own device drivers for diagnostic instruments across the kiosk range
Take a sensor from datasheet to a reading that a doctor will sign off on
Work with the QA team on IEC 62304 documentation for every release
Debug in the field - the interesting failures happen in clinics, not on your desk
What we are looking for
Strong C or C++ on embedded Linux or an RTOS
Comfortable with UART, I2C, SPI and a logic analyser
Have shipped firmware that someone outside your team depended on
Bonus: medical devices, or anything else with a regulator attached