Product Owner

Budget : 23 lpa

Experience : 5+ years

This role is for a Product Owner in the Healthcare IT domain .

The person acts as a bridge between business (healthcare users) and technical teams (developers, testers) .

They need both domain knowledge (healthcare, EHR, clinical / revenue cycle workflows) and technical understanding (APIs, databases, integrations) along with strong communication and stakeholder management skills .

Technical Skills

Must Have

Strong Healthcare domain knowledge (clinical workflows or revenue cycle – billing, claims, patient data flow).

Worked in Agile / Scrum methodology (used in IT projects).

Ability to write requirement documents and create wireframes (basic mockups of screens).

Understanding of Software Development Lifecycle (SDLC) .

Knowledge of APIs, SQL databases, integrations .

Expert backlog management (managing features & user stories for the dev team).

Good to Have

Ability to write basic SQL queries .

Cloud basics (AWS).

Familiarity with healthcare IT standards – FHIR, HL7, REST APIs, EHR systems.

Knowledge of system integrations tools like Rhapsody, Corepoint, Mirth.

Soft Skills

Strong problem-solving skills.

Excellent communication (both written and verbal).

Ability to explain technical / complex topics in simple language.

Decision-making skills .

Strong stakeholder management (coordinate between doctors, healthcare staff, business, and IT teams).

Education / Certifications

No strict requirement listed, but healthcare IT certifications (like HL7, FHIR, AWS basics, Agile / Scrum certifications ) would be a plus.

Experience

Total : 5+ years overall.

Relevant : 3+ years in Healthcare IT as a Business Analyst / Product Owner .

Key Responsibilities

Manage the product backlog (deciding what features the dev team should build first).

Break features into user stories (small work items for developers).

Understand customer & product needs and act as the voice of business for the dev team.

Work with the Product Manager on feature priorities.

Review test cases and ensure they meet acceptance criteria.

Approve completed user stories once tested and demoed.

Create UML diagrams (simple workflow diagrams).

Create wireframes (simple sketches / screens for new features).

Understand system architecture, data flow, and integrations (how different healthcare systems talk to each other).