Robotics Engineer (Firmware & Hardware)

Full-time · 1–3 years experience

Location: Bangalore

This is a full-stack embedded role — you will grow into owning the platform from PCB to writing the firmware along with designing, bringing up, and validating the hardware it runs on.

This is a full-stack electronics role weighted towards hardware. You will grow into owning the controller board from schematic and layout, through fabrication and bring-up, to the wiring and grounding that ties the robot together — and write the firmware that runs on it.

1. Firmware

What you'll do

● Design and maintain firmware in C on a real-time OS for 32-bit ARM Cortex-M microcontrollers: task architecture, inter-task communication, and interrupt-driven, DMA-based peripheral drivers.

● Develop drivers for a variety of modules, sensors, and field devices — working from the datasheet over interfaces such as SPI, I²C, UART, GPIO, CAN/CAN-FD, and RS-485 (Modbus RTU).

● Develop and maintain communication between the microcontroller and an on-board computer over serial and Ethernet links, using a DDS-based middleware protocol.

● Contribute to the design of a mixed-signal controller PCB — schematic review, component selection, BOM and layout work (Fusion 360 or KiCad).

● Bring up and validate controller boards: rail checks, bus signal integrity on the scope and root-causing board-level defects.

● Maintain firmware and hardware documentation: design notes, interface specifications, BOMs, test points, bring-up reports, and change history.

Must have

● B.E./B.Tech/M.E./M.Tech in Electronics, Electrical, Computer Engineering or equivalent.

● Strong embedded C (C11) on 32-bit MCUs; comfortable with memory-mapped peripherals, linker scripts and debugging hard faults.

● Hands-on RTOS experience (FreeRTOS or similar): tasks, queues, semaphores, priorities, and diagnosing concurrency issues such as priority inversion and races.

● Experience with at least two or more of the given: CAN/CAN-FD, Modbus/RS-485, UART, DMA, Ethernet/LwIP, SPI/I²C.

● Experience with a major MCU vendor ecosystem (e.g.,



Infineon PSOC Creator, STM32CubeIDE or similar): HAL-level drivers, vendor configuration tools, SWD/JTAG debugging and build process.

● Sound knowledge of PCB design fundamentals: component selection and footprints, decoupling, grounding and return paths, and routing practices.

● Fluency with lab instruments — oscilloscope, logic analyzer, power supplies, electronic load — and the habit of verifying on the wire, not just in code.

● Version control discipline (Git) and clear documentation of designs, development reports, and defects.

Valuable to have but not mandatory

● Hands-on board bring-up: verifying power rails, clocks, and communication interfaces on first prototypes, and root-causing board-level defects.

● Robotics, AGV/AMR, automotive, or industrial automation background.

● Power supply design experience for battery-powered systems: DC-DC converter selection and integration, input protection, and power budgeting across logic and actuator rails.

● Robotics middleware experience: ROS 2 and/or resource-constrained middleware clients on MCUs.

● CANopen protocol knowledge (object dictionary, SDO/PDO, drive profiles such as CiA 402).

● Working knowledge of EMI/EMC fundamentals.

2. Hardware

What you'll do

● Design mixed-signal controller PCBs: power tree, component selection, schematic capture and design review (Fusion 360 or KiCad).

● Lay out multilayer boards: stackup, placement, decoupling, ground and return paths, and routing of noise-sensitive nets.

● Take boards through fabrication and assembly: fab outputs (Gerbers, drill, pick-and-place), BOM management, and coordinating with PCB vendors.

● Bring up and validate boards: rail and clock checks, bus signals on the scope,



load and thermal checks, and root-causing board-level defects.

● Write firmware in C on 32-bit ARM Cortex-M microcontrollers: bring-up and test code for new boards, and drivers for sensors and field devices.

● Plan system-level electrical integration: connectors and wiring harnesses, cabling and termination, fusing, and grounding scheme.

● Maintain hardware documentation: schematics, BOMs, test points, bring-up reports, wiring diagrams and change history.

Must have

● B.E./B.Tech/M.E./M.Tech in Electronics, Electrical, Computer Engineering or equivalent.

● Hands-on PCB design: schematic capture and multilayer layout in KiCad, Fusion 360, Altium or similar.

● PCB fundamentals: component selection and footprints, following the layout guidance in a datasheet, decoupling, grounding and return paths, and routing practices.

● Hardware side of digital interfaces — SPI, I²C, UART, GPIO, CAN/CAN-FD, RS-485, Ethernet — transceivers, termination and biasing.

● Working embedded C on 32-bit MCUs: able to bring up a board or set up configurations in a vendor ecosystem (STM32CubeIDE, Infineon PSOC Creator or similar), write or modify HAL-level drivers, and debug over SWD/JTAG.

● Fluency with lab instruments — oscilloscope, logic analyzer, power supply, electronic load, multimeter — and the habit of verifying on the wire, not just in the schematic.

● Comfortable with hand soldering, rework and probing on prototype boards.

● Version control discipline (Git) and clear documentation of designs, reports and defects.

Good to have

● Robotics, AGV/AMR, automotive, or industrial automation background.

● Battery-powered systems: pack integration, BMS interfacing, and high-current layout.

● PCB design and IEC standards, and EMI/EMC fundamentals.

● Signal integrity and thermal analysis, including simulation where it helps.

● Designing test jigs and fixtures for board validation and production testing.

● Exposure to RTOS-based firmware or robotics middleware (FreeRTOS, ROS 2).

📌 Robotics Engineer (Firmware+Hardware) (Bengaluru)
🏢 NMTronics India
📍 Bengaluru