Backend Lead– AI-Native Care Orchestration Platform, Pune

Role: Backend Lead– AI-Native Care Orchestration Platform Location: Pune / Remote (with overlap) Mode :Full-time About Azodha: Healthcare is moving out of hospitals—into homes, virtual care, and distributed models. The technology to run this shift doesn’t really exist yet. Azodha is solving that. We siton top of existing systems and coordinate what actually makes care delivery work—people, workflows, logistics, and data—in real time. The result is a single system that replaces fragmented tools and manual coordination. We’re not another point solution. We’re building the operating layer fordecentralized care.What this role is really about: You’ll be shaping backend systems used directly by clinicians and care teams—where scheduling, coordination, and data exchange need to work reliably across fragmented systems. This isn’t just about writing code—you’ll also shape how backend engineering is done here.You’ll: Set the technical direction. Raise the bar on system design and execution. Help other engineers grow into strong system thinkers. If you enjoy owning both systems and the people building them, this will feel like the right scope. What you’ll work on: Backend systems that hold up in the real world.Design and evolve backend services using Node.js and TypeScript. Build REST APIs and GraphQL endpoints powering web and mobile applications. Model and manage data using PostgreSQL and related tools. Work with event-driven systems for coordination, notifications, and integrations. AI as part of the system (not a side feature)Integrate AI into backend workflows—automation, orchestration, and decision systems. Work with LLMs, AI pipelines, and intelligent data flows in production. Think through real trade-offs: latency, reliability, cost, and safety. Data that drives real-time decisions Design data flows and pipelines that support operational workflowsWork with tools like Airbyte, dbt, Airflow / AWS Glue where needed Enable systems to react in real time—not just report Systems that don’t get to go down Run and scale systems on AWS (ECS, EC2, S3, RDS, Lambda). Own CI/CD, observability, and production reliability. Build for environments where failures have real-world consequences.Interoperability (where things get interesting) Work with HL7 / FHIR and EMR integrations. Handle real-world healthcare data and constraints. Design systems that make disconnected platforms actually work together. Leadership&Ownership Set direction for backend architecture and engineering practices. Review designs and code with a focus on long-term quality and scalability. Mentor engineers and help them grow in system design and ownership. Drive clarity in ambiguous problem spaces and align teams around solutions.Partner closely with product, frontend, mobile, and integrations teams. Take ownership of outcomes—not just tasks What you’ll influence Backend architecture across the platform. How AI is used in real production systems. Engineering standards, system design, and technical direction. The way care delivery workflows scale in decentralized environments.What we’re looking for Strong hands-on experience with Node.js, TypeScript, and distributed systems. Experience designing APIs (REST / GraphQL) and working with PostgreSQL. Comfortable working with event-driven architectures. Experience with AWS and production-grade infrastructure. Ability to reasonabout systems end-to-end, not just individual services.Experience leading projects or mentoring engineers (formally or informally). Exposure to healthcare (HL7/FHIR) is helpful but not required. Interest in AI systems and how they behave in production. Why this is worth your time The problems are real, messy, and unsolved. The systems you work on directly impact clinicians and patients.You’ll have real ownership—not a narrow slice of a large org. You’ll work on AI systems that are actually used in production. You’ll shape both the technology and the engineering culture If you’re looking for: Another microservice in a large org → this isn’t it Clean, well-definedproblems → also not it