Professional Cloud Network Engineer
VPC design, hybrid connectivity, network services and edge security on Google Cloud.
$
I design, automate and operate cloud infrastructure that stays up when it matters. Four clouds, nine certifications, and a strong preference for infrastructure that is written down rather than clicked together.

cloud engineer @ microsoft
aws · gcp · azure · oci
0+
Years in cloud
Since 2021
0
Certifications
4 providers
0
Clouds shipped on
AWS · GCP · Azure · OCI
0+
Workloads migrated
Zero-downtime cutovers
A short version of the last four years, minus the buzzwords.
I'm a cloud engineer who spends his days somewhere between a terraform plan and a kubectl describe. Over the last four-plus years I've moved workloads across AWS, GCP and Azure, replaced click-ops with reproducible infrastructure, and made a lot of 3 AM pages stop happening.
I hold nine cloud certifications across four providers — five of them Google Cloud Professional level — but the part I actually enjoy is the unglamorous work: shaving minutes off a deploy pipeline, writing the module nobody has to touch again, and making the on-call rotation boring.
Right now I work at Microsoft on cloud engineering. Before that I was at Searce, running migrations and platform work for enterprise customers.
Education
B.Tech, Computer Science & Engineering
Lovely Professional University · 2018 — 2022
Regions I have shipped into
Write it down
Anything created by clicking through a console is a future outage. Terraform first, exceptions justified.
Alert on symptoms
A page should mean a user is having a bad time — not that a CPU graph crossed a line somebody picked in 2019.
Boring deploys
The best release is the one nobody notices. Small, reversible, automated, and dull by design.
Least privilege, always
Wide IAM is the debt you only find out about during the incident review. Scope it now.
From a first AWS internship to cloud engineering at Microsoft.
Cloud engineering across the Azure platform — helping enterprise customers land, scale and operate workloads that cannot afford to fall over.
Honest levels. Hover any skill to see what I actually did with it.
Four providers, production workloads on all of them.
5x Professional certified — architecture, network, security, devops
Solutions Architect Associate; EKS, IAM, CloudFormation
Day job — landing zones, AKS, Entra ID
OCI Foundations certified
If it was clicked in a console, it gets written down.
Reusable modules, remote state, drift control
Three-tier stacks, nested templates
Config management for Linux fleets
Azure-native deployments
Clusters across three clouds, centrally managed.
Upgrades, autoscaling, RBAC, troubleshooting
Multi-stage builds, slim images
Managed control planes on all three
Hybrid fleet management
Chart authoring and release management
Deploys should be boring and repeatable.
Build, test, plan/apply, OIDC to cloud
Declarative pipelines, shared libraries
GitOps delivery to Kubernetes
Alerts that map to symptoms, not to CPU graphs.
Exporters, recording rules, alertmanager
SLO dashboards teams actually open
Boundary design across AWS/GCP/Azure
Edge protection and log correlation
Enough code to make the infrastructure behave.
boto3, automation, glue services
The universal cloud duct tape
Reading operators, small CLIs
MySQL, RDS, Cloud SQL
Where all of this actually runs
Migrations, platforms and automation — with the numbers that mattered.
Not a specific customer's diagram — the pattern underneath most of them. Tap any box.
hover or tap a component
Left rail is how code gets to production. Centre is the request path. Right rail is how anyone finds out when it breaks.
Five of them Google Cloud Professional level. Useful mostly because the study forced depth.
VPC design, hybrid connectivity, network services and edge security on Google Cloud.
Access control, data protection and network defence for Google Cloud environments.
Continuous delivery pipelines, SRE practice and service performance optimisation.
Designing secure, scalable and highly available solutions on Google Cloud.
Deploying applications, monitoring operations and managing enterprise solutions.
Designing scalable, fault-tolerant and cost-aware systems on AWS.
Foundational AWS services, architecture, security and pricing fluency.
Core Azure services, cloud concepts, security, privacy, compliance and pricing.
OCI compute, storage, networking and identity fundamentals.
Open to conversations — about roles, architecture reviews, or a migration you would rather not run alone.
Open to conversations
Based in Gurugram, India, comfortable across time zones. Replies usually land within a day.