Positions:2 Full Time
Experience
4 - 6 Years
Backend Engineer — Platform
Bangalore, India (Hybrid / Remote)
About the Role
We are building the next generation of conversational AI for healthcare — autonomous agents that connect patients with care, navigate appointments, and close gaps in clinical workflows for leading US health systems.
We are looking for a Backend Engineer to join our Platform team. You will design, build, and own backend services that power our AI-driven healthcare products — writing production-quality code in Java and Python, contributing to distributed system architecture, and taking end-to-end ownership of features from design through delivery.
This is a high-ownership role for someone who wants to build meaningful products at scale in a fast-moving, technically rigorous environment — and who is comfortable collaborating across time zones with teammates in India and the United States.
What You'll Do
Backend Development & Ownership
Design, develop, and maintain backend services and APIs using Java and Python — writing clean, well-tested, production-ready code that handles real patient interactions at scale
Take end-to-end ownership of features — from initial design through development, testing, deployment, and post-launch monitoring — without needing constant oversight
Debug and resolve production issues promptly — you treat reliability as a first-class concern and understand the clinical consequences of systems that are slow or unavailable
Develop a deep understanding of customer pain points — review support issues, monitor customer-facing errors, and react quickly when production incidents affect patients or clinicians; use that context to prioritize fixes and shape technical decisions that solve the right problems
Actively use AI-assisted development tools such as Claude to accelerate coding, design review, and documentation — we expect fluency with modern AI dev tooling, not just awareness of it
Participate in code reviews — giving and receiving substantive technical feedback that raises the quality bar for the whole team
System Design & Architecture
Design and evolve microservices and distributed system components — with a clear understanding of tradeoffs around consistency, availability, latency, and fault tolerance
Contribute to architectural discussions with a point of view — propose solutions, identify risks, and push back constructively when you see a better path
Write clear, detailed design documents that communicate your approach to peers and stakeholders — we value written technical thinking as much as working code
Design for observability from the start — logging, metrics, alerting, and tracing are part of the feature, not an afterthought
Ensure services meet compliance requirements — including HIPAA and data privacy standards appropriate for healthcare applications
Quality & Engineering Rigor
Write comprehensive test plans and own test coverage for your components — unit, integration, and end-to-end — as part of normal delivery, not a separate phase
Define and track quality metrics for services you own — error rates, latency percentiles, throughput — and act on them proactively
Maintain operational rigor across your services — keep runbooks current, ensure alerts are actionable rather than noisy, participate actively in post-incident reviews, and continuously reduce toil through automation and improved tooling
Contribute to on-call rotations and participate in incident response — you understand how the services you build behave under pressure
Document what you build — API contracts, runbooks, architecture decisions — so the team can operate and evolve your work without depending on you personally
Cross-Team Collaboration
Work closely with teammates across India and the United States — communicate clearly in writing, run effective async handoffs, and participate constructively in cross-timezone meetings
Collaborate with AI, product, and infrastructure teams to deliver features that span multiple services — understanding dependencies and coordinating delivery across team boundaries
Surface technical risks and schedule concerns early — to your tech lead, manager, and cross-functional partners — with proposed mitigations, not just status updates
What We're Looking For
Required
3–5 years of professional software engineering experience, with a strong focus on backend systems at a software or technology company
Hands-on proficiency in Java and Python — you've used both in production, not just in coursework or side projects
Solid understanding of microservices architecture and distributed systems — you've designed and operated services that handle real production load, and you understand what goes wrong at scale
Experience writing design documents and technical specifications — you can communicate a system design clearly in writing before writing a line of code
Experience writing test plans and owning end-to-end quality for backend components — testing is part of how you ship, not something you do at the end
Comfort using AI-assisted development tools — Claude, GitHub Copilot, or similar — as part of your everyday engineering workflow
Proficiency with Git and GitHub — pull requests, branching strategies, code review workflows, and CI/CD pipelines integrated with version control
Strong written and verbal communication in English — this role requires clear async communication across time zones with US-based teammates
Ability to take ownership and drive features to completion independently — you don't need to be told what to do next once requirements are clear
Strongly Preferred
Experience at a company with a rigorous engineering culture — strong code review practices, design document culture, on-call ownership, and high bar for production quality
Exposure to AI or machine learning systems in production — building APIs or services that wrap LLMs, handle model inference, or process conversational data
Experience in healthcare technology or other regulated industries — familiarity with HIPAA, data residency requirements, or audit logging
Familiarity with major cloud platforms such as AWS or Azure — compute, storage, messaging, and managed database services; we use both and value breadth over depth in any single provider
Familiarity with API design patterns — REST or event-driven architectures — and the tradeoffs between them
Experience with observability tooling — Grafana, CloudWatch, OpenTelemetry, or similar — for dashboards, alerting, and distributed tracing
You're Probably Not the Right Fit If
You prefer to hand off your work to QA or ops teams — this role requires full ownership through deployment and beyond
You rely on verbal communication over written artifacts — in a distributed team, clear writing is a core engineering skill, not a soft skill
You're not comfortable with ambiguity — requirements evolve and systems need to adapt; you'll need to make sound technical decisions with incomplete information
About the Team
Our team is a small, experienced group of engineers with backgrounds at large-scale technology companies. We operate with high ownership, direct communication, and a strong preference for written clarity over meeting-heavy processes.
We've built conversational AI healthcare agents from scratch — handling real-time patient communication, care navigation, and appointment scheduling for health system partners. We care about latency, reliability, compliance, and shipping things that actually work for patients and clinicians.
We're at an exciting stage — our AI work has real distribution into health systems across the country, and a genuine opportunity to have clinical impact at scale. This role is based in Bangalore, India, and works closely with a distributed team including colleagues in the United States.
PIc4144867f437-37437-41465305
