I build systems that don't break at 3 AM. Backend developer focused on the unglamorous parts: correctness, reliability, and making operators' lives easier.
I design systems to prevent bad states from happening in the first place. Type safety, validation layers, state machines—boring stuff that saves you from midnight debugging sessions.
Your claims processor dealing with 200 submissions a day deserves a UI that doesn't make them want to quit. Bulk actions, clear errors, no cognitive overload.
When something fails in a reconciliation run, someone needs to understand why. I build systems where every error is traceable, explainable, and fixable without a developer.
Big bang releases are for people who like stress. I prefer incremental changes with clear rollback paths. Your production environment will thank you.
Data modeling matters. Normalize where integrity matters, denormalize for speed and auditability. Every schema decision is a bet on future maintenance pain.
Structured logging, correlation IDs, context at every level. When production breaks, you shouldn't need to deploy debug builds to figure out what happened.
Handles duplicate requests and network retries without charging users twice. Every payment or refund is recorded correctly and traceable.
Placing an order triggers background steps like payment and notifications. Messages don't get lost on crashes, and failed steps retry safely.
Batch tool that compares two systems (bank vs internal data) and groups mismatches into clear "reasons" for fast human review.
Runs background jobs on a schedule with protection against duplicate runs. Keeps full history, saves errors, supports reruns.
Sends events to external systems with retry support. Tracks delivery status and allows replaying events when the target is ready.
Limits requests per user per time window. Supports different limits per user type, works across multiple servers via Redis.
Structured logging with per-request tracking IDs and consistent context. Answers "what happened?" quickly when production breaks.
Supports large files processed safely in background. Includes virus scanning, safe storage, and clear status updates.
I'm interested in backend-heavy roles where correctness matters more than move-fast-break-things. If you're building financial systems, government platforms, or anything where "it mostly works" isn't good enough—let's talk.