Senior Cloud Engineer

Role Overview

We are looking for a resource to support our cloud engineering team. This is enterprise-scale platform work, not single-application DevOps: the client distinguishes clearly between an engineer who builds infrastructure for one application team, and one who builds a platform or self-service system that hundreds of applications and many different teams can consume. Candidates need genuine experience with the latter.

Key Responsibilities

• Design, build, and maintain enterprise cloud infrastructure and CI/CD pipelines using Terraform and GitHub Actions

• Build reusable, self-service platform capabilities consumable by many application teams - not point solutions for a single team

• Own the full lifecycle of cloud services: observability, security vulnerability management, and RBAC (role-based access control)

• Participate in full SDLC activities, including requirement gathering and enterprise architecture discussions with client stakeholders

• Maintain thorough documentation, planning artifacts, and detailed ticket updates for client visibility

• Operate within the client's enterprise governance, security, and change-management frameworks as a platform contributor - not just an infrastructure builder

Core Technical Skills

•     Terraform - hands-on Infrastructure-as-Code experience (top priority)

•     GitHub / GitHub Actions - CI/CD pipeline design and management

•     Microsoft Azure as primary cloud platform; GCP or AWS experience is a plus but not required

• Python, used alongside Terraform for automation and scripting where IaC alone isn't sufficient

• YAML for CI/CD pipeline configuration

• SQL / PostgreSQL and Azure App Service (service-level cloud skills)

• Kubernetes / containerization working knowledge (deep expertise required for at least one team hire - see Preferred below)

Requirements

Enterprise Cloud Engineering Competencies (Required)

This backfill is explicitly for enterprise-level talent, not application-level DevOps - this was the client's number one screening criterion. Candidates must be building platforms consumed by hundreds of applications and many teams, not infrastructure for a single

team, and should bring:

• True enterprise-scale delivery experience: shared, self-service platforms consumed by many independent application teams, not single-application deployments

• Enterprise governance and landing-zone experience: multi-subscription/multi-account structuring, policy-as-code, and consistent tagging/naming standards enforced at scale

• Identity and access management at scale: Azure AD/Entra ID, RBAC and least-privilege design, service principal / managed identity governance

• Enterprise network architecture: hub-spoke topology, VNet peering, private endpoints, network segmentation

• Security posture and compliance for regulated industries: vulnerability management, threat modeling, audit readiness, and comfort with the change-control standards banks impose on vendors

• Observability at scale: centralized logging, monitoring, and alerting (Azure Monitor/Log Analytics or equivalent), operating to SLA/SLO expectations

• Cost governance / FinOps awareness across many consuming teams

• Comfortable operating within formal change-management/ITSM processes (CAB approvals, detailed ticketing discipline)

• Resilience and disaster-recovery planning - designing for high availability, since platform outages affect many downstream teams

• Architecture-level thinking for platform-level (vs. service-level) engagements - the client considers this non-negotiable at platform scale

• Full SDLC fluency, including requirement gathering and enterprise architecture discussions with client stakeholders

• Strong written communication: detailed documentation, planning in Excel, and thorough ticket-level updates - enterprise clients expect constant visibility into status

• Able to explain technical approach and reasoning in depth; this work is reviewed closely by the client's own in-house architects

• Kubernetes / containerization expertise at depth (needed for at least one of the team's hires)

• Formal cloud platform experience beyond working knowledge (Azure, GCP, or AWS), e.g., Infrastructure-as-Code / Terraform exposure

Preferred / Nice to Have

• Prior banking or financial-services experience

•     Lead-level experience: TL/Architect-level capability plus current hands-on delivery, with proven ability to manage 2–3 engineers