Migration Engineer

You will run migrations end to end. Scoping an estate, designing the target,

planning the waves, doing the cutovers, and being the person who stays calm

when something does not behave the way the runbook said it would.

This is hands on. You will spend your time in the AWS console and the CLI, in

Linux and Windows servers, and in migration tooling. It is not a project management job with a technical title.

What you will do

Run discovery across customer estates: build the inventory, map the dependencies, and work out what breaks when each piece moves. Most of the risk in a migration is found here or not at all.

Plan the migration. Wave design, sequencing, cutover windows, rollback positions, and the assessment that tells a customer honestly what this will cost them in time and disruption.

• Have you worked in Migration Projects ?
• Do you have any experience in AWS Cloud ?

CloudiQS is a UK AWS Advanced Tier Services Partner and managed service

provider. We are AWS only, which means our engineers go deep rather than wide.

We move customers off ageing estates and onto AWS, and we run what we build afterwards.

We are small enough that your work is visible and the customers are real. UK

businesses with production systems and genuine consequences if a cutover goes wrong., Design target architectures on AWS, and increasingly on HPE VM Essentials as customers move off VMware.

Build and run migrations using RiverMeadow, AWS Application Migration Service and AWS Database Migration Service.

Write the infrastructure rather than clicking it. CloudFormation, Terraform, Python and Bash.

Rebuild the services that underpin an estate on the far side: DNS, DHCP, Active

Directory, file and print, certificates. These are what actually decide whether a Monday morning goes well.

Run the cutovers, including out of hours, and the rollbacks when they are needed.

Write the runbooks and low level designs that let the next engineer do it without you.

Hand the result to our managed service team and support it while it beds in.

What we need

Real migration experience. At least one estate moved to AWS that you can talk

through in detail, including what went wrong.

Discovery and planning, not just execution. You can walk into an undocumented

estate, work out what is there, and produce a wave plan a customer will sign.

VMware vSphere in anger. vCenter, ESXi, datastores, and the habits of estates

that have been running for a decade.

Strong Linux and Windows Server administration.

AWS to a working depth: VPC design, EC2, IAM, S3, and the networking that joins them together.

Automation rather than repetition. Bash and Python, or PowerShell if that is your background.

Infrastructure as code, CloudFormation or Terraform.

Core network services, properly. DNS and DHCP design rather than just

configuration, Active Directory sites and services, and what happens to all of it when the underlying addresses change.

Networking you can reason about under pressure. Routing, firewalls, VPNs, load

balancing, and what a packet actually does.

Useful, and we will teach you the rest

HPE VM Essentials or Morpheus. Database migration work across SQL Server,

MySQL, PostgreSQL or Oracle. Hyper-V, Nutanix or other hypervisors you have

moved workloads off. Backup and disaster recovery tooling. AWS certifications,

though we care more about what you have built.

You do not need Kubernetes, application development, or a long list of

programming languages. We would rather you were strong at the things above.

What you get

Work that ships. Migrations have an end date and a result you can point at.

AWS depth rather than a thin layer across three clouds.

Certification and training paid for, and the time to do it.

A say in how we work. We are still small enough that good ideas land.