About the role
About the company and the productIndia 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: Amazon Web Services (AWS), Terraform, GitHub Actions, Docker, TypeScript and NestJS services, PostgreSQL 16, Python for the AI services.
What you will build • The whole AWS footprint as Terraform code: Virtual Private Cloud (VPC), Elastic Container Service (ECS) Fargate, Relational Database Service (RDS) PostgreSQL, DynamoDB, Simple Storage Service (S3), OpenSearch, Redis, EventBridge and CloudFront. • Continuous integration and deployment (CI/CD) on GitHub Actions: build, test, migrate, deploy, roll back. Deployment must be boring. • Environments: development, staging, pre-production with anonymised data, and production. • Monitoring and alerting that a twelve-person team can actually respond to, with centralised logs and traces. • Backup and disaster recovery with a tested restore, not a documented one. • The on-premise edge gateway image that runs inside a hospital's local network for analyser connectivity and Local Area Network mode when the internet is down.
Responsibilities • Own infrastructure cost, keep it inside the agreed monthly budget, and report it monthly. • Own security hygiene: least-privilege identity and access management (IAM), secrets management, encryption at rest and in transit, patching, and network boundaries. • Own remediation for the Vulnerability Assessment and Penetration Test (VAPT) in month 5 — coordinate the external firm and drive every finding to closure. • Make the developer experience good. A new engineer should be productive on day two. • Set up data-residency arrangements appropriate to Indian health data. • Be the person who can tell, at 2 am, whether the problem is our service, the database, or the hospital's internet connection.
Requirements • Four or more years on AWS in production, including ECS or equivalent container orchestration, RDS, IAM and VPC networking. • Terraform written and maintained by you, with proper modules and state management. • Ownership of a CI/CD pipeline, including the database migration step. • Observability in practice: you have been on call, and you have tuned alerts that were too noisy. • Linux and networking fundamentals — you can debug why a device inside a hospital cannot reach a service.
Good to have • Compliance work: ISO 27001, SOC 2, or Indian health data regulation. • On-premise or hybrid deployments, and hardware appliances in the field. • Real cost optimisation on a live bill. • Experience supporting customers with unreliable connectivity.
Your first 90 days • Month 1 — all environments live, CI/CD running, the walking skeleton deployed automatically. • Month 2 — monitoring, alerting and centralised logs in place; backups running with a tested restore. • Month 3 — the edge gateway image built and running against analyser simulators.
How we workTwo-week sprints. Everything is code — infrastructure included. Code review on every pull request.