- 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
- 14engineering teams onboarded to the AI toolchain
My recent work
DevToolkit
Paste a docker-compose file and get Kubernetes manifests you can apply, or a Helm chart. I built DevToolkit as the home for the specific config conversions people still do by hand, with 7 more converters planned for 2027.
Live at devtoolkit.cloud.run. Health checks, startup order and volumes come out as working Kubernetes, and only what has no Kubernetes match stays as a note.
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 the jobs onto TeamCity and the internal deployment system team by team until no jobs were left, then shut the servers down.
One delivery path, one less platform to babysit and $54k a year saved on servers and agents. In on-demand test 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 designed the migration and built self-service scripts that scanned each stack and gave its team the exact steps.
13 teams migrated their own stacks off the deprecated runtimes and off Jenkins, each on its own schedule.
Shared AI platform
I designed a shared AI platform on EKS where every app and workflow calls one LiteLLM gateway and only the gateway talks to Bedrock, with per-team keys, cost caps and audit logs. I picked the AWS region, set up Bedrock and n8n and proposed Argo CD for deploys, which the design review adopted.
17 internal apps and workflows and 6 teams outside my own run on one governed platform, with spend tracked per team.




