Building the systems behind the software
I’m a Senior Staff DevOps Engineer at Experian. My work brings together cloud infrastructure, platform engineering, automation, and reliability — the pieces that help teams ship software and keep it running.
Over the past decade, I’ve worked on AWS infrastructure, internal developer platforms, delivery workflows, and Python services. The part I keep coming back to is turning a recurring problem into something simpler and reusable: an API, an automated workflow, or a platform capability that makes someone else’s work easier.
Experience gives you better questions
Working with a tool and understanding what happens underneath it are different kinds of knowledge. I want to keep strengthening that second kind: how Linux manages a process, how memory behaves, and what happens as a request travels across a network.
That’s the thread running through this notebook. I’m revisiting operating systems and networking deliberately, connecting the fundamentals to the cloud and platform work I do.
Why GurujiX exists
Writing helps me find the gaps in my understanding. A lab makes an explanation testable. Teaching a concept makes me ask whether I can explain it without hiding behind terminology.
I’ve shared AWS and DevOps concepts through DevOps Monk, workshops, and mentoring. GurujiX brings that same impulse into a personal space: useful explanations, honest experiments, and projects with the reasoning left in.
If you’re curious about the systems beneath the software, I hope something here helps a concept click — or gives you a good question to investigate next.
Let’s talk
Have an engineering question, an idea to explore, or a different take on something I’ve written? I’d love to hear from you.
Drop me a line at cvamsikrishna11@gmail.com, or connect with me on LinkedIn.
Step into the notebook ↗