Member of Technical Staff

About the Role

As a Member of Technical Staff on the Wind River Linux team, you are the senior technical anchor for a safety-critical embedded Linux platform. You own architecture-level decisions across the Yocto build system, Linux kernel, and multiple BSPs, drive the OSS/upstream strategy, and act as the technical force-multiplier who makes the whole team better. This is a hands-on technical leadership role, you set direction and still solve the hardest problems yourself.

You are the person the team leans on when a cross-layer, cross-repo problem spans the kernel, the BSP, the build system, and a customer's field deployment all at once.

What You'll Do

Linux Kernel & Low-Level Development

• Own kernel maintenance across LTS lines: backports, CVE remediation, -stable rebases, and local-patch discipline where upstream isn't an option.
• Debug deep kernel, driver, networking, and boot issues across ARM/x86 (and PPC/RISC-V where relevant) using GDB, JTAG, ftrace/kernel tracing, and perf tooling.
• Drive determinism, real-time (PREEMPT_RT), and reliability improvements that hold up under safety-critical scrutiny.

Multi-BSP & Yocto Build System

• Serve as 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.
• Own the Yocto/OpenEmbedded architecture: layers, templates, bblayers/local.conf behavior, recipe design, and the build-farm topology that produces the release matrix.
• Resolve the cross-layer, cross-repo problems (recipe + BSP + kernel + template interactions) that no single track owner can close alone.

OSS & Upstream

• Define and drive the upstream strategy, what we push upstream vs. carry as local patches, and represent WRLinux technical direction in OSS communities.
• Champion upstream-first CVE handling and reduce the local-patch maintenance burden over time.

Release Engineering & Quality

• Own the reliability of release-critical systems: OOBE/Sanity gates, the CVE-verification pipeline, SBOM/IP flow, and the CI that ties them together.
• Make and be accountable for architecture calls on the tooling migration (source host, CI, issue tracking) and the CVE-automation stack.
• 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.

Technical Leadership & Mentoring

• Provide technical direction, design reviews, and code reviews that raise the whole team's bar.
• Mentor engineers and compress their ramp-up under an AI-paired model.
• Remove single points of failure by documenting and systematizing product knowledge.
• Support customer escalations as the deep technical specialist of last resort.

What You Bring

• BE/BTech or ME/MTech in CS/ECE/EE or equivalent; 8–12 years in embedded Linux.
• Deep expertise in Linux kernel (architecture, drivers, debugging) and C; strong Python for tooling/automation; C++ a plus.
• Extensive hands-on Yocto/OpenEmbedded and BSP experience, multi-board bring-up, layer/recipe architecture, hardware-software integration.
• Proven technical leadership and mentoring of engineering teams.
• Strong debugging with GDB, JTAG, kernel tracing, and performance tooling.
• Familiarity with ARM/x86 (PPC/RISC-V a plus), networking, and virtualization.
• Agile + CI/CD fluency; Git/Linux daily driver.
• Excellent communication and cross-functional stakeholder skills; effective in a globally distributed team.

Nice to Have

• OSS/upstream contribution track record (kernel or Yocto layers).
• Edge-AI inference stacks on embedded silicon (TensorRT, OpenVINO, ONNX Runtime, TF Lite).