ABOUT WIND RIVER
Wind River is a global leader in delivering software for mission-critical intelligent systems. For more than four decades, the company has been an innovator and pioneer, powering billions of systems that require the highest levels of security, safety, and reliability.
Wind River helps customers across automotive, aerospace, defense, industrial, medical, and telecommunications industries solve complex technology challenges on their journey toward the new intelligent machine economy. The company’s software powers generation after generation of the safest, most secure systems in the world. Examples include playing a key role in NASA space missions such as Artemis I, the James Webb Space Telescope, and multiple Mars rovers. We’ve achieved recent 5G milestones including the world’s first successful 5G data session with Verizon and building one of the largest Open RAN networks in the world with Vodafone.
The company has received industry recognition for its technology innovation and leadership, and for its workplace culture, including global Great Place to Work certification and being named a “Top Workplace” for ten consecutive years. If you want to be part of a unique culture where the lived experience is based on our cultural attributes of growth mindset, customer-focus, and diversity, equity, inclusion & belonging, come join us and help advance the future software defined world.
About the Role
As a Member of Technical Staff on the Wind River Linux team, you're the senior technical anchor for a safety-critical embedded Linux platform — and this is a build-and-decide role, not a keep-it-running one. You own the architecture-level calls across the Yocto build system, Linux kernel, and multiple BSPs; you drive where we go upstream; and you build the engineering workflows the whole team runs on. Yes, you'll keep the platform solid — but the reason this role exists is to move it forward: the tooling migration, the AI-native engineering stack, the upstream strategy, and the cross-layer problems no single track owner can close.
You're the person the team leans on when a problem spans the kernel, the BSP, the build system, and a customer's field deployment all at once — and the one who decides how we solve that class of problem for good, not just this once.
What You'll Do
Linux Kernel & Low-Level Development
Drive determinism, real-time (PREEMPT_RT), and reliability improvements that hold up under safety-critical scrutiny — you set the technical bar here.
Debug the deepest kernel, driver, networking, and boot issues across ARM/x86 (and PPC/RISC-V where relevant) with GDB, JTAG, ftrace, and perf.
Own kernel maintenance across LTS lines as the baseline — backports, CVE remediation, -stable rebases, local-patch discipline — and, more importantly, decide the strategy that shrinks that burden over time.
Multi-BSP & Yocto Build System
Own the Yocto/OpenEmbedded architecture — layers, templates, recipe design, and the build-farm topology that produces the release matrix.
Serve as the technical expert across multiple BSPs (Intel x86, ARM/Zynq MP, NXP i.MX, TI, NVIDIA Tegra, and the growing edge-AI board set): machine configs, kernel provider resolution, layer architecture, and platform bring-up.
Resolve the cross-layer, cross-repo problems (recipe + BSP + kernel + template) that no single track owner can close alone.
Build the Way the Team Works
Drive AI-native engineering — CVE triage, test generation, build diagnosis — as the person who builds the workflows the team runs on, not just consumes them.
Make and own the architecture calls on the tooling migration: source host, CI, issue tracking, and the CVE-automation stack.
Own the reliability of release-critical systems — OOBE/Sanity gates, the CVE-verification pipeline, SBOM/IP flow, and the CI that ties them together.
OSS & Upstream
Define and drive the upstream strategy — what we push upstream vs. carry as local patches — and represent WRLinux's technical direction in OSS…