Remote Principal Cloud Engineer (Microsoft Azure) at MRIoA
Salt Lake City, UT
—
Jul 12, 2026
Salt Lake City, UT
Jul 20, 2026
What this job asks for AI summary
A senior individual-contributor role focused on designing and owning Azure cloud infrastructure for a healthcare utilization management company. The position covers everything from hub-spoke networking, IaC, and CI/CD pipelines to identity, security controls, and compliance evidence for HITRUST and SOC2. It also carries responsibility for mentoring systems administration and security staff and leading cloud migration projects end-to-end.
Senior level · 7+ years · Remote · Full-time
Advertised as Principal, but the requirements read as Senior.
“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
Roughly 890 people nationally plausibly meet what this posting asks for (software developers). range 180–1,600
Applicant volume Light — Few people clear these requirements, so an application that does clear them gets looked at. Worth applying to even if you miss a nice-to-have.
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).
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 is titled 'Principal Cloud Engineer' but the actual scope — owning cloud architecture for a single organization, mentoring adjacent teams, and reporting to a Manager of IT & IS — is consistent with a Senior individual contributor, not a true Principal (org-wide technical authority across multiple product lines). Seniority is assessed as Senior accordingly.
SOC classification is Medium confidence. The role writes and ships Infrastructure as Code (Terraform/Bicep), CI/CD pipelines, and automation scripts (15-1252 Software Developers), but also has a substantial systems/network operations and administration dimension (15-1244). The IaC and pipeline-building work is the primary day-to-day output, so 15-1252 is preferred.
The JD states 7–10 years of total infrastructure/cloud experience and separately 5 years of senior/principal-level Azure experience. Total experience minimum is set to 7 years (the lower bound of the stated range); the 5-year Azure figure is captured on the Azure skill.
A Bachelor's degree is listed but the JD explicitly accepts 'equivalent professional experience' as an alternative, so the degree requirement is set to None.
Three Azure certifications (AZ-104, AZ-700, AZ-305) are hard-gated with the phrase 'required — must already hold.' AZ-400 is listed as 'strongly preferred' and is marked accordingly.
AZ-400 appears under the certifications section with 'strongly preferred' language rather than 'required — must already hold,' so it is treated as preferred.
ZTNA, Azure AI, and healthcare data exchange standards (HL7/EDI/SFTP) are explicitly flagged as 'preferred' in the JD.
No compensation figures are provided in the posting.
Ignored 2 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): Azure Privileged Identity Management, Azure 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.