> Markdown version of [/jobs/ext/4760460-embedded-systems-software-engineer](https://www.wearedevelopers.com/jobs/ext/4760460-embedded-systems-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Embedded Systems Software Engineer - **Company:** LUMIJES TECHNOLOGIES CORPORATION - **Location:** Gainesville, FL, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Board Bringup, Altium Designer, ARM Architecture, Automation of Tests, Computer Engineering, Software Debugging, Device Drivers, Electronic Design Automation, Linux on Embedded Systems, Middleware, Ethernet, EtherCAT, Firmware, FreeRTOS, Joint Test Action (IEEE Standards), Python (Programming Language), Motion Planning, Real-Time Operating Systems, Data Streaming, Universal Asynchronous Receiver/Transmitter, USB, Data Logging, Scripting, Serial Peripheral Interface, PIC Microcontroller, Mobile Robots, Isaac Sim, Bare Metal, Real Time Data, U-Boot, NVIDIA Jetson, Data Pipelines - **Published:** November 17, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=b9aff52d10ca1d4b ## About the Role We want engineers who are just as comfortable with a scope probe in hand as they are in a debugger, and who do not wait for someone else to tell them where the problem is. * 5+ years of professional embedded systems experience, with hardware you have helped bring up and ship, not just support. * Strong C and C++ for firmware and drivers, plus working Python for test automation and scripting. * Microcontrollers and RTOS: ARM Cortex-M, STM32, ESP32, or similar, using bare-metal or RTOS environments such as FreeRTOS, Zephyr, or ThreadX. * Embedded Linux: kernel configuration, device trees, U-Boot, and board support packages (BSPs). * Lab and debugging tools: hands-on with oscilloscopes, logic analyzers, protocol analyzers, and JTAG/SWD debuggers. * Networking and busses: practical implementation of serial and field busses like CAN, EtherCAT, I2C, and SPI. * B.S., M.S., or Ph.D. in Computer Engineering, Electrical Engineering, Robotics, or a related field. NICE TO HAVE: * ROS/ROS 2 middleware and robotics data streaming experience (TF, sensor topics). * Familiarity with robot simulation and motion planning tools such as NVIDIA Isaac Sim, MuJoCo, MoveIt, or cuRobo. * PCB design experience in Altium Designer or KiCad, enough to suggest schematic fixes with confidence. * Knowledge of motor control (PID, encoder feedback) and power electronics. * A background deploying mobile robots, drones, or autonomous systems into unstructured, real-world environments. ## Description You will own the foundation the rest of the platform runs on. Your work decides whether the system is fast, deterministic, and safe enough to sit next to a patient. * Board bring-up and validation: bring up, test, and debug new PCBs, read schematics and layouts, and use lab tools to isolate hardware faults from software faults. * Firmware and drivers: write low-level firmware for MCUs on bare-metal or RTOS, and develop device drivers for embedded Linux platforms and SOMs such as NVIDIA Jetson and AMD Kria. * Communication stacks: implement and tune real-time data protocols across the robot, including CAN/CAN FD, EtherCAT, I2C, SPI, UART, USB, and Ethernet. * Sensor and actuator integration: connect cameras (GMSL, MIPI CSI-2), LiDARs, IMUs, encoders, and motor controllers with synchronized data pipelines and deterministic timing. * Diagnostics and safety: build watchdogs, safe-stop routines, telemetry logging, and hardware-in-the-loop (HIL) test fixtures, because field reliability is not optional in a clinical device. * Cross-functional collaboration: work side by side with electrical, mechanical, controls, and robotics software (ROS/ROS 2) engineers to balance power, thermal, and bandwidth constraints., We move fast by design. We do not speculate; we prototype, test, and learn. There is no approval committee reviewing your technical decisions and no six-month roadmap insulating you from accountability. You own your boards, your firmware, and your outcomes. The people who love working here are the ones who cannot leave a flaky signal alone until they know exactly why it is happening. They find meaning in work that is genuinely difficult and genuinely consequential, and they get uncomfortable when things slow down for reasons they can control.