← BACK

Shrinivas Katti

Senior DevOps & Platform Engineer

DevOps journey · Cloud Infrastructure Specialist — GCP · Bengaluru, India

I work on the unglamorous layer: the provisioning, the pipelines, the access paths, the clusters everyone else ships onto. Six years in — currently as a senior DevOps specialist at a consultancy, which means I've rebuilt this layer for consumer-scale companies with very different constraints and learned which parts actually generalise.

The pattern I keep returning to is the same. Take something that only works because one person remembers how, and turn it into something that works because it's written down, peer-reviewed and automated. Self-service instead of tickets. Short-lived certificates instead of a shared bastion key. An alert you trust instead of forty you ignore.

Lately that means AI infrastructure — RAG systems over operational knowledge, LLM observability, the delivery scaffolding that decides whether a model reaches production or just demos well.

01

Runtime Config

not on the resume

$ cat ~/.shrinivasrc

FIRST_SUSPECT
=
"DNS"
# it is always DNS
SECOND_SUSPECT
=
"the YAML indentation"
MOST_TYPED_COMMAND
=
"kubectl describe pod"
PAGER_PHILOSOPHY
=
"if it wakes me twice, I automate it"
GYM_SPLIT
=
"push / pull / legs / incident"
PREFERRED_COMMUTE
=
"two wheels, no traffic"
CAMERA_ROLL
=
"90% bikes, 10% dashboards"
TABS_VS_SPACES
=
"YAML — so neither, and both hurt"
COST_DASHBOARD
=
"open in a pinned tab, always"
DEPLOY_ON_FRIDAY
=
false
# I have learned things

$ uptime
6 years · 4 clouds · 3 continents of latency · 0 unrecoverable outages

02

Contact

I answer everything

Request resume

Leave your email and number and I'll send the resume over on WhatsApp or email — usually the same day.

Your details are used only to send you the resume and reply. Not shared, not subscribed to anything.

Based in Bengaluru, India. Open to platform, SRE and AI-infrastructure work — remote or hybrid.