Build a product that connects people with health knowledge they would otherwise never discover. CureforME is building a private health-research membership that connects a persons background, interests and records with relevant global research, emerging technologies and natural approaches. This is an opportunity to help shape an early product, make technical decisions and own working systemsnot simply complete isolated tickets.

Role & responsibilities The experience brings together a personal profile, weekly research briefs and follow-up questions—supported by source evidence, comparisons, discovery maps and ongoing updates to information a member previously saved. We help members understand and access information; we do not diagnose or prescribe.

1. The complete member application

- Build a polished, responsive React/Next.js and TypeScript application that works well on phones and desktop.
- Develop onboarding, separate member profiles, record uploads, document views and correction flows.
- Build personalised weekly briefs, finding details, source references, comparisons with a member’s stated current approach, and map-based discovery.
- Build question submission, follow-up, answer history and clear status tracking.
- Surface relevant changes to previously saved findings, products or records through continuity updates.
- Make navigation, deep links, forms and notifications work end to end, including loading, empty, error, retry and permission-denied states.

• Build internal research-review tools, institution invitations and basic subscription or billing workflows.

1. Backend services and data infrastructure

- Build Python/FastAPI or equivalent services, application APIs and integrations with clear contracts.
- Design PostgreSQL schemas, migrations, indexes and efficient queries.
- Create scheduled ingestion pipelines for permitted APIs, web pages, documents and other authorised sources.
- Handle pagination, rate limits, background jobs, retries, partial failures and reproducible reprocessing.
- Parse HTML, PDFs and scanned records using suitable extraction and OCR tools.
- Preserve original documents, source links, publication and retrieval dates, page or passage references, permissions and extraction confidence.
- Deduplicate records, resolve identities and model relationships between sources, research findings,



products and relevant entities.

• Maintain version history and detect changes without silently overwriting earlier information.

1. AI and retrieval features

- Integrate model APIs, keyword search and semantic retrieval into useful product workflows.
- Produce structured, validated outputs connected to supporting source passages.
- Support profile-to-information matching while keeping uncertain matches reviewable.
- Build evaluation examples and tests for extraction quality, relevance, citation correctness and failure cases.
- Measure and improve model/API cost, latency and reliability.

• Treat retrieved documents and model outputs as untrusted input; protect confidential data and prevent unsupported output from being treated as verified information.

1. Production quality and ownership

- Implement authentication, server-side authorisation, secure file access and appropriate member/staff permissions.
- Ensure members cannot access one another’s records and institutions do not receive automatic access to private member information.
- Write unit, integration and end-to-end tests, including meaningful permission-boundary checks.
- Own deployments, CI/CD, monitoring, safe logging, backups, recovery and production debugging.
- Instrument useful product events without exposing sensitive content.
- Improve accessibility, mobile usability, performance and operational reliability.

• Work directly with the founder, clinical research lead and delivery team to clarify requirements, explain trade-offs and ship improvements.

Preferred candidate profile At least 2 years of professional software engineering experience, with evidence of personally shipping and maintaining working products or systems.

- Strong ability in either Python/backend/data engineering or React/TypeScript/full-stack product engineering, plus the ability to contribute across the stack.
- Practical SQL, API integration, debugging, Git and automated-testing skills.




- Understanding of authentication, permissions and secure handling of private information.
- Ability to turn an unclear requirement into a sensible implementation, test it and explain the result.
- Strong ownership: you investigate failures, communicate early and follow work through to a reliable outcome.

For backend-focused candidates:

Strong Python, SQL, database design, ingestion pipelines and background processing are essential. Practical retrieval or model-API experience is valuable.

For product-focused candidates:

Strong React, TypeScript, responsive UI development and backend integration are essential. You should understand server-side application logic, authentication and permission checks—not only frontend styling.

USEFUL ADDITIONAL EXPERIENCE

Next.js, FastAPI, Node.js, Docker, cloud deployment, Playwright, OCR, multilingual documents, graph modelling, vector search, document viewers, maps, payments or privacy-sensitive products.

You do not need every listed framework. Healthcare experience, a postgraduate degree, a particular graph database and training AI models from scratch are not requirements.

WHAT STRONG OWNERSHIP LOOKS LIKE

- A complete member journey: someone can explain their interests, receive useful source-linked information, compare possibilities, ask a question and return to an answer.
- A dependable information system: new or changed sources can be processed, traced, evaluated and reviewed without losing history.
- A product that improves through real usage: you identify weak points, propose better approaches and ship measurable improvements.

• Maintainable engineering: clear interfaces, helpful tests, controlled costs and systems another engineer can understand.

AN EXAMPLE OF THE WORK A member opens a weekly finding on their phone, checks the original source, compares it with an approach they already use and submits a question. Later, the underlying source changes. The system preserves both versions, identifies a possible connection to the saved finding and makes the supporting evidence available for review. The member can understand what changed, while their private records remain protected.

Our two engineers will work together across this complete experience.

Perks and benefits

Equity Vesting

📌 Fullstack Engineer (New Delhi)
🏢 Cure For Me
📍 New Delhi