Head of Pharmacogenomics (PGx)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the job posting. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, privacy notice, etc. Also remove duplicated lines. We need to preserve all substantive information. Let's extract content. The posting starts: "Who We Are & What We Do At Helix, our mission is simple: to help everyone improve their lives through their DNA. Ready to make a real-world impact with your skills? At Helix, we're transforming healthcare by making genomics a standard of care. We partner with health systems and life science companies to accelerate the integration of genomic data into clinical practice. Join us in building a future where healthcare is personalized, proactive, and powered by genomics. As the business leader for pharmacogenomics at Helix, you’ll define what we build, how our solutions are put into practice, and how the PGx business grows. Working across Commercial, Product, Medical, and Operations, you’ll shape our go-to-market strategy, influence the product roadmap, and engage directly with health-system and health-plan leaders to turn PGx capabilities into products and partnerships that improve care and lower the cost of care. Why this role is different Shape the future of PGx adoption: Helix’s Sequence Once, Query Often® model makes genomic insights available on demand at the point of care. You’ll build on that advantage to define how health systems and health plans use PGx to inform medication decisions, and create the products and partnerships that make PGx a standard part of patient careA builder’s mandate: You’ll have the opportunity to shape a growing business from the ground up, with a direct connection between customer needs, product decisions, commercial strategy, and clinical adoptionFind and Build High-Value PGx Use Cases: Working closely with customers, you’ll identify patient populations where PGx can improve care and lower total cost of care, then turn those opportunities into compelling value propositions and scalable rollout plans As Head Of Pharmacogenomics At Helix, You Will Own the PGx business mandate: Set the growth strategy for Helix’s PGx business, with accountability for product adoption and customer engagement across health systems and health plansDevelop compelling PGx ROI models: Inform the design of ROI models that demonstrate the economic value of PGx across fee-for-service and risk-bearing organizationsServe as the external subject matter expert: Represent Helix in conversations with health system and health plan executives, pharmacy leaders, and clinical teams to design and deploy enterprise PGx programsShape the product roadmap: Translate customer and clinical needs into product priorities, including EHR-embedded Clinical Decision Support, patient identification, drug-gene interaction alerting, and pharmacist workflowsBuild the go-to-market motion: Partner with Marketing and Business Development to define target customers, sharpen the Helix PGx value proposition, and create the materials and commercial strategies that turn interest into adoptionInform strategy through clinical and market Insight: Track evolving clinical guidelines,, reimbursement trends, and developments in PGx to identify new product and commercial opportunities" Then "About You" bullet list. Then "The Ideal Candidate Will Have ..." Then "Expected Interview Process" list. Then "Expected Pay For This Role" details. Then "Aside from working alongside brilliant... we also provide great benefits:" list. Then "What To Expect During Your First 90 Days" description. Then "Compensation The base pay range for this role is $206,000 – $265,000 per year." We need to produce sections: maybe About the role (description), Responsibilities (list of duties), Requirements/Qualifications/Skills (maybe combine), Benefits, Pay. We must not create sections with placeholder text. We need to decide which sections have real content. - About the role: The initial paragraph describing mission and role could be "About the role". That seems appropriate. - Responsibilities: The bullet list under "As Head Of Pharmacogenomics At Helix, You Will ..." includes many responsibilities. Also earlier "Why this role is different" includes responsibilities. So we can create a Responsibilities section with list items. - Requirements/Qualifications/Skills: The "About You" and "The Ideal Candidate Will Have" sections contain qualifications. Could combine into Requirements (or Qualifications). We need to decide which heading(s) to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can pick a few that have content. Probably we need Requirements (or Qualifications) and maybe Skills. But we should not create thin sections. Let's see content: About You: - 7+ years of experience in pharmacogenomics, precision medicine, clinical digital health, or a related product or commercial role, ideally at a PGx or precision medicine company - Experience leading complex enterprise conversations with health system or health plan executives and building a clear clinical and economic case for adoption - Strong understanding of EHR integration, clinical decision support, and physician and pharmacist workflows - Ability to translate customer and clinical needs into product priorities and commercial strategies - Clear, credible communicator who can work effectively across clinical, commercial, product, and technical teams - AI tools are a natural part of how you work – to synthesize clinical literature, model ROI scenarios, and move faster on customer deliverables The Ideal Candidate Will Have: - PharmD, MD, or advanced degree in a relevant clinical, scientific, or health related field - Experience in health system pharmacy, comprehensive medication management, or clinical decision support - Experience developing health economic models, ROI cases, reimbursement strategies, or value-based commercial arrangements These are qualifications/requirements. Could be under "Requirements" or "Qualifications". We'll choose "Requirements". Could also add "Skills" but maybe not needed. Benefits: The paragraph after "Aside from working alongside brilliant..." lists benefits: Comprehensive Health Insurance with Date of Hire eligibility, Above average employer paid premium coverage, 12 weeks Helix Paid Parental Leave option, 401(k) with employer matching of up to 3% and 100% Vesting on the Date of Hire, Comprehensive Well-Being Benefits, Flexible PTO, Remote options for many roles and a home office stipend. That's substantive. Pay: The "Expected Pay For This Role" includes base salary range, bonus, equity description. Also later "Compensation The base pay range for this role is $206,000 – $265,000 per year." So we have pay info. Schedule: Not mentioned. No schedule info. So we should not create Schedule section. We also have "What To Expect During Your First 90 Days" which could be considered "Onboarding" but not in allowed headings. Could be part of About the role? Might be better to include as a separate section? The allowed headings list does not include "Onboarding" or "First 90 Days". We could incorporate into About the role or maybe treat as Responsibilities? Probably better to include as a separate section named "What to Expect" but not allowed. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. But we should prefer those headings. However we could still add other headings if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but not strictly limited? It says "e.g." meaning examples. But to be safe, we stick to those. Thus we can incorporate the first 90 days info into About the role or maybe as a separate section named "What to Expect" but that's not in list; maybe better to include under About the role. We also have "Expected Interview Process" which is about hiring process; not needed for job description? Could be omitted as it's not substantive about role? It's part of posting but maybe we can drop as it's not role content. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Interview process is not exactly those but could be considered application instructions? It's part of hiring process. Might be considered application instructions. Safer to omit. Thus final sections: About the role, Responsibilities, Requirements, Benefits, Pay. Now we need to format. Use

for each section heading. Under each heading, use

for prose,

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. Let's craft About the role prose: combine the initial mission description and role overview. We need to include: mission, transforming healthcare, partnering, building future, As the business leader for pharmacogenomics you’ll define..., Working across Commercial, Product, Medical, and Operations..., Why this role is different: shape future of PGx adoption, builder’s mandate, find and build high-value PGx use cases. We'll write a paragraph(s) that capture all. Responsibilities list: extract from "As Head Of Pharmacogenomics At Helix, You Will Own the PGx business mandate:" etc. List items: - Own the PGx business mandate: Set the growth strategy for Helix’s PGx business, with accountability for product adoption and customer engagement across health systems and health plans - Develop compelling PGx ROI models: Inform the design of ROI models that demonstrate the economic value of PGx across fee-for-service and risk-bearing organizations - Serve as the external subject matter expert: Represent Helix in conversations with health system and health plan executives, pharmacy leaders, and clinical teams to design and deploy enterprise PGx programs - Shape the product roadmap: Translate customer and clinical needs into product priorities, including EHR-embedded Clinical Decision Support, patient identification, drug-gene interaction alerting, and pharmacist workflows - Build the go-to-market motion: Partner with Marketing and Business Development to define target customers, sharpen the Helix PGx value proposition, and create the materials and commercial strategies that turn interest into adoption - Inform strategy through clinical and market Insight: Track evolving clinical guidelines, reimbursement trends, and developments in PGx to identify new product and commercial opportunities Also earlier "Why this role is different" includes: Shape the future of PGx adoption: define how health systems and health plans use PGx to inform medication decisions, and create the products and partnerships that make PGx a standard part of patient care; builder’s mandate: shape a growing business from the ground up, with direct connection between customer needs, product decisions, commercial strategy, and clinical adoption; Find and Build High-Value PGx Use Cases: identify patient populations where PGx can improve care and lower total cost of care, then turn those opportunities into compelling value propositions and scalable rollout plans. We could incorporate those as responsibilities as well. Might be redundant but we should preserve all. Let's combine them into list items, avoiding duplication. We'll create a comprehensive list: - Shape the future of PGx adoption: define how health systems and health plans use PGx to inform medication decisions, and create the products and partnerships that make PGx a standard part of patient care - Builder’s mandate: shape a growing business from the ground up, with a direct connection between customer needs, product decisions, commercial strategy, and clinical adoption - Find and build high-value PGx use cases: identify patient populations where PGx can improve care and lower total cost of care, then turn those opportunities into compelling value propositions and scalable rollout plans - Own the PGx business mandate: set the growth strategy for Helix’s PGx business, with accountability for product adoption and customer engagement across health systems and health plans - Develop compelling PGx ROI models: inform the design of ROI models that demonstrate the economic value of PGx across fee-for-service and risk-bearing organizations - Serve as the external subject matter expert: represent Helix in conversations with health system and health plan executives,