I build backend systems because I genuinely enjoy the chaos of distributed architecture, async workflows, queues, caching, databases, and services all somehow cooperating without collapsing into smoke.

There’s something ridiculously satisfying about watching dozens of tiny moving parts work together like a machine nobody notices until it stops working.

Backend engineering feels less like programming and more like designing an invisible city: services talking to services, events triggering pipelines, containers spinning up, logs screaming for attention, caches saving everyone’s lives quietly in the background.

That stuff is fun to me.
Concerning? Probably. But still fun.

• designing microservice architectures
• building event-driven systems
• making APIs fast enough to feel unfair
• debugging weird distributed system issues
• optimizing databases nobody wanted optimized
• building internal platforms that teams actually rely on
• turning “temporary fixes” into things that survive production

I love understanding how systems behave under pressure.
The moment traffic spikes, queues back up, memory usage starts climbing, and everything gets slightly cursed?
That’s where engineering gets interesting.

Most of the stuff I enjoy lives far away from shiny UI buttons.

I like:

• backend architecture
• infrastructure
• system design
• async processing
• observability
• reliability
• scaling problems
• platform engineering
• making complicated systems feel simple

The frontend exists too, respectfully.
I touch it when necessary and then quietly return to the server room.

Node.js, TypeScript, NestJS, Express, Redis, PostgreSQL, MongoDB

Kafka, BullMQ, Docker, Kubernetes

Prometheus, Grafana, Loki

AWS, EKS, Helm

React, Next.js

• I think in systems, not isolated features
• I read architecture diagrams for fun
• I like tracing requests across services
• I overthink naming things
• I enjoy refactoring ugly code a little too much
• I will absolutely open Grafana dashboards just to “check something”

I like breaking systems apart just to understand how they work.
Then rebuilding them cleaner.

Good backend engineering is invisible.

Nobody celebrates it when everything works.
But the second it fails, suddenly everyone becomes a distributed systems expert.

“Some people enjoy sunsets.
I enjoy watching healthy queues and stable response times.”

My commit history is powered by caffeine, curiosity, and occasional production fear.