01 · Business platform
CRM Platform
An in-house CRM for leads, pipelines and follow-ups, built so the sales team spends its time on customers instead of on the tool.
Angular.NET / C#SQL Server
Open to new projectsTechnical Team Lead · Full Stack
I build software that survives the real world.
Four years across web, cloud and Windows desktop. Today I lead a team of 4+ engineers building in-house business platforms: CRM, HRMS and the workflows that keep a company running.
4+engineers I lead
.NET · Angular · SQL
.NET / C#AngularSQL ServerCloudflareTeam leadershipCRMHRMSExploring GCP · AWS · Azure.NET / C#AngularSQL ServerCloudflareTeam leadershipCRMHRMSExploring GCP · AWS · Azure
01 — About
Engineering decisions first, pixels second.
I design and build resilient software across web, cloud and Windows desktop, and I stay responsible for it after launch.
Most of my work sits in the layers that decide whether a product holds up: how the data is modelled, where the boundaries go, what happens when an integration fails halfway through, and how much of that complexity the person on screen ever has to see.
As a technical team lead I spend a real part of the week on reviews, mentoring and untangling requirements that arrived vague. Accessibility is not a feature I bolt on. If an interface only works for a confident user on a fast laptop with good eyesight, it is unfinished.
Currently
Leading 4+ engineers on in-house CRM and HRMS products.
4+Years shipping production systems
4+Engineers on my team
4Platforms: web, cloud, mobile, desktop
WCAGAccessibility as a baseline
02 — Selected work
Four systems, four different kinds of hard.
Each one had a constraint that shaped the architecture more than any framework choice did. Open a card for the full case study.
02 · Business platform
HRMS Suite
Attendance, leave, payroll inputs and employee records in one system, with roles and permissions designed in from day one.
Angular.NET / C#Roles & permissions
03 · Automation
CareerCoach Engine
A scheduling workflow that connects mentors, clients, Google Calendar and Google Meet. Booking, reminders and links resolve themselves.
Google Calendar APIGoogle MeetAutomation
04 · Accessibility
Sehat Sathi
Medical tracking for older adults and less technical users. Clear navigation, useful defaults, fewer decisions per screen.
WebUXAccessibility
03 — Toolkit
What I reach for, and why.
Backend & data
CoreC# / .NETSQL ServerREST APIs
Frontend
CoreAngularTypeScriptAccessible UI
Desktop
CoreWPFOffline-first
Cloud & delivery
In productionCloudflareCI / CD
Currently exploring
LearningGoogle CloudAWSAzure
Leadership
DailyCode reviewsMentoringPlanning
04 — Approach
Good architecture is a series of deliberate trade-offs.
01
Map the problem before writing the code.
The data model, the owners and the edge cases get agreed first. It is cheaper to change a diagram than a database.
02
Leave room for change without building for it.
Clear boundaries and small interfaces, so tomorrow's requirement is an addition, not a rewrite.
03
Make the interface honest.
Show people what the system is actually doing, including when it fails, in plain language.
04
Own it in production.
Logging, permissions and monitoring are part of the build, and I stay responsible after launch.
05 — Journey
Four years of shipping, leading and learning.
Now
Technical Team Lead, Full Stack
Leading a team of 4+ engineers building in-house CRM, HRMS and business workflow products with .NET, Angular and SQL.
Earlier
The systems years
Roster and attendance systems, scheduling automation with Google APIs, and .NET / WPF desktop tools for operations teams.
Where it started
Learning by shipping
Small real projects for real users, which taught me that the hard part is rarely the framework.
Education
MCA and BCA
Master of Computer Applications, after a Bachelor of Computer Applications.
06 — Contact
Have a difficult system to untangle?
Tell me what you are building. I reply within two working days.