About

My work sits at the intersection of product and delivery: I own architecture decisions, but I'm also the person doing sprint planning, code review, client-facing delivery and the occasional 2am production fix. That combination — building the thing and being accountable for it staying up — has shaped how I think about software more than any single technology has.

Most of the interesting problems I've worked on aren't about a specific framework. They're about state: a service ticket moving through four different actors without losing track of itself, a medical instrument that can't assume the network is there, a trading dashboard that has to feel instant at P90 while handling real load. I like that kind of problem more than I like new tooling, though I use plenty of it.

Before RedoQ I spent two years in fintech, first at Quantorix and then at Phlo Systems in the UK, building risk-management and hedging platforms for commodities and futures trading — real-time, latency-sensitive, unforgiving of sloppy state management. Before that, at IEMLabs, I built a plagiarism-detection platform on microservices while also teaching web development to students, which is probably where I picked up whatever patience I have for mentoring.

Outside client work I write and maintain a handful of open-source projects I use as an excuse to learn systems from the inside — Englang, a small English-like programming language with its own lexer and parser, and DemoGit, a C# reimplementation of Git's object model. Neither is trying to be a product; both taught me more than most tutorials do.

I've spent a fair amount of time in Kolkata's student and startup community too — mentoring at hackathons (StatusCode, InnoFusion, Double Slash), speaking at UEM, Jadavpur University, IEM Newtown and The Neotia University, and organizing for UXINDIA as their Kolkata ambassador. I'm a B.Tech graduate (CSE) from University of Engineering & Management, Kolkata, and an alumnus of Webel's Software Development Facilitation incubation program.