Data Management Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. The posting includes: About The Role (we have that). Responsibilities (Key Responsibilities). Required Skills (list). Knowledge and Experience (maybe combine as Requirements/Qualifications). Education (maybe part of Qualifications). No explicit Benefits, Pay, Schedule. So we should not create those sections. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to parse the posting. Let's extract sections: About The Role: paragraph(s). The text: "We are hiring a remote based Data Manager Lead / Data Manager II to join our Parexel team. Location: Continental US About The Role The Data Manager Lead / Data Manager II provides technical expertise across all aspects of Data Management and serves as the primary Data Management point of contact for assigned studies. This role is responsible for ensuring contracted Data Management deliverables are met with a focus on quality and timeliness, while collaborating closely with cross-functional teams across global geographies. The successful candidate will manage study data delivery timelines, including Go-Live, Interim Deliveries, and Final Database Lock, while working with minimal guidance from Line Managers and/or Subject Matter Experts. The Data Manager II may also provide mentorship to Assistant Data Managers and Data Management peers." We need to keep all that. Probably we can combine the first sentence as part of About the Role. Responsibilities: "Key Responsibilities" then bullet list? The posting lists responsibilities in paragraphs but we can treat each sentence as list items? The instruction: Use

  • for any list of duties/requirements/benefits. The responsibilities are enumerated as separate sentences but not bullet list. We could still put them in
    • each as a duty. That seems appropriate. Let's list responsibilities: - Cross-Functional Data Management Leadership - Manage study data delivery timelines, including Go-Live, Interim Deliveries, and Final Database Lock. - Collaborate with Clinical, Biostatistics, Database Programming, Medical, Medical Writing, and other cross-functional stakeholders across global regions. - Manage and coordinate the integration and utilization of ancillary systems, as appropriate. - Identify risks and issues impacting study delivery, define mitigation strategies, and drive issue resolution with stakeholders. - Review and analyze study metrics to identify trends and summarize study health. - Review Master Services Agreements, Service Level Agreements, and contracts to manage sponsor-specific metrics and Key Performance Indicators. - Attend cross-functional meetings and prepare agendas, meeting minutes, action logs, and decision logs. - Bid Pursuits and Proposals - Demonstrate technical and operational Data Management expertise and capabilities tailored to sponsor needs. - Provide input for bid pursuit presentations and materials. - Effectively represent the Data Management function as part of a cross-functional team during sponsor presentations. - Quality Management and Compliance - Ensure compliance with Standard Operating Procedures and ICH/GCP guidelines. - Maintain inspection-ready Trial Master Files. - Identify and document quality issues, ensuring appropriate resolution and closure. - Prepare for and participate in internal, sponsor, and regulatory audits and inspections. - Drive and implement corrective and preventive actions and share lessons learned across projects and programs where appropriate. - Financial and Resource Management - Collaborate with Delivery Leads and line management to ensure appropriate project resourcing and staff assignments. - Identify and request functional resources required for project delivery. - Support the resolution of Data Management-related project variances, including scope changes where applicable. - Company Initiatives - Provide Data Management input to organizational initiatives. - Collaborate with cross-functional stakeholders to provide meaningful feedback on initiatives. - Ensure information maintained in management systems is accurate and up to date. - Training and Development - Maintain required training compliance, including on-the-job training. - Deliver project-specific training to internal Data Management teams. - Support identified development goals and training needs. - Provide on-the-job training when needed. We could keep subheadings? Not required; we can just list all responsibilities as
    • . But we need to preserve all detail. Could group under headings but not required. Simpler: just list each bullet as
    • . However we lose the grouping headings like "Cross-Functional Data Management Leadership". The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we drop the subheadings, we lose some detail (the category headings). Are those considered substantive? They are headings within responsibilities. Might be considered part of the content. We could keep them as or maybe as

      before list? But we are told to use

      • for any list of duties/requirements/benefits. Could we have a

        for the heading then a

        ? Probably acceptable: we can have a

        with the heading (like "Cross-Functional Data Management Leadership") then a

        with its items. That preserves the heading. Similarly for other sections. Now Required Skills: list of skills. The posting: "Required Skills Strong ability to lead and collaborate with global teams across multiple time zones and cultures.End to Strong negotiation and influencing skills.Excellent interpersonal, written, and verbal communication skills.Strong learning agility and knowledge-sharing mindset.Flexibility and adaptability in changing environments.Effective presentation skills.Strong customer focus with the ability to build rapport and trust.Commitment to quality with a methodical and accurate approach to work.Strong time management and prioritization skills.Proven problem-solving and root cause analysis capabilities.Strong sense of ownership and accountability.Ability to travel as required.Written and spoken fluency in English." It seems there is a typo: "End to" maybe meant "and". We'll keep as is? Probably we should keep the text exactly but maybe fix obvious typo? The instruction: do NOT invent or summarize away detail. Changing "End to" to "and" could be considered inventing? It's a typo; but we might keep as is. However it's weird. Might be better to keep as given: "Strong ability to lead and collaborate with global teams across multiple time zones and cultures.End to Strong negotiation and influencing skills." That seems odd. Could be a formatting issue: maybe missing period. We'll keep as is. We'll treat each skill as separate
        • . We need to split by periods? The text: "Strong ability to lead and collaborate with global teams across multiple time zones and cultures.End to Strong negotiation and influencing skills.Excellent interpersonal, written, and verbal communication skills.Strong learning agility and knowledge-sharing mindset.Flexibility and adaptability in changing environments.Effective presentation skills.Strong customer focus with the ability to build rapport and trust.Commitment to quality with a methodical and accurate approach to work.Strong time management and prioritization skills.Proven problem-solving and root cause analysis capabilities.Strong sense of ownership and accountability.Ability to travel as required.Written and spoken fluency in English." We can split at each capital letter after a period? Might be messy. Simpler: we can keep the whole block as a

          under Skills heading. But instruction says use

          • for any list of duties/requirements/benefits. Skills is a list, so we should use list. We could manually split by obvious separators: each skill ends with a period before next capital letter (except maybe "End to". We'll just split by "." and then trim. Let's attempt: 1. Strong ability to lead and collaborate with global teams across multiple time zones and cultures 2. End to Strong negotiation and influencing skills 3. Excellent interpersonal, written, and verbal communication skills 4. Strong learning agility and knowledge-sharing mindset 5. Flexibility and adaptability in changing environments 6. Effective presentation skills 7. Strong customer focus with the ability to build rapport and trust 8. Commitment to quality with a methodical and accurate approach to work 9. Strong time management and prioritization skills 10. Proven problem-solving and root cause analysis capabilities 11. Strong sense of ownership and accountability 12. Ability to travel as required 13. Written and spoken fluency in English We'll keep as is. Now Knowledge and Experience: This section includes many items. Could treat as Requirements or Qualifications. We'll make a section "Requirements" maybe. Or "Qualifications". The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications if content exists. We have Knowledge and Experience (maybe Requirements) and Education (maybe Qualifications). We'll split: Requirements = Knowledge and Experience; Qualifications = Education. Let's extract Knowledge and Experience bullet-like sentences: "Strong experience within the clinical research industry. 6+ years of hands on Clinical Data Management experience Hands-on Data Management expertise across all phases (startup, conduct, closeout) Experience authoring/coauthoring standard Data Management documents Hands on experience working in Medidata Rave Proven experience leading project and program teams. Good understanding of project tools, reports, and processes related to project financial management, including forecasting, revenue recognition, scope of work, and departmental budgets. Good understanding of Clinical Study Team roles outside of Data Management. Strong knowledge and application of ICH-GCP guidelines, local regulatory requirements, Standard Operating Procedures, and study-specific procedures. Awareness of SDTM, CDISC, and CDASH standards. Strong technical proficiency with Clinical Trial/Data Management Systems such as InForm, Rave, Veeva, DataLabs, and Microsoft Office applications." We'll put each as
          • under Requirements. Education: "Bachelor’s degree and/or other qualifications in a science or clinical-related field." We'll put as

            under Qualifications (or maybe as

            • but it's single item). Could be

              . Now we need to ensure we don't include boilerplate like location line? The location line: "Location: Continental US". That's substantive? It's location info. Should we include? The instruction: preserve ALL substantive information. Location is substantive. Where to put? Could be part of About the Role paragraph. We'll include it in About the Role as a sentence. Now we need to output only HTML fragment, no /, no markdown. Let's construct:

              About the Role

              We are hiring a remote based Data Manager Lead / Data Manager II to join our Parexel team. Location: Continental US. The Data Manager Lead / Data Manager II provides technical expertise across all aspects of Data Management and serves as the primary Data Management point of contact for assigned studies. This role is responsible for ensuring contracted Data Management deliverables are met with a focus on quality and timeliness, while collaborating closely with cross-functional teams across global geographies. The successful candidate will manage study data delivery timelines, including Go-Live, Interim Deliveries, and Final Database Lock, while working with minimal guidance from Line Managers and/or Subject Matter Experts. The Data Manager II may also provide mentorship to Assistant Data Managers and Data Management peers.

              Responsibilities

              • Cross-Functional Data Management Leadership
                • Manage study data delivery timelines, including Go-Live, Interim Deliveries, and Final Database Lock.
                • Collaborate with Clinical, Biostatistics, Database Programming, Medical, Medical Writing, and other cross-functional stakeholders across global regions.
                • Manage and coordinate the integration and utilization of ancillary systems, as appropriate.
                • Identify risks and issues impacting study delivery, define mitigation strategies, and drive issue resolution with stakeholders.
                • Review and analyze study metrics to identify trends and summarize study health.
                • Review Master Services Agreements, Service Level Agreements, and contracts to manage sponsor-specific metrics and Key Performance Indicators.
                • Attend cross-functional meetings