Senior Cloud Migration Engineer/Architect (AWS To GCP Migration)

Key Responsibilities: Migration Strategy and Delivery Leadership:

• Own the end to end technical strategy for the AWS to GCP migration, including target architecture, migration sequencing, and cutover approach.
• Produce and maintain the Technical Design Document (TDD), including low level component diagrams, at a level of detail a client engineering team can implement against.
• Establish and maintain a Key Design Decision (KDD) log capturing the rationale for major architecture choices, for example service equivalency decisions such as Cloud Run versus other compute options.
• Build and maintain a Migration and Rollback Plan, and an accurate, current Component Inventory of everything in scope for migration.
• Run weekly governance and status reporting, and maintain a Deliverables and Acceptances Log so the client always has a clear, current record of what has been delivered and approved.

Migration Execution:

• Author and maintain Terraform modules for OpenStack (Nova, Neutron, Cinder, Octavia) and AWS (EC2, VPC, EKS, RDS, ALB, IAM).
• Integrate Ansible for VM-level configuration management on OpenStack bare-metal and instances.
• Enforce IaC policy compliance using Checkov, OPA/Conftest, and tfsec before every terraform apply.
• Maintain DRY, versioned, reusable module registries in GitLab or S3-backed Terraform registries.

Kubernetes Container Platform:

• Diagnose and resolve codebase divergence between environments, including establishing a snapshot and reconciliation approach where none currently exists.
• Lead migration of core services, including compute, container workloads, and identity/authentication, from the source cloud to GCP equivalents.
• Own data migration validation where the target uses a different database engine than the source (for example, a document or key-value store migration such as DynamoDB to Firestore), including building or reviewing validation scripts and consistency reports.
• Define and implement a cross-cloud connectivity approach (private networking between environments) for the duration of the migration.
• Define the scope and implementation of any cross-cloud abstraction layer required to keep the platform portable during and after migration.
• Plan and execute large scale data and feed migrations (dozens of independent feeds or integrations), with a clear enablement and validation package for each.
• Migrate logging and observability tooling, for example a self-managed ELK stack, to GCP native or GCP-compatible equivalents, with log routing fully validated before cutover.

Infrastructure and Compatibility:

• Build and maintain the target GCP landing zone and core infrastructure using IaC, Terraform preferred, so environments are repeatable, reviewable, and version controlled.
• Own the CI/CD pipeline build for the new environment.
• Drive remediation of the service compatibility assessment, translating flagged incompatible services into a prioritized, sequenced backlog ahead of cutover.
• Review pull requests from client engineers where the client team is doing migration work in parallel, and keep that work aligned to the agreed target design.

Cutover and Post-Migration:

• Plan and lead the production cutover, including go and no go criteria, rollback triggers, and a data consistency and parity validation approach.
• Produce platform documentation and operational runbooks, and lead technical handover and enablement sessions for the client s internal team.
• Provide a defined period of post-cutover expert advisory support, including an operational protocol and escalation matrix.

Required Skills and Experience:

• Proven experience leading at least one large scale, production cloud migration end to end, from planning through cutover, ideally cross-cloud.
• Deep, hands on GCP experience across compute (Compute Engine, GKE, Cloud Run, App Engine), data and storage (Firestore, Cloud SQL, Cloud Storage, Bigtable, Memorystore), and networking (VPC, Cloud Load Balancing, Cloud NAT, Cloud DNS).
• Working familiarity with AWS is useful for reading and reasoning about the source environment, for example Cognito, DynamoDB, and Lambda, though deep AWS expertise is not required for this role.
• Advanced Terraform experience, including reusable modules, state management, and automated deployment workflows.
• Experience migrating between different database engines, including designing or validating data consistency and correctness checks.
• Strong troubleshooting skills across distributed systems, using Cloud Logging, Cloud Monitoring, and Cloud Audit Logs for root cause analysis.
• Demonstrated ability to write clear technical design documentation, and to run structured governance and status reporting for a client or stakeholder audience.
• Comfortable owning ambiguous, partially defined scope and turning it into a documented, sequenced plan under time pressure.

Preferred Qualifications:

• Experience migrating identity and authentication between cloud providers, for example Cognito to an equivalent GCP or third party identity service.
• Experience migrating self-managed Elasticsearch or ELK deployments to managed or cloud native alternatives.
• Working knowledge of cloud security fundamentals, such as IAM, least privilege, Secret Manager, and VPC Service Controls, sufficient to keep the migrated environment secure by design. This is not primarily a security hardening role.
• Experience standing up a post go-live managed services capability: ongoing monitoring, operational efficiency improvements, and automated operational actions.
• Experience with data sovereignty sensitive or regulated workloads, and with multi-region deployments.

Interview Process

• 2 Technical Rounds

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.