Senior HPC Systems Architect at Lambda
San Jose, CA
$255,000–$340,000
Jul 26, 2026
San Jose, CA
Jul 28, 2026
What this job asks for AI summary
A Senior HPC Systems Architect role at an AI cloud infrastructure company, responsible for designing and architecting large-scale GPU clusters and liquid-cooled HPC systems from rack/pod layout through compute fabric sizing. The position spans high-performance networking, power and cooling, data center design, and AI-scale infrastructure, with a mix of hands-on technical design, performance benchmarking, and cross-team technical leadership. Candidates should have deep expertise in GPU clusters, InfiniBand/Ethernet networking, and distributed storage at scale.
Senior level · 8+ years · San Francisco-Oakland-Berkeley, CA · 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.
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
Rare in this occupation — lead with these, and say what you built with them.
What the occupation pays Median $165,256 (middle half $104,590–$211,000).
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 (5)
The posting mentions a salary range exists ('has been set based on market data') but does not disclose the actual figures.
SOC 15-1299 (Computer Occupations, All Other) is used because HPC Systems Architect is a specialized infrastructure design role that does not map cleanly to Software Developers (15-1252) or Network/Systems Admins (15-1244); 15-1244 is noted as a plausible alternative given the infrastructure operations overlap.
The role is based in San Francisco or San Jose; both fall within the San Francisco-Oakland-Berkeley, CA CBSA (41860). San Jose is technically within the San Jose-Sunnyvale-Santa Clara CBSA (41940), but the posting lists both cities as options without specifying a primary, so the larger SF metro is used.
Ansible, Terraform, and Kubernetes appear together under 'Nice to Have' as automation/orchestration tools; they are listed as separate preferred skills rather than strict alternatives, though the posting groups them as a single bullet.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): capacity planning.
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.