Backend Engineer

Healthcare in India is fragmented by design: insurance lives in one place, OPD in another, diagnostics somewhere else, and the hospital is a separate journey entirely. Even Healthcare was built to close that gap. The platform combines clinical care delivery with insurance-like coverage, so a member can consult a doctor, book a lab test, get hospitalised, and have the claim settled without leaving the Even ecosystem.

The team opened its first hospital in Bengaluru last year. Two more are on the way this year, with five to six planned by the end of next year. Managed care programs for chronic conditions, a consumer app, telemedicine, and a UPI scanner built directly on bank rails round out the surface area. Under 25 engineers have built all of it.

A full-stack healthcare system, built from Bengaluru, for India.

Even's backend team is lean by design: under 25 engineers building the software that doctors, hospitals, and patients depend on daily. The team has depth at the junior end. What it needs now is someone who arrives with their own thinking, does their own groundwork, and brings conclusions to the table.

The surface area is wide and consequential. A hospital management system is being built from scratch. Claims processing is still largely manual, with the first layer of LLM automation in place and several more to go. The EMR platform, cashless settlements, telemedicine, and partner integrations all need senior hands. You will work closely with the CTO and tech leads, but the expectation is clear: identify the next problem worth solving before anyone hands it to you, and implement the solution yourself. The first stretch is IC work; mentoring the junior engineers is part of the seat, not a separate job.

The hospital management system, from scratch. Even is building it now. You pick up the hardest parts and drive them to production.

Claims automation, layer by layer. One LLM layer is in place. You design and ship the next several, moving the process from largely manual to largely automated.

The EMR and cashless settlement infrastructure. Core clinical systems that doctors and patients depend on daily. You hold the quality bar and push the surface forward.

Partner and vendor integrations. Labs, diagnostics, banks, payment gateways, KYC providers. You own the integration layer end to end.

Developer tooling and internal platforms. Even's engineers build their own leverage: a time-machine DB viewer, an LLM-based data science engine. You add to that stack.

Problem identification, not just execution. By week six, you are expected to surface the next gap worth solving, bring a point of view on how to close it, and implement the solution yourself.

Mentorship of junior engineers. The team skews junior. You raise the floor without waiting to be asked.

You have five or more years of backend engineering, with real IC depth. You have not drifted into pure code-review mode. You still write, structure, and reason through code yourself.

Strongly typed languages are your home. Golang, Java, or C++ is your core stack. You can pick up a new language fast because your fundamentals are solid, not because you rely on AI to fill the gaps.

You explain trade-offs, not just decisions. When you propose an approach, you can walk through the alternatives you considered and why you landed where you did. This is how you earn trust at Even.

You have built on distributed systems at scale. Performant, reliable, production-grade. You know what breaks and why.

You identify problems before they are handed to you. In past roles, you have walked into a room with a diagnosis, not a question. That instinct is what the CTO and tech leads are making room for.

You can translate technical thinking for non-technical stakeholders. Clinical teams, business leads, and product managers are your collaborators. You get out of the tech bubble and make your reasoning legible to them.

Early-stage startup pedigree, especially in the building phase. You joined a company when the systems were still being invented, not after the playbook was written. People who built Swiggy, Zomato, Dunzo, or CRED in their early chapters know what this feels like.

Own the problem, not just the ticket. You are expected to identify what needs solving before it lands in a sprint. Diagnosis is part of the job.

Do the groundwork yourself. Come to the CTO or tech leads with conclusions, not questions. The discussion is a calibration, not a kickoff.

Translate across the room. Engineering sits alongside clinical, business, and product teams. You make your thinking legible to people who do not share your vocabulary.

Back your proposals with reasoning. If you are recommending an approach, you have already considered the alternatives. Trade-off clarity is how trust is built here.

Build leverage, not just features. Even's engineers build tools that make the whole team faster. That instinct is expected, not optional.

Move fast without losing the basics. AI-assisted development is the norm. Knowing when the output is wrong is the skill. Clean code, clear structure, and sound fundamentals are non-negotiable.

Mentor without being asked. The team skews junior. You raise the floor as a matter of course, not as a formal responsibility.

Series A, with a 1:1 ESOP match on your cash component, vested over four years with a one-year cliff. Cash between 50L and 70L, with room for the right person. The equity is structured so you can tilt the mix toward cash or toward upside, depending on what you are optimising for. A founding-level seat in a system that will run India's next hospital chain.