Job Description & Details
This is a senior-heavy architecture role where you won't just be drawing diagrams; you'll be actively driving massive enterprise cloud transformations and legacy Java app modernizations. If you enjoy untangling complex infrastructure bottlenecks and scaling Kubernetes platforms, this gig has your name on it. It requires someone who can walk the talk and lead engineering teams through high-stakes cloud migrations.
What You'll Actually Be Doing
Your day-to-day will involve designing resilient multi-tenant environments on GCP, setting up robust CI/CD pipelines, and writing clean Terraform code to provision infrastructure at scale. You'll spend a good chunk of your time figuring out how to migrate monolithic Java applications into containerized microservices running on Kubernetes without breaking production. Expect to collaborate heavily with security, development, and leadership teams to ensure cloud governance doesn't slow down feature delivery.
The Core Tech Stack
You need deep, battle-tested expertise in Google Cloud Platform, Kubernetes (GKE), and Terraform as an Infrastructure-as-Code standard. Because this role heavily focuses on modernizing legacy systems, strong familiarity with Java application architecture and modern CI/CD tooling is absolute non-negotiable. If you haven't spent years managing production-grade GCP environments and debugging container orchestration issues at scale, you're going to struggle here.
Interview Expectations
Be ready for the hiring manager to grill you on advanced Kubernetes networking and failure modes—they'll likely ask you to troubleshoot a complex cluster outage scenario where pods are failing to resolve DNS and traffic routing is bottlenecked. They want to see how you systematically debug under pressure rather than just guessing solutions. You should also expect a deep dive into your Terraform state management strategies and how you handle zero-downtime migrations for stateful Java workloads in the cloud.
Application Advice
Make sure your resume doesn't just read like a laundry list of tech buzzwords; highlight specific cloud migration metrics, such as how many nodes you managed or how much you reduced deployment times using Terraform and CI/CD. Explicitly weave keywords like 'Google Cloud Platform', 'Kubernetes', 'Terraform', and 'Java application modernization' directly into your work history bullets to easily clear the ATS filters and prove you have the exact enterprise scars they are looking for.