Get more replies from employers
Send a job-specific resume in minutes.
Dozee Health AI in Bengaluru invites a Firmware Test Engineer with 2-3 years of hands-on experience in firmware or embedded systems. The role focuses on testing device functionality on real hardware, running long loops, and investigating failures to understand causes, not just what broke.
You will collaborate with firmware engineers, grow into test automation, HIL setups, and firmware CI/CD pipelines, contributing to reliability and observability of Dozee devices.
Overview: Dozee Health AI is a pioneer in Contactless Remote Patient Monitoring (RPM), proven to drive transformation at scale. Headquartered in Bengaluru, India, Dozee has emerged as India s no. 1 RPM Company.
We are seeking visionary individuals to help us in this very exciting journey. As a part of our dynamic team, you ll have the opportunity to collaborate with top healthcare providers in the country, applying AI-powered RPM solutions to tackle some of the most pressing challenges in healthcare - enhancing staff efficiency, improving patient outcomes, and pioneering the next generation of care models.
We are looking for a Firmware Test Engineer with 2-3 years of hands-on experience in firmware or embedded systems, who is passionate about understanding how devices behave in the real world. This role is ideal for engineers who enjoy working with real hardware, running systems in long loops, and investigating failures to understand not just what broke, but why.
You will work closely with firmware engineers to test device functionality, identify regressions, and improve system reliability. Over time, you will grow into building test automation, hardware-in-the-loop (HIL) setups, and firmware CI/CD pipelines.
If you are a firmware engineer-or come from a related embedded background-and are curious, motivated, and eager to expand your skill set into testing, automation, and reliability engineering, you are welcome to apply.
As our devices and firmware scale, informal or manual testing is no longer sufficient. Devices must behave correctly not only in ideal conditions, but also across resets, power cycles, degraded communication, and long-running field scenarios.
This role exists to ensure that firmware failures are found early, in the lab-not in the field. By investing in firmware test engineering, we aim to improve observability, reduce deployment risk, and increase confidence in every firmware release.