I build the systems you never see — but always rely on.
Kafka consumers eating 1B+ daily events. YouTube billing for 2B+ users.
Backend is where the real work happens.
5+ years in the trenches at Google, Salesforce, and Walmart. My specialty is the stuff most engineers shy away from — high-throughput distributed systems, complex data pipelines, and backend infrastructure that has to work every single time, at scale.
I've shipped Kafka consumers processing 1B+ daily events, led teams that delivered $60M+ in new revenue, and optimized pipelines serving millions of warehouse units. The best systems are invisible — and I like building those.
Led a team of 4 at a hackathon to build a voice-driven e-commerce assistant. Search by voice, get sentiment analysis, manage orders — all via ChatGPT. We won.
A Selenium-powered Instagram bot that auto-logs in, tracks engagement, scrapes hashtags, and builds an influencer database. Because manual is slow and scripts are forever.
A backend engineer's take on personal branding. No frameworks, no npm install, no bundle size anxiety. Just HTML, CSS, vanilla JS — and a lot of Claude Code.
AWS Lambda + DynamoDB — a tiny backend that counts every visit to this page. Zero servers, zero maintenance, $0/month. This page: loading… visits.
Got an interesting engineering problem? A hard distributed systems question? Or just want to nerd out about Kafka? I'm in.