I build payment systems and internal platforms that survive production.

Senior Software Engineer / Tech Lead specializing in fintech backends, payments, cloud infrastructure, and system architecture.

Payments & reconciliation

Webhook-safe flows, recovery paths, traceability

Wallets & ledgers

Balance correctness, lifecycle states, auditability

Event-driven services

Queues, workers, idempotency, retries

AWS / K8s / CI/CD

Deploy safely, monitor, iterate

Selected Work

Systems I've built

Wallet & Transaction Processing

Problem

Needed reliable balance tracking and payment state management across multiple providers.

Outcome

Designed a ledger-based system with idempotent webhooks and event-driven processing.

Node.js Django MySQL Redis

Multi-Gateway Payment Layer

Problem

Payment flows were tightly coupled and hard to monitor or reconcile.

Outcome

Built a unified layer with queue-based processing and webhook reconciliation.

Node.js Python BullMQ RabbitMQ

CRM Re-Architecture

Problem

Legacy system was slowing development and affecting reliability.

Outcome

Led incremental re-architecture, improving performance without downtime.

React APIs Elasticsearch AWS
Services

What I can help with

Architecture & Re-Architecture

Breaking down legacy systems into scalable, maintainable architectures.

Typical outcomes
  • Faster deployments
  • Reduced coupling
  • Clear migration paths
System Design Microservices

Backend APIs & Integrations

Designing robust APIs and integrating external services safely.

Typical outcomes
  • Reliable integrations
  • Clean API contracts
  • Proper error handling
REST GraphQL Webhooks

Payment Systems

Wallets, gateways, webhooks, reconciliation, failure-safe flows.

Typical outcomes
  • Zero missed transactions
  • Full audit trails
  • Recovery paths
Payments Ledgers Queues

Cloud & DevOps

Dockerized deployments, Kubernetes, CI/CD, monitoring.

Typical outcomes
  • Safe deploys
  • Repeatable builds
  • Production observability
AWS K8s Docker
Process

How I approach problems

01

Understand

Map the current flow, identify bottlenecks, and clarify technical and business constraints before writing any code.

02

Design

Build for retries, timeouts, recovery paths, and visibility into production behavior. Assume failure happens.

03

Ship

Roll out incrementally, monitor closely, and iterate based on real-world feedback. Production is the test.

Writing

Latest thoughts

Coming Soon

Designing Payment Systems That Don't Lose Money

Lessons from building transaction processing systems with proper idempotency, reconciliation, and failure handling.

Coming Soon

Event-Driven Architectures in Real Fintech Products

Practical patterns for queues, workers, and async processing in production payment systems.

Coming Soon

Lessons from Re-Architecting Legacy Systems

How to incrementally modernize a running system without breaking what already works.

Let's work together

Available for consulting, contract work, or full-time opportunities in fintech and backend engineering.

Start a conversation