> backend_engineer / distributed_systems / problem_solver
I build event-driven backend systems and
design fault-tolerant architectures.
Turning complex problems into reliable, scalable code.
// 01 — about
I'm a backend engineer who cares about systems that stay correct under failure — not just ones that work on the happy path. Queues, retries, idempotency, and event-driven architecture are where I spend most of my thinking.
When I'm not building APIs or reasoning about failure modes, you'll find me grinding LeetCode problems, maintaining pygraphkit on PyPI, or debugging something that shouldn't have broken.
I'm currently open to backend engineering internships and interesting open source collaborations.
// 02 — skills
// 03 — projects
Built a multi-tenant CI/CD orchestration platform integrating GitHub, GitLab, and Bitbucket. Designed a fault-tolerant, event-driven architecture that decouples webhook ingestion from CI execution using dedicated BullMQ workers backed by Redis. Enforced per-repository HMAC-SHA256 secrets via automated OAuth provisioning, and implemented at-least-once, idempotent job processing with exponential backoff for reliable Slack notifications and outbound webhook delivery.
Architected and deployed a cloud-hosted backend on Azure that automates Coursera financial-aid applications end to end. Orchestrated asynchronous processing pipelines using background workers and state tracking to isolate client-facing APIs from compute-heavy AI generation. Built a scraping and caching layer over a SQLite-backed catalog of 6,600+ courses, and integrated the Gemini API with structured, context-aware prompt-generation workflows.
Built and published pygraphkit, a Python library providing reusable implementations of core graph algorithms with a clean and consistent API. Released as a stable v1.0.0 package on PyPI with full test coverage, CI, and documentation.
// 04 — achievements
// 05 — contact
Have an interesting project, opportunity, or just want to talk
backend systems?
My inbox is always open.