Senior Platform Engineer

F5 F5 · Enterprise · Seattle, WA

Platform/Cloud Engineers to build and operate a secure, scalable cloud landing zone and platform foundations. Define and automate governance using policy-as-code, create reusable infrastructure-as-code (IaC) libraries, and enable teams through CI/CD pipelines and GitOps practices. Requires deep hands-on expertise in at least one major cloud (Azure or AWS preferred).

What you'd actually do

  1. Design, build, and operate cloud landing zones (multi-account/subscription, org structure, network, identity, logging, security baselines).
  2. Implement governance and guardrails using policy-as-code (e.g., Azure Policy, AWS Organizations/SCPs, OPA/Conftest), including exception handling and auditability.
  3. Deliver an infrastructure platform as a product to the internal development community.
  4. Develop reusable IaC modules/libraries (Terraform primary; Bicep/ARM and CloudFormation also valued) and promote standard patterns for teams.
  5. Build and maintain CI/CD pipelines for infrastructure, OS Images, containers, and platform components using GitOps workflows (PR-based changes, automated validation, progressive delivery).

Skills

Required

  • cloud infrastructure engineering (Azure, AWS, GCP)
  • Infrastructure as Code (Terraform)
  • landing zones / foundational cloud platforms
  • policy-as-code
  • CI/CD for infrastructure
  • configuration management/automation
  • IAM
  • network security
  • encryption
  • key management
  • secure-by-default patterns
  • Git-based workflows
  • Scripting/programming (Python, Bash, PowerShell, Go)

Nice to have

  • Network Engineering
  • hybrid-cloud connectivity
  • network security policy automation
  • cloud native network architectures
  • Data Center automation
  • GCP, OCI, IBM Cloud
  • NIST CSF
  • NIST 800-171
  • SOX
  • SOC 2
  • ISO 27002
  • Kubernetes/platform experience
  • service mesh
  • container platform operations
  • platform engineering concepts
  • developer portals/catalogs
  • golden paths
  • internal products
  • observability stacks
  • SAFe

What the JD emphasized

  • policy-as-code
  • infrastructure-as-code
  • landing zones
  • CI/CD
  • GitOps