Avive Solutions
Firmware Engineer - IoT
About this role
Avive Solutions, a growth-stage medical device company, seeks an experienced Firmware Engineer to design and develop embedded firmware for innovative AED (Automated External Defibrillator) devices. You'll architect IoT-connected systems from concept through production, working on digital/analog peripherals, communication protocols, and hardware integration for life-saving cardiac response technology.
What you'll do
- Architect and implement embedded firmware for AED devices and connected systems
- Design embedded systems with digital, analog, and wireless communication capabilities
- Conduct testing, debugging, and validation of firmware from development through production
- Participate in PCBA-level hardware integration and system testing
- Collaborate on serial and wireless communication protocol implementation
- Support volume production and field deployment of medical devices
What they're looking for
- Embedded firmware development and architecture
- Digital and analog circuit design
- Serial communication protocols (UART, SPI, I2C)
- Wireless communication systems
- Hardware debugging and testing
- PCBA and electronics integration
- C/C++ or embedded programming languages
- Real-time embedded systems
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Avive Solutions
Avive develops innovative medical devices for cardiac arrest response, including IoT-connected AED (Automated External Defibrillator) systems. The company is hiring for integration engineers and firmware engineers to build and maintain critical system infrastructure and embedded firmware for their life-saving cardiac response technology.
View all jobs at Avive SolutionsLikely interview questions
- Can you walk us through a firmware project where you designed an embedded system from concept to volume production? What were the key challenges?
- Describe your experience with wireless communication protocols in IoT devices—which have you worked with and how did you handle connectivity issues?