Senior Infrastructure Manager – Software Delivery
Wells Fargo · MCLEAN, VA
$139,000–$260,000from the description
Jul 24, 2026
MCLEAN, VA
Jul 25, 2026
What this job asks for AI summary
A senior management role overseeing enterprise software delivery infrastructure, with responsibility for teams handling software packaging, patch readiness, repository management, release automation, and lifecycle governance across on-premises, cloud, and hybrid environments. The position involves setting modernization strategy, building self-service and CI/CD capabilities, and reducing manual processes. It suits an experienced infrastructure leader with deep backgrounds in Kubernetes/OpenShift, Infrastructure as Code, secrets management, and enterprise GitOps practices.
Senior level · 7+ 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
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $178,991 (middle half $141,096–$225,584). 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 Bachelor's degree is listed under 'Desired' (not 'Required'), so it is treated as preferred and not a hard gate.
OpenShift and Kubernetes are listed together as a single platform requirement ('OpenShift/Kubernetes'); they are emitted as separate skills with each as the other's alternative, since both are named and the slash here denotes interchangeable platforms rather than a combined stack.
The 7+ years of 'infrastructure engineering and operations experience' appears twice in the Required Qualifications — treated as a single gate.
Management/leadership experience (3+ years) is a stated hard gate but names no specific technology or tool, so it is captured in the overall years minimum context only and not emitted as a skill per extraction rules.
No specific cloud provider (AWS, Azure, GCP) is named; 'cloud architecture' is extracted as the stated requirement.
Ignored 3 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): infrastructure engineering, secrets management, cloud architecture.
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.