Head of Product

We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, privacy statement link, etc. Must preserve substantive info. We need to identify sections: About the role? The posting includes "Role Summary". Could map to "About the role". Responsibilities: "What You Will Be Doing" includes duties. Also "Senior Leadership" and "Cross-functional Collaboration & Knowledge Sharing". Could be part of responsibilities. Qualifications/Skills: "Who we are looking for" includes culture and benefits? Actually "Who we are looking for" includes growth & value creation? It lists culture description and benefits? Actually after that there is "We are an equal opportunities employer..." which is boilerplate to remove. Benefits: The posting lists benefits under "Some interesting points about us:" includes Competitive salary + bonus opportunities, Training and development programmes, Hybrid/flexible working, Share incentive plan, Increased annual leave with tenure, Pension/401k, Healthcare (including vision & dental) + additional benefits, Life insurance, Short & Long Term Disability, Enhanced maternity and sick pay, Paid Bonding Leave, Performance and growth framework, Staff referral scheme, Wellbeing initiatives and positive culture, Annual company get-together. Also earlier "Competitive salary + bonus opportunities" etc. So we can create Benefits section with those items. Pay: Not explicitly stated salary amount, only "Competitive salary + bonus opportunities". That's vague but still mentions compensation. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state competitive salary + bonus opportunities, which is about pay. So we could include Pay section with that statement. However they said prefer few substantive sections over many thin ones. Could combine Pay and Benefits? But they said use headings for Benefits, Pay, Schedule. If we have info for Pay, we should include Pay section. Benefits we have many. Schedule: they mention hybrid/flexible working, Flex Day programme. That's schedule info. So we can include Schedule section. Thus sections: About the role (Role Summary), Responsibilities (What You Will Be Doing + Senior Leadership + Cross-functional Collaboration), Qualifications/Skills? The posting includes "Who we are looking for" which is more about culture and benefits, not qualifications. There's no explicit qualifications like experience, education. So we may omit Qualifications/Skills if no specific content. Could include "Who we are looking for" as maybe "Qualifications" but it's mostly culture. Might be better to omit Qualifications/Skills as no specific qualifications listed. However we could treat "Who we are looking for" as describing desired traits: they mention culture, but not specific skills. The rule: never emit heading followed by filler/placeholder text. If we put Qualifications but content is vague like "We are looking for..." it's still substantive? It describes culture and benefits, not qualifications. Might be better to not include Qualifications/Skills. Thus sections: About the role, Responsibilities, Benefits, Pay, Schedule. We must use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not omit details. So we need to include all duties listed under "What You Will Be Doing" and also Senior Leadership and Cross-functional Collaboration details. That's a lot. We'll need to capture them as list items. We must not repeat job title. Must not include boilerplate like EEO, privacy statement link, equal opportunities employer, etc. We must remove duplicated lines. Let's extract content. First, Role Summary paragraph: "At Diaceutics we believe that every patient should have access to the right treatment at the right time. We provide the world’s leading pharmaceutical companies with an end-to-end solution for the launch of precision medicine diagnostics enabled by DXRX – The Diagnostic Network®. DXRX is the world’s first diagnostic commercialization platform for precision medicine, integrating multiple pipelines of real-world diagnostic testing data from a global network of laboratories. Role Summary The Head of Product leads and builds the product function across Diaceutics’ product areas, ensuring a coherent and aligned approach to product strategy, prioritization and execution across customer groups. The role is accountable for the product portfolio operating as a unified whole, with clear prioritization, effective planning cycles and strong cross-functional alignment. This is the first hire in a new structure, responsible for building a high-performing product function that translates strategy into customer value, commercial growth and market differentiation. You will shape the function as you build it, hiring product area teams in sequence and evolving the design as the work matures. Product roles are changing, and an AI-enabled function needs fewer and different roles, with definition and build held together in product engineering teams. You will be comfortable with ambiguity and with building while the function is being established. Product and data work hand in hand at Diaceutics. Every product is built on the DXRX data asset, so product decisions and data decisions are made together: data feasibility is confirmed before work is prioritized, the Data function is a design partner from the earliest stage, and roadmaps are shaped jointly with data leadership." We need to put this under About the role heading. Use

  for prose. Could break into multiple paragraphs but okay. Next, "What You Will Be Doing Duties and responsibilities will include:" then list. Let's extract each bullet: - Product Strategy Leading the product function as a cohesive portfolio, ensuring alignment of priorities and solutions across all customer groups. Building the function gradually: hiring Product Area Leads, Product Engineers and shared roles in sequence, and adjusting the design as AI tooling changes what each role needs to be. Working closely with the Data function: joint roadmap shaping with data leadership, data feasibility confirmed with the Data Product Lead before prioritization, and data treated as a design input from the earliest stage of every product decision. Owning portfolio-level planning processes, including quarterly planning cycles, ensuring they are well structured, effective and deliver clear decisions. Establishing consistent standards across the function, including roadmap structure, requirements definition, pricing and product packaging. Identifying and resolving cross-area dependencies, overlaps and conflicts, ensuring decisions are made at the appropriate level. Owning the product interface with the ring-fenced innovation team: the gating process, protection of the innovation ring-fence, and the routes by which innovation work graduates back into the core product and delivery pipeline. Supporting Product Area Leads with complex prioritization, stakeholder engagement and commercial decision-making. Partnering with Sales, Marketing and Customer Success to balance short-term commercial needs with long-term portfolio priorities. Managing shared design and product support roles, ensuring capacity is allocated effectively against priorities. Collaborating with Product Marketing to ensure the value proposition for each area is clear and supporting go-to-market planning in partnership with commercial teams. Maintaining a consistent and clear pricing framework across the portfolio and supporting pricing decisions. Embedding prototype-led, AI-first ways of working, including keeping product definitions structured and current enough to be machine-readable as agent-based buying and selling develops. Providing clear and accurate reporting on product development status, risks and decisions required, and supporting board-level and investor-facing materials where the portfolio must be clearly represented. - Senior Leadership Lead and develop a team of People Leaders and professionals across the Product function holding definition and building together, with accountability for outcomes end to end within each product area. Exemplify the One Diaceutics Leadership behaviors as a senior leader. Act as a trusted advisor and execution partner to the Chief Product & Technology Officer, advising on portfolio-wide investment, prioritization and resourcing decisions. Build strong, trusted relationships across the executive leadership team. Shape the evolution of the Product operating model, challenging thinking, setting direction and ensuring readiness to deliver strategic priorities. - Cross-functional Collaboration & Knowledge Sharing As a member of the Extended Leadership Team (ELT), bridge strategy and execution, reducing siloed thinking and driving operational excellence across Diaceutics. Partner closely with Sales, Client Services, Client Success, Data & Analytics, and Marketing to translate client needs and delivery insights into improvements that strengthen the company’s offering and to deliver a seamless end-to-end client experience. Represent Diaceutics externally with credibility and professionalism as a senior leader. We need to include all these as list items under Responsibilities. Could group under subheadings? Not allowed; only h3 for section headings. Could keep as flat list. Next, "Measure of Success" section includes metrics. Could be part of Responsibilities? Might be its own section but not in allowed headings list. Could treat as part of Responsibilities or maybe as a separate section like "Metrics". But not in allowed headings; we should not create new headings. Could incorporate into Responsibilities as list items. Next, "Who we are looking for" includes culture description and benefits. We'll extract benefits for Benefits section. Also maybe some traits: "Life at Diaceutics Culture is a powerful driver..." etc. That's more about culture, not qualifications. Could be omitted. Benefits list: - Competitive salary + bonus opportunities - Training and development programmes - Hybrid / flexible working (including Flex Day programme) - Share incentive plan - Increased annual leave with tenure - Pension/401k - Healthcare (including vision & dental) + additional benefits - Life insurance - Short & Long Term Disability - Enhanced maternity and sick pay - Paid Bonding Leave - Performance and growth framework - Staff referral scheme - Wellbeing initiatives and positive culture - Annual company get-together Also maybe "Competitive salary + bonus opportunities" is pay. Pay section: "Competitive salary + bonus opportunities". Could also mention "Competitive salary + bonus opportunities" as pay. Schedule section: "Hybrid / flexible working (including Flex Day programme)". Also maybe "All of our employees work remotely or in a hybrid model, collaborating together as a global community." That's schedule info. Thus schedule: hybrid/remote/flexible, Flex Day programme. Now we need to output HTML fragment. Structure:

  About the role

  ... (role summary paragraph)

  Responsibilities

  • ... each duty
  ...

  Benefits

  • ... each benefit
  ...

  Pay

  Competitive salary + bonus opportunities

  Schedule

  Hybrid / flexible working (including Flex Day programme); all employees work remotely or in a hybrid model, collaborating together as a global community.

  We must ensure we don't include boilerplate like "We are an equal opportunities employer..." etc. Check for duplicated lines: Ensure we didn't repeat any. Now craft the HTML. We need to be careful to preserve all substantive information from responsibilities list. Let's copy each bullet exactly as in text, maybe adjust punctuation. Let's list them: Product Strategy: 1. Leading the product function as a cohesive portfolio, ensuring alignment of priorities and solutions across all customer groups. 2. Building the function gradually: hiring Product Area Leads, Product Engineers and shared roles in sequence, and adjusting the design as AI tooling changes what each role needs to be. 3. Working closely with the Data function: joint roadmap shaping with data leadership, data feasibility confirmed with the Data Product Lead before prioritization, and data treated as a design input from the earliest stage of every product decision. 4. Owning portfolio-level planning processes, including quarterly planning cycles, ensuring they are well structured, effective and deliver clear decisions. 5. Establishing consistent standards across the function, including roadmap structure, requirements definition, pricing and product packaging. 6. Identifying and resolving cross-area dependencies, overlaps and conflicts, ensuring decisions are made at the appropriate level. 7. Owning the product interface with the ring-fenced innovation team: the gating process, protection of the innovation ring-fence, and the routes by which innovation work graduates back into the core product and delivery pipeline. 8. Supporting Product Area Leads with complex prioritization, stakeholder engagement and commercial