Product Analyst
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info.
Let's parse the job posting.
Content:
- Title: Healthcare Cerner Product Analyst Opportunity!! (but we should not repeat job title as heading)
- Hosted by: Robert Reyes (metadata)
- Salary: $54 - $64 per hour (Pay)
- About us: Prestige Hospital System Placed #1 in both California in a broad assessment of excellence in hospital-based patient care. Why join us? Competitive Salary$$ Stellar Benefits (Medical, Dental Vision, Life Insurance) Flexible Schedule Job Stability Career growth The position offers a competitive salary If you are passionate, thrive in a fast-paced environment and are ready to take your career to the next level, we would love to hear from you.
- Job Details: As a Consulting Product Analyst in the Tech Services industry, you will play a crucial role in the design, implementation, and ongoing management of digital & data products and services. You will work closely with various enterprise stakeholders to articulate business requirements, build user stories, and identify value propositions. Your role will include conducting market research to understand industry problems and find innovative solutions, as well as evangelizing digital & data product offerings to business stakeholders to continually develop and expand the product roadmap.
- Responsibilities: list bullet points:
- Customer Service: Resolve customer questions and complaints, handle service problems and tickets, and maintain a pleasant and professional image.
- Solution Design and Development: Analyze events, documentation, requirements, and needs to design and develop solutions.
- Performance Improvement/Transformation/Innovation: Actively participate in performance improvement activities, identify and proactively pursue business transformation, use innovation to enhance/solve current system and business workflow problems.
- Technical Skills and Industry Knowledge: Familiarize yourself with multiple application systems/business functions with working knowledge of selected systems/functions.
- Teamwork and Project Management: Lead work efforts, use planning skills to manage and complete work efforts on time and on budget.
- Reports & Analytics: Generate both standard and ad hoc reports, design and assist in developing nonstandard/custom reports as required.
- Training: Work with customers and/or vendors on training on new systems being implemented and rolled out for use in the departments.
- Qualifications:
- Bachelor’s Degree in a related field required.
- Minimum 2 years of experience in product/business analysis.
- Experience in a Cerner (Oracle Health) environment required.
- Development abilities in visualization tools (Tableau and Power BI) required.
- Experience working with users to capture requirements and develop workflow diagrams that translate to application builds.
- Experience analyzing and recommending appropriate technical solutions to support the overall enterprise.
- Experience with Agile Project Management methodologies.
- Experience managing multiple priorities and operating in a fast-paced, ambiguous, and complex environment with autonomy.
- Proficient in Microsoft Word, Excel, PowerPoint, Project, and Visio.
- Healthcare IS experience preferred.
- 5+ years of experience in a related field.
Note: There's some duplication: Minimum 2 years and 5+ years? Might be contradictory but we preserve both.
- Benefits: Stellar Benefits (Medical, Dental Vision, Life Insurance) Flexible Schedule Job Stability Career growth. Also Competitive Salary$$ (but salary already covered). So Benefits: Medical, Dental, Vision, Life Insurance; Flexible Schedule; Job Stability; Career growth.
- Pay: $54 - $64 per hour.
- Schedule: Not explicitly given besides Flexible Schedule mentioned under benefits. Could treat as Schedule section if we have explicit schedule info. The posting says "Flexible Schedule" under benefits. Could treat as Schedule section with "Flexible Schedule". However we need to avoid placeholder text like "not specified". Since we have "Flexible Schedule" we can include Schedule section.
- About the role: Could be the initial description: "As a Consulting Product Analyst..." That's job details. Could be "About the role" section.
We need to decide sections: About the role (job summary), Responsibilities, Qualifications (maybe combine Requirements and Qualifications?), Skills (maybe technical skills), Benefits, Pay, Schedule.
We must not repeat job title as heading. Use for each section heading.
We must use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information; do not invent or summarize away detail.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We must not include sections with filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". So we should not include Pay if it's just "$54 - $64 per hour" - that's specific, okay. Schedule: "Flexible Schedule" is specific enough.
Benefits: list items: Medical, Dental, Vision, Life Insurance; Flexible Schedule; Job Stability; Career growth. However Flexible Schedule also appears as schedule; we might duplicate but okay.
We need to avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in original. But we might want to avoid repeating same content in two sections? Not required to deduplicate. However we should not create sections that are just filler. If we put Flexible Schedule both under Benefits and Schedule, it's okay.
But we might decide to put Flexible Schedule only under Schedule, and Benefits list medical etc. However the original says "Stellar Benefits (Medical, Dental Vision, Life Insurance) Flexible Schedule Job Stability Career growth". So Flexible Schedule is part of benefits list. We could keep it there and also have Schedule section maybe redundant. Better to follow instruction: include a section ONLY when the posting has real, specific content for it. The posting does mention Flexible Schedule as part of benefits, but not a separate schedule detail like "Monday-Friday 9-5". So we could treat Schedule as not present; we could omit Schedule section. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Flexible Schedule, which is a schedule attribute. So we could create Schedule section with "Flexible Schedule". But then we would be duplicating content. Might be okay but could be considered redundant. However we can decide to include Schedule section with "Flexible Schedule" and keep Benefits without Flexible Schedule (maybe just medical etc). But then we would be dropping some substantive info (Flexible Schedule) from Benefits. To preserve all substantive info, we need to keep Flexible Schedule somewhere. If we put it only under Schedule, we still preserve it. Benefits would then lack Flexible Schedule but we could still list medical etc. That's okay because we preserved the info elsewhere. However the original grouping had Flexible Schedule under benefits; moving it to Schedule is still preserving. It's not inventing or summarizing away detail. It's just re categorizing. That seems acceptable.
Thus we will have sections:
- About the role (summary)
- Responsibilities
- Qualifications (maybe combine Requirements and Qualifications)
- Skills (maybe technical skills like Tableau, Power BI, MS Office, etc.)
- Benefits
- Pay
- Schedule
We need to ensure we don't create sections with only placeholder text. All have content.
Now extract content for each.
About the role: Could be the paragraph after "Job Details:"? Actually there is "Job Details Job Details: As a Consulting Product Analyst..." That's the role description. Also there is earlier "A bit about us: Prestige Hospital System..." That's about the company, not role. Could treat as About the company but not required. The instruction says use headings like About the role, Responsibilities, etc. So we can put About the role as the description of the role: "As a Consulting Product Analyst in the Tech Services industry, you will play a crucial role in the design, implementation, and ongoing management of digital & data products and services. You will work closely with various enterprise stakeholders to articulate business requirements, build user stories, and identify value propositions. Your role will include conducting market research to understand industry problems and find innovative solutions, as well as evangelizing digital & data product offerings to business stakeholders to continually develop and expand the product roadmap."
That seems appropriate.
Responsibilities: list as given.
Qualifications: list all qualification items.
Skills: Could extract technical skills: Development abilities in visualization tools (Tableau and Power BI); Proficient in Microsoft Word, Excel, PowerPoint, Project, and Visio; maybe also Agile Project Management methodologies (though that's more methodology). Could also include experience with Cerner, etc. But those are qualifications. To avoid duplication, we could keep Qualifications as all requirements, and Skills maybe just the technical tools. However the instruction says use sections only when posting has real specific content for it. It does have technical skills list. So we can create Skills section with those.
But we must preserve all substantive info; if we move some qualifications to Skills, we need to ensure we didn't lose any. We'll keep Qualifications as the list of requirements (education, experience, etc.) and Skills as the specific tools/proficiencies.
Let's list Qualifications items:
- Bachelor’s Degree in a related field required.
- Minimum 2 years of experience in product/business analysis.
- Experience in a Cerner (Oracle Health) environment required.
- Experience working with users to capture requirements and develop workflow diagrams that translate to application builds.
- Experience analyzing and recommending appropriate technical solutions to support the overall enterprise.
- Experience with Agile Project Management methodologies.
- Experience managing multiple priorities and operating in a fast-paced, ambiguous, and complex environment with autonomy.
- Proficient in Microsoft Word, Excel, PowerPoint, Project, and Visio. (This could also be skill)
- Healthcare IS experience preferred.
- 5+ years of experience in a related field.
Note: There's also "Development abilities in visualization tools (Tableau and Power BI) required." That's a skill.
Thus Qualifications could exclude the technical tools and visualization tools, leaving them for Skills.
But we need to be careful not to lose the "Development abilities in visualization tools (Tableau and Power BI) required." We'll put that in Skills.
Also "Proficient in Microsoft Word, Excel, PowerPoint, Project, and Visio." could be Skills.
Thus Skills section: Development abilities in visualization tools (Tableau and Power BI); Proficient in Microsoft Word, Excel, PowerPoint, Project, and Visio.
Benefits: Stellar Benefits (Medical, Dental Vision, Life Insurance) Flexible Schedule Job Stability Career growth. We'll list: Medical, Dental, Vision, Life Insurance; Job Stability; Career growth. (Flexible Schedule moved to Schedule).
Pay: $54 - $64 per hour.
Schedule: Flexible Schedule.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce something like:
About the role
As a Consulting Product Analyst in the Tech Services industry, you will play a crucial role in the design, implementation, and ongoing management of digital & data products and services. You will work closely with various enterprise stakeholders to articulate business requirements, build user stories, and identify value propositions. Your role will include conducting market research to understand industry problems and find innovative solutions, as well as evangelizing digital & data product offerings to business stakeholders to continually develop and expand the product roadmap.
Responsibilities
- Customer Service: Resolve customer questions and complaints, handle service problems and tickets, and maintain a pleasant and professional image.
- Solution Design and Development: Analyze events, documentation, requirements, and needs to design and develop solutions.
- Performance Improvement/Transformation/Innovation: Actively participate in performance improvement activities, identify and proactively pursue business transformation, use innovation to enhance/s
- for any list of duties/requirements/benefits, and
for prose. We must preserve all substantive information; do not invent or summarize away detail. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We must not include sections with filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". So we should not include Pay if it's just "$54 - $64 per hour" - that's specific, okay. Schedule: "Flexible Schedule" is specific enough. Benefits: list items: Medical, Dental, Vision, Life Insurance; Flexible Schedule; Job Stability; Career growth. However Flexible Schedule also appears as schedule; we might duplicate but okay. We need to avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in original. But we might want to avoid repeating same content in two sections? Not required to deduplicate. However we should not create sections that are just filler. If we put Flexible Schedule both under Benefits and Schedule, it's okay. But we might decide to put Flexible Schedule only under Schedule, and Benefits list medical etc. However the original says "Stellar Benefits (Medical, Dental Vision, Life Insurance) Flexible Schedule Job Stability Career growth". So Flexible Schedule is part of benefits list. We could keep it there and also have Schedule section maybe redundant. Better to follow instruction: include a section ONLY when the posting has real, specific content for it. The posting does mention Flexible Schedule as part of benefits, but not a separate schedule detail like "Monday-Friday 9-5". So we could treat Schedule as not present; we could omit Schedule section. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Flexible Schedule, which is a schedule attribute. So we could create Schedule section with "Flexible Schedule". But then we would be duplicating content. Might be okay but could be considered redundant. However we can decide to include Schedule section with "Flexible Schedule" and keep Benefits without Flexible Schedule (maybe just medical etc). But then we would be dropping some substantive info (Flexible Schedule) from Benefits. To preserve all substantive info, we need to keep Flexible Schedule somewhere. If we put it only under Schedule, we still preserve it. Benefits would then lack Flexible Schedule but we could still list medical etc. That's okay because we preserved the info elsewhere. However the original grouping had Flexible Schedule under benefits; moving it to Schedule is still preserving. It's not inventing or summarizing away detail. It's just re categorizing. That seems acceptable. Thus we will have sections: - About the role (summary) - Responsibilities - Qualifications (maybe combine Requirements and Qualifications) - Skills (maybe technical skills like Tableau, Power BI, MS Office, etc.) - Benefits - Pay - Schedule We need to ensure we don't create sections with only placeholder text. All have content. Now extract content for each. About the role: Could be the paragraph after "Job Details:"? Actually there is "Job Details Job Details: As a Consulting Product Analyst..." That's the role description. Also there is earlier "A bit about us: Prestige Hospital System..." That's about the company, not role. Could treat as About the company but not required. The instruction says use headings like About the role, Responsibilities, etc. So we can put About the role as the description of the role: "As a Consulting Product Analyst in the Tech Services industry, you will play a crucial role in the design, implementation, and ongoing management of digital & data products and services. You will work closely with various enterprise stakeholders to articulate business requirements, build user stories, and identify value propositions. Your role will include conducting market research to understand industry problems and find innovative solutions, as well as evangelizing digital & data product offerings to business stakeholders to continually develop and expand the product roadmap." That seems appropriate. Responsibilities: list as given. Qualifications: list all qualification items. Skills: Could extract technical skills: Development abilities in visualization tools (Tableau and Power BI); Proficient in Microsoft Word, Excel, PowerPoint, Project, and Visio; maybe also Agile Project Management methodologies (though that's more methodology). Could also include experience with Cerner, etc. But those are qualifications. To avoid duplication, we could keep Qualifications as all requirements, and Skills maybe just the technical tools. However the instruction says use sections only when posting has real specific content for it. It does have technical skills list. So we can create Skills section with those. But we must preserve all substantive info; if we move some qualifications to Skills, we need to ensure we didn't lose any. We'll keep Qualifications as the list of requirements (education, experience, etc.) and Skills as the specific tools/proficiencies. Let's list Qualifications items: - Bachelor’s Degree in a related field required. - Minimum 2 years of experience in product/business analysis. - Experience in a Cerner (Oracle Health) environment required. - Experience working with users to capture requirements and develop workflow diagrams that translate to application builds. - Experience analyzing and recommending appropriate technical solutions to support the overall enterprise. - Experience with Agile Project Management methodologies. - Experience managing multiple priorities and operating in a fast-paced, ambiguous, and complex environment with autonomy. - Proficient in Microsoft Word, Excel, PowerPoint, Project, and Visio. (This could also be skill) - Healthcare IS experience preferred. - 5+ years of experience in a related field. Note: There's also "Development abilities in visualization tools (Tableau and Power BI) required." That's a skill. Thus Qualifications could exclude the technical tools and visualization tools, leaving them for Skills. But we need to be careful not to lose the "Development abilities in visualization tools (Tableau and Power BI) required." We'll put that in Skills. Also "Proficient in Microsoft Word, Excel, PowerPoint, Project, and Visio." could be Skills. Thus Skills section: Development abilities in visualization tools (Tableau and Power BI); Proficient in Microsoft Word, Excel, PowerPoint, Project, and Visio. Benefits: Stellar Benefits (Medical, Dental Vision, Life Insurance) Flexible Schedule Job Stability Career growth. We'll list: Medical, Dental, Vision, Life Insurance; Job Stability; Career growth. (Flexible Schedule moved to Schedule). Pay: $54 - $64 per hour. Schedule: Flexible Schedule. Now we need to output HTML fragment only, no /, no markdown. We'll produce something like:
About the role
As a Consulting Product Analyst in the Tech Services industry, you will play a crucial role in the design, implementation, and ongoing management of digital & data products and services. You will work closely with various enterprise stakeholders to articulate business requirements, build user stories, and identify value propositions. Your role will include conducting market research to understand industry problems and find innovative solutions, as well as evangelizing digital & data product offerings to business stakeholders to continually develop and expand the product roadmap.
Responsibilities
- Customer Service: Resolve customer questions and complaints, handle service problems and tickets, and maintain a pleasant and professional image.
- Solution Design and Development: Analyze events, documentation, requirements, and needs to design and develop solutions.
- Performance Improvement/Transformation/Innovation: Actively participate in performance improvement activities, identify and proactively pursue business transformation, use innovation to enhance/s