
Principal Engineer, Embedded Systems
Palo Alto, CAFull-timeSeen 1mo agoStill listed 4 days ago
See where you stand before you apply. No sign-up to start.
You apply on the posting's application page, with no Olive account needed.
Watch jobs like this. New roles like this one near Palo Alto, CA, by email.
Don't just apply. Show up ready.
Olive works from this exact posting.
At a glance
Olive focuses on jobs in the United States, including remote roles you can work from there.
Requirements
Credentials this posting asks for.
Job overview
Edgerun seeks a Principal Engineer of Embedded Systems to lead firmware and control development for advanced powered exoskeletons used by soldiers. The role involves owning the full control stack, setting architecture standards, managing OTA updates, building data collection, hiring and leading engineers, and conducting field tests, all in a fast‑paced, in‑person environment in Palo Alto.
Skills & qualifications
Skills
Qualifications
Full job description
Edgerun's mission is to remove civilization-level physical constraints limiting the human body. We believe a future where humans keep pushing into the unknown is far better than one where we send machines in our place. That starts on the battlefield, doubling what a soldier can carry and how far they can carry it. Read more about our mission here. PRINCIPAL ENGINEER, EMBEDDED SYSTEMS As a Principal Engineer of Embedded Systems, you will be responsible for advancing technical boundaries of firmware and control for the world's most advanced powered exoskeleton systems, worn by soldiers in active combat. You will work with a talented team of accomplished engineers to develop the embedded software stack, including real-time motor control, gait detection, human intent inference, and sensor fusion. You should thrive in a fast-paced, dynamic environment where you adapt quickly, love to solve hard problems, and are confident enough to make the call and secure enough to take real pushback on it. This is a foundational role. Your architecture and decisions will define what this company builds for years to come. RESPONSIBILITIES
- Own the full control stack: FOC and current loop, torque control, joint control, the gait and assist algorithm, and user intent detection above it
- Set the architecture, interfaces, and standards the rest of the engineering team writes against
- Decide how the device behaves when something goes wrong: sensor faults, low battery, unexpected loads
- Own the update path: over-the-air firmware, rollback, and the telemetry link to the app
- Build the data collection that turns field use into design decisions
- Hire and lead the firmware engineers who build under you
- Run field tests and turn what you see there into changes to the system
BASIC QUALIFICATIONS
- Bachelor's degree in electrical engineering, computer engineering, computer science, or another engineering discipline
- 8+ years of embedded firmware experience, including ownership of a complete stack on hardware that shipped and was used by real people
- Proficiency in embedded C or C++ and real-time systems
- BLDC motor control at the loop level: FOC, current and torque control, and position, velocity, or impedance control
PREFERRED SKILLS AND EXPERIENCE
- You can name the MCU, the RTOS or bare metal design, the loop rates, and why you chose each
- Encoder processing, IMU and sensor fusion, high frequency control loops, and CAN
- Running learned models on a microcontroller: quantization, inference budgets, and keeping a network fed inside a hard real-time loop
- State machine or actor-based embedded architectures, built-in self test, and fault handling on hardware people depend on
- You understand how the physical product gets built, not only how it is programmed. You have specified parts, worked with suppliers, and know what manufacturing does to an electronics design
- You have set architecture other engineers wrote against, and you still write code yourself
- You have taken over someone else's system, including undocumented or inherited code, and made it yours
- Safety-critical or medical device firmware
- Debugging hardware you cannot physically touch, from logs alone
- Things you build outside work: motor controllers, robots, your own RTOS
HOW WE WORK
- Hardware on real operators in real field conditions within weeks of concept, not years
- Firmware updates ship over the air every one to two weeks
- Small team, one owner per category, nobody owning a slice of someone else's problem
ADDITIONAL REQUIREMENTS
- Full time and in person in Palo Alto
- Travel to field tests, including overseas
- Must be willing to work extended hours and/or weekends as needed
APPLY FOR THE JOB To apply for this role, provide us with the best evidence of your ability to execute. We would like to see what you have designed, built, and tested, so please include links, video, and photographs. A resume is welcome but not required. None of this has to be a perfect match. We care more about raw ability than a checklist, so if that's you, reach out.
How this job compares
Set against the 1,604 open Principal Engineer jobs on Olive Jobs, counted November 16, 2026.
- Pay
- This postingNot listed
- California median$180–277K/yr268 salary ranges
- Openings
- Olive Jobs lists 297 open Principal Engineer jobs in California and 1,604 across the US. 16% of them nationwide are listed as remote or flexible.
- Hiring the most in California
- Northrop Grumman46 open
- Palo Alto Networks17 open
- Amazon15 open
- Experience
- This posting asks for at least 11 years of experience; Principal Engineer postings that state a minimum ask for 8 years at the median (1,411 postings).
- Education
- This posting asks for a bachelor's degree; 645 of the 1,604 open Principal Engineer jobs (40%) ask for a bachelor's degree or higher.
Counted across the open, public US postings on Olive Jobs on November 16, 2026. Figures based on too few postings are left out.
Prepare for this role
You've read the whole posting — now see how you match it.



