Firmware Engineer
Bytebeam · Bangalore, India
Bytebeam is hiring a Firmware Engineer to develop and test firmware for automotive telematics devices, working with the Firmware Tech Lead.
What you will do
- Write and test firmware in C/C++ for microcontroller-based telematics devices.
- Develop and integrate drivers and modules for peripherals such as cellular/LTE, GNSS, BLE, CAN/OBD, sensors, and storage.
- Implement communication over UART, SPI, I2C, CAN, and USB.
- Support board bring-up, peripheral validation, and hardware-software integration with the hardware team.
- Debug firmware issues using scopes, logic analyzers, and JTAG/SWD, and chase problems down to root cause.
- Write unit and on-target tests, and contribute to the firmware CI and build process.
- Participate in code reviews, follow the team's coding standards, and keep your code clean and well documented.
- Help triage and reproduce field issues and improve on-device logging and diagnostics.
What you need
- 1-3 years of hands-on embedded firmware development in C/C++ for microcontrollers.
- Solid fundamentals in microcontrollers, interrupts, memory, and at least one RTOS or bare-metal environment.
- Working knowledge of embedded communication interfaces: UART, SPI, I2C, and ideally CAN or USB.
- Comfortable reading schematics and datasheets and using basic lab tools.
- Cares about code quality: clean, readable, tested code and willingness to learn from code review.
- A debugging mindset and the persistence to get to root cause.
- B.E./B.Tech in ECE, EEE, CS, or related.
Good to have
- Exposure to automotive or telematics firmware.
- Familiarity with version control, CI, and static analysis.
- Awareness of automotive coding standards and functional safety basics.
- Some embedded Linux exposure in addition to MCU firmware.
- Use of AI/LLM coding tools as part of your workflow.
- Personal or academic projects on real hardware.
How to apply
- Tell us about an embedded project you built including hardware, your code, what broke, and how you figured out why.