Azure Cloud Engineer at Schnabel Engineering
Greensboro, NC
$100,000–$130,000from the description
Jul 23, 2026
Greensboro, NC
Jul 25, 2026
What this job asks for AI summary
This role centers on designing, building, and operating Microsoft Azure cloud infrastructure for an engineering consultancy, with responsibility spanning networking, security architecture, disaster recovery, and data platforms. Day-to-day work includes managing Azure firewalls, VNets, and hybrid connectivity, writing Infrastructure as Code in Bicep, integrating AI and analytics services, and maintaining observability across production environments. It suits an experienced Azure practitioner comfortable owning end-to-end cloud operations in an enterprise setting.
Senior level · 5+ years · 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
Rare in this occupation — lead with these, and say what you built with them.
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 (6)
The role is a genuine hybrid between cloud infrastructure operations (15-1244) and cloud software/IaC engineering (15-1252). The presence of Bicep IaC authoring, API design and integration, and building automation tips it toward 15-1252, but a meaningful portion of the work is operating and administering existing Azure infrastructure, making 15-1244 a credible runner-up.
No office location is specified in the posting; Schnabel has 32 US offices. The compensation note mentions geographic variation, suggesting the role may be filled at any of their locations. CBSA and state are left blank accordingly.
The posting does not explicitly state remote or on-site; remote is set to false as a conservative default given the enterprise/production operations context and no remote language.
Azure certification (e.g., Azure Administrator, Azure Security Engineer, Azure Solutions Architect) is listed as required but is a credential, not a named technology — it is not emitted as a skill per extraction rules.
PowerShell and Azure CLI appear together under Preferred Skills as scripting/automation options and are captured as a single preferred skill with Azure CLI as an alternative.
Active Directory is implied by the preferred 'Entra ID / AD integration' item and is captured as a preferred skill alongside Entra ID (which is required from the main requirements block).
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.