Cloud Migration Engineer

Further•Cleveland, OH

1d•Hybrid

About The Position

Cloud Migration Engineer You are the engineer clients trust to move their infrastructure to GCP without drama. No data loss, no unplanned downtime, no surprises. You've done this before at production depth — not as a supporting player, but as the person who owned the outcome.Half your work is technical: designing the migration architecture, writing the Terraform that makes it repeatable, and executing the cutover with the discipline that comes from having seen what goes wrong. The other half is client-facing: translating messy real-world infrastructure (legacy systems, undocumented dependencies, nervous stakeholders) into a migration plan that the client can understand and the build team can execute.You use AI to work more efficiently. You don't use it as a substitute for knowing what you're doing. You will sit in our headquarters in Dallas, TX on a hybrid schedule. The team is in office on Tuesdays, Wednesdays and Thursdays.

Requirements

8-12 years of cloud engineering experience, with a track record of owning GCP migrations end to end at production depth.
Proven success migrating production workloads to GCP with no data loss and no unplanned downtime.
You can walk us through a migration you owned, what went wrong, and how you handled it.
Strong Terraform expertise: you write infrastructure as code by default, not as an afterthought.
Multi-cloud fluency: you understand the source environments clients are migrating from and can map their architecture to GCP equivalents without starting from scratch.
Consulting or client-facing experience: you can lead a room, manage expectations, and communicate technical risk to people who don't want to hear it.
Clear, direct written communication: migration plans, runbooks, and handoff docs that someone else can actually use.

Nice To Haves

GCP Professional certifications (Cloud Architect, Data Engineer, or equivalent).
Experience with containerized workloads: GKE, Cloud Run, or equivalent.
Familiarity with data migration tooling: Database Migration Service, Datastream, Transfer Service.
Exposure to compliance requirements in migration contexts: data residency, encryption in transit and at rest, audit logging.
Experience with CI/CD pipeline migration and modernization.

Responsibilities

Migration architecture and planning: assessing client environments, mapping dependencies, designing the target GCP architecture, and producing a phased migration plan that accounts for real operational constraints.
Infrastructure as code: writing and maintaining Terraform configurations that make every migration repeatable, auditable, and reversible where it needs to be.
The cutover: owning the execution of production migrations with zero data loss and no unplanned downtime. You've done this enough times to know where it goes wrong and how to prevent it.
Client communication: running technical discovery sessions, presenting migration plans to non-technical stakeholders, and keeping clients informed at every phase without burying them in detail.
Post-migration validation: performance baselines, monitoring setup, and the handoff documentation that means the client isn't dependent on you forever.