Staff Infrastructure Software Engineer

Staff Infrastructure Software Engineer

What this role actually is
This is a Staff Infrastructure Software Engineer  role that happens to build the platforms underneath infrastructure — think: the control planes, APIs, and systems that other engineers rely on, not the day-to-day operation of that infrastructure.

The calibration note is the most important part of this brief, and it''s worth repeating back to the manager if you''re ever unsure on a submittal: they explicitly do not want people whose experience is:
Operating or administering systems
Configuring infrastructure (standing up VMs, managing storage arrays by hand)
Working at the application or device layer
They do want people who''ve built the software that platform depends on — e.g., someone who wrote the control plane that manages VM provisioning, not someone who provisions VMs; someone who built a storage orchestration service, not someone who manages a SAN.
Specialty priority, per your ask: Hypervisor/virtualization and Storage are the top two areas of focus, with Windows, Linux, and Networking rounding things out — but always in service of "did they build software systems in this space," not "do they have hands-on ops experience in this space."