Staff Embedded Software Engineer

Embedded Software Engineer Staff (L6 equivalent), scope across multiple teams 8-12 years

Other levels: Embedded Software Engineer Senior Embedded Software Engineer Principal Embedded Software Engineer Lead Embedded Software Engineer Junior Embedded Software Engineer

✓ Which company are you aiming at?

To generate precise rejection-prevention feedback and application strategy, tell us where you're targeting.

Apple

NVIDIA

Tesla

Qualcomm

Bosch

Garmin

2 Send your application

You need an account so we know where to send the feedback.

Create an account Sign in

The job description

Tech stack. C/C++, ARM Cortex-A/M, FreeRTOS/Linux, driver development, system debugging, performance profiling, technical mentorship

About the role

You will join a consumer electronics company shipping tens of millions of connected devices a year. The embedded software group spans multiple product teams that share silicon but diverge in features, and staff engineers are the connective tissue: the people who make sure architecture decisions survive contact with four different roadmaps. This role matters because without staff-level ownership, shared firmware becomes a bottleneck that slows every product line at once.

What you will achieve

Own the shared firmware platform used by four product teams, resolving cross-team architectural conflicts and keeping the platform roadmap unblocked quarter to quarter with a published decision log
Drive a 25% reduction in system RAM usage across the device portfolio by redesigning buffer management and heap policies on the common platform, verified by automated memory reporting in CI
Ship a unified logging and crash-reporting pipeline that cuts average time-to-root-cause on field issues from days to hours, adopted by every product team within two quarters
Lead the migration of legacy drivers to a testable, mockable driver framework, reaching 80% unit test coverage on shared components and zero coverage regressions on new code
Mentor senior and mid-level engineers across teams, running the firmware guild's design review forum and architecture decision records that new hires cite in onboarding surveys

What you will bring

Must-haves

8-12 years developing embedded software, with significant time on shared platforms or SDKs consumed by multiple teams with different release cadences
Strong C/C++ with deep systems knowledge: memory allocators, cache behavior, DMA coherency, and interrupt latency measured on real hardware
Experience debugging the hardest class of bugs (intermittent field crashes, memory corruption, timing-dependent failures) with a structured, evidence-driven methodology
Proven cross-team influence: driving alignment on technical direction across teams with competing priorities without escalating every disagreement
Hands-on driver development for complex peripherals such as display, camera, audio, or high-speed serial interfaces
Experience with both RTOS and embedded Linux targets, with clear judgment about when each is the right tool for a product
Clear technical writing: architecture docs, ADRs, and postmortems that teams actually read and reference months later

Nice-to-haves

Performance profiling expertise including tracing, cycle-accurate analysis, and power-correlated profiling
Experience with manufacturing test software or factory calibration flows that run at production line speeds
Knowledge of wireless stacks at the driver boundary, including BLE and Wi-Fi coexistence issues