Principal Linux Architect
Fiserv · Alpharetta, GA
—
Jul 17, 2026
Alpharetta, GA
Jul 21, 2026
What this job asks for AI summary
A senior-level architecture role focused on setting the strategic direction for enterprise Linux platforms spanning on-premises, cloud, and hybrid environments within a large fintech organization. Day-to-day work involves defining standards and reference architectures, governing container platforms, leading automation and Infrastructure as Code initiatives, and serving as the top escalation point for complex Linux issues. The role suits a deeply experienced Linux architect comfortable engaging both engineering teams and executive stakeholders.
Senior level · 12+ years · National · 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.
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 (8)
The title is 'Principal Linux Architect' but the actual scope and requirements — 12+ years Linux engineering, 8+ years enterprise architecture, deep hands-on IaC and automation — are well within the Senior band. The 'Principal' label here reflects Fiserv's internal leveling rather than org-wide technical authority in the BLS sense; the role is sized as Senior.
SOC classification is a genuine judgment call: the role writes and ships infrastructure-as-code (Terraform, Ansible, automation frameworks) and architects platforms, pointing to 15-1252 Software Developers; however, it also has a strong systems/operations flavor (Linux OS standards, patching, storage, networking, DR). 15-1244 is listed as the runner-up.
No work location or CBSA is specified in the posting. A long list of states where the role is explicitly NOT eligible is provided (Colorado, California, DC, Hawaii, Illinois, Massachusetts, Maryland, Minnesota, New Jersey, New York, Nevada, Rhode Island, Vermont, Virginia, Maine, Washington), but no positive location is named.
The degree requirement states 'Bachelor's degree … or equivalent military/work experience,' so no hard degree gate applies.
AWS, Azure, and GCP are all named together as a required multi-cloud strategy; they are listed as separate skills because the JD expects all three, not as interchangeable alternatives. The 'alternatives' array on AWS is populated only to satisfy the schema convention for the 'or similar' pattern — in this posting all three clouds are genuinely co-required.
OpenShift, Service Mesh technologies, observability platforms, and CIS benchmarks appear under the 'great to have' (preferred) section.
Relevant certifications (RHCA, AWS Solutions Architect Professional, Azure Solutions Architect Expert, CKA, Terraform Associate) are listed as preferred/nice-to-have and are not emitted as skills per extraction rules (they are credentials, not named technologies).
No compensation figures are provided in the posting; the JD explicitly warns that any salary ranges on external job boards are third-party estimates.
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.