Website:
Job details:
Product Engineer — Intern
3-Month Internship • Path to Full-Time • Bengaluru (Remote-First)
Location
Bengaluru-based; work is remote-first, with in-person client visits, demos, and team syncs as needed
Duration
3 months (internship), with conversion to full-time Product Engineer for strong performers
Function
Product Engineering
Reports to
Manager, Product Engineering
Stipend
₹15,000 / month
About SurgySurgy Innovation Labs builds an AI-first Hospital Operating System for mid-market hospitals across India and the GCC. Our live product suite includes:
- SurgyScribe — AI clinical documentation and ambient voice-to-note for doctors
- SurgyInsight — predictive analytics and BI layered directly on hospital data
- SurgyCRM — patient engagement and lead-to-treatment CRM with a predictive layer
- SurgyLearn (SurgyAcademy) — training and certification for hospital staff and external learners
- SurgyFrontdesk — AI-assisted front-desk and OPD workflow automation
We're live across 8 paying hospital groups — 242+ centres and 2,000+ users — across India, Kuwait, and Bahrain, and are currently building out the next layer of the Hospital Operating System (OPD, IPD, ER, Billing, Lab, Oncology, and more) with marquee hospital partners.
Learn more at surgy.health.
The RoleThis isn't a typical dev-intern or PM-intern role. Depending on what's live at the time, you'll either pick up an existing Surgy module and take it further, or start a new one from scratch — either way, you own the entire lifecycle yourself: discovery, requirements, design, build, test, and demo, with AI tools (vibe coding, vibe prototyping) as a default part of how you work, not an experiment on the side. You'll work directly alongside Product Engineering, Deep-Tech & Platform, and QA Automation, and get real exposure to how a fast-moving healthcare SaaS company makes product decisions in the room with actual hospitals. We're looking for someone who wants full accountability for something real, fast, rather than a narrow slice of a larger team's work.
What You'll OwnOne or two modules from Surgy's product suite — for example SurgyScribe, SurgyInsight, SurgyCRM, SurgyLearn, SurgyFrontdesk, or a new Hospital OS module such as SurgyOPD or SurgyBilling. Depending on what's live at the time, you'll either inherit an existing module — its roadmap, backlog, and open issues — and take it further, or start a new one from the ground up, beginning with discovery. Either way, you own it end to end: strategy, requirements, client communication, design, build, test, and demo.
Core ResponsibilitiesDiscovery & Product Strategy
- Run discovery conversations with hospital stakeholders (doctors, nurses, admin, billing staff) to surface real workflow problems.
- Translate discovery findings into a clear problem statement and product bets for your module(s).
- Keep your module's roadmap aligned to Surgy's Quality Excellence, Value Maximization, and Revenue Realization thesis.
Requirements Analysis
- Own the PRD for your module(s): write it, iterate it, and keep it current as scope evolves.
- Resolve ambiguity and contradictions in requirements yourself before escalating.
- Break requirements into engineering-ready epics and stories in Plane.
Client Communications
- Be a direct point of contact for assigned hospital stakeholders on your module — via WhatsApp, calls, or email, logged same-day in Plane.
- Run requirement-gathering and UAT sessions directly with clients, without a proxy.
- Communicate scope, timelines, and trade-offs plainly — no over-promising.
Regular Cadence
- Run a predictable weekly cadence: standups, sprint reviews, and stakeholder status updates for your module.
- Surface progress, blockers, and risks proactively — don't wait to be asked.
- Keep status visible and current in Plane at all times.
User-Oriented Design
- Design workflows and screens around how hospital staff actually work, not how the system happens to be built.
- Prototype fast — Figma or AI-assisted vibe prototyping — before writing production code.
- Validate design decisions with real users, not assumptions.
Software Development
- Build and ship your module's features end to end — frontend, backend, and integrations as needed.
- Write code the rest of the engineering team can maintain, not just code that runs.
- Use AI coding tools (vibe coding) to move fast, while staying personally accountable for what ships.
Testing & QA Automation
- Test your own module thoroughly before handoff — QA is not a safety net for untested code.
- Work directly with the QA Automation team to define test cases and get automated coverage in place for your module.
- Close the loop on defects — verify fixes, don't just log them.
Product Demos
- Demo your module to internal stakeholders and clients yourself, confidently.
- Handle live questions and objections in the room.
- Turn demo feedback into backlog items within the same cadence cycle.
AI-Native Way of Working
- Use AI tools across the lifecycle — discovery synthesis, PRD drafting, prototyping, coding, and test-case generation.
- Vibe coding and vibe prototyping are the expected default, not a shortcut you need to justify — but you own the judgment on what actually ships.
- Bring new AI tools or workflows to the team when you find something that works.
What We're Looking For- Final-year student or recent graduate in Computer Science, Engineering, Design, or a related field — or equivalent portfolio/project experience.
- Comfortable writing and shipping code in any stack; we care about output, not the specific language.
- Already using AI tools (ChatGPT, Claude, Cursor, or similar) as part of how you build, not just how you search.
- Can hold a requirements conversation and a demo directly with a non-technical stakeholder.
- Bias toward ownership — comfortable being the one person accountable for a module end to end, not just a ticket.
- Based in, or able to relocate to, Bengaluru.
Nice to Have- A hackathon build, personal project, or freelance work shipped to real users.
- Exposure to Figma or another design/prototyping tool.
- Interest in, or exposure to, healthcare and hospital workflows.
- Familiarity with tools like Plane, Jira, or Linear.
What Success Looks Like at 3 Months- Your assigned module(s) are live in production with real usage — not just a demo build.
- A current, accurate PRD and backlog exist for your module.
- You've delivered at least one client-facing demo independently.
- QA Automation has signed off on your module's core flows.
- You've kept a clean track record of on-time weekly updates, with no surprises.
Click on Apply to know more.
