Enterprise platforms don’t age gracefully. What worked at 200 employees becomes a liability at 2,000 — tightly coupled applications, manually managed infrastructure, deployment processes that require institutional knowledge to operate, and security models that were designed for on-prem and were never meant for cloud-native workloads.
I’m Amit Malhotra, a Principal GCP Architect based in Toronto with 20+ years in IT and 6+ years hands-on with Google Cloud, Terraform, GKE, and DevSecOps. I specialise in the architectural work that makes enterprise modernisation succeed — not just lifting workloads to GCP, but redesigning the platform foundation so it’s secure, automated, and built to support engineering teams for the next decade. I’ve done this across some of the most complex and regulated enterprise environments in North America, including RBC, Tangerine Bank, Telus Health, and Loblaws — environments where getting the architecture wrong has real operational and compliance consequences.
Every enterprise modernisation engagement I run is guided by the SCALE Framework — my structured architectural methodology for GCP platforms. It ensures the platform we build is secure by design, cloud-native, Terraform-automated, DevSecOps-integrated, and built for elastic scalability from day one. It’s what separates a clean modernisation from one that creates new technical debt while resolving the old.
PROBLEMS I SOLVE
I’m typically engaged when an enterprise engineering team is dealing with one or more of these situations — often several at once:
Infrastructure provisioned by hand with no Terraform or IaC foundation — no reproducibility between Dev, Staging, and Production, and configuration drift that causes bugs you can only find in production.
The most common mistake in enterprise modernisation is starting the migration before the architecture is right. I’ve seen teams spend months moving workloads to GCP only to find the security model doesn’t meet their compliance requirements, the network design can’t support their workloads, and the infrastructure has no Terraform automation — just the same manual processes running in a new environment.
My approach is to get the foundation right before anything moves. That means designing the multi-project GCP landing zone, Workload Identity Federation model, Terraform module structure, and GKE cluster architecture first — so every workload we migrate lands on a solid, standardised platform rather than adding to the technical debt.
What I design and implement in enterprise modernization engagements:
What a Modernized GCP Platform Looks Like After We Work Together
Enterprise modernization isn’t measured in lines of Terraform or number of services migrated. It’s measured in what your engineering team can do that they couldn’t before:
When Enterprise Teams Typically Engage Me
I’m typically brought in at one of these inflection points — often when an internal team has hit the limits of what they can solve without an independent architectural perspective:
Planning an Enterprise GCP Modernization? Let’s Start With an Honest Conversation.
Enterprise modernisation projects fail when the architecture isn’t right before migration begins. I start every engagement with a free 30-minute architecture review — an honest assessment of your current GCP environment, what’s worth keeping, what needs redesigning, and what the right sequence is for getting there without disrupting production.
Whether you’re in the early planning stages or mid-way through a modernisation that’s stalled, I work directly with your engineering team — no sales layer, no junior delivery, no hand-offs. Just a Principal GCP Architect with hands-on experience in the environments your platform needs to match.
Book a Free Architecture Review
Based in Toronto (EST), working with engineering teams across Canada & USA
Speak directly with me — a Principal Cloud Architect — about your GCP architecture, security, platform engineering, or MLOps goals. I typically respond within one business day.
✓ Free 30-minute call ✓ No proposal, no pressure ✓ Responds within one business day
