Pune, Maharashtra, India

Bhramar Raut

Associate Product Manager

Former Wipro Project Engineer with hands-on HIMS Product Implementation and Product Management support experience across healthcare workflows.

I translate stakeholder requirements into structured workflows, user stories, acceptance criteria, Jira work items and UAT-ready product behaviour — connecting healthcare context, functional analysis and cross-functional delivery.

HIMS/HMIS · Requirements · User Stories · Jira · Agile · UAT · Product Implementation

View HIMS ExperienceView Case StudiesResumeContact
Bhramar Raut — Associate Product Manager Portfolio

Professional proof

Wipro · HIMS/HMIS

Project Engineer · 28 Sep 2022–31 Jan 2025

HIMS Product Implementation

Product Management & Functional Support

  • Requirements & Workflow Analysis
  • User Stories & Acceptance Criteria
  • Jira, Agile & Cross-functional Coordination
  • Functional Validation & UAT

HIMS Product Implementation & Product Management Support

Wipro · Healthcare Workflows to UAT

How I worked across HIMS healthcare workflows — supporting requirements, workflow analysis, user stories, acceptance criteria, Jira, functional validation and UAT as a Project Engineer.

View HIMS experience & scope →

01 / Selected work

EdTech
Project-based Product Case Study

Skillverse.in

Requirements, user flows & validation

Req Flow AI Test
View case study →

02 / Admissions ops

Flow
Admissions operations
Role
Access & permissions

Catalyx

Role
Module
Permission
Branch
Lead
State
View case study →

Core capabilities

Structured work. Testable expectations.

Requirements

Clarification, user-story support and stakeholder context.

Execution

Jira maintenance, Agile ceremonies and limited engineering coordination.

Acceptance

UAT, expected-versus-actual checks and documented findings.

Skills & experience levels →

Background

Product, business & technical context

Wipro brought HIMS Product Implementation and Product Management support experience across healthcare workflows. BrickBillion added customer communication and business operations experience. Java Full Stack training supports my understanding of software delivery.

PSM I · Scrum.org, 2026
B.E. Civil Engineering (Honors) · RTMNU · CGPA 7.81

Open to opportunities

Let’s talk Product.

Associate Product Manager

Open to Product opportunities · Pune, Maharashtra, India

Contact me

Experience

Product exposure. Business context.

HIMS Product Implementation and Product Management support at Wipro, followed by business operations at BrickBillion. Each role is presented with its actual scope.

HIMS Product exposure

Wipro · HIMS/HMISRequirements · Jira · UAT · Healthcare Workflows

Business context

BrickBillionCustomers · Operations · Coordination

Technical foundation

Java Full StackWipro Velocity / StackRoute
  1. 2025–26Feb 2025–Mar 2026

    BrickBillion Properties

    Manager — Business Operations Support

    Business operations · Pune

    Supported customer enquiries, operational follow-ups, sales and marketing activities and stakeholder communication. This work added practical understanding of customer needs, information flow and day-to-day business constraints.

    Business operations experience; presented separately from Product Management work.

  2. 2022–25Sep 2022–Jan 2025

    Wipro Limited

    Project Engineer

    Full-time · Official designation

    HIMS Product Implementation and Product Management support across healthcare workflows including Patient Registration, Appointment, OPD, IPD/ADT, Billing, Laboratory, Radiology, Pharmacy and Discharge. Supported requirements analysis, workflow clarification, user stories, acceptance criteria, Jira, functional validation, UAT and cross-functional coordination.

    Employment: 28 Sep 2022–31 Jan 2025 · Pune District, Maharashtra, India · Remote

    View HIMS Product Experience →
  3. 2022Apr–Jul 2022

    Wipro Velocity / StackRoute

    Intern / Java Full Stack technical training

    Internship / Training

    Technical foundations in Java, application architecture, databases, REST/API concepts and the software development lifecycle.

Project-based Product Case Study

Skillverse & Catalyx

Requirements, workflow decisions, AI-assisted delivery and validation. These case studies are separate from formal employment.

View Case StudiesSkills →

HIMS Product Implementation & Product Management Support

Wipro · HIMS Product Implementation

Project Engineer supporting HIMS implementation, functional analysis and Product Management activities across healthcare workflows.

Company

Wipro LimitedFull-time

Official designation

Project Engineer28 Sep 2022–31 Jan 2025

Functional scope

HIMS Product ImplementationProduct Management & Functional Support

Domain

Healthcare · HIMS/HMISPune District, Maharashtra · Remote

Role overview

Worked as a Project Engineer supporting the implementation and functional operations of a Hospital Information Management System (HIMS/HMIS), collaborating with product, functional, technical and business stakeholders across healthcare workflows.

My contribution sat across the full HIMS product and software delivery lifecycle — from requirement clarification and workflow analysis through user stories, Jira work items, functional validation, UAT and post-implementation support.

Healthcare product context

A Hospital Information Management System (HIMS) digitises and connects core hospital operations — from patient registration and OPD consultation to IPD/ADT, billing, laboratory, radiology, pharmacy and discharge. Understanding these workflows as both operational processes and system-functional requirements was central to my work.

Healthcare workflows supported

Patient access

  • Patient Registration
  • Appointment scheduling
  • OPD encounter management

Clinical & inpatient

  • IPD / ADT (Admission, Discharge, Transfer)
  • Bed allocation
  • Discharge workflows

Diagnostics & pharmacy

  • Laboratory orders and results
  • Radiology orders and reports
  • Pharmacy and dispensing

Billing & revenue

  • OPD and IPD Billing
  • Insurance coordination workflows

Requirements & workflow analysis

Worked with business and healthcare stakeholders to understand operational requirements, identify workflow gaps and support their translation into system functionality. This involved clarifying requirements before they could move into development.

  • Worked with healthcare and business stakeholders to understand operational requirements and identify workflow gaps.
  • Analysed existing HIMS workflows to clarify expected system behaviour across modules.
  • Documented requirements, observations and clarifications to support structured delivery.
  • Distinguished between agreed requirements, open questions and assumptions.

Product lifecycle — Healthcare software delivery

  1. 01Healthcare Stakeholder Need
  2. 02Requirement Clarification
  3. 03Workflow Analysis
  4. 04User Story / Acceptance Criteria Support
  5. 05Jira Work Item
  6. 06Development & QA Clarification
  7. 07Functional Validation
  8. 08UAT / Release Validation
  9. 09Issue Tracking & Follow-up
  10. 10Go-Live / Post-Implementation Support

Requirements & analysis

Discovery & definition

  • Stakeholder requirements gathering and clarification.
  • Workflow gap identification across HIMS modules.
  • Requirement documentation and functional notes.
  • Translation of operational needs into system functionality.

Product definition

User stories & criteria

  • Supported user story and acceptance criteria preparation.
  • Maintained Jira work items and backlog records.
  • Coordinated with Development and QA for functional clarification.
  • Tracked issues through resolution across HIMS modules.

Validation

Functional validation & UAT

  • Participated in functional validation and UAT activities.
  • Verified HIMS workflows against business requirements.
  • Documented observations, defects and change requirements.
  • Supported go-live and post-implementation activities.

Issue analysis across HIMS modules

Supported users in analysing functional issues across HIMS modules and identifying whether issues were related to workflow, configuration, data, integration or application behaviour. This required understanding both the healthcare process and the underlying system logic.

Cross-functional collaboration

Worked closely with Product and Functional teams on requirements, user stories, acceptance criteria, Jira tickets, defect clarification, prioritisation inputs and feature validation. Coordinated with Development and QA teams to clarify expected system behaviour and track issues through resolution.

Practical HIMS understanding

Developed strong practical understanding of how healthcare requirements move through the product and software lifecycle — from requirement identification and analysis through workflow clarification, development, testing, UAT, implementation and post-go-live support.

Relevance to Product Management

This experience directly supports Associate Product Manager work: understanding user and stakeholder problems, translating requirements into structured work, coordinating cross-functional delivery and validating that implemented behaviour matches agreed expectations.

Scope boundaries · What I did not own

I did not independently own the product roadmap, product strategy, product vision, prioritisation authority, go-to-market, A/B testing, product analytics, KPIs or pricing. Project Engineer is my actual Wipro designation. I am targeting Associate Product Manager as my career positioning.

Case Studies

Product case studies

Project-based Product Case Studies: requirements, user flows, delivery decisions and validation checks.

01

EdTech / Project-based Product Case Study

Skillverse.in

Turning EdTech requirements into testable journeys with AI-assisted delivery and human review.

WorkflowRequirements → validation

My contribution

  • Requirements
  • User journeys
  • Functional validation
  • Issue reproduction
  • Fix verification
  1. 01Requirement
  2. 02User journey
  3. 03AI iteration
  4. 04Functional validation
  5. 05Fix verification
View case study →
02

Admissions ops / Project-based Product Case Study

Catalyx

Workflow definition, role-aware validation and product operations across admissions modules.

Role-awareAccess → expected behavior

My contribution

  • Workflow definition
  • Role-based behaviour
  • Delivery tracking
  • Permissions
  • Functional validation
Role Module Permission Branch Lead State
View case study →

Project-based Product Case Study

Skillverse.in

From EdTech requirements to testable learner journeys.

Requirement
User journey
AI-assisted iteration
Validation

My contribution

Requirements decomposition, user-flow definition, AI-assisted implementation review, functional validation and OpenProject tracking.

Evidence scope

Project contribution and approach. No user, revenue, conversion or retention outcomes are claimed.

01 / Problem & context

Skillverse is a multi-role EdTech project covering onboarding, authentication, courses, library, payments, entitlements and administration. The product challenge was to make expected behavior consistent across a journey rather than review each screen in isolation.

Users & workflow

Learner and administrator workflows connect registration, access and course availability. Role and account state influence what a person should be able to see or do.

Requirements

Clarify the role, preconditions, intended action and resulting access state. Connect onboarding, authentication and entitlement expectations before checking the interface.

02 / Analysis & key decisions

The existing work emphasized explicit user journeys before AI-assisted execution. Smaller, testable behavior descriptions made it possible to review output against requirements. The trade-off: rapid draft generation still required deliberate validation and correction.

  1. Problem
  2. Analysis
  3. Decision
  4. Execution
  5. Validation
  6. Learning

03 / Execution & work breakdown

Work was broken into expected journeys, implementation behavior, review findings and fix-verification tasks. OpenProject provided work-item status and delivery visibility.

Tools used in project work: OpenProject for work items; AI-assisted tools for implementation drafts and review. Generated output was reviewed against expected behavior.

04 / Validation & testing

Review expected versus actual behavior, record role and state, reproduce the issue, then re-test after correction. An illustrative acceptance check would ask whether a learner’s course access matches the confirmed entitlement state; it is a test-design example, not a claimed production incident.

Ambiguity encountered

An apparently complete screen does not establish correct behavior across account, payment and access states. Gaps in the requirement can become plausible but incorrect AI-generated behavior.

What changed after review

Expected-versus-actual findings informed requirement clarification and further implementation review. The work used correction and re-test cycles.

05 / What I learned

Acceptance criteria need to describe state changes and access rules clearly enough for someone else to repeat the check. AI-assisted output increases the importance of that clarity.

What I would improve next

Create a role/state test matrix earlier, add API-level checks as my technical depth develops, and keep clearer links between work items, acceptance criteria and review evidence.

For a Product hiring manager

What this demonstrates

Product thinking through requirement decomposition, user-flow reasoning, explicit expected behavior, delivery follow-up and validation. This is project-based practice, separate from enterprise Product Management support.

Project-based Product Case Study

Catalyx

Making admissions workflows understandable across roles and branches.

Role
Branch
Lead
Permission
State
Follow-up

My contribution

Requirements decomposition, role/access behavior, workflow definition, AI-assisted coordination, output validation and documentation.

Evidence scope

Project contribution and approach. No user, revenue, conversion or retention outcomes are claimed.

01 / Problem & context

Catalyx is an admissions and revenue-operations product concept covering leads, counselor work, follow-ups, branch operations and reporting. The challenge was to express who can act on which information, in which state.

Users & workflow

Counselor, branch and administrative concepts shaped lead assignment, follow-up scheduling and information visibility.

Requirements

Describe lead states, assignments, follow-up timing, branch restrictions and permissions. Reporting and conversion tracking were part of the requirements.

02 / Analysis & key decisions

The core decision framework connected module, role, permission and workflow state. Validating only whether someone could log in would miss the more important question: could the appropriate role see or change the appropriate lead?

  1. Problem
  2. Analysis
  3. Decision
  4. Execution
  5. Validation
  6. Learning

03 / Execution & work breakdown

Work items organized module workflows, user journeys, expected behavior, dependencies and status. OpenProject supported reviewable checkpoints during AI-assisted delivery.

Tools used in project work: OpenProject for work items; AI-assisted tools for implementation drafts and review. Generated output was reviewed against expected behavior.

04 / Validation & testing

Compare expected and actual lead transitions, assignment behavior and branch visibility. An illustrative check would cover an assigned lead within the permitted branch and a restricted record outside it. This describes test coverage, not a reported security incident.

Ambiguity encountered

Access depends on both role and context. Branch restrictions, lead state and counselor assignment needed to be considered together rather than treated as unrelated screen settings.

What changed after review

Expected-versus-actual findings informed requirement clarification and further implementation review. The work used correction and re-test cycles.

05 / What I learned

Business workflow understanding makes requirements more precise. A permission matrix and a lead lifecycle describe different parts of the same user experience.

What I would improve next

Document a compact role/branch matrix, make state-transition acceptance checks explicit earlier, and add dated feedback records so future iterations can show exactly what changed.

For a Product hiring manager

What this demonstrates

Operational problem framing, role-aware user flows, requirements clarity and delivery validation. It shows how I connect business context to testable behavior.

Skills

What I can contribute

Requirements, execution and acceptance — with a clear distinction between professional use, project work, foundations and learning.

Used professionallyWipro · HIMS/HMIS

Requirements analysis · Workflow analysis · Jira · User-story support · Acceptance criteria · Functional validation · UAT · Agile / Scrum · Cross-functional coordination · Healthcare workflows · Issue analysis · Post-implementation support

HIMS Product Implementation & Product Management support. View Wipro HIMS scope →

Project-based experienceSkillverse & Catalyx

Workflow mapping · Role/state reasoning · Requirements decomposition · Functional validation · OpenProject · AI-assisted delivery review

Explore the case studies →

Technical foundationsTraining / course knowledge

Java Full Stack · SDLC · Databases · REST/API concepts · AWS / cloud fundamentals

Technical foundations for engineering conversations.

Currently developingNextLeap Product Manager Fellowship

Product Discovery · User Research / JTBD · Prioritization · Product Metrics · Analytics / SQL · Excel / Google Sheets · UX · Technical Product Thinking · Product Strategy Fundamentals · AI Product Concepts

Sep 2026–Dec 2026 · Enrolled / In Progress.
Learning / In Progress — module completion or professional mastery is not implied.

Selected credentials

  • Professional Scrum Master I — Scrum.org, 2026
  • Databases and SQL for Data Science with Python — IBM/Coursera, 2025 · Foundational coursework
  • AWS Certified Cloud Practitioner — Earned 2023; expired 2026 · Historical credential

Product Notes

Three working frameworks

Short explanations of how I approach requirements and review.

Requirements → work items

Start with the stakeholder problem, the affected role and the intended result. Separate an agreed requirement from an assumption or an open question. Break the workflow into reviewable work items, each with preconditions, expected behavior and acceptance criteria.

Keep a link between the original context and the work item. When feedback changes the expectation, update the requirement and the acceptance check together. Clarification supports a decision; priority and scope still need an accountable decision-maker.

Acceptance criteria & UAT

A useful acceptance criterion describes observable behavior: given a role and starting state, when an action occurs, what should happen? Include relevant permissions, invalid inputs and state changes alongside the happy path.

For UAT, record the starting conditions, steps, expected result and actual result. Make the finding repeatable, clarify any disputed expectation and re-test the agreed correction. A successful screen is only part of a successful workflow.

AI-assisted delivery needs human review

Use a clear requirement to constrain an AI-assisted draft. Review the output against user flows, roles and states; a plausible interface does not establish correct behavior.

Separate generation from acceptance. Record gaps, make the correction explicit and repeat the check. Keep responsibility for requirements, review and acceptance visible rather than treating generated output as evidence of correctness.

Proof / Certifications

Certifications

Certifications, course foundations and learning in progress.

Formal learning supports the professional and project evidence.

Credentials show formal learning evidence; projects show practical application.

Contact

Discuss a Product opportunity

Connect about Associate Product Manager opportunities and early-career Product work.

Email
raut.bhramar@gmail.com
Email me
Phone
+91 8989412921
Call
Professional
LinkedIn GitHub
Looking for

Associate Product Manager · Early-career Product roles

Review the full profile

Recruiter view →

Page Not Found

This route doesn't exist.

Go Home