Cloud Engineer - Journeyman at ASM Research
Fairfax, VA
—
Jul 7, 2026
Fairfax, VA
Jul 20, 2026
What this job asks for AI summary
A mid-level cloud engineering role focused on designing and operating secure multi-cloud and hybrid infrastructures for government enterprise systems. Day-to-day work spans building Infrastructure as Code pipelines, configuring cloud networking and security controls, implementing monitoring and disaster recovery solutions, and supporting DevOps practices. Suited to engineers with 4–7 years of relevant experience who hold an active Secret clearance and US citizenship.
Mid level · 4+ years · National · Secret clearance
“or” means any one of them counts — you don't need all of them.
Posted 2 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
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 title 'Cloud Engineer – Journeyman' carries no standard seniority level word, so the title states no level. The 4–7 year experience range and scope (implementing/configuring within enterprise teams, not setting org-wide direction) maps to Mid-level.
SOC classification is a genuine judgment call: the role writes IaC code and builds automation pipelines (pointing to 15-1252 Software Developers), but also heavily operates and manages cloud infrastructure, networking, and security controls (pointing to 15-1244). The IaC/automation emphasis tips the primary classification to 15-1252.
Location is not stated in the posting. The government/DoD context and Secret clearance requirement strongly imply a US-based, likely on-site or hybrid position, but no specific city or metro was provided.
Terraform, CloudFormation, and ARM templates are listed together as interchangeable IaC options under the required qualifications; Terraform is used as the primary name with the others as alternatives.
CloudWatch, Azure Monitor, and Stackdriver are listed as interchangeable monitoring examples under required qualifications; CloudWatch is used as the primary name.
Splunk and Elastic appear in the responsibilities narrative (not a dedicated requirements section) as monitoring/logging examples. They are treated as preferred rather than hard gates.
Docker and Kubernetes appear only under Preferred Qualifications.
AWS and Azure certifications (Solutions Architect, DevOps Engineer, Administrator Associate) are listed under Preferred Qualifications and are not extracted as skills since they are credentials rather than named technologies.
Degree requirement is set to None because the JD explicitly states 'equivalent experience may be considered.'
Requires a Secret clearance — the cleared population is a small fraction of this occupation, so the real candidate pool is materially smaller than the estimate below, which does not model clearance.
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.