8+ years of firmware engineering, with deep hands-on BMC experience
Hands-on expertise with at least one production BMC stack (OpenBMC, AMI MegaRAC, or equivalent), including the embedded Linux, U-Boot, and device tree layers underneath
Demonstrated experience leading BMC bring-up on new server platforms — working from schematics, I2C/PMBus device maps, GPIO assignments, and platform power sequencing
Strong C/C++ on embedded Linux; comfortable in Python or shell for automation and tooling
Deep familiarity with BMC management protocols and standards: IPMI 2.0, Redfish, PLDM, MCTP, and NC-SI
Hands-on debugging across BMC-to-host interfaces: eSPI, LPC, IPMB, KCS, BT (Block Transfer)
BS/MS in CS, EE, CompE, or equivalent experience
Experience working with ODM/OEM partners on BMC firmware — leading engagements is a plus, but strong technical collaboration counts
Familiarity with Yocto / BitBake (or equivalent build systems for embedded Linux distributions)
Production experience: BMC firmware you've shipped is running in a fleet today, and you've debugged it there
BMC security work: secure boot, RoT, DICE, SPDM, attestation, firmware resiliency, or response to a real firmware CVE
Familiarity with DC-MHS / DC-SCM and current OCP hardware management direction
Track record of growing a firmware engineering team — hiring, technical mentorship, and setting engineering practices