Firmware Test Engineer

Job description

**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. ### **Role Overview** 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. ### **Why This Role Exists** 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. ### Responsibilities - Test the functional behavior of device firmware on real hardware - Run devices in continuous loops and long-duration tests to validate stability - Test firmware behavior across resets, power cycles, and firmware upgrades - Identify failures, inconsistencies, and regressions in firmware behavior - Report issues clearly and work closely with firmware engineers to debug and resolve them - Capture, analyze, and interpret device logs and test outputs - Build and maintain hardware-in-the-loop (HIL) test setups - Contribute to device CI/CD pipelines - Improve test coverage, reliability, and execution time - Take ownership of specific test areas or workflows ### Requirements - 2-3 years of experience in firmware, embedded systems, or a related field - Basic understanding of embedded systems and firmware behavior - Ability to work hands-on with hardware systems - Programming experience in Python (for tests and tooling) - Basic familiarity with C or C++ to understand firmware behavior and logs - Experience working with UART/USB/BLE or similar device interfaces - Experience working in a Linux development environment - Ability to analyze logs and identify abnormal or unexpected behavior - Basic knowledge of Git or version control systems - Strong curiosity and a willingness to learn ### Who Should Apply - Engineers with 2+ years of firmware or embedded experience - Engineers who enjoy breaking systems to understand them - Firmware engineers interested in testing, automation, and reliability - Candidates who like working with real hardware, not just simulations ### Good to Have - Understanding of black-box and white-box testing for firmware - Ability to design tests based on: - External behavior and interfaces (black-box) - Firmware internals, state transitions, and logs (white-box) - Familiarity with structured and unstructured logging - Exposure to RTOS-based systems (Zephyr, FreeRTOS, or similar) - Familiarity with firmware upgrade or OTA/DFU workflows - Experience with or interest in hardware-in-the-loop (HIL) testing - Exposure to CI/CD pipelines for embedded or firmware projects - Experience running long-duration, loop-based, or stress tests