Senior Cloud Platform Engineer

Our client, runs governed infrastructure across Azure, AWS, and on-prem for multiple portfolio companies. We want a Senior Cloud Platform Engineer who works as a peer on the platform. You’ll work from design through production, troubleshoot hard problems without help, and raise our bar for automation, security, and documentation.

What you will build

Paved roads

• Shared Terraform modules that teams use to get their environments: networking, storage, identity, compute, secrets, and monitoring, with secure defaults built in.
• Versioned, tested, documented modules, so a team can move to a new version without asking us.
• Policy as code (Azure Policy, conftest, SCPs and RCPs) that catches problems at plan time, not after apply.
• Self-service: a team fills in a short tfvars file and gets a working, compliant environment.

Projects

• Platform projects, from design to production, with the architect. A current example is a secure platform that shares petabyte-scale data with our portfolio companies across Azure, AWS, and on-prem.
• Infrastructure for the teams we serve: GPU capacity for machine learning, remote workspaces, and hybrid connectivity to the datacenter.
• Proofs of concept that settle a design question quickly, with real numbers. This includes judging which new cloud features are worth adopting.

The platform itself

• Landing zones and guardrails: management groups and subscriptions in Azure; Organizations, OUs (organizational units), SCPs, RCPs, and account vending in AWS.
• Networking: hub-and-spoke and Transit Gateway, firewalls, private endpoints and VPC endpoints, DNS, ExpressRoute, Direct Connect, and VPN.
• Identity: Entra ID, managed identities, IAM Identity Center permission sets, cross-account roles, and workload identity federation (OIDC). No stored secrets or long-lived keys where federation is possible.
• CI/CD for infrastructure: GitHub Actions with OIDC, self-hosted runners, and plan review in every pull request.

What you will also run

Builders run what they build. You take part in:

• the on-call rotation for the platform, with the security team for incidents
• escalations that cross identity, networking, and pipelines: find the root cause, fix it, and write it up so it doesn’t come back
• findings from Defender for Cloud, Security Hub, GuardDuty, and Access Analyzer, turned into preventive controls rather than one-off fixes
• monitoring and alerting for what you ship, so that every alert has an owner
• cost tracking for your projects, with right-sizing when the numbers say so
• runbooks, so someone else can operate what you built

We would rather you automate an operational task than do it twice.

Must have

• 5 or more years building cloud infrastructure in production. Deep experience in Azure or AWS, and solid working experience in the other.
• You have built Terraform modules that other teams used. You can talk about how you versioned, tested, and released them, and what you would do differently. You are comfortable with imports, state moves, and refactors on live infrastructure.
• Strong networking: routing, DNS, private connectivity, firewalls, and hybrid links (ExpressRoute or Direct Connect, and VPN).
• Identity and access in both clouds. Azure: Entra ID, RBAC (role-based access control), managed identities, and private-only service design. AWS: how IAM policies are evaluated, SCPs, permission boundaries, cross-account trust, and STS.
• CI/CD for infrastructure, preferably GitHub Actions with OIDC federation.
• Methodical troubleshooting using the evidence: Activity Log, CloudTrail, flow logs, and policy simulation, until you find the root cause.
• Security-first habits: least privilege, no secrets in code, logging, and audit by default.
• Careful production habits: you check before you change or delete, plan the rollback, and document as you go.
• You have taken at least one infrastructure project from an empty repo to production.
• Clear writing for engineers, app teams, and leadership: design docs, runbooks, and post-incident write-ups.

Nice to have

• Module testing and policy tools: Terratest, conftest or OPA, tflint, Checkov or Trivy.
• Platform engineering: internal developer platforms, golden paths, templates, or service catalogs.
• AWS Control Tower and AFT (Account Factory for Terraform).
• Entra-to-AWS federation and single sign-on.
• Kubernetes on AKS or EKS: workload identity, IRSA or Pod Identity, Helm, and GitOps tools such as Argo CD or Flux.
• GPU or HPC infrastructure: GPU VM families, schedulers such as Slurm, or high-throughput storage.
• Supporting data platforms (Snowflake, Databricks, or similar) from the infrastructure side.
• Regulated data: ITAR or EAR, CMMC or NIST 800-171, SOC 2.
• Ansible, and scripting in Python, Bash, or PowerShell.
• Zero-trust network tools such as Zscaler (including TLS inspection) or Tailscale.
• Certifications: Azure Solutions Architect Expert, AWS Solutions Architect Professional, or Security Specialty.