Senior Industry Practice Director Healthcare Provider

We need to output HTML fragment with sections: About the role? Actually the posting includes "Life at UiPath" intro, "Your mission", "What you'll do at UiPath", "What you'll bring to the team", "Ideal backgrounds", "What Distinguishes You", "This Role Is Not", "Success looks like", "Maybe you don’t tick all the boxes..." etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. The posting does not have explicit Benefits, Pay, Schedule. So we should not create those sections. We need to map content to appropriate headings: "About the role" could be the introductory paragraph about UiPath and mission. "Responsibilities" could be "What you'll do at UiPath". "Requirements" could be "What you'll bring to the team" plus maybe "Ideal backgrounds". "Qualifications" maybe combine? But we need to avoid thin sections. Probably we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills? However the instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require using all; only when posting has real specific content. So we need to decide which sections we have content for. We have: - Intro: "Life at UiPath ..." plus "Your mission". That's about the role and company. Could be "About the role". - Responsibilities: "What you'll do at UiPath" (list of duties). Good. - Requirements: "What you'll bring to the team" (experience, etc.) plus "Ideal backgrounds". Could be Requirements. - Qualifications: maybe "What Distinguishes You" (traits). Could be Qualifications or Skills. - Skills: maybe "What Distinguishes You" also could be Skills. But we need to avoid duplication. Better: Use About the role, Responsibilities, Requirements, Qualifications. Possibly Skills not needed separately. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, privacy policy, etc. Also remove "Many of our roles allow for flexibility..." etc? That's about work arrangement; could be considered Benefits? But it's not explicit benefits; it's about flexibility. Might be considered a benefit but not explicit. The instruction: never create Benefits/Schedule/Pay sections unless posting actually states them. The posting mentions flexibility: "Many of our roles allow for flexibility in when and where work gets done." That's about schedule/remote/hybrid. Could be considered Schedule? But it's not explicit schedule details. Safer to omit Benefits/Schedule/Pay sections. We also need to remove duplicated lines, cookie/navigation/legal/EEO etc. So remove the paragraph about diversity, EEO, privacy policy, accommodations, etc. Also remove "Maybe you don’t tick all the boxes above—but still think you’d be great for the job? Go ahead, apply anyway. Please." That's application instruction? It's encouraging to apply; maybe considered application instruction; we should remove application instructions. The instruction says remove application instructions. So remove that encouraging apply line. Also remove "Applications are assessed on a rolling basis..." etc. That's also application instruction. Remove. Also remove "To review these and other legal disclosures, visit our privacy policy." Remove. Now we need to preserve all substantive information. Let's extract substantive content: Intro paragraph: "Life at UiPath The people at UiPath believe in the transformative power of automation to change how the world works. We’re committed to creating category-leading enterprise software that unleashes that power. To make that happen, we need people who are curious, self-propelled, generous, and genuine. People who love being part of a fast-moving, fast-thinking growth company. And people who care—about each other, about UiPath, and about our larger purpose. Could that be you?" Then "Your mission" paragraph: "UiPath is scaling its Healthcare & Life Sciences business across Healthcare Provider organizations — health systems, hospitals, and ambulatory networks — and we are hiring a senior industry leader to help define where the provider market is today, where it is going next, and how UiPath wins repeatedly at scale. This is a hands-on, action-oriented industry role for someone who has lived inside hospitals, health systems, or provider operations and wants to apply that experience to shape executive conversations, inform product direction, and build repeatable, high-impact sales motions. This role does not carry a sales quota and is not a product management role. Success is measured by clarity, repeatability, and impact on growth." Then "What you'll do at UiPath" with bullet points (actually paragraphs with colon). We need to convert to

• . The content includes multiple bullet-like sentences each starting with a bold phrase? Let's parse: "Build a clear point of view on the Healthcare Provider market Systematically document:What health systems, hospitals, and ambulatory networks are doing todayCommon patterns and use cases across provider organizations — from revenue cycle and patient access to clinical operations, care management, and workforceDevelop a clear, defensible POV on what provider organizations should be doing next to drive repeatable outcomes under margin pressure, workforce shortages, and value-based care demandsTranslate your market POV into clear, repeatable sales plays aligned to specific buyer personas (CFO, CIO, Chief Nursing Officer, VP Revenue Cycle, VP Clinical Operations) and business outcomesEquip sales teams with structured narratives that resonate with health system executives Analyze opportunity size and prioritization Partner with Sales, Strategy, and Product to:Estimate TAM for priority provider use cases and plays (e.g., revenue cycle management, prior authorization, denials management, patient access/scheduling, clinical documentation, care coordination, discharge planning, EHR interoperability)Help prioritize functions, workflows, and care settings based on impact, scale, and repeatability to the portfolioProvide structured, evidence-based input into product strategy:What are the highest-impact areas that will drive business value for health systems and hospitals Drive executive-level customer engagement Engage senior leaders across health systems and provider organizations as a peer advisorContribute to outcome-focused conversations across our provider portfolioBe used strategically to drive industry credibility and to accelerate decision-making" We need to split into logical items. Probably each sentence after colon is a duty. Let's create list items: - Build a clear point of view on the Healthcare Provider market - Systematically document: - What health systems, hospitals, and ambulatory networks are doing today - Common patterns and use cases across provider organizations — from revenue cycle and patient access to clinical operations, care management, and workforce - Develop a clear, defensible POV on what provider organizations should be doing next to drive repeatable outcomes under margin pressure, workforce shortages, and value-based care demands - Translate your market POV into clear, repeatable sales plays aligned to specific buyer personas (CFO, CIO, Chief Nursing Officer, VP Revenue Cycle, VP Clinical Operations) and business outcomes - Equip sales teams with structured narratives that resonate with health system executives - Analyze opportunity size and prioritization - Partner with Sales, Strategy, and Product to: - Estimate TAM for priority provider use cases and plays (e.g., revenue cycle management, prior authorization, denials management, patient access/scheduling, clinical documentation, care coordination, discharge planning, EHR interoperability) - Help prioritize functions, workflows, and care settings based on impact, scale, and repeatability to the portfolio - Provide structured, evidence-based input into product strategy: What are the highest-impact areas that will drive business value for health systems and hospitals - Drive executive-level customer engagement - Engage senior leaders across health systems and provider organizations as a peer advisor - Contribute to outcome-focused conversations across our provider portfolio - Be used strategically to drive industry credibility and to accelerate decision-making That seems fine. Now "What you'll bring to the team": list: - 10+ years in healthcare, with deep, hands-on experience inside Provider organizations (health systems, hospitals, or ambulatory networks); exposure to Payer, BioPharma, or Medical Device environments is a plus - Leader with experience in provider-side functions such as Revenue Cycle, Clinical Operations, Care Management, Patient Access, Enterprise IT, or Compliance - Experience driving or influencing large-scale transformation initiatives inside a health system or hospital environment - Familiarity with the EHR and interoperability landscape (e.g., Epic, Oracle Health/Cerner) and provider regulatory/reimbursement dynamics (e.g., CMS, value-based care, HIPAA) Then "Ideal backgrounds (You may come from:)": list: - Digital transformation or operational leadership roles inside health systems, hospitals, or ambulatory networks - Industry strategy or principal roles at healthcare software companies serving Provider organizations - Healthcare-focused consulting roles with accountability for outcomes in provider settings These could be part of Requirements or Qualifications. We'll combine them under Requirements maybe. Then "What Distinguishes You": list: - You are action-oriented and comfortable within ambiguity - You naturally document, structure, and synthesize what you see - You think in patterns, plays, and leverage points - You can connect market insight to commercial opportunity - You influence without needing formal ownership These could be Skills or Qualities. Then "This Role Is Not": list of what it's not. Could be a note but maybe not needed as section. Could be included under About the role? Might be considered a clarification. Could be a short paragraph. Then "Success looks like": list: - Clear, documented Healthcare Provider POVs used across the company - Repeatable sales plays adopted by teams globally - Product decisions informed by real customer evidence from health systems and hospitals - Health system executives who view UiPath as a long-term strategic partner That could be a section maybe "Success metrics" but not in allowed headings. Could be part of About the role? Might be better as a separate section "Success" but not in allowed list. The allowed headings are limited; we could omit this section if not matching allowed headings. However we need to preserve ALL substantive information. If we omit a section, we lose that info. But we could incorporate that info into another section like About the role or Responsibilities? The success looks like is about what success looks like; could be placed under About the role as a description of expected outcomes. That seems okay. Thus we can have sections: About the role (includes intro, mission, success looks like, role not), Responsibilities, Requirements (includes what you'll bring, ideal backgrounds), Qualifications/Skills (maybe combine distinguishing traits). But we need to avoid thin sections. Perhaps we can have About the role, Responsibilities, Requirements, Qualifications (distinguishing traits). That's four sections. Let's craft HTML:

  About the role

  Life at UiPath ... Could that be you?

  Your mission: ... Success is measured by clarity, repeatability, and impact on growth.

  Success looks like: Clear, documented Healthcare Provider POVs used across the company; Repeatable sales plays adopted by teams globally; Product decisions informed by real customer evidence from health systems and hospitals; Health system executives who view UiPath as a long-term strategic partner.

  This role is not a quota‑carrying sales role, product management role, solution architecture or engineering role, or passive advisory or evangelist position.

  Then Responsibilities:

  Responsibilities

  • Build a clear point of view on the Healthcare Provider market
  • Systematically document:
    • What health systems, hospitals, and ambulatory networks are doing today
    • Common patterns and use cases across provider organizations — from revenue cycle and patient access to clinical operations, care management, and workforce
  • Develop a clear, defensible POV on what provider organizations should be doing next to drive repeatable outcomes under margin pressure, workforce shortages, and value-based care