> Markdown version of [/jobs/ext/3776034-sr-cloud-application-migration-engineer-azure-cloud-migration](https://www.wearedevelopers.com/jobs/ext/3776034-sr-cloud-application-migration-engineer-azure-cloud-migration). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Sr. Cloud Application Migration Engineer Azure Cloud Migration - **Company:** People Force Consulting Inc. - **Location:** United States - **Experience:** Expert - **Contract:** Contract - **Skills:** Application Programming Interfaces (APIs), Amazon Web Services, Microsoft Azure, Big Data, Software as a Service, Databases, Data Validation, Data Integrity, Software Design Documents, Disaster Recovery, Domain Name System (DNS), Middleware, Network Topologies, Identity and Access Management, Virtual Private Networks (VPN), Microsoft SQL Server, SQL Azure, PCI Data Security Standards, Role-Based Access Control, Smoke Testing, SQL Databases, Google Cloud, Enterprise Software Applications, Load Balancing, Azure Data Factory, Database Migration, Build Management, Bicep, Cloud Migration, CIS Benchmarks - **Published:** October 16, 2026 - **Apply:** https://www.dice.com/job-detail/97b2c43c-5a60-43a2-83d0-d8ed79ece2bb ## About the Role 15+ years of experience supporting enterprise applications or infrastructure migrations 10+ years in cloud/infrastructure engineering, with a minimum of 5 years in Azure specifically (AWS/Google Cloud Platform experience does not substitute). Led at least two end-to-end Azure data center migration programs - from landing zone design through production cutover and hypercare exit. Personally executed production cutovers using Azure Migrate, including DNS cutover, replication failover, and post-migration application validation. Authored Bicep or ARM IaC for multi-application Azure environments - not just used existing modules, but written them. Migrated or managed SQL Server in Azure - shared instances, Always On configuration, or database migration using Azure Database Migration Service. Worked in a regulated environment (HIPAA, PCI-DSS, FedRAMP, or equivalent) - understands the difference between 'deployed in Azure' and 'compliant in Azure'. Experience working in healthcare ## Description We are seeking an experienced Lead Cloud Migration Engineer to support a large scale data center migration to Microsoft Azure for a healthcare payer organization. This role is a key contributor within the migration factory, responsible for executing repeatable migration activities across multiple waves, including building target environments, coordinating testing, executing cutovers, and managing post go live stabilization. The Lead Cloud Migration Engineer is the single technical authority for the Azure migration program. This is not a pure advisory or design role - you will design, build, validate, and execute. You will set technical standards, own the infrastructure-as-code delivery, lead cutover nights, and be accountable for the technical integrity of every migration from Wave 1 through Wave 4. The right person brings both architectural depth (landing zone design, governance, security baselines) and hands-on migration execution experience (Azure Migrate, ASR, Bicep, DNS cutover, rollback procedures). If you have only designed on whiteboards, this is not the right role. If you have only executed migrations without owning the architecture, this is not the right role. We need both. The ideal candidate is hands on, highly organized, and comfortable operating in structured, wave based migration programs within regulated healthcare environments (HIPAA/HITECH), where precision, communication, and operational rigor are critical. Key Responsibilities Design and own the Azure Landing Zone: hub-and-spoke network topology, ExpressRoute/VPN connectivity, NSG policy, DNS zones, subscription and management group hierarchy. Build and maintain the Bicep/ARM module library - the authoritative IaC for all migrated workloads. Every infrastructure component is code; no manual provisioning in production. Define and enforce naming conventions, tagging taxonomy, RBAC model, Azure Policy assignments, and resource lock strategy across all waves. Lead the technical discovery for each application - validate scope, document dependencies (shared SQL instances, integration endpoints, certificate chains, service accounts), and produce the migration design document. Own the Azure Migrate project: configure replication, monitor replication health, manage test failover cycles, and sign off on replication readiness before each approval block opens. Author and maintain the technical runbook (playbook) for every application cutover - step-by-step execution sequence, rollback triggers, decision points, and owner assignments. Lead cutover execution on production nights: execute the runbook, manage the technical team, make rollback decisions within the agreed time box, and confirm application health before declaring success. Validate DNS cutover, SSL/TLS certificate continuity, IP allowlist updates, firewall rule migration, and F5/load balancer reconfiguration as part of every cutover sequence. Manage shared SQL instance migrations - coordinate multi-application joint cutovers, validate data integrity post-migration (row counts, checksums, referential integrity). Support the Enterprise Architecture review gate in each approval block - produce the technical evidence package (network diagram, Bicep validated, security controls mapped, DR tested). Ensure every migrated workload meets BCDR requirements: Azure Backup policy, Azure Site Recovery replication (where applicable), RPO/RTO validation, and DR test evidence. Serve as the primary technical escalation point for the delivery team and the QA Engineer during non-production testing, the approval block, and hypercare. Provide technical input to the CAB submission package - confirm the runbook is approved, Bicep is validated, all pre-cutover checks are complete, and the rollback procedure is tested. Lead technical retrospectives after each wave - capture lessons learned, update the IaC library, refine the approval block evidence template, and communicate changes to the program team. Mentor junior cloud engineers on Bicep authoring, Azure Migrate configuration, and migration runbook structure. Manage the relationship with managed service provider, and application vendors where vendor involvement is required for migration. Migration Factory Execution Execute standardized migration factory processes across multiple application waves Build and configure target environments in Azure following approved landing zone and platform standards Support re hosted, re platformed, and lightly modernized applications Ensure readiness of infrastructure, middleware, and application dependencies prior to migration Environment Build & Readiness Coordinate provisioning of compute, storage, networking, security, and access for target environments Validate environment readiness against migration and security checklists Partner with platform, network, security, and IAM teams to resolve blockers Ensure target environments meet performance, availability, and compliance requirements Testing Coordination & Validation Coordinate and support application, integration, performance, and user acceptance testing (UAT) Validate connectivity to upstream and downstream dependencies (databases, APIs, batch jobs, vendors) Track test defects and coordinate remediation with application and infrastructure teams Ensure formal sign off prior to scheduled cutovers Cutover & Go Live Execution Execute application cutovers according to approved runbooks and schedules Coordinate activities across application, infrastructure, network, security, and business teams Support data validation, smoke testing, and functional verification post cutover Ensure minimal disruption to business operations during go live events Post Go Live Stabilization Own post go live (hypercare) support windows for migrated applications Monitor application behavior and coordinate rapid issue resolution Track and document post migration defects and lessons learned Support formal transition to steady state operations upon stabilization Documentation & Reporting Contribute to migration runbooks, wave plans, and readiness artifacts Maintain accurate migration status, risks, and issues Provide input to continuous improvement of migration factory processes Support audit and compliance documentation as required