I'm a self-taught software engineer who cares more about how systems actually work than about which framework happens to be trendy this year. My day-to-day tools are Go, TypeScript/JavaScript, Python, and Node.js — but the language is never really the point. The point is what's underneath it: how state gets stored and replicated, how work gets scheduled and distributed across machines, how a system behaves under contention, and how it stays correct when parts of it fail.
I lean backend and systems-heavy, though I'm comfortable shipping a full product end-to-end — including the frontend — when a project calls for it.
"I'd rather understand why something works than memorize that it does."
- 🔭 Currently building goK8s, a from-scratch reimplementation of core Kubernetes internals in Go
- 🧠 Focused on deep, systems-level engineering — distributed systems, concurrency, storage internals, and scheduling — over any single framework or language
- 🧩 Backend-first across Go, TypeScript/Node.js, and Python, with React on the frontend when a project needs one
- ☸️ Comfortable with containerized, orchestrated systems — Docker and Kubernetes
- 🌱 Studying system design in depth — data replication, scaling strategies, contention handling, and real-time delivery patterns
- 🐧 Daily driver: Arch Linux, Neovim
- 🎯 Open to remote software engineering opportunities
The areas I actively study and build around — not just terms I've heard of:
| Area | What I work through |
|---|---|
| 🌐 Distributed Systems | Consistent hashing, sharding, replication, consensus fundamentals |
| 🗄️ Data & Storage | LSM-trees, write-ahead logs, SQL vs. NoSQL tradeoffs, schema design under scale |
| 🔒 Concurrency & Contention | Optimistic/pessimistic locking, distributed locks, atomic operations, queue-based serialization |
| ⚙️ Async & Reliability | Job queues, dead-letter queues, idempotency, backpressure, DAG-based task orchestration |
| ⚡ Real-Time Systems | Long polling, SSE, WebSockets, pub/sub fan-out architectures |
| ☸️ Orchestration | Container scheduling, control loops, reconciliation — the mechanics behind tools like Kubernetes, not just their CLIs |
|
☸️ goK8s A ground-up reimplementation of core Kubernetes internals in Go — API server, etcd-backed object storage, watch mechanism, scheduler, and kubelet — built to understand control-loop systems at the source-code level.
|
🛡️ Edge-Aware Cybersecurity Orchestrator A distributed threat-detection system for edge/IoT devices: a Go orchestrator, lightweight Go edge agents, and a Python ML-driven anomaly analyzer, coordinated over secure channels with a React dashboard.
|
A real-time, multi-user code editor with a TypeScript backend and React frontend, deployed to a live Kubernetes cluster with a full CI pipeline and Cypress end-to-end test coverage.
|
| Languages | Backend & Systems | Data & Storage | Infrastructure | Frontend |
   
|
|
  
|
 
|
   
|
Tools & Daily Driver
|
|
|
|
|
|
|
|
|
Go and TypeScript are my present. Rust is the deliberate next step — once the Go and systems foundations are fully solidified, it's the language I'm planning to go deep on for low-level, performance-critical work.
[email protected] | LinkedIn | 🌍 Open to remote opportunities