About & professional journey

A long-form CV, written in prose.

Two roles, both contracts with the National Informatics Centre, both centred on building digital services for citizens and government users. What follows is the long version — the short version is the timeline below.

  1. Aug 2023 –
    Present

    Senior Developer (contract)
    NIC Punjab · iHRMS Punjab

    Working on the iHRMS Punjab programme on the .NET MVC + SQL Server stack. Primary responsibility is the Medical Reimbursement module, with additional contributions across other iHRMS modules. Recent technical work has focused on:

    • Modernizing the front-end across multiple iHRMS modules — jQuery and Bootstrap version upgrades, consolidating UI patterns, and replacing legacy components.
    • Migrating document storage from SQL Server FILESTREAM to an SFTP-based architecture, reducing database footprint and improving file-handling reliability.
    • Building reporting, workflow, and approval-flow features across the Medical Reimbursement module’s multi-level review pipeline.
    • Adjacent work on other iHRMS modules where shared infrastructure or UI work crosses module boundaries.

    Stack · ASP.NET MVC  ·  C#  ·  SQL Server  ·  jQuery  ·  Bootstrap  ·  SFTP

  2. Dec 2019 –
    Aug 2023

    Programmer (contract)
    NIC Karnataka · KSAT case‑management

    Worked on a digitized court-application system for the Karnataka State Administrative Tribunal. The system covered the full case lifecycle — from case receipt and registration through hearings, orders, and final disposal.

    This was my grounding in e-governance systems — case-management workflows, role-based approvals, and the practical realities of building digital services for government users.

    Stack · PHP  ·  Laravel  ·  Apache  ·  Tomcat  ·  HTML  ·  CSS  ·  JavaScript  ·  jQuery

Elsewhere on the internet

The places I’m findable, and the projects I quietly maintain.

How I work, briefly

I am most useful at the seam between an old codebase and whatever it’s being asked to do next. Migration work is unglamorous and high-leverage, and I have come to enjoy it. I prefer reading code to reading specs, and I prefer writing prose about the system to drawing diagrams of it.

I lean AI-native in the workflow but old-school in the mental model. The model is fast at producing plausible code; my job is to know which parts of the codebase the plausible code will quietly break. That’s the job.