I build backend systems that don't fall over at 3am — and occasionally win the war against Kubernetes YAML.
I'm a senior backend engineer with ~5 years in the trenches — mostly Python, mostly Django, mostly convincing distributed systems to behave. My favorite kind of bug is the one that only shows up in production, at scale, right after everyone's gone home.
Lately I've been:
- 🏥 Building HIPAA-compliant infrastructure for a telehealth platform, with LLM workflows woven in
- 🩺 Architecting a clinic management platform from scratch — patient app, doctor app, staff portal, the whole stack (React Native/Expo + Next.js + Supabase)
- 🧩 Nerding out over RLS policies, async pipelines, and the occasional deep dive into neural nets just for fun
- 🚀 Thinking about SaaS products that solve real problems for real markets, not just resume-driven development
Not currently building: another to-do app.
| Layer | Stack |
|---|---|
| Backend | Django, DRF, Flask, Celery, Redis |
| Frontend | React, React Native (Expo), Next.js, Redux |
| Data | PostgreSQL, MySQL, MongoDB, Supabase |
| Infra | AWS (EKS, RDS, EC2, S3, Lambda), Kubernetes, Docker, GCP |
| Currently learning | LLM workflow infra, semantic search, formal verification (because apparently 3 jobs isn't enough) |
I'm always up for a conversation about backend architecture, healthcare tech, or why your Celery queue is silently dying. Reach out — I reply faster than most of my Kubernetes pods restart.
Built with Python, caffeine, and a mild distrust of anything that "should just work."