The Person Behind the Code

20+ Years Building
Enterprise Systems
That Last

I started Abstech Solution because I got tired of watching well-intentioned projects fail — not from lack of effort, but from lack of architecture. Every system I build is designed to outlast the engagement.

Work With Me → View LinkedIn Profile
A
Abstech Solution
Senior Full-Stack Architect
.NET 8 / C# Angular 17+ Clean Architecture DDD / CQRS Azure / AWS AI / LLM Pune, India
20+
Years experience
50+
Projects delivered
4
Core specialisms
The Story

Why Abstech Exists

I've spent over two decades inside enterprise organisations — banks, insurance companies, logistics platforms, and SaaS startups — watching the same failure repeat itself. A promising product gets built fast, then falls apart under its own weight. Not because the developers were bad. Because the architecture was never designed for longevity.

Early in my career I learned that the most expensive line of code is the one you have to rewrite in two years. That conviction shapes everything I build. Clean Architecture isn't a philosophy I learned from a book — it's the hard-won result of having to maintain systems I built badly early on, and fixing other people's systems that were built even worse.

"I founded Abstech because I wanted to offer clients something agencies rarely can: a single senior engineer with the architectural depth to design the right system, and the accountability to build it properly — with no juniors silently introduced halfway through."

Today, Abstech works with CTOs, founders, and engineering leaders who are serious about code quality, scalability, and long-term maintainability. The client base is small by design — I take on fewer projects than I could, because every engagement gets my full attention.

Career Timeline

Two Decades,
One Focus

From junior developer to senior architect. Every role built on the last — each one adding a layer of perspective that now benefits every Abstech client.

2004 – 2007
Junior .NET Developer
First enterprise role. Built ASP.NET WebForms applications. Learned the hard way what unmaintainable code looks like from the inside.
2007 – 2011
Mid-Level Developer → Team Lead
Led a team of 6 developers on a large-scale insurance platform. First exposure to domain-driven design and SOA patterns.
2011 – 2015
Senior .NET Architect
Designed and delivered multiple enterprise systems across banking and logistics. Adopted Clean Architecture and CQRS as core patterns. First Azure cloud deployments.
2015 – 2019
Principal Architect — SaaS Platforms
Principal architect on two SaaS products reaching 100k+ users. Led microservices migration, Azure-native redesign, and DevOps transformation.
2019 – 2023
Independent Consultant
Served 15+ clients across UK, US, and India as independent consultant. Specialised in legacy modernisation and cloud architecture reviews.
2023 – Present
Founder — Abstech Solution
Founded Abstech to formalise the practice and take on complex, architecture-first engagements. Added AI/LLM integration as a fourth core service area.
By the Numbers
20+
Years in enterprise development
50+
Enterprise projects delivered
12+
Legacy systems modernised
3
Countries currently serving

Industries served

Banking & FinTech Insurance Logistics & Supply Chain SaaS Platforms Healthcare E-Commerce Government / Public Sector
Architecture Philosophy

How I Think
About Code

These aren't abstract principles. They're the direct result of 20+ years of maintaining systems — my own, and other people's.

01 / Principle
Business logic belongs in the domain
The core of your application — the rules that make your business work — must not live in a controller, a database trigger, or a stored procedure. It lives in the domain layer, protected by proper encapsulation. This is non-negotiable on every project.
02 / Principle
Dependencies always point inward
Your domain doesn't know about SQL Server. Your use cases don't know about Angular. Inversion of control isn't a pattern to apply when convenient — it's the load-bearing structure of every system I build.
03 / Principle
Testability is a design goal, not a QA task
If a class is hard to unit-test, it's not a testing problem — it's an architectural problem. I design for testability first. Tests are how I verify that the architecture is actually clean.
04 / Principle
Simple before clever
Microservices are not the default answer. Event sourcing is not always needed. CQRS adds overhead. I apply patterns only when the problem justifies the complexity — and I explain why in the architecture documentation.
05 / Principle
Your team must own the codebase
An architecture that only I can maintain is a liability, not an asset. Every system I deliver includes ADRs explaining every significant decision, so your team can extend it confidently without calling me.
06 / Principle
Measure before optimising
Performance bottlenecks are discovered by profiling, not predicted by intuition. I build for correctness and clarity first — then use data to identify and solve actual performance problems, not imaginary ones.
Credentials

Certifications & Training

Update this section with your real certifications before going live.

☁️
Microsoft Certified: Azure Developer Associate
Microsoft · AZ-204
🏗️
Microsoft Certified: Azure Solutions Architect Expert
Microsoft · AZ-305
🔶
AWS Certified Solutions Architect – Associate
Amazon Web Services · SAA-C03
🐳
Certified Kubernetes Application Developer
CNCF · CKAD

⚠ Replace with your actual certifications — only list what you hold.

Ready to work with a senior architect?

Let's talk about what you're building — or what you need to rebuild.