Ratan Sanjay

I get genuinely excited breaking down how large systems handle scale — how databases choose consistency over availability, why event-driven architectures win at certain problem sizes, and when a monolith is actually the right call. I spend time reading about distributed systems, message queues, and caching strategies even when a project doesn't demand it.

The TCP handshake, DNS resolution chains, HTTP/2 multiplexing — understanding what actually happens between a browser and a server makes me write better APIs. I find it hard to build reliable networked software without knowing what's happening at the transport layer, so I keep digging deeper.

Pursuing Google's Cybersecurity Certificate and Cisco certifications isn't just credential-chasing — I'm genuinely curious about threat models, secure-by-default API design, and why most vulnerabilities come down to trust boundary mistakes. I apply this to how I design auth flows and handle user data in my own projects.

I care about what happens below the framework level: how the OS schedules processes, why memory layout matters for cache performance, what a compiler does to my loops. This layer doesn't show up in user stories, but it's where the 10x performance wins come from — and understanding it makes debugging feel like reading instead of guessing.

Beyond making things work, I care about making them maintainable. I think about naming, separation of concerns, and keeping complexity local. Not for aesthetics — but because messy code slows teams down and erodes confidence in the codebase. Good structure is a product decision, not a luxury.

I keep a reading list of engineering blogs, research papers, and post-mortems from companies like Cloudflare, Stripe, and Notion. Real system failures teach more than any textbook. I treat learning like a background process — always running, not a sprint before an interview.