Hello, I’m Jagwinder.

I started in 2007, writing .NET applications for businesses that needed a system to match the way they already worked. My work has kept that shape ever since. The tools changed. VB.NET gave way to C# and ASP.NET Core, and on-premises servers gave way to Azure. The job underneath stayed the same. Understand the process first, then design something that supports it without adding complexity the business does not need.

I spent close to a decade at FIS, working on financial technology used by banks: cheque and transaction processing, document imaging, archival and retrieval, reporting, and fraud and risk review. Those systems ran at high volume, and a defect in production reached real customers the same day. Most of my work there was backend: C# services, REST APIs, SQL Server and Oracle, and the root-cause analysis that comes with software people depend on every day. I also mentored developers, and getting a junior engineer to the point where they could ship production changes on their own turned out to be one of the more satisfying parts of that job.

A large share of my time has gone into integration: connecting systems that were never designed to talk to each other, and doing it so the connection survives real traffic and real failures. In recent years that has mostly meant Azure: Service Bus, API Management and Event Grid, together with the messaging patterns that keep those pieces reliable. I care about clear boundaries, simple designs and code the next engineer can read without me sitting beside them. Good software should solve the problem without becoming the problem.

At the moment I am building Siftworks, an IT consulting business where I help solve problems for businesses. I am deepening the Azure side of my work and looking carefully at where AI genuinely helps, both in how software gets built and in what can be built on top of Azure.

Through Siftworks, the project that takes most of my attention is BusyBay, a SaaS platform for automotive workshops covering bookings, customers, invoices and service workflows. It is where I work across the whole thing: backend development, APIs, Azure services, architecture, and the product decisions about what should exist at all. Making those calls and then living with them has taught me more than reading about them ever did.

I have recently started writing about what I learn and build, mostly around .NET, Azure and the practical side of engineering, and I would like to contribute more to open source. Both come from the same idea: doing the work in public is a fair test of how well I actually understand it.

This site is where that record lives. My resume has the detail of where I have worked; the rest is what I am building and writing about now.