MayaMD — PPHM Solution (S.V.M.)

Daffodil Software · Nov 2021 – Apr 2022

MayaMD was my first full-time gig out of school — a personalized public-health management platform. I joined as a fresher, was dropped straight into a healthcare product, and had to absorb a lot in a hurry. Looking back, it's the project that taught me how to ship inside a real codebase with a real review process.

what I worked on

• UI work alongside cross-functional teams — translated advanced design and product requirements into React components, improving user experience and interface functionality on top of an existing system.
• Third-party lab API integrations that enhanced data interoperability and streamlined diagnostic workflows. The same problem space I'd hit again in HIMS Agroha later.
• Built and deployed API endpoints — first real exposure to writing the backend half of the features I owned.
• PDF generation pipeline using Puppeteer + EJS — automated document creation for reports and patient-facing artefacts.

what stuck with me

• The first job teaches you the shape of professional software — review cycles, branch hygiene, what production logging really looks like. The specific tech stack matters less.
• Healthcare APIs are the kind of thing where small bugs become very real problems quickly. I learned to read API specs three times before writing the integration once.
• Redux-Saga is great when you stop fighting it and start trusting the side-effect tree.

what I'd do differently

• I'd ask more questions, earlier. I treated "I don't know what this means" as a personal gap to fix on my own time. It would have been faster — and better for the product — to ask the BA in week one.
• I'd push back on pure-implementation scope and ask "why this decision?" more. I shipped what was asked. I should have, sometimes, made the case for shipping something better.