Senior Cloud Infrastructure Engineer at UJET
$150,000–$175,000from the description
Jul 6, 2026
—
Jul 21, 2026
What this job asks for AI summary
A senior infrastructure role focused on owning and evolving the foundational cloud layer — GCP networking, Kubernetes clusters, Terraform-based infrastructure-as-code, IAM, secrets management, and observability foundations. The work involves setting architecture standards, reducing systemic risk, driving cost optimization, and enabling product engineering teams through reusable, secure-by-default infrastructure patterns. Suits experienced platform or SRE engineers comfortable operating at the layer below applications.
Senior level · 5+ years · Remote · Full-time
“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
Roughly 24,900 people nationally plausibly meet what this posting asks for (software developers). range 7,300–37,400
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
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 (10)
The role sits squarely at the boundary between 15-1252 (Software Developers) and 15-1244 (Network and Computer Systems Administrators). It is classified as 15-1252 because the JD explicitly emphasizes writing and shipping infrastructure code — Terraform IaC standards, Go/Python automation tooling, reusable infrastructure patterns, and internal developer platform work — rather than purely operating existing systems.
GCP is listed as the primary required cloud platform; the JD's 'or equivalent cloud platforms' qualifier means AWS and Azure are named as alternatives rather than separate requirements.
Terraform is listed under Requirements with 'or similar' — alternatives reflect common IaC substitutes.
Go and Python appear together as scripting/automation options ('Go, Python, etc.'); Go is listed as the primary with Python as an alternative since both satisfy the same requirement.
VPCs, load balancing, and DNS are listed together as a single networking requirement block under Requirements; they are emitted as separate skills because they are distinct capabilities, not interchangeable options.
Prometheus and OpenTelemetry appear only under Preferred Qualifications ('Familiarity with observability systems') and are marked preferred accordingly.
Multi-region/HA design, infrastructure security/compliance, and internal developer platform experience are listed under Preferred Qualifications and are not emitted as hard-gate skills.
The posting tags both #LI-Remote and #LI-Hybrid; per caller instruction, remote=true is set and no metro is inferred.
The '5–10+ years' range yields the overall years minimum of 5 (the stated minimum).
Caller marked this a fully-remote role — scored against the national candidate pool.
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.