Engineering systems that survive the messy reality of production.

1. Why Healthcare & High-Consequence Systems?

Many software engineering careers are spent tweaking consumer feeds or marketing funnels. My path shifted fundamentally when I began working directly with public health programmes and hospital clinics.

In rare disease care (such as Hemophilia and Thalassemia), software is not a convenience—it is a critical link in patient survival. A patient experiencing a sudden joint bleed needs clotting factor concentrate immediately. If a district hospital counter cannot locate a patient's historical dosage or has unexpectedly run out of vials while a facility 40 km away holds expiring surplus, the result is permanent disability or tragedy.

Seeing these failure modes firsthand inside district hospital wards in Punjab and Madhya Pradesh defined my engineering philosophy: software must be built for the people actually using it under pressure—busy clinic staff, nurses, and data operators on spotty broadband connections.

2. SoftEdge Technology Solutions & My Practice

I founded SoftEdge Technology Solutions to serve as the engineering engine for building our own software products (iCare and TaskEdge) and partnering with select enterprise clients on complex software architecture.

Depending on the engagement:

• Enterprise Product Builds: Full-stack applications, data pipelines, and multi-tenant SaaS platforms are contracted through SoftEdge Technology Solutions with dedicated team execution.
• Strategic Advisory & Fractional CTO: High-level system architecture audits, technical diligence, and sprint roadmapping can contract directly with me or via SoftEdge.

3. Core Engineering Principles

• Relational Integrity First: Transactions, database constraints, and audit ledgers are non-negotiable. Never substitute distributed complexity for a well-modeled, indexed PostgreSQL schema.
• Lightweight, Dependency-Conscious Stacks: Keep frontend payloads minimal so applications load in sub-second times on 3G hospital dongles. Avoid unnecessary runtime framework churn.
• Deterministic AI over Hallucinatory Chat: Language models belong in bounded, strongly-typed pipelines with strict schema enforcement (Pydantic / Zod) and citation verification.
• Direct Stakeholder Alignment: I sit down with doctors, state health commissioners, and operations leads to observe real workflow bottlenecks before writing a line of architecture.

4. Founder & Technical Journey