Backend Lead — Revenue and Supply

Positions - 1

Experience - 6–8 years

Reports to- Tech Lead / Architect

Location - Chennai, with travel to the pilot hospital

Type - Full-time

About The Company And The Product

India Health Link is building a new multi-tenant Hospital Management Information System (HMIS) — one platform serving many hospitals — with Artificial Intelligence (AI) features delivered as optional plug-ins on top of a core that works fully without them. It is a greenfield build, and the first pilot hospital goes live in month 6.

Our stack: TypeScript, NestJS (Node.js backend framework), PostgreSQL 16, React, React Native, Amazon Web Services (AWS) — ECS Fargate, RDS, DynamoDB, S3, Redis, EventBridge — Terraform, GitHub Actions, Playwright.

Why this role exists

Money and stock are the two areas where a bug is not really a bug — it is a hospital's revenue leaking, or a drug count that does not match what is on the shelf. This role owns both, plus the discipline of getting a release out every sprint.

What You Will Build

• Tariff engine: multiple rate cards per hospital — cash, corporate, Third Party Administrator (TPA), Pradhan Mantri Jan Arogya Yojana (PMJAY) — with package and exclusion rules.
• Charge capture driven by events: an order placed anywhere in the hospital becomes a billable line automatically.
• Billing: outpatient and inpatient billing, cashier and day-close, advances, refunds, credit notes, and Goods and Services Tax (GST) treatment.
• Claims and TPA workflow: pre-authorisation, queries, submission and tracking.
• Pharmacy, stock ledger and procurement: an append-only ledger where every movement is a posting and stock on hand is always derivable.
  
  

Responsibilities

• Lead the Revenue and Supply pod — yourself, one backend engineer and one frontend engineer.
• Own the rules test pack: build it from fifty real anonymised bills from the pilot hospital, and treat a failing case as a release blocker.
• Own release discipline — versioning, migrations, rollback plan, release notes.
• Review all code touching money or stock, without exception.
• Work with the Chartered Accountant and GST consultant on statutory correctness in month 4.
  
  

Requirements

• Strong NestJS or an equivalent Node.js framework, with PostgreSQL.
• Has owned a payments, ledger, billing or accounting-like domain in production — you understand why you never update a posted row.
• Event-driven patterns: queues, idempotent consumers, eventual consistency, and the ability to explain it to a finance user.
• Real SQL, including reconciliation queries and reporting under load.
• Has led two or three engineers.
  
  

Good to have

• Indian statutory context: GST on healthcare services, Tax Deducted at Source (TDS), e-invoicing.
• Hospital or insurance billing exposure.
• Inventory or warehouse systems.
  
  

Your first 90 days

• Month 1 — the tariff data model and the charge-capture event contract agreed and built.
• Month 2 — outpatient billing end to end, with the rules test pack running in continuous integration.
• Month 3 — pharmacy sale and stock ledger live in the demo build.
  
  

How We Work

Two-week sprints. Trunk-based development with short-lived branches. Code review on every pull request. Database changes only through migrations. Automated tests are mandatory around money, stock and clinical-safety paths.