Staff Software Engineer, Networking (Seattle or SF Bay Area) at Docker
San Francisco, CA
$170,350–$275,550from the description
Jul 26, 2026
San Francisco, CA
Jul 28, 2026
What this job asks for AI summary
A Staff Software Engineer role focused on the networking stack powering Docker's Sandboxes platform, spanning local and cloud environments. The engineer will set technical direction, make architectural decisions affecting multiple products, and lead a small team building high-performance networking infrastructure for microVM orchestration and multi-tenant agentic workloads. Strong fit for someone with deep Linux/cloud networking expertise and a track record of technical leadership at scale.
Staff level · 8+ years · Remote · Full-time
Quick apply — this platform usually takes a CV and a few fields.
“or” means any one of them counts — you don't need all of them.
Posted 3 times — it's one opening, so apply once.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
What the occupation pays Median $138,970 (middle half $107,524–$175,762). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
The role is classified as Software Developers (15-1252) rather than Network/Systems Admins (15-1244) because the JD centers on designing and building networking software — data-plane and control-plane components, microVM orchestration infrastructure, and CI/CD automation — rather than operating existing infrastructure. The alt code 15-1244 is noted because the networking operations and on-call responsibilities add a meaningful ops dimension.
OVS/OVN and DPDK are listed together in a single requirement alongside Linux networking and eBPF; each is emitted as a separate skill since they are distinct technologies.
AWS is listed as the primary cloud platform; Azure, GCP, and OCI are also named in the same requirement. Azure and GCP are captured as alternatives; OCI is a less common substitute and omitted from alternatives.
CI/CD, monitoring, and infrastructure-as-code tooling are described with 'familiarity with' language in the qualifications, indicating preferred rather than hard-gated requirements. Terraform is used as the canonical representative for infrastructure-as-code tooling.
The degree requirement states 'Bachelor's degree … or equivalent practical experience,' which is treated as no hard degree gate.
The role is remote-first with no specific metro; compensation range is US-only per the posting.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): container orchestration.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.