- Build time60+ min down to 20
- Test environment start25 min to 5
- Serverless stacks migrated297
- Repositories moved to GitHub~500
- MCP tools behind one gateway92
Zain Baloch
I make infrastructure invisible to the teams building on it, so they ship fast and stay secure.
Google Data Analytics ProfessionalGoogle · 2025
AWS Certified DevOps Engineer - ProfessionalAmazon Web Services · 2024
HashiCorp Certified: Terraform Associate (003)HashiCorp · 2024
Certified Jenkins EngineerCloudBees · 2024
Magento Certified Developer PlusAdobe Commerce · 2017
- Cloud
- Infrastructure
- Delivery
- AI platform
- Code
- 297serverless stacks migrated by the 13 teams that owned them
- ~500repositories moved from Bitbucket to GitHub
- 92internal tools behind one MCP gateway
- 28engineering teams onboarded to the AI toolchain
My recent work
Jenkins retirement
Jenkins got slower the longer it ran. Stuck processes, a main process at 18GB, scheduled restarts to keep it alive and big repositories timing out on checkout. I moved every job onto TeamCity and the internal deployment system team by team until Jenkins was gone.
One delivery path and one less platform to babysit. In dynamic environments an app deploy now takes about 5 seconds, where Jenkins took minutes.
Serverless migration framework
297 serverless stacks owned by 13 teams sat on runtimes heading for end of life, with their pipelines going away alongside Jenkins. I built self-service scripts that scanned each stack and output the exact steps and the infrastructure team handled the Terraform side.
13 teams migrated their own stacks off the deprecated runtimes and off Jenkins, each on its own schedule.
Build once, deploy anywhere
ECS, EKS, Lambda and frontends each had their own build and release path, so the same change behaved differently depending on where it landed. I led one packaging model for all of them, from design to implementation with several teams, where an artifact is built once and promoted between environments untouched.
35 components onto TeamCity, 25 onto the deployment system and P95 deployment time down 8 minutes 41 seconds.
Shared AI platform
Teams were each setting up their own model access, with per-team spend hard to attribute. I built one platform on Bedrock and EKS with a LiteLLM gateway for per-team keys and cost control, deployed with Argo CD. A teammate built the LiteLLM and Onyx pieces from the plan.
The AI PR reviewer, n8n automations and the internal assistant all run on one governed platform, with spend attributable to the team that caused it.




