ourkingg

Backend engineer with hands-on experience building reliability-critical systems, including billing, automation, and infrastructure workflows.

In my current work, I focus on backend services where correctness, idempotency, and failure handling matter — such as payment flows, provisioning automation, and real-time system state.

I’m transitioning into Web3 from a backend and infrastructure background, with particular interest in systems where incorrect state or retries can directly lead to financial or operational loss.

I’m drawn to Web3 not for hype, but for its hard engineering problems: state consistency, automation under failure, and systems that must be correct by design.