Level 3 – Firmware Engineer

Role Overview

We are looking for a hands-on Level 3 Firmware Engineer with strong fundamentals in embedded systems and practical experience developing, debugging, and validating firmware for MCU-based products.

The engineer should be comfortable working close to the hardware, debugging peripheral-level issues, analyzing communication protocols, and independently bringing up and testing firmware on embedded platforms.

Key Responsibilities

- Develop, integrate, debug, and maintain embedded firmware for MCU-based products.
- Work closely with hardware engineers during board bring-up, peripheral validation, and debugging.
- Configure and use MCU peripherals such as timers, ADC, PWM, GPIO, UART, SPI, I²C, and watchdogs.
- Develop interrupt-driven firmware and understand interrupt priorities, timing, latency, and concurrency.
- Debug communication and peripheral-level issues using oscilloscopes, logic analyzers, multimeters, and other electronic test equipment.
- Analyze firmware and hardware interactions to identify root causes of failures.
- Perform unit-level, integration, and hardware-level testing.
- Write clean, modular, maintainable, and well-documented embedded C code.
- Participate in code reviews, firmware architecture discussions, debugging, and product validation.
- Work with cross-functional teams including hardware, system, testing, and manufacturing teams.
- Support production issues and provide root-cause analysis for field and manufacturing failures.

Required Technical Skills

Embedded C & MCU Fundamentals
- Strong programming skills in Embedded C.




- Good understanding of:

o Timers and counters o Interrupts and interrupt handling o GPIO o PWM o ADC fundamentals o Watchdog timers o DMA o Memory architecture and memory-mapped peripherals
- Positive understanding of real-time firmware concepts and timing constraints.

Communication Protocols

Strong fundamental understanding and hands-on experience with:
- UART
- SPI
- I²C The candidate should be able to understand protocol timing, signal behavior, configuration registers, and debug communication issues at the hardware level.

MCU Platforms

Hands-on experience with one or more of the following MCU families:
- STMicroelectronics STM32 – STM32F0/F1/F3/F4/G0/G4/L4/H5/H7
- Microchip/Atmel AVR – ATmega / ATtiny
- Renesas – RA / RX / RL78
- Texas Instruments – MSPM0 / MSP430 / C2000 / Tiva
- Other ARM Cortex-M based microcontrollers

Hardware Debugging & Test Equipment

Hands-on experience using:

- Logic analyzers
- Oscilloscopes
- Digital multimeters
- Programmable power supplies
- Electronic loads
- JTAG/SWD debuggers
- Protocol analyzers The engineer should be capable of independently using test equipment to investigate firmware, timing, communication,



and hardware-interface problems.

Good to Have

- Understanding or hands-on experience with FOC (Field-Oriented Control) algorithms.
- BLDC/PMSM motor-control firmware experience.
- RTOS experience such as FreeRTOS, Zephyr, or ThreadX.
- Experience with CAN / CAN-FD.
- Experience with RS-485 / Modbus.
- Experience developing scalable and reusable firmware platforms, including reusable drivers, HALs, and middleware.
- Experience migrating firmware or applications between different MCU platforms/architectures.
- Experience with bootloaders, OTA firmware updates, and firmware upgrade mechanisms.
- Experience with USB, Ethernet, or wireless communication protocols.
- Experience with Git and contemporary software development workflows.
- Understanding of embedded software testing and static analysis.

Expected Level of Independence A Level 3 Firmware Engineer should be able to:
- Take ownership of a firmware module from requirement through validation.
- Bring up MCU peripherals with limited supervision.
- Read MCU reference manuals and datasheets and configure peripherals independently.
- Debug firmware using both software debugging tools and physical measurements.
- Identify whether an issue is caused by firmware, hardware, timing, or communication, and systematically isolate the root cause.
- Develop reusable and maintainable firmware rather than tightly coupled product-specific code.
- Work independently on moderately complex firmware features while seeking architectural guidance when required.

📌 Firmware Engineer (Hyderabad)
🏢 Kryon Technology
📍 Hyderabad