Open to Senior / Lead Engineering roles · Remote

I build payment infrastructure that isn't allowed to fail.

Senior Software Engineer with 8+ years designing and scaling distributed payment systems — gateway integrations, wallet migrations, and resilience engineering that keep money moving for millions of users, reliably, at scale.

8+
Years of experience
100K+
Daily transactions handled
2M+
Users migrated, zero fund loss
98%
Peak refund success rate
Selected Work

Systems I've architected and shipped

Five projects that show the range — real-time fraud checks, large-scale migrations, and the resilience engineering that keeps payment systems trustworthy under load.

PayWithQR

Swiggy

Architected a real-time QR payment validation and fraud-check solution to reduce dependency on cash-on-delivery, integrating live fraud signals into the checkout path without adding user-facing latency.

Impact: Reduced COD dependency with real-time fraud validation at checkout
GoKafkaRedisMicroservices

Refund Retry & Resilience Engine

Swiggy

Designed a retry system combining circuit breakers, idempotency guarantees, and backoff strategies to make refund processing resilient to partner and network failures at scale.

Impact: Refund success rate 70% → 98%, 50K+ refunds/day, 85% less manual effort
GoKafkaCircuit BreakersIdempotency

Swiggy Money Wallet Migration

Swiggy

Led the migration of Swiggy's wallet platform for its full user base, building a robust rollback mechanism so the migration could be reversed safely at any stage if issues surfaced.

Impact: 2M+ users migrated with zero fund loss and a full rollback safety net
JavaDynamoDBMySQL

Multi-Gateway Payment Platform

Swiggy

Led integration of 8+ payment gateways, designing standardized, scalable adapters so new gateways could be onboarded quickly without touching core checkout logic.

Impact: 100K+ daily transactions at <500ms p99 latency across 8+ gateways
gRPCSpring BootAWS

Multi-Wallet Refund System

Myntra Jabong

Built a dead-letter-queue-backed refund retry system with idempotency guarantees across multiple wallet types, eliminating a large monthly volume of manual refund processing.

Impact: Refund success 65% → 98%, eliminating 15K+ manual refunds a month
GoJavaDLQMongoDB
Experience

8+ years, four companies, one thread: payments at scale

Software Development Engineer II · Swiggy
Sept 2021 – Present
  • Architected PayWithQR and led integration of 8+ payment gateways handling 100K+ daily transactions at <500ms p99 latency
  • Designed a refund retry system improving success rate 70% → 98%, cutting manual effort by 85%
  • Delivered a 2M+ user wallet migration with zero fund loss; mentor 5+ engineers on system design and production readiness
Software Development Engineer I · Myntra Jabong (Flipkart Group)
Sept 2019 – Aug 2021
  • Redesigned the paisa-apportioning algorithm, reducing refund disputes by 40%
  • Built a multi-wallet refund retry system improving success from 65% to 98%, eliminating 15K+ manual refunds/month
  • Owned features end-to-end — design, production rollout, and on-call
Software Developer · CarWale (CarTrade Tech)
Jun 2018 – Sept 2019
  • Built 8+ microservices spanning auth, payments, offers, and user systems
  • Designed DB schemas and Elasticsearch indices achieving sub-100ms query latency
SDE Intern · Amazon
May 2017 – Jul 2017
  • Built an event processing pipeline using SQS and SNS with encryption; achieved 90% test coverage
Skills

What I build with

Languages

GoJavaC#JavaScript

Backend

MicroservicesgRPCREST APIsSpring BootEvent-Driven Systems

Data & Storage

MySQLDynamoDBMongoDBElasticsearchRedis

Messaging

KafkaRabbitMQAWS SQS/SNS

Cloud & Infra

AWS (EC2, S3, Lambda, IAM)DockerKubernetes

Observability

PrometheusGrafanaELK

Core Concepts

High AvailabilityCircuit BreakersRetryIdempotencySharding
Education

Background

B.Tech, Computer Science & Engineering

Maulana Azad National Institute of Technology (MANIT), Bhopal · 2014 – 2018

CGPA 8.59

Let's talk

Open to senior and lead engineering roles in fintech, marketplaces, and infrastructure — remote-friendly.