Senior Firmware Engineer, Platform
Neros Technologies
<p><strong>Who we are</strong></p> <p>Neros is a defense technology company rebuilding America’s drone industrial base. We design and manufacture high-performance unmanned systems that are tested in combat, iterated at startup speed, and built at massive scale. Our team culture is fast, hands-on, and obsessed with closing the gap between design and deployment.</p> <p>As drones transform the character of warfare, Neros is delivering the systems the West needs to compete on the modern battlefield and deter the adversaries of democracy. We’re hiring engineers, operators, and builders who want to move fast, take on extreme ownership, and get capability into the hands of warfighters in months, not years.</p> <p><strong>What you will be doing</strong></p> <p>Neros builds first-person-view drones for the modern battlefield. As a Senior Firmware Engineer on the Platform team, you will own the common runtime, libraries, SDK, and build system that our flight, ground-station, and autonomy software teams build on — across microcontroller and Linux targets alike. Your customers are other engineers, and the hardest problems in this space are the ones that surface where their code meets the platform.</p> <p><strong>Responsibilities</strong></p> <ul> <li>Own the common runtime and libraries every firmware team consumes — logging, telemetry, IPC, configuration — on MCU-based systems and Linux targets</li> <li>Own the build system and cross-compile toolchain: fast, reproducible, hermetic builds across every target we ship, and the SDK other teams consume</li> <li>Design and maintain the interfaces other teams build on, keeping them stable as the platform evolves underneath</li> <li>Solve the hard, ambiguous problems that surface where the platform meets its consumer teams</li> <li>Drive resource trade-offs — compute, memory, bandwidth — when subsystems compete for the same budget</li> <li>Raise the firmware engineering bar through patterns, code review, and mentoring</li> </ul> <p><strong>You should have the following</strong></p> <ul> <li>Mastery of embedded C on shipped products, with fluency across both MCU/RTOS and embedded Linux environments</li> <li>Have built platform code that other engineers depended on — libraries, SDKs, or protocols consumed by multiple teams — and kept them stable through change</li> <li>Hands-on ownership of an embedded build system (e.g. Bazel) — cross-compilation across multiple targets, dependency management, and build reproducibility</li> <li>Track record of owning problems that spanned team or subsystem boundaries and driving them to shipped resolution</li> <li>Strong resource-constrained design judgment — compute, memory, and bandwidth trade-offs on real hardware</li> <li>Debugging mastery — a history of cracking the bugs others gave up on</li> <li>Hands-on: you still ship code, and your technical influence comes from the work</li> </ul> <p><strong>Nice to have</strong></p> <ul> <li>Bazel specifically, especially for embedded/cross-compiled targets — or migrating a firmware org onto it</li> <li>Embedded Linux platform internals — kernel, BSPs, Yocto/Buildroot — alongside MCU work</li> <li>Flight-stack experience — Betaflight, PX4, or similar</li> <li>DSP, comms, or RF-adjacent firmware</li> <li>Visible open-source systems work</li> <li>You fly — FPV, RC, or drones generally</li> </ul> <p><strong>US Salary Range</strong></p> <p>$195,000 – $273,000 USD</p> <p>The salary range for this role is an estimate based on a wide range of compensation factors, inclusi