I am a backend engineer focused on distributed systems that move state, money, and long-running workflows safely through unreliable environments.

I design Go services from architecture to production: service boundaries, data models, consistency guarantees, asynchronous messaging, recovery workers, observability, deployment guardrails, and the operational tools needed to understand a system under pressure.

My background spans high-load products operating at up to 50k RPS, payment and settlement infrastructure, marketplace workflows, platform engineering, and backend teams built from zero. I care less about adding another service and more about making the whole system easier to reason about.

Go-first   failure-aware   architecture-to-production   operationally explicit

A modular Steam Deck systems plugin spanning user interface integration, Linux input, isolated workers, guarded device recovery, localization, and deterministic release automation.

A production-minded order lifecycle service demonstrating durable workflow orchestration, explicit state transitions, typed PostgreSQL persistence, API contracts, and a reproducible local environment.

A repeatable remote-debugging environment for Go applications built around Delve and Docker.

• Model failure and recovery before polishing the happy path.
• Make state transitions explicit, idempotent, and reconcilable.
• Ship telemetry as part of system behavior, not as an afterthought.
• Automate delivery without hiding operational risk or removing human control.
• Keep service boundaries aligned with data ownership and team ownership.

I am always interested in difficult backend problems, open-source systems work, and conversations about architecture that survives production.

LinkedIn | 4deus Mod | 4deus Community