I am a tech lead. I work at Tata Consultancy Services, mostly on backend systems, platform engineering, and the unglamorous parts of distributed systems that decide whether anything else works.
I write here occasionally, mostly when something I learned on the job feels general enough to share. The recurring themes are API design, databases, observability, Go and JavaScript, and the small operational decisions that compound over time.
I keep a low personal footprint online by choice. The blog is the most accurate picture of how I think about the craft.
Mohd. Hamza Shaikh Platform Engineer & Tech Lead - TCS Labs
I’m a Platform Engineer with six years of experience designing, scaling, and securing enterprise-grade infrastructure. I currently serve as a Tech Lead within TCS Labs - a Center of Excellence operating independently from core corporate IT governance - where my team builds a next-generation Internal Developer Platform for one of the world’s largest organizations.
My career started in 2020 at Tata Consultancy Services, where I graduated into a two-year consulting placement focused on monolithic Java applications. That work was grounding, but the real turning point came in my third year when I joined the Meshery project through an LFX internship. That experience cracked open the cloud-native world for me. I got comfortable with CNCF technologies, the open source way of working, and - perhaps most importantly - a completely different philosophy about what infrastructure should do for developers.
Following the internship, I was invited to join a small, newly formed team backed by two TCS senior leaders as executive sponsors. That team became TCS Labs, and the platform we’re building sits on a CNCF-native stack with Meshery at the center. Meshery’s ability to serve as a service provider-grade, multi-tenant, and highly customizable platform - with collaboration built in and integrations across AWS, GCP, Azure, and the broader CNCF ecosystem - made it the right foundation. It didn’t just shape my early career; it permanently changed the trajectory of it.
Today, my mandate at TCS Labs is to architect and lead one component of an IDP designed to serve an organization with hundreds of thousands of employees and clients. The hardest problems I work on live at the intersection of scale, isolation, and usability:
Outside of TCS Labs, I’m an active contributor to Meshery and the Meshery Operator, working primarily in Go and TypeScript. My open source contributions have earned me GitHub’s “Pull Shark” and “Pair Extraordinaire” badges - but what I’m more proud of is the collaborative culture those reflect.
One thing that sets me apart from most infrastructure engineers: I genuinely care about design. I maintain projects like awesome-design-systems and custom vscode-icons because I believe internal developer tools deserve the same craft and intention as consumer products. A platform that’s hard to use is a platform that doesn’t get used.
I describe my relationship with open source as “happy go lucky” - and I mean it. I mentor junior engineers making the shift from traditional IT to platform engineering, and I spend my downtime at the intersection of design and code: custom developer workflows, aesthetic terminal environments, unified design systems for internal tooling.
Infrastructure should empower developers. That’s the principle I build everything around.