You would design the target architecture before anything moves, then run migrations in waves with defined exit criteria.
We care a great deal about what the estate costs to run and whether recovery objectives have actually been tested. If you have opinions about both, you will fit here.
What you will do
- Design Azure landing zones: subscription topology, identity, networking and policy
- Assess workloads and plan migration waves with explicit exit criteria
- Implement cost governance — tagging policy, budgets, right-sizing and non-production lifecycle
- Design and test backup, recovery and failover, and prove RPO/RTO rather than assert them
- Build infrastructure as code and deployment automation
- Operate hybrid estates as a single environment with consistent identity and monitoring
What we are looking for
- Production Azure experience across compute, networking and identity
- Infrastructure as code, ideally Terraform or Bicep
- Migration experience — you have moved real workloads, not only built greenfield
- Understanding of cloud cost drivers and how to govern them
- Windows Server and Active Directory fundamentals
- Willingness to test recovery properly, including the parts that are inconvenient