Principal Multi-Cloud Architect
CyberData Technologies · Bethesda, MD
—
Jul 22, 2026
Bethesda, MD
Jul 24, 2026
What this job asks for AI summary
A hands-on principal-level architecture role supporting a federal research organization across AWS, Azure, and GCP. The position covers secure cloud design, Infrastructure as Code with Terraform, CI/CD pipelines, container orchestration, cloud security and identity patterns, AI/ML governance, and observability integrations with tools like Splunk and OpenSearch — all within federal compliance frameworks such as FISMA, FedRAMP, and Zero Trust. Suits a seasoned multi-cloud engineer with deep federal security experience who can also advise leadership and lead cross-organizational technical working groups.
Senior level · 10+ years · 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.
Why we read it this way (10)
No work location or metro area is specified in the posting. The role supports a federal research organization, suggesting a likely Washington D.C. area placement, but this cannot be confirmed from the text alone.
The title is 'Principal Multi-Cloud Architect,' but the actual requirements (10+ years total, 5+ years in cloud, deep expertise in 2 of 3 cloud providers) are consistent with a Senior-level role on a normal career ladder. The 'Principal' designation appears to be a title/grade label at this employer rather than evidence of org-wide technical authority across multiple teams.
The degree requirement accepts 'equivalent relevant experience' in lieu of a formal degree, so no minimum degree is hard-gated.
The posting requires the ability to obtain a federal suitability determination and system access, but does not gate on a specific US security clearance level — this is a suitability/background check, not a clearance.
SOC classification is Medium confidence: the role is genuinely hybrid between hands-on IaC/pipeline engineering (15-1252) and multi-cloud infrastructure operations (15-1244). The emphasis on Terraform module development, CI/CD pipeline governance, and 'hands-on architecture' tips it toward 15-1252, but the strong operational and monitoring responsibilities make 15-1244 a credible alternative.
AWS, Azure, and GCP are all listed as required together — the JD requires deep expertise in at least two and working knowledge of the third. All three are marked required to reflect this multi-cloud gate.
GitHub is listed in the required section with GitLab and Azure DevOps as named alternatives ('GitHub, GitLab, Azure DevOps, or a comparable platform').
Splunk and OpenSearch appear together in the required section as the named monitoring platforms; OpenSearch is also listed separately as a preferred tool in context of additional integrations.
AWS Inspector, AWS Detective, AWS Config, and Amazon ECS appear in the preferred section alongside the other AWS services listed; they are omitted here as they were not individually called out as distinct skills beyond the broader AWS service list.
No compensation information is provided in the posting.
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.