Analytics Senior Consultant
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience", etc. Do not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes pay range: "For U.S. based positions only, the pay range for this position is $101,600.00-$152,400.00 Annual." Also mentions performance based incentive compensation. Benefits: "GE HealthCare offers a competitive benefits package, including not but limited to medical, dental, vision, paid time off, a 401(k) plan with employee and company contribution opportunities, life, disability, and accident insurance, and tuition reimbursement." Also mentions relocation assistance: "Relocation Assistance Provided: No". Also mentions travel ability up to 70%. Also mentions "Why Join GE HealthCare" which is more like a description but could be part of Benefits? Might be considered a section but not required headings. We can include a "Why Join GE HealthCare" as maybe a
but not in list of allowed headings? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests we can use those. Probably better to stick to those headings where content exists.
We have:
- About the Role: there is a section "About the Role" with content: "As part of the CareIntellect and Command Center Delivery team, you will help hospital systems implement advisory and technology solutions that improve healthcare operations. Command Center software, including its “Tiles,” is designed to dynamically optimize the coordination of patient care."
- Responsibilities: The "What You Will Do" section enumerates many duties. That's responsibilities.
- Requirements: There's "Required Qualifications" with subparts: Education and Experience, Analytics And Technical Capabilities, Client And Delivery Capabilities, Travel Ability.
- Preferred Qualifications: separate.
- Skills: Could be derived from Preferred Qualifications? Might be considered Skills. But we could treat "Preferred Qualifications" as Skills section? The instruction says use headings like Skills. We could create a Skills heading for preferred qualifications (like experience with certain tools). However we need to ensure we don't create thin sections. The preferred qualifications list is substantive.
- Benefits: we have benefits description.
- Pay: we have pay range.
- Schedule: Not explicitly given; there is travel ability but not schedule. So we should not create Schedule section unless posting states it. It does not mention schedule like full-time, part-time, shift. So omit.
We also need to remove boilerplate: EEO, visa sponsorship, drug screen, vaccination, relocation assistance? Relocation assistance is substantive: "Relocation Assistance Provided: No". That's a detail we should keep. Could be placed under Benefits or a separate note. Probably include in Benefits as a bullet.
Also "Application Deadline: October 02, 2026" is application instruction; we should remove per instruction: remove application instructions. So drop that.
Also "Why Join GE HealthCare" is not boilerplate; it's a motivational paragraph. Could be included as a section maybe "About the Company" but not in allowed headings. Could be omitted or included as a
under maybe a generic section? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that paragraph. Where to put? Could be under a heading like "Why Join GE HealthCare" but that's not in the list. However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests we can use those examples. It might be okay to add a heading like "Why Join GE HealthCare". But to be safe, we could incorporate that paragraph into a
under maybe "About the Role" or as a separate
named "Why Join GE HealthCare". I'd argue it's substantive and we should keep it; using a heading is fine.
We also need to remove duplicated lines. Look for duplicates: The job description summary at top repeats some content; we should not duplicate. We'll just use the substantive sections.
Now craft HTML.
Structure:
About the Role
As part of the CareIntellect and Command Center Delivery team, you will help hospital systems implement advisory and technology solutions that improve healthcare operations. Command Center software, including its “Tiles,” is designed to dynamically optimize the coordination of patient care.
Responsibilities
- Lead customer problem solving and outcome definition by independently structuring complex problems, analyzing root causes, and guiding stakeholders from ambiguity to aligned decisions.
- Translate customer goals into key performance indicators (KPIs), analytical questions, success measures, and adoption plans; track progress and demonstrate measurable outcomes.
- Lead solution design and configuration through structured design, workflow, and configuration sessions with clear objectives, disciplined facilitation, and documented decisions. Understand Tile users and barriers to adoption, and recommend workflow, configuration, coaching, or product enhancements that improve usage and outcomes.
- Deliver advanced analytics and data-driven insights by gathering, validating, joining, analyzing, and synthesizing data from multiple sources. Create analyses and visualizations that translate complex findings into concise, decision-oriented stories for technical and non-technical audiences.
- Translate business and workflow needs into product requirements by developing analytical use cases, functional requirements, user stories, acceptance criteria, data specifications, and feature recommendations. Apply an end-to-end understanding of the data journey—from source feeds through transformation logic and stored procedures to user-facing Tile features—to support effective product configuration and delivery.
- Manage product stories, defects, testing, and technical issue resolution by validating data outputs, isolating issues, documenting findings, and coordinating resolution with Product and Engineering. Use relevant delivery and technical tools to import, inspect, and validate data across multiple data sources and environments, and clearly explain logic-based criteria, data requirements, tradeoffs, and solution limitations to client IT, integration, operational, and clinical stakeholders.
- Own a customer-facing workstream or Tile configuration through production, including project planning, milestones, dependencies, testing, activation, risk mitigation, and delivery quality. Build trusted relationships with manager- and director-level client stakeholders, serve as the primary point of contact for the assigned workstream, and prepare concise, client-ready analyses, specifications, status updates, recommendations, and executive-level presentation materials.
- Drive adoption and continuous product improvement by partnering with program teams to validate analytics, coach users on interpretation and application, and support sustained product adoption. Surface client needs, delivery risks, product opportunities, and potential enhancements, routing or escalating decisions through the appropriate governance channels.
- Support Digital Twin delivery by running scenarios on validated models and contributing to model validation with guidance from senior technical experts, as needed.
- Strengthen team capability and delivery consistency by coaching and mentoring junior team members across analytics, product, technical, consulting, and client-delivery practices; providing timely feedback and recognition; and creating meaningful work while maintaining accountability for workstream quality, timelines, and outcomes. Share reusable analyses, specifications, best practices, and lessons learned across programs, and contribute to a collaborative, inclusive, ownership-oriented culture grounded in humility, transparency, focus, trust, and integrity.
Requirements
Education and Experience: Bachelor’s degree in Engineering, Mathematics, Statistics, Data Science, Health Sciences, Computer Science, Health Informatics, or a related discipline. Minimum of 4 years of experience in healthcare analytics, technical consulting, product delivery, healthcare software implementation, or a related client-facing field, with demonstrated ownership of defined workstreams or solution components.
Analytics And Technical Capabilities: Demonstrated ability to independently analyze complex data, perform root-cause analysis, and translate findings into actionable business or operational recommendations. Hands-on SQL experience, including joining multiple datasets, validating data, and investigating data-quality or product issues. Experience translating business needs into functional requirements, analytical use cases, data specifications, user stories, or acceptance criteria. Experience supporting the lifecycle of an analytics or software product, including requirements, design, testing, defect management, release, activation, and user feedback.
Client And Delivery Capabilities: Ability to communicate technical concepts clearly to non-technical audiences and operational needs clearly to technical teams. Demonstrated client-facing facilitation, stakeholder management, and presentation skills, including experience leading working sessions and influencing decisions without direct authority. Strong project-management discipline, including planning, dependency tracking, scope management, risk mitigation, and consistent delivery of high-quality work.
Travel Ability: Ability to travel regularly, up to 70%, to client sites as needed.
Preferred Qualifications
- Master’s degree in a quantitative, technical, healthcare, or business discipline.
- Experience in acute-care hospital operations, patient flow, access, capacity management, clinical workflows, or healthcare informatics.
- Experience with healthcare data standards and interfaces such as Health Level Seven (HL7), Fast Healthcare Interoperability Resources (FHIR), application programming interfaces (APIs), or electronic health record/electronic medical record (EHR/EMR) source systems.
- Experience with analytics and visualization tools such as Python, R, Tableau, Power BI, Qlik, or comparable platforms.
- Experience with Agile product-delivery tools and practices, including story and defect management, with familiarity with Rally or comparable tools.
- Working knowledge of tools used in data and integration delivery, such as Postman, HL7 viewers, database clients, secure remote-access tools, or comparable utilities.
- Formal training or applied experience in structured problem solving, process improvement, change management, Lean, or Six Sigma.
- Ability to work effectively in ambiguous, cross-functional environments, demonstrating curiosity, sound judgment, adaptability, and a strong sense of ownership.
Benefits
- Medical, dental, vision coverage
- Paid time off
- 401(k) plan with employee and company contribution opportunities
- Life, disability, and accident insurance
- Tuition reimbursement
- Relocation assistance: Not provided
Pay
For U.S. based positions only, the pay range for this position is $101,600.00‑$152,400.00 Annual. Compensation decisions are dependent on facts and circumstances; performance‑based incentive compensation (cash bonus and/or long‑term incentives) may be available.
Why Join GE HealthCare
This role offers the opportunity to independently own meaningful customer workstreams that combine analytics, healthcare operations, technology, and consulting. Through CareIntellect and Command Center delivery, you will help healthcare organizations turn complex operational and clinical data into solutions that improve coordination, adoption, and measurable outcomes.
We need to ensure we didn't include any boilerplate like EEO, visa sponsorship, drug screen, vaccination, etc. We removed those.
Check for any duplicated lines: we didn't repeat.
Check for any placeholder text like "commensurate with experience
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience", etc. Do not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes pay range: "For U.S. based positions only, the pay range for this position is $101,600.00-$152,400.00 Annual." Also mentions performance based incentive compensation. Benefits: "GE HealthCare offers a competitive benefits package, including not but limited to medical, dental, vision, paid time off, a 401(k) plan with employee and company contribution opportunities, life, disability, and accident insurance, and tuition reimbursement." Also mentions relocation assistance: "Relocation Assistance Provided: No". Also mentions travel ability up to 70%. Also mentions "Why Join GE HealthCare" which is more like a description but could be part of Benefits? Might be considered a section but not required headings. We can include a "Why Join GE HealthCare" as maybe a
but not in list of allowed headings? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests we can use those. Probably better to stick to those headings where content exists.
We have:
- About the Role: there is a section "About the Role" with content: "As part of the CareIntellect and Command Center Delivery team, you will help hospital systems implement advisory and technology solutions that improve healthcare operations. Command Center software, including its “Tiles,” is designed to dynamically optimize the coordination of patient care."
- Responsibilities: The "What You Will Do" section enumerates many duties. That's responsibilities.
- Requirements: There's "Required Qualifications" with subparts: Education and Experience, Analytics And Technical Capabilities, Client And Delivery Capabilities, Travel Ability.
- Preferred Qualifications: separate.
- Skills: Could be derived from Preferred Qualifications? Might be considered Skills. But we could treat "Preferred Qualifications" as Skills section? The instruction says use headings like Skills. We could create a Skills heading for preferred qualifications (like experience with certain tools). However we need to ensure we don't create thin sections. The preferred qualifications list is substantive.
- Benefits: we have benefits description.
- Pay: we have pay range.
- Schedule: Not explicitly given; there is travel ability but not schedule. So we should not create Schedule section unless posting states it. It does not mention schedule like full-time, part-time, shift. So omit.
We also need to remove boilerplate: EEO, visa sponsorship, drug screen, vaccination, relocation assistance? Relocation assistance is substantive: "Relocation Assistance Provided: No". That's a detail we should keep. Could be placed under Benefits or a separate note. Probably include in Benefits as a bullet.
Also "Application Deadline: October 02, 2026" is application instruction; we should remove per instruction: remove application instructions. So drop that.
Also "Why Join GE HealthCare" is not boilerplate; it's a motivational paragraph. Could be included as a section maybe "About the Company" but not in allowed headings. Could be omitted or included as a
under maybe a generic section? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that paragraph. Where to put? Could be under a heading like "Why Join GE HealthCare" but that's not in the list. However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests we can use those examples. It might be okay to add a heading like "Why Join GE HealthCare". But to be safe, we could incorporate that paragraph into a
under maybe "About the Role" or as a separate
named "Why Join GE HealthCare". I'd argue it's substantive and we should keep it; using a heading is fine.
We also need to remove duplicated lines. Look for duplicates: The job description summary at top repeats some content; we should not duplicate. We'll just use the substantive sections.
Now craft HTML.
Structure:
About the Role
As part of the CareIntellect and Command Center Delivery team, you will help hospital systems implement advisory and technology solutions that improve healthcare operations. Command Center software, including its “Tiles,” is designed to dynamically optimize the coordination of patient care.
Responsibilities
- Lead customer problem solving and outcome definition by independently structuring complex problems, analyzing root causes, and guiding stakeholders from ambiguity to aligned decisions.
- Translate customer goals into key performance indicators (KPIs), analytical questions, success measures, and adoption plans; track progress and demonstrate measurable outcomes.
- Lead solution design and configuration through structured design, workflow, and configuration sessions with clear objectives, disciplined facilitation, and documented decisions. Understand Tile users and barriers to adoption, and recommend workflow, configuration, coaching, or product enhancements that improve usage and outcomes.
- Deliver advanced analytics and data-driven insights by gathering, validating, joining, analyzing, and synthesizing data from multiple sources. Create analyses and visualizations that translate complex findings into concise, decision-oriented stories for technical and non-technical audiences.
- Translate business and workflow needs into product requirements by developing analytical use cases, functional requirements, user stories, acceptance criteria, data specifications, and feature recommendations. Apply an end-to-end understanding of the data journey—from source feeds through transformation logic and stored procedures to user-facing Tile features—to support effective product configuration and delivery.
- Manage product stories, defects, testing, and technical issue resolution by validating data outputs, isolating issues, documenting findings, and coordinating resolution with Product and Engineering. Use relevant delivery and technical tools to import, inspect, and validate data across multiple data sources and environments, and clearly explain logic-based criteria, data requirements, tradeoffs, and solution limitations to client IT, integration, operational, and clinical stakeholders.
- Own a customer-facing workstream or Tile configuration through production, including project planning, milestones, dependencies, testing, activation, risk mitigation, and delivery quality. Build trusted relationships with manager- and director-level client stakeholders, serve as the primary point of contact for the assigned workstream, and prepare concise, client-ready analyses, specifications, status updates, recommendations, and executive-level presentation materials.
- Drive adoption and continuous product improvement by partnering with program teams to validate analytics, coach users on interpretation and application, and support sustained product adoption. Surface client needs, delivery risks, product opportunities, and potential enhancements, routing or escalating decisions through the appropriate governance channels.
- Support Digital Twin delivery by running scenarios on validated models and contributing to model validation with guidance from senior technical experts, as needed.
- Strengthen team capability and delivery consistency by coaching and mentoring junior team members across analytics, product, technical, consulting, and client-delivery practices; providing timely feedback and recognition; and creating meaningful work while maintaining accountability for workstream quality, timelines, and outcomes. Share reusable analyses, specifications, best practices, and lessons learned across programs, and contribute to a collaborative, inclusive, ownership-oriented culture grounded in humility, transparency, focus, trust, and integrity.
Requirements
Education and Experience: Bachelor’s degree in Engineering, Mathematics, Statistics, Data Science, Health Sciences, Computer Science, Health Informatics, or a related discipline. Minimum of 4 years of experience in healthcare analytics, technical consulting, product delivery, healthcare software implementation, or a related client-facing field, with demonstrated ownership of defined workstreams or solution components.
Analytics And Technical Capabilities: Demonstrated ability to independently analyze complex data, perform root-cause analysis, and translate findings into actionable business or operational recommendations. Hands-on SQL experience, including joining multiple datasets, validating data, and investigating data-quality or product issues. Experience translating business needs into functional requirements, analytical use cases, data specifications, user stories, or acceptance criteria. Experience supporting the lifecycle of an analytics or software product, including requirements, design, testing, defect management, release, activation, and user feedback.
Client And Delivery Capabilities: Ability to communicate technical concepts clearly to non-technical audiences and operational needs clearly to technical teams. Demonstrated client-facing facilitation, stakeholder management, and presentation skills, including experience leading working sessions and influencing decisions without direct authority. Strong project-management discipline, including planning, dependency tracking, scope management, risk mitigation, and consistent delivery of high-quality work.
Travel Ability: Ability to travel regularly, up to 70%, to client sites as needed.
Preferred Qualifications
- Master’s degree in a quantitative, technical, healthcare, or business discipline.
- Experience in acute-care hospital operations, patient flow, access, capacity management, clinical workflows, or healthcare informatics.
- Experience with healthcare data standards and interfaces such as Health Level Seven (HL7), Fast Healthcare Interoperability Resources (FHIR), application programming interfaces (APIs), or electronic health record/electronic medical record (EHR/EMR) source systems.
- Experience with analytics and visualization tools such as Python, R, Tableau, Power BI, Qlik, or comparable platforms.
- Experience with Agile product-delivery tools and practices, including story and defect management, with familiarity with Rally or comparable tools.
- Working knowledge of tools used in data and integration delivery, such as Postman, HL7 viewers, database clients, secure remote-access tools, or comparable utilities.
- Formal training or applied experience in structured problem solving, process improvement, change management, Lean, or Six Sigma.
- Ability to work effectively in ambiguous, cross-functional environments, demonstrating curiosity, sound judgment, adaptability, and a strong sense of ownership.
Benefits
- Medical, dental, vision coverage
- Paid time off
- 401(k) plan with employee and company contribution opportunities
- Life, disability, and accident insurance
- Tuition reimbursement
- Relocation assistance: Not provided
Pay
For U.S. based positions only, the pay range for this position is $101,600.00‑$152,400.00 Annual. Compensation decisions are dependent on facts and circumstances; performance‑based incentive compensation (cash bonus and/or long‑term incentives) may be available.
Why Join GE HealthCare
This role offers the opportunity to independently own meaningful customer workstreams that combine analytics, healthcare operations, technology, and consulting. Through CareIntellect and Command Center delivery, you will help healthcare organizations turn complex operational and clinical data into solutions that improve coordination, adoption, and measurable outcomes.
We need to ensure we didn't include any boilerplate like EEO, visa sponsorship, drug screen, vaccination, etc. We removed those. Check for any duplicated lines: we didn't repeat. Check for any placeholder text like "commensurate with experience