Cloud Migration Engineer

<p>WE’RE HIRING! If you love data and are looking for unlimited growth opportunities, we want to talk with you about joining Further.</p> <p>Further is a data, cloud, and AI company whose focus is helping companies turn raw data into the right decisions. We have an <a href="https://www.gofurther.com/who-we-are">award winning culture</a> of extraordinary people. Our purpose is to enable people to thrive so that businesses can thrive. We believe that the work you do should matter - it should be meaningful to you professionally and personally, and it should have a positive impact on both you and our clients.&nbsp; If this sounds exciting to you, let’s chat!</p> <h3>Cloud Migration Engineer</h3> <p>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.&nbsp;</p> <p><strong>What experience should you have:</strong></p> <ul> <li class="whitespace-normal break-words pl-2">8-12 years of cloud engineering experience, with a track record of owning GCP migrations end to end at production depth.</li> <li class="whitespace-normal break-words pl-2">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.</li> <li class="whitespace-normal break-words pl-2">Strong Terraform expertise: you write infrastructure as code by default, not as an afterthought.</li> <li class="whitespace-normal break-words pl-2">Multi-cloud fluency: you understand the source environments clients are migrating from and can map their architecture to GCP equivalents without starting from scratch.</li> <li class="whitespace-normal break-words pl-2">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.</li> <li class="whitespace-normal break-words pl-2">Clear, direct written communic