• 💼 Backend Engineer with real-world experience in high-scale FinTech systems
• 🏦 Built and worked on payment processing, clearing & transaction lifecycle systems
• ⚡ Strong in System Design (HLD + LLD) with production mindset
• 🔄 Hands-on with Concurrency, Multithreading & Async systems
• 📈 Focused on scalability, reliability, and low-latency backend services
• 🧠 Problem solver with strong foundation in DSA + system thinking

• Designing event-driven microservices architectures
• Handling millions of transaction flows reliably
• Building idempotent APIs for financial systems
• Debugging distributed systems issues in production
• Optimizing database queries & reducing latency
• Designing fault-tolerant and self-healing systems

• Distributed Systems & Microservices Architecture
• CAP Theorem & Consistency Tradeoffs
• High Availability & Fault Tolerance
• API Design (Idempotency, Rate Limiting, Retries)
• Caching (Redis, In-memory, CDN strategies)
• Database Design (Indexing, Partitioning, Sharding)
• Event-driven systems (Kafka / Pub-Sub)

• Java, Spring Boot (Primary Stack)
• REST APIs, Async APIs, Webhooks
• Authentication & Authorization (JWT, OAuth)
• API Gateway & Routing Layers
• Observability (Logging, Metrics, Tracing)

• Multithreading & Parallel Processing
• Thread Pools, Executors
• Race Condition handling
• Deadlock prevention strategies
• Async / Non-blocking architectures
• Performance tuning (CPU, memory, DB)

• End-to-end payment flow: Authorization → Clearing → Settlement → Reconciliation
• Transaction lifecycle management
• Handling duplicate & retry-safe processing
• Designing idempotent financial APIs
• Ledger & balance consistency understanding
• Working with real-time and batch processing systems

Java Python C++ JavaScript Go

Spring Boot Django Flask Node.js Gin

PostgreSQL MySQL MongoDB Redis

AWS GCP Docker Kubernetes Git

Kafka Pub/Sub Event-driven systems

✔️ Write production-grade, scalable code
✔️ Design systems that fail gracefully & recover automatically
✔️ Think in terms of throughput, latency & reliability
✔️ Prefer clean architecture & maintainability over hacks

• 🔹 High-scale Payment Processing System
• 🔹 Distributed Rate Limiter (Redis + Token Bucket)
• 🔹 Event-driven Notification System (Kafka)
• 🔹 Idempotent Transaction Processing API

“Simple systems scale. Complex systems fail. Design for clarity, then optimize for scale.”