Azure Infrastructure Engineer
Bright Vision Technologies · San Jose, CA
$100,000–$150,000from the description
Jul 16, 2026
San Jose, CA
Jul 20, 2026
What this job asks for AI summary
Senior level · 5+ years · Remote · Bachelor's required · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 9 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
Roughly 3,350 people nationally plausibly meet what this posting asks for (software developers). range 690–5,000
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
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 (11)
The role title carries no seniority level word, so advertised seniority is Unspecified; however, the 5+ years overall / 3+ years Azure requirement and the scope (architecture reviews, mentoring, DR strategy, cost optimization) firmly support a Senior classification.
SOC classification is Medium-confidence: the role writes IaC, automation scripts, and CI/CD pipelines (pointing to 15-1252 Software Developers), but also operates and administers Azure infrastructure at scale (pointing to 15-1244). The primary day-to-day emphasis on building and shipping infrastructure-as-code and automation tips the balance to 15-1252.
The JD states '5 or more years of cloud engineering experience, with at least three years focused on Microsoft Azure' — the overall years minimum is set to 5 (the overall role-level gate); the 3-year Azure-specific figure is captured on the Azure skill's years demanded.
The JD header says '6+ years experience required' but the Required Qualifications section states '5 or more years.' The more specific, section-level figure (5) is used for the overall years minimum; the discrepancy is noted here.
Terraform/Bicep/ARM templates are listed as a single interchangeable requirement in the Required Qualifications section; Terraform is used as the primary name with the others as alternatives.
Azure DevOps and GitHub Actions are presented as interchangeable CI/CD options in both the responsibilities and required qualifications; captured as one skill with GitHub Actions as an alternative.
Microsoft Defender for Cloud, Sentinel, Azure SQL, Cosmos DB, Synapse Analytics, Data Factory, Event Hubs, and Istio/Linkerd appear in responsibilities narrative or the Preferred Qualifications section rather than as hard gates in Required Qualifications, so they are marked preferred.
Azure certifications (Azure Solutions Architect Expert, Azure DevOps Engineer Expert) are listed under Preferred Qualifications only and are not emitted as skills per extraction rules (certifications are not concrete technologies).
FinOps practices and regulated-environment experience (HIPAA, PCI-DSS, SOC 2, FedRAMP) are listed under Preferred Qualifications and name no specific tool, so they are omitted from the skills list.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): Microsoft Defender for Cloud.
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.