Lead, Platform Software

Neros Technologies•Torrance, CA

About The Position

Neros builds the embedded software that powers our drones and ground systems. As a Lead, Platform Software Engineer, you will build and lead the team that owns our foundational embedded platform — the Linux distribution, kernel, bootloader, common runtime, and SDK that our flight, ground-station, and autonomy software teams build on. You will own the platform's roadmap, reliability, and engineering quality while growing and leading the team behind it and treating every other engineering team as your customer.

Requirements

Has led a software team as a hands-on manager — owning both people management and technical direction
Deep embedded-platform background: custom Linux (Yocto/Buildroot), kernel/BSPs, bootloaders, and the runtime/SDK layer other teams build on
Track record of running a platform or foundational-software team as a product — stable interfaces, versioning, and consumer teams who could depend on it
Strong judgment on build-vs-adopt, interface design, and resource trade-offs across an embedded system
Able to operate as the interface between the team and senior leadership — managing expectations upward and clearing execution blockers
Player-coach: still technically credible enough to review BSP/kernel/runtime code and make architecture calls

Nice To Haves

Experience building an embedded platform team from a small nucleus
MCU/RTOS platform work alongside embedded Linux
Bazel or comparable build-system leadership across cross-compiled targets
Real-time, safety-relevant, or mission-critical embedded platforms
Background bringing up new computer platforms from prototype to production

Responsibilities

Lead and grow the Platform Software engineering team, including hiring, mentorship, and performance management
Own the roadmap and delivery of the embedded platform — Linux distribution and BSPs, kernel and bootloader, common runtime and libraries, and the cross-compile toolchain and SDK
Run the platform as a product: keep the interfaces our flight, ground, and autonomy teams depend on stable, versioned, and evolving without breaking them
Make the hard architecture calls — build vs. adopt, interface design, and resource allocation across subsystems
Set and uphold engineering quality practices — code review, testing, and CI/CD — for foundational software
Stay hands-on: review platform code and own architecture, not just process