> Markdown version of [/jobs/ext/4775274-sr-staff-firmware-engineer](https://www.wearedevelopers.com/jobs/ext/4775274-sr-staff-firmware-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Sr. Staff, Firmware Engineer - **Company:** Ayar Labs - **Location:** San Jose, CA, United States - **Experience:** Expert - **Salary:** $197,000 - $229,000 - **Contract:** Permanent contract - **Skills:** C (Programming Language), Artificial Intelligence, C++ (Programming Language), Datasheets, Software Debugging, Embedded Software, Firmware, FreeRTOS, Python (Programming Language), Computer Equipment, Integration Tests, Bare Metal, U-Boot - **Published:** November 18, 2026 - **Apply:** https://www.careerbuilder.com/job-details/sr-staff-firmware-engineer-san-jose-ca--ecb3e256-46f9-4dcb-be1a-d983532a77be ## About the Role Computer Firmware, Willing to Travel, Electricity, Optics, Photonics, Computer Hardware, Artificial Intelligence (AI), Input/Output, Ecosystems, Semiconductors, * Embedded firmware background that includes owning the verification strategy and test infrastructure for at least one shipping product * Strong C, C++ and Python * Experience building hardware-in-the-loop rigs and a firmware CI and regression system * Board-level debug with oscilloscopes, logic analyzers and datasheets * Technical leadership across teams or sites, and clear technical writing, * Optical module firmware and management standards; platform management and BMC firmware; silicon photonics; manufacturing test; secure boot; Zephyr, FreeRTOS or bare-metal firmware. Photonics experience is not required. ## Description This is a senior individual contributor role. You will set the technical direction for firmware verification and lead the engineers across a geographically dispersed team, including contract staff, who write tests against it. Essential Functions * Own the verification strategy and test plan, including what results are required before a release ships * Define and automate the release gate, with authority to block a release * Own hardware-in-the-loop regression and the unit and integration test harness * Root-cause escaped defects and close the coverage gaps they expose * Write specifications and review test code for engineers in other time zones, working mostly asynchronously