Backend Developer — Distributed Systems, Networking & Low-Latency Applications
I've spent the last 7 years building backend systems — mostly distributed infrastructure, network protocols, and things that need to handle a lot of traffic without falling over. I care about writing efficient code: safe memory handling, solid concurrency, and cutting out latency wherever it hides.
- High-Load Infrastructure & Scalability: Distributed systems and microservices that can take a beating — high concurrent traffic, minimal downtime.
- Low-Level & Network Engineering: Comfortable close to the metal — TCP/IP, raw sockets, async I/O, and custom protocols when the standard ones don't cut it.
- Security & Cryptography: Building auth systems, encrypting data in transit, and keeping things memory-safe across distributed setups.
- Performance Optimization: Profiling memory usage, cutting unnecessary allocations, tuning GC behavior — basically making things run lean.
Depending on what a project needs, I reach for one of these — from low-level performance work to full-stack delivery:
| Language | Where I Use It |
|---|---|
| Go | Microservices and concurrent backend services — my go-to for REST/gRPC APIs. |
| Rust | When things need to be fast and safe — low-level tools, performance-critical code. |
| Java | Enterprise backend work and distributed systems that need to scale. |
| Python | Automation, quick prototypes, and async services. |
| TypeScript | Full-stack work where type safety actually matters. |
| JavaScript | Web interfaces and Node.js — the usual async stuff. |