Director of Product Management - Evidence Platform

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 specific content. We must not repeat job title as heading. Remove boilerplate like EEO, legal, etc. Also remove application instructions. Keep all substantive info. We need to parse the posting. First part: description of Truveta, mission, hybrid model, etc. That could be "About the role" or "About Truveta"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" containing overview of role and company. Then "Responsibilities" with bullet list. Then "Required Qualifications" maybe as "Requirements" or "Qualifications". They said use headings like Requirements, Qualifications, Skills. We need to decide. Probably "Qualifications" for required qualifications, and maybe "Preferred Qualifications" could be under "Preferred Qualifications" but we may combine? They said include a section only when posting has real specific content. We have both Required and Preferred qualifications. Could have "Required Qualifications" and "Preferred Qualifications" as separate sections under headings "Qualifications" maybe? But they gave examples: Requirements, Qualifications, Skills. Could treat "Required Qualifications" as "Qualifications" and "Preferred Qualifications" as "Preferred Qualifications" maybe as a subsection? But they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "Qualifications" for required, and maybe "Preferred Qualifications" as a separate heading? Not in list but could still be used? Safer to follow examples: we can have "Qualifications" for required, and maybe "Preferred Qualifications" as a separate heading but not in examples; but they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should stick to those headings; we can still add other headings if needed but better to follow. We could put both required and preferred under "Qualifications" with sub-bullets? But they said use

• for any list of duties/requirements/benefits. So we can have a
  for qualifications, mixing required and preferred? Might be okay but we need to preserve all info. Could separate into two
  under same heading with headings inside? Not allowed? Could use

  to label "Required:" then list. But better to have two sections: "Required Qualifications" and "Preferred Qualifications". The instruction didn't forbid other headings, just gave examples. So we can include those. Also "Skills" maybe not explicitly listed; we could omit if not present. There's no explicit skills list separate from qualifications. Could omit Skills. Benefits: there is a "Why Truveta?" and "We Offer" paragraph listing benefits: Interesting and meaningful work, Great benefits package, Comprehensive benefits with strong medical, dental and vision insurance plans, 401K plan, Professional development & training opportunities, Work/life autonomy via flexible work hours and flexible paid time off, Generous parental leave, Regular team activities (virtual and in-person). Also base pay range. So we can have Benefits section with those bullet points. Pay section: base pay range $253,000 to $280,000. Also mention additional compensation like incentive pay and stock options. So Pay section. Schedule: mention hybrid model, in-person attendance required at least once per year for onsite meeting, optimize meeting hours in PT, avoid recurring meetings after 3pm PT, ad hoc meetings 8am-6pm PT. That's schedule info. So we can have Schedule section. Also "About the role": we can include description of Truveta mission, hybrid model, etc. Also the opportunity description: "Build the platform that powers the next generation of AI-native clinical research." etc. That could be part of About the role. We must not include boilerplate like EEO, legal, visa sponsorship, etc. Also remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. So we need to cut the final paragraphs about visa sponsorship, EEO encouragement, etc. Also the line "Please note that all applicants must be authorized to work in the United States..." etc. Remove. Also remove "If you are based in California, we encourage you to read this important information for California residents linked here." That's also boilerplate. Also remove "We appreciate your interest in the position and encourage you to explore future opportunities with us." That's application instruction? Might be considered boilerplate; better to remove. Now produce HTML fragment. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Required Qualifications

  • ...
  ...

  Preferred Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  The base pay for this position is $253,000 to $280,000. The pay range reflects the minimum and maximum target. Pay is based on several factors including location and may vary depending on job-related knowledge, skills, and experience. Certain roles are eligible for additional compensation such as incentive pay and stock options.

  Schedule

  Truveta offers a hybrid work model with the flexibility to work from anywhere. In‑person attendance is required at least once per year for an onsite meeting. Meeting hours are optimized for the Pacific Time Zone; recurring meetings are avoided after 3 pm PT, while ad hoc meetings may occur between 8 am and 6 pm PT.

  Check we didn't repeat job title. Good. Now ensure we preserved all substantive info from posting. Let's extract About the role content: The first paragraphs about Truveta mission, hybrid model, etc. Also the opportunity description: "This Opportunity “Build the platform that powers the next generation of AI-native clinical research.” Evidence is one of Truveta’s three core product pillars, alongside Data and Intelligence. Reporting to the Head of Evidence, you will lead the Product Management organization within Evidence and partner to shape the strategy, roadmap, and customer experience of the Evidence Platform. The Evidence Platform enables researchers, healthcare organizations, and life science companies to transform one of the world’s largest collections of healthcare data into trusted real-world evidence (RWE). It provides the reusable platform capabilities that power clinical research, regulatory evidence generation, healthcare analytics, AI-powered research, and future healthcare applications. You will join a small, highly collaborative team and lead a growing Product Management organization. This role combines organizational leadership with hands-on product management. In addition to leading the Product Management organization, you will personally own strategic product areas, partner closely with customers and engineering teams, and drive products from discovery through launch and continuous improvement, helping define the platform that enables the next generation of AI-native clinical research. A successful Director of Product Management at Truveta is someone who: Thinks in platforms rather than point solutions, building reusable capabilities that support multiple products, workflows, and customer segments. Leads by example, balancing organizational leadership with hands-on ownership of strategic product areas and close partnership with customers and Engineering. Is deeply curious about researchers, healthcare organizations, and life science customers, meeting them where they work rather than forcing them into predefined workflows. Uses customer insights, experimentation, and product data to continuously improve products and prioritization. Builds high-performing Product Management teams while creating clarity and alignment across Engineering and cross-functional stakeholders." We need to include that in About the role paragraph(s). Could be multiple

  tags. Now Responsibilities: list from "Responsibilities" section: Product leadership, Platform strategy and customer value, Data-driven product management, Cross-functional leadership. Each has sub-bullets. We'll flatten into

  • items. Let's extract: Product leadership - Lead, coach, and grow the Product Management organization for the Evidence Platform. - Personally own one or more strategic product domains, driving product discovery, customer validation, feature definition, prioritization, launch, and continuous improvement. - Partner with the Head of Evidence to translate long-term product vision into strategy, roadmaps, priorities, and measurable outcomes. - Build a high-performing product organization with clear ownership, accountability, and execution. Platform strategy and customer value - Develop a deep understanding of researchers, healthcare organizations, pharmaceutical companies, and life science customers, translating their needs into reusable platform capabilities. - Define and evolve the platform strategy, balancing customer value, scientific rigor, engineering investment, extensibility, scalability, and long-term platform evolution. - Stay close to customer workflows, product behavior, and technical tradeoffs while simplifying research workflows and enabling future AI-powered experiences. Data-driven product management - Establish a culture of data-driven product management using customer insights, product metrics, experimentation, and business outcomes. - Define product success metrics, evaluate customer behavior and outcomes, identify opportunities, and continuously improve the product portfolio. Cross-functional leadership - Partner closely with Engineering, Design, Data, Intelligence, Catalysts, Evidence Services, Customer Success, Product Marketing, Sales, and executive leadership. - Drive alignment across organizations while balancing customer-facing innovation with platform scalability, reliability, and operational excellence. Now Required Qualifications list: - Bachelor’s degree or higher in Computer Science, Engineering, Life Sciences, Statistics, Public Health, Healthcare, or a related quantitative field. - 10+ years of Product Management experience, including significant experience leading Product Managers or product teams. - Demonstrated success building enterprise SaaS, platform products, data platforms, analytics platforms, research platforms, AI-enabled products, or other complex data-intensive software. - Strong understanding of clinical research, real-world evidence (RWE), real-world data (RWD), healthcare analytics, clinical informatics, biomedical informatics, or life sciences. - Proven ability to translate long-term product strategy into measurable execution. - Demonstrated experience owning strategic product areas end-to-end while leading and developing Product Managers. - Systems thinking with the ability to identify reusable platform capabilities that support multiple products, workflows, and customer segments rather than isolated solutions. - Strong product judgment balancing customer needs, scientific rigor, technical constraints, extensibility, and long-term platform evolution. - Strong analytical mindset with experience using customer behavior, experimentation, and product metrics to guide product decisions. - Excellent communication and stakeholder management skills across engineering, clinical, commercial, and executive leadership. Preferred Qualifications list: - Experience building products for pharmaceutical, biotechnology, healthcare, medical device, CRO, academic research, or research-intensive software organizations. - Experience supporting observational research, clinical trials, regulatory submissions, or regulatory-grade evidence generation. - Experience working with healthcare data including EHR, claims, genomics, imaging, registries, or other real-world data sources. - Experience building extensible platform products, shared platform capabilities, or data products supporting multiple solution areas. - Experience designing products that integrate naturally into researcher workflows rather than requiring customers to adopt entirely new ways of working. - Experience using Azure DevOps (ADO) for roadmap planning, backlog management, portfolio management, and cross-team coordination. - Experience building AI-enabled products, analytics platforms, or research software. - Advanced degree such as an MS, PhD, MD, MPH, or MBA. Benefits list from "We Offer": - Interesting and meaningful work for every career stage - Great benefits package - Comprehensive benefits with strong medical, dental and vision insurance plans - 401K plan - Professional development & training opportunities for continuous learning - Work/life autonomy via flexible work hours and flexible paid time off - Generous parental leave - Regular team activities (virtual and in-person) Also maybe "We have strong, established leadership with decades of success. We are well-fund