About Eka.Care
Eka.Care is building the healthcare infrastructure layer for India — a GenAI-powered platform trusted by millions of patients, doctors, and healthcare providers.
From EMRs to intelligent clinical workflows, Eka operates at the intersection of healthcare delivery and AI innovation. Hundreds of clinics, hospitals, and health platforms rely on Eka to power real-world healthcare operations.
Our next frontier is
conversational AI agents
— systems that can triage patients, manage appointments, and integrate seamlessly into healthcare workflows across WhatsApp, web, and mobile platforms. These are
production-grade systems
handling real users and real clinical scenarios — not prototypes.
What we're looking for:
You write like you think.
Your PRDs are clear enough for an engineer to build from without a walkthrough. Your prompt drafts are specific enough to test. You've always been the person on a team who ends up writing the thing that everyone else reads.
You're technically curious:
You want to know why the LLM gave the wrong answer : was it context window? A malformed tool call? An ambiguous system prompt? You don't need to be an engineer, but you should find these questions genuinely interesting rather than things to hand off.
You have a GTM instinct.
You understand that a product nobody buys is a failed product. You think about who the buyer is, what they're afraid of, and how to make the value case in a 15-minute demo. You've probably written a pitch, a case study, or a competitive breakdown at some point.
You hold data to a high standard.
Structured data powering AI systems breaks in subtle ways — a mismatched enum, a null field in a required column, a schema that drifted without anyone noticing. You find this kind of work satisfying, not tedious.
Required experience
2–3 years in a product or technical program management, or similar role.
Hands-on experience with LLM tools: ChatGPT, Claude, Gemini, or any prompt engineering work (personal projects count; we want to see that you've actually used these tools to build or solve something)
Familiarity with REST APIs: able to read API documentation, understand request/response structures, and use Postman or equivalent
Strong written communication.
Comfortable with structured data and basic analytics: reading a CSV, writing basic SQL, or interpreting a funnel metric without needing hand-holding.
Nice to have
Prior exposure to healthcare workflows: EMR systems, clinical data, appointment scheduling, or diagnostics
Experience writing GTM materials: positioning documents, sales decks, case studies, or launch briefs
Familiarity with agent frameworks or tool-use patterns in LLMs
Any experience on the client-facing or solutions side: onboarding a client, running a demo, managing an integration timeline
What good looks like (6-month mark)
You've owned at least one client integration end-to-end: from reading the API documentation to the first live session
You've shipped at least one prompt or conversation flow improvement backed by data : you saw the failure pattern, diagnosed it, fixed it, and measured the result
You've contributed to the GTM story for one of our AI products : a positioning brief, a demo narrative, or a client case study that the sales team actually uses
Why this role is interesting
The overlap between AI product management and healthcare is one of the least-explored, highest-leverage spaces in tech right now. You'll work on problems that don't have playbooks yet; what does a reliable AI triage flow look like? How do you QA a conversational product? How do you sell a product that most of your buyers have never seen before?
You'll get exposure to the full product lifecycle in a compressed timeline: requirements, integration, prompt design, data quality, metrics, GTM, and client success.
And the work is grounded. You're not building a recommendation algorithm for engagement metrics. You're building something that helps a patient get the right appointment, or understand what their lab report means.
What this role is NOT
This is not a traditional consumer PM role.
If you're looking for user research, design sprints, and a quarterly roadmap review with a design team ; this isn't that. The work is faster, more technical, and more client-driven.
This is not a "write specs and hand them off" role.
You're expected to stay close to the integration, the data, and the metrics. Ownership here means following the work through to the outcome.
This is not a pure GTM or marketing role.
GTM is a meaningful part of the job, but it's grounded in technical product understanding. You won't be writing copy from a brief ; you'll be writing the brief.
Employee Benefits
Insurance Benefits
Medical Insurance
Accidental Insurance
Parental Support
Maternity Benefit
Paternity Benefit Program
Mobility Benefits
Relocation Benefits
Transfer Support Policy
Retirement Benefits
Employee PF Contribution
Flexible PF Contribution
Gratuity
NPS
Leave Encashment
Other Benefits
Salary Advance Policy
