Backend engineer building reliable production systems in Go.
I work on the parts of a system where correctness matters most: authentication, authorization, API contracts, data boundaries, and safe production changes.
My recent work includes designing role- and scope-based access control, integrating short-lived token flows, evolving database-backed services, and turning production bottlenecks into small, measurable fixes. I try to make failure modes explicit, keep contracts reviewable, and leave systems easier to operate than I found them.
- Access control — authentication, authorization, roles, scopes, and audit trails
- API design — HTTP APIs, OpenAPI contracts, idempotency, and compatibility
- Data systems — PostgreSQL, Supabase integrations, schema evolution, and consistency
- Reliability — observability, concurrency, performance, and fail-closed behavior
- Delivery — focused tests, race detection, CI, staged rollouts, and practical rollback paths
Most of my recent production work lives in private repositories. My public history also includes web and cross-platform applications; that background still helps me design backend contracts with the client on the other side in mind.
I prefer explicit contracts over hidden assumptions, focused evidence over confident guesses, and the smallest change that fully solves the problem.
Outside of code, I watch a lot of films. I like stories that stay with you, shift perspective, and remain kind to people even in the middle of chaos.
Please, be kind. Especially when we don't know what's going on.
— Everything Everywhere All at Once