I started as a .NET developer inside large enterprises, on the kind of systems nobody writes blog posts
about: poorly documented, business-critical, and older than some of the people maintaining them. Reading
those systems — reverse-engineering what they did and why — turned out to be the most useful education I
could have asked for, and it is where I fell in love with architecture.
That path led to an internal promotion to Software Architect, and today I help organizations modernize
enterprise software: understanding the business problem first, then choosing technology. I believe
architecture is about making trade-offs explicit rather than chasing trends, and I have stayed
deliberately hands-on — I still enjoy coding, and I still build small things for fun.
Away from the keyboard I am a proud father of a 3-year-old, and most of my time outside work belongs
to her. The rest goes to music, cricket, table tennis, volleyball, photography and travel — some of which
you can see in the photos below.
// architecture principles
Decisions I keep making
Written the way architects record decisions — as ADRs. These have survived contact with
banking mainframes, healthcare platforms and everything in between.
ADR-001accepted
Business before technology
A system exists to serve a business capability. Understand the domain, the constraints and who pays the
cost of change before opening the technology catalog.
ADR-002accepted
Architecture is trade-offs
There are no best practices, only fitting ones. The architect's job is to make trade-offs explicit,
choose deliberately, and write the reasoning down.
ADR-003accepted
Incremental modernization
Big-bang rewrites of running businesses fail quietly and expensively. Strangle legacy at the seams —
anti-corruption layers, parallel runs, reversible steps.
ADR-004accepted
AI accelerates engineers
AI tooling is a force multiplier for reverse engineering, documentation and migration — in the hands of
engineers who can judge the output. It replaces toil, not thinking.
ADR-005accepted
Simple systems scale
Complexity is the real legacy. The systems that survive decades are the ones a new engineer can reason
about in a week — design for that engineer.
ADR-006accepted
Teams own architecture
Architecture handed down as a diagram dies in the first sprint. It works when the teams building the
system understand, challenge and own the decisions.
// what I work on
The shape of the work
a. Enterprise modernization
Taking systems that have quietly run a business for twenty or thirty years — mainframe estates, aging
platforms — and moving them forward without stopping the business. Discovery, reverse engineering,
target-state design, and a migration path measured in reversible steps.
b. Software architecture
Designing distributed systems and the boundaries between them. Architecture governance, reviews and
decision records; making sure the important trade-offs are made on purpose, by the people who will live
with them.
c. AI-assisted engineering
Putting AI to work on the unglamorous middle of modernization: understanding undocumented code,
generating first-draft documentation and tests, accelerating migration. Grounded in engineering judgment,
not demos.
d. Technical leadership
Leading two to three engineering teams at a time — mentoring, running architecture workshops, reviewing
designs and code, and doing the technical discovery and pre-sales work that shapes an engagement before
it starts.
// experience
Where the miles come from
Luxoft
Senior Software Architect2025 —
present
Modernization practice — enterprise banking modernization for a major financial
institution.
enterprise modernization
COBOL modernization
IMS
DB2
AI-assisted engineering
architecture governance
technical discovery
enterprise pre-sales
multiple engineering teams
Hyland
Developer 3 → Software Architect 32019 —
2025
R&D, healthcare content services — promoted internally from developer to architect.
The day job, described without the confidential parts — and the things I build on my
own time, because I still enjoy building software.
enterprise work
Core banking modernization
Luxoft · banking & capital management
Problem
A major financial institution running core workloads on a COBOL / IMS / DB2 estate that is expensive
to change and hard to staff.
Architecture
Incremental modernization: AI-assisted reverse engineering of the legacy estate, target-state design,
and governance to keep dozens of workstreams coherent.
Contribution
Architecture ownership, technical discovery and pre-sales, and leading multiple engineering teams
through the migration.
Outcome
A modernization path the business can actually take — reversible steps instead of a bet-the-bank
rewrite.
Healthcare platform modernization
Hyland · healthcare R&D
Problem
A long-lived C++ healthcare content platform that needed to evolve without disrupting clinical
workflows.
Architecture
C++ → .NET migration shaped by domain-driven design, with anti-corruption layers isolating new
services from legacy internals.
Contribution
Architecture and design ownership, workshops, mentoring, and hands-on debugging when it mattered.
Outcome
A platform teams could extend again — and an internal promotion from developer to architect along the
way.
Fixed income analytics engine
FactSet · financial analytics
Problem
Analytics for fixed income securities where correctness and speed are both non-negotiable.
Architecture
A high-performance C++ calculation engine, with Python automation around its nightly production
jobs.
Contribution
Product engineering on the engine and the operational tooling around it.
Outcome
Faster, more reliable analytics delivery — and a Star Award on the way out.
Examination delivery modernization
Cognizant · assessment industry
Problem
A leading assessment agency's examination delivery system: business-critical, legacy ASP.NET, thinly
documented.
Architecture
Reverse engineering the existing behavior, then refactoring the full stack while supporting live
operations.
Contribution
Full-stack development and application support — the apprenticeship that started all of the above.
Outcome
A maintainable system, and a Rising Star award for the work.
personal projects
Gratitude
A small Firebase-backed app where people write down gratitude towards others. Built to learn, kept
because it is nice.
Travel, family and friends — the parts of life that do not fit in an ADR.
Lepchajagat 2024 Pine viewLepchajagat 2024 Tulika and StutiGoa 2022 South Goa cyclingGoa 2022 VarcaJaipur 2022 Hawa MahalAgra 2023 Agra FortDarjeeling 2024 With StutiDarjeeling 2024 With StutiDarjeeling 2024 With Stuti and TulikaKolkata 2022 Pre-wedding photoshootLadakh 2018 Ladakh tourTrek 2013 Varsey Rhododendron SanctuaryFamily, 2014 Brother's thread ceremonyKerala 2015 With familyDurgapur M.Tech friends groupRecovery day M.Tech friends groupDurgapur winter Early morning selfieGangtok 2018 Selfie from GonjangLadakh 2018 Wanna make it wallpaper?Ladakh 2018 Crowded Pangong
// technical expertise
Tools of the trade
Grouped by capability, because the capability matters more than the logo.
Architecture
enterprise architecture
solution architecture
domain-driven design
distributed systems
modernization
Backend
Java
C#
.NET
Spring Boot
Frontend
React
Cloud
AWS
containers
Legacy
COBOL
IMS
DB2
C++
// contact
Let's talk systems
I enjoy discussing enterprise architecture, modernization
and difficult engineering problems. If you're building or modernizing large software systems, I'd be
happy to connect.
.jpg)
.JPG)
.jpg)
.JPG)
.jpg)
.JPG)
.JPG)
.JPG)
.jpg)
.jpg)
 - Copy.jpg)
 - Copy.jpg)
 - Copy.jpg)
 - Copy.jpg)
 - Copy.jpg)
 - Copy.jpg)
 - Copy.jpg)
 - Copy.jpg)