This is a role at the intersection of engineering, partnerships, and program management. As Healthi's Tech Lead for Partner Integrations, you will be the single point of contact for every new integration we build with healthcare providers (labs, hospitals, diagnostics chains) and channel partners (healthtech apps, insurtech, employee benefits, and HR platforms) and the steward of relationships with every partner we've already integrated.
That said, this role does require some prior leadership experience, at least 1-2 years running a small engineering team with real delivery and mentoring accountability or a high‑visibility role where you have managed third‑party integrations and relationships. Beyond that, the bar is what you can demonstrably do, not how long you've been doing it.
New Partner Integrations, End‑to‑End
- Be the single point of contact for every new integration from the first technical conversation through delivery, go‑live, and ongoing engagement.
- Scope integrations jointly with partner technical teams: data flows, identity and auth, sync vs async patterns, event semantics, error handling, SLAs.
- Translate partner‑side ambiguity and constraints into clear execution plans for the Healthi team.
- Sequence work across multiple concurrent partners so we deliver predictably even when external dependencies are messy.
- Own the go‑live: cutover, sign‑off, and a clean transition into steady‑state operations.
Ongoing Partner Relationship Management
- Be the technical face of Healthi to existing integrated partners such as labs, hospitals, healthtech, insurtech, benefits, and HR platforms.
- Run regular check‑ins, handle escalations, and own SLA conversations.
- Identify expansion opportunities – most integrations grow over time, and that growth has to be actively driven, not reactively engaged.
- Coordinate change requests, deprecations, version upgrades, and partner‑driven roadmap items with the Healthi team.
Engineering Leadership
- Lead a team of 2+ engineers focused on integrations and platform work.
- Run design and code reviews; set engineering standards; mentor and unblock.
- Make pragmatic architecture trade‑offs: speed vs maintainability, bespoke vs standardised, build vs buy.
- Hire engineers as the team grows, with a sharp eye for ownership and an execution mindset.
Hands‑on Technical Contribution
- Represent Healthi in conversations with CTOs and other senior technology leaders at the partners.
- Build credibility through technical expertise and product intimacy.
- Personally own architecture for complex or high‑stakes integrations.
- Contribute code in the critical path when it matters.
- Drive engineering best practices around API design, event handling, and infrastructure‑grade reliability.
Program Management And Visibility
- Maintain a clear pipeline view of integration projects, including status, dependencies, partner‑side blockers, and internal blockers.
- Proactively communicate up to leadership and across Healthi.
- Build the muscle on the team for predictable delivery against external commitments.
Communication and Stakeholder Management
- Run a meeting with a partner's CTO and a partner's product manager in the same call without confusing either.
- Write clearly. Internal updates, partner emails, technical specs – all in your own voice, all on time.
- Instinctively track commitments, deadlines, and owners. Things don't fall through the cracks on your watch.
- Disagree without being disagreeable, and hold a technical position without breaking the relationship.
Curiosity and Initiative
- Integrations work rewards curiosity disproportionately, and we hire for it deliberately.
- Don't wait to be told what's broken or what's next. You notice, and you act.
- You're genuinely interested in how Indian healthcare and benefits tech actually works – the standards, the standards everyone ignores, the workarounds, the politics.
- Enjoy talking to people who do different jobs from yours.
Requirements
- Strong API design fundamentals, REST and GraphQL, with real opinions on versioning, errors, idempotency, and pagination.
- Solid grasp of integration patterns, webhooks, event streams, polling, file drops, message queues (RabbitMQ and Kafka) and when each is the right choice.
- Authentication and security across partners: OAuth flows, mTLS, signed JWTs, IP allow‑listing, key rotation, and SAML 2.0 protocols.
- Data mapping and transformation, including the unglamorous reality of reconciling partners' inconsistent schemas to ours.
- Integration observability distinct from product observability, logging, replay, dead‑letter queues, partner‑facing status, and asynchronous design patterns.
- Comfortable across our stack: Java (Spring Boot), Python, Ruby on Rails (good to have), MongoDB / PostgreSQL / MySQL, Docker, Azure, GraphQL, APIM, Metabase.
- Healthcare data exposure (HL7 FHIR, ABDM) is a real plus.
- Familiarity with HRMS / benefits APIs (Darwinbox, Keka, Plum, and similar) or insurtech APIs is also genuinely valuable.
Bonus
- Direct experience integrating with Indian healthcare providers, insurers, or benefits platforms.
- Exposure to AI / LLM‑based integrations.
- Ruby on Rails familiarity (parts of our stack).