Backend engineer focused on Go, distributed systems, networking, and crypto infrastructure.
I build low-level infrastructure around VPN routing, network control planes, proxy orchestration, health checks, failover logic, and system-level services. My recent work focuses on routing reliability under unstable network conditions: watchdog recovery, tunnel health monitoring, traffic policy design, DNS behavior, and fail-closed networking.
I am especially interested in crypto infrastructure where backend engineering meets real network behavior: Ethereum nodes, JSON-RPC systems, P2P networking, decentralized routing, node reliability, observability, and distributed system failure modes.
My strength is working close to the system layer: understanding how services actually behave under latency, packet loss, blocked routes, DNS failures, broken tunnels, and unreliable upstreams — then designing software that detects, isolates, and recovers from those failures.
Looking for remote backend, infrastructure, or crypto engineering roles where Go, networking, reliability, and distributed systems matter.
There are only two hard things in computer science: cache invalidation, naming things, and debugging distributed systems in production.