Backend & Infrastructure Engineer. Distributed systems, real-time control loops, and the observability to prove they work.
I build backend systems that have to hold up under real load, and the tooling that tells you when they don't.
Right now that means real-time robotics teleoperation: streaming controller input through an IK solver into a hardware control loop, and keeping it stable over networks that are anything but. Before that, production Kubernetes and platform work.
What I care about:
- Systems that degrade gracefully instead of falling over
- Observability as a first-class feature, not an afterthought
- Infrastructure and DX work that makes everyone else faster
- Open source, especially the unglamorous CI/CD parts
I contribute where the infrastructure is: CI/CD, observability, and developer experience.
| Org | What I work on |
|---|---|
| OWASP Nest | Backend models and tests, SlackBot automation, schema validation, frontend features |
| LitmusChaos | CI quality gates, contributor onboarding and local setup |
| Palisadoes Foundation | Reusable CI/CD workflows, repo migration, OpenTelemetry observability |
Axon · NestJS React PostgreSQL Redis Gemini GCP
Multi-tenant WhatsApp automation SaaS. Drag-and-drop canvas for building chatbot flows, a provider-agnostic conversation engine, and an LLM fallback for anything off-script.
Wanderlust · AWS EC2 Kubernetes Docker Node.js MongoDB
3-tier cloud-native app on a self-managed Kubernetes cluster. Built DevOps-first, optimizing for infrastructure reliability over feature count.
Languages ·
Backend & Frontend ·
Data ·
Cloud & Ops ·
Building something that needs to stay up at 3am? · Let's talk
Star anything you find useful.