Senior Backend Architect · 7+ years · Node.js, NestJS, TypeScript, AWS I build multi-tenant SaaS backends and real-time systems that hold up in production.
Currently Sr. Backend Architect at ZMC Technologies, shipping backend infrastructure for AI-augmented messaging, real-estate SaaS, and business-automation platforms.
The recent thing I'm proudest of: I took a hot-path API from ~200ms to ~20ms by flattening the queries, adding the right index, dropping in a cache-aside layer, and cutting the serialization down to what the caller actually needs. I rebuilt the whole technique in a public repo: api-latency-case-study. Clone it, docker compose up, npm run bench, and you can watch the delta on your own machine.
I design multi-tenant NestJS backends: how the tenants are isolated, where the domain boundaries live, and how the background workers stay honest when the queue backs up.
I chase latency the boring way, by measuring. Query plans, connection pools, cache layers, serialization. Whichever one is lying about the p95, I want the number before and the number after.
I build ingestion pipes for AI-augmented messaging. WhatsApp, Messenger, Instagram, web chat, with the pieces that stop the LLM from ever finding out a delivery failed: idempotency keys, retry with backoff, dead-letter queues.
I own the whole path from schema to deploy. Not just the middle. Postgres and Mongo schemas, Docker, Nginx, PM2, GitHub Actions, AWS and DigitalOcean.
Client work delivered through my dev agency Prokken and, more recently, as Sr. Backend Architect at ZMC. Most of the source is under NDA, so the list below is what you can go visit. I'm happy to walk through architecture and what was specifically mine in an interview.
Between 2021 and 2025 I founded and solo-engineered two SaaS products through my own agency Prokken:
- A unified social-media publishing and analytics API (same category as Buffer or Hootsuite).
- A unified sales / messaging inbox aggregating Email, LinkedIn, WhatsApp, Instagram, and Telegram into a single Kanban-based CRM (same category as Front or Missive).
Both were acquired by US SaaS companies in 2025. Product names, acquirer identities, and terms are covered by acquisition NDAs and cannot be listed publicly. Contracts and NDAs on file; happy to walk through architecture, my specific technical scope, and provide documentation under mutual NDA in an interview.
- mallahyari/system-design-visualizer#4 - I added Google Gemini as an alternative provider to OpenAI for the image-to-diagram analysis. Merged upstream in Dec 2025.
Language and runtime: Node.js, TypeScript Frameworks: NestJS, Express, Next.js Data: MongoDB, PostgreSQL, MySQL, Redis Messaging and realtime: BullMQ, RabbitMQ, MQTT, Socket.io, Redis Pub/Sub, WebSockets Cloud and ops: AWS, DigitalOcean, Docker, Nginx, PM2, GitHub Actions Testing: Jest, Supertest, Cypress, autocannon Cross-cutting: GraphQL, REST, webhooks, multi-tenant SaaS, caching, performance
LinkedIn · Email · Portfolio · Telegram · WhatsApp · YouTube
