┌─────────────────────────────────────────────────────────────┐
│ │
│ $ whoami │
│ > arshdev singh │
│ $ describe --brief │
│ > backend engineer. microservices nerd. bug whisperer. │
│ │
└─────────────────────────────────────────────────────────────┘
I build things for the internet — mostly the parts you don't see.
Distributed systems, event-driven architectures, and the occasional rabbit hole (pun intended, RabbitMQ is real).
I'm a full-stack engineer with a strong pull toward the backend — the kind of engineer who loses sleep over message delivery guarantees and gets unreasonably excited about distributed system patterns.
languages:
fluent: [TypeScript, JavaScript]
functional: [Java, C++]
backend:
runtime: Node.js
frameworks: [Express.js, NestJS]
messaging: [RabbitMQ, BullMQ]
patterns: [Outbox-Inbox, BFF, Microservices]
frontend:
ui: [React.js, Next.js, Redux]
styling: [TailwindCSS, ShadCN, MUI]
databases: [PostgreSQL, MongoDB, Redis]
devops:
containers: Docker
ci: GitHub Actions
cloud: Cloudflare R2
tools: [Git, Postman, VS Code, IntelliJ, Linux]Because love is more fun when there's a message queue involved
A high-concurrency dating platform with a microservices backbone. WebSocket chat that held 200+ simultaneous connections without breaking a sweat. A two-phase media upload pipeline that kept storage lean with automated orphan cleanup. Built to be fast, fault-tolerant, and surprisingly smooth.
TypeScript Node.js Next.js RabbitMQ Socket.io MongoDB Redux TailwindCSS
Zero message loss. No, seriously — zero.
A deep-dive into distributed reliability. Implemented the Outbox-Inbox pattern across 3 microservices to guarantee exactly-once semantics. Layered in a 3-stage fault tolerance pipeline: immediate retries → exponential backoff → dead-letter isolation. The kind of system that doesn't panic when a service crashes mid-flight.
TypeScript NestJS RabbitMQ PostgreSQL TypeORM Docker
- 🧩 368+ LeetCode problems — graphs and DP are basically therapy at this point
- 🐇 I've named more RabbitMQ queues than I'd care to admit
- 📡 Genuinely fascinated by what happens at the boundary between reliable and unreliable systems
- ☕ Debugging is just reading the stack trace at the right zoom level
Currently: building cool stuff @ Zenmonk · Open to opportunities · Always up for a good system design convo
Ship it. Learn from it. Build it better.


