Software engineer with 12+ years crafting scalable, cloud-native systems for fintech, banking, advertising, and e-commerce — mostly in Kotlin, mostly thinking about how distributed systems should talk to each other.

I've spent the last decade solving problems at scale, mostly in spaces where getting it right matters: fintech systems that can't lose money, ad platforms that need to handle millions of events per second, and e-commerce journeys where a slow checkout costs real dollars. That experience has shaped how I think about building systems.

System Design & Architecture
If you're staring at a problem that doesn't fit neatly into a single database or machine, I can help. I'm comfortable navigating the tradeoffs between consistency, availability, and partition tolerance — not as abstract concepts, but as real decisions you have to make when your payment system goes down at 3 AM. I've designed systems that handle millions of transactions, architected microservices ecosystems that didn't collapse under their own complexity, and learned (often the hard way) what works and what becomes a nightmare.

Engineering Leadership & Team Building
I've led teams through architectural pivots, coached engineers on distributed systems thinking, and helped organizations scale from scrappy startups to multi-team setups. What matters to me is building teams that ship fast without burning out — and making sure the technical strategy actually aligns with where the business is trying to go, not just where the tech wants to live.

Event-Driven Systems & Microservices
This is where I spend most of my energy. I've built production Kafka-based systems, designed service boundaries that actually stick, and learned to manage the complexity that emerges when you're coordinating work across multiple services. I've seen what works (clear ownership, proper monitoring, discipline around service contracts) and what becomes a disaster (services that are too chatty, events without schema versioning, ops blind to what's happening in the system).

Kotlin is my primary language for the last 5+ years. It's clean, expressive, and pragmatic — I've used it to build everything from fintech backends to advertising platforms. Before that, Java was my home on the JVM, and I still lean on that deep understanding of the platform. I've built production systems in .NET too, and I'm comfortable in that ecosystem.

On the backend, I spend a lot of time thinking about microservices — service discovery, API design, managing transactions across services, dealing with the failures that are inevitable when you're distributed. Kafka is a tool I know well; I've designed topics, handled exactly-once semantics, and built event processors that don't fall over under load. For cloud infrastructure, I'm at home in AWS (EC2, RDS, Lambda, SQS, SNS) and GCP (Compute Engine, Cloud SQL, Pub/Sub) — I can make infrastructure-as-code decisions confidently. Docker I know deeply; Kubernetes I have solid exposure to. On databases, PostgreSQL is my first choice; I know query tuning and schema design for systems that need to scale. Node.js rounds out the backend story — full-stack work, REST/GraphQL APIs, integrating seamlessly with frontend teams.

The frontend side: I've built component hierarchies in React that don't make engineers cry, and managed state thoughtfully. I've also led frontend architecture work in Angular and understand the full framework stack.

What ties it all together is observability. You can't run distributed systems blind — monitoring, logging, alerting, and the discipline to set them up right from day one. Same with CI/CD — I care about pipeline design that doesn't slow teams down.

• Founder, N75 Lab Private Limited — strategic technology consulting
• Tech Consultant, Equal Experts — leading the post-purchase journey for a leading e-commerce platform, focused on customer experience

• Engineering Lead, MettaRev (Pune, Q1 2024) — took a co-operative banking MVP from idea to validated market entry, onboarding early customers on Node.js, Angular, Postgres, and AWS
• Quantcast (Berlin, 2023–2024) — spotted visibility gaps in ad campaign reporting and architected an end-to-end Kotlin/GCP/Java solution that gave clients better controls, visibility, and margins
• Layer (Berlin, 2020–2023) — led engineering through a shift to microservices and event-driven architecture, and helped steer a strategic product-engineering pivot
• N26 (Berlin) & ThoughtWorks (Pune) — where I built my foundations in fintech and enterprise-grade engineering

Functional programming, distributed systems, and microservices architecture — the kind of problems where good design decisions compound. I write about this (and whatever else is on my mind) over on the blog.

📫 Let's talk — system design, distributed systems, or building teams that ship. I'm always happy to hear from you.