Software engineer working at the intersection of payment systems, Android engineering, and reliability.
I work on Android systems in a payment environment. My public repos focus on the same themes I care about at work: reliable transaction flows, observability, and safer mobile-client behavior.
- Payment and transaction reliability
- Secure Android client engineering
- Observability and platform fundamentals
- Kotlin, Java, Spring Boot, Go, FastAPI, Docker, Prometheus, Grafana, Helm
A Spring Boot backend lab for payment reliability scenarios: idempotent payment creation, duplicate webhook handling, guarded state transitions, settlement batching, reconciliation mismatch detection, manual review, audit events, tests, and CI.
A self-hosted uptime and latency monitoring lab using Go, FastAPI, Prometheus, Grafana, Alertmanager, Docker Compose, and Helm.
It includes local verification scripts, proof screenshots, dashboard evidence, and CI checks.
A Kotlin Android security lab for device-risk checks, sensitive action gating, HMAC request signing, encrypted local storage, certificate pinning tradeoffs, and local security events.
The project is intentionally public-safe: no real payment processing, no bank integration, and no claim of bypass-proof security.
I care about systems where correctness and trust matter: payment states, failure handling, security boundaries, observability, and clear operational evidence.
The projects here are not clones of employer systems. They are safe, focused labs built to show how I think through real engineering problems without exposing internal code or private workflows.