About

Hey, I’m Rishi! I’m a staff-level reliability engineer and technical leader based in Chicago.

I like following hard problems wherever they lead. I started my career in front-end development, expanded into full-stack engineering, and eventually moved deeper into CI/CD, developer tooling, cloud infrastructure, platform engineering, and site reliability.

That shift came from a simple interest: making complex systems easier to build and safer to operate.

Over the past decade, I’ve helped scale reliability teams, improve system performance, strengthen delivery workflows, tune databases and APIs, build internal developer tools, and reduce annual cloud costs by more than $1 million. I care about technical quality, but I care just as much about whether the work creates real value for the business and the people who depend on it.

I don’t see systems and people as separate problems. Reliable software depends on clear plans, useful tools, focused work, thoughtful communication, and teams that trust one another.

How I work

I follow my curiosity

At my first job, I earned the nickname “Spelunker” because I was always digging through unfamiliar parts of the codebase. That instinct has stayed with me. I like understanding how things work across layers, finding the real source of a problem, and sharing what I learn with the people around me.

I optimize for lasting impact

Fixing the immediate problem matters. Leaving behind better tooling and documentation makes the next problem easier to solve. Shared practices also help the team avoid solving the same problem twice.

I lead with empathy

Engineering is a human system. I try to create an environment where people can ask questions, challenge assumptions, take ownership, and grow. I believe teams do their best work when expectations are clear and people feel trusted.

What I write about

This site is where I work through ideas and share what I’m learning.

My writing moves between the technical details of software and the way engineering teams work. I may dig into PostgreSQL or build systems, then turn to project planning, imposter syndrome, or what it takes to disconnect from work.

Those topics belong together for me because software is shaped by more than code. The systems we run reflect how teams make decisions and how they support the people doing the work.

Outside of work

I’m usually reading, trying a new restaurant, dancing whether or not anyone else is, or occasionally playing League of Legends with friends. I’m always interested in new ideas, new food, and conversations that change how I think.

You can connect with me on LinkedIn if you want to talk about reliability, developer effectiveness, engineering culture, or something I’ve written.