Backend
APIs, real-time communication & server-side systems
- Node.js
- Express
- TypeScript
- WebSockets
- Socket.IO
A little about how I approach engineering.
My engineering journey began with the typical frontend-to-full-stack path, building applications with React and Node.js. But over time, I became more interested in what happens behind the application than what happens on the screen.
That curiosity pushed me further down the stack — exploring databases, networking, reverse proxies, caching, containers, and distributed systems. Today, I focus primarily on backend engineering, infrastructure, and system design, while still being comfortable building modern frontends when needed.
I believe good software engineering goes beyond writing code. Understanding the systems underneath an application helps me build software that is reliable, observable, and designed to scale.
Technologies and engineering concepts I use to build reliable, scalable web systems.
APIs, real-time communication & server-side systems
Data storage, caching & system architecture
Containers, networking & traffic management
Modern interfaces & component-driven development
A real-time communication platform engineered for high-concurrency event broadcasting and resilient connection handling.
How my interests evolved from building applications to understanding the systems behind them.
Focusing on architecture, orchestration, caching layers, networking, and understanding how systems behave beneath the application layer.
Moved deeper into backend engineering — building robust APIs, working with databases, real-time systems, caching, and service architecture.
Started by building modern web applications with the MERN stack and Next.js while learning the fundamentals of the request-response lifecycle.
Open to engineering opportunities, collaborations, and conversations around backend systems, infrastructure, and building things that scale.