Global Project Manager - Personalized Healthcare Solutions

We need to output HTML fragment with sections: About the role? The posting includes description of role, responsibilities, qualifications, benefits, pay, schedule. We must not repeat job title. Use

for each section heading. Use

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

  for prose. Remove boilerplate like EEO, etc. Also remove duplicated lines, navigation, cookie, etc. Must preserve all substantive info. We need to identify sections: The posting includes: - Intro about Roche culture (maybe "About Roche" or "About the role"? The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if there is real content. We have content: The Position description: "As part of the Project Management Chapter, the Global Project Manager (GPM) plays a key role..." That's responsibilities. Then "The Opportunity:" with bullet-like paragraphs each starting with a bold heading (Companion Diagnostics (CDx) Project Ownership, Schedule Management, Resource Management, Budget Management, Scope & Change Management, Stakeholder & Communication Management, Project Risk Management, Quality Management & Project Health, Partner & Vendor Management, Methodology & Execution). Those are responsibilities/duties. Then "Who You Are:" with requirements: Bachelor's degree, 4 years experience, etc. That's qualifications/requirements. Then "Preferred Qualifications:" with Master's/PhD etc. That's also qualifications/preferred. Then "This is a hybrid position with an expectation of on-site presence in the Oro Valley, AZ campus ~2 days/week." That's schedule. Then "Relocation benefits are not available for this posting." That's maybe benefits? Actually it's a note about relocation benefits not available. Could be part of Benefits section? But we only include Benefits if posting actually states them. There's a line: "This position also qualifies for the benefits detailed at the link provided below." That's a generic statement; but no specific benefits listed. The instruction: never create Benefits section unless posting actually states them. It says "qualifies for the benefits detailed at the link provided below." That's not stating specific benefits; it's a reference. Likely we should not create a Benefits section because no specific benefits are listed. However we could include a short paragraph referencing benefits link? But we must not invent detail. Probably omit Benefits section. Pay: "The expected salary range for this position based on the primary location of Arizona is $87,900 - $163,200. USD Annual. Actual pay will be determined based on experience, qualifications, geographic location, and other job-related factors permitted by law. A discretionary annual bonus may be available based on individual and Company performance." That's pay info, so we need a Pay section. Schedule: hybrid position expectation on-site ~2 days/week. That's schedule. We also have "Other duties as assigned by leadership" - that's part of responsibilities. We need to remove boilerplate: EEO, equal opportunity, accommodations, etc. Also remove duplicated lines. We need to preserve all substantive info: include the intro about Roche culture? That's maybe "About the role"? Actually the intro about Roche culture is more about company. Could be "About Roche" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put the introductory paragraph under "About the role". That seems appropriate: description of role and company culture. Thus sections: - About the role: include the first paragraph about Roche culture and the mission statement, plus maybe "The Position A healthier future..." Actually that's also part of role description. We'll combine. - Responsibilities: list all duty items from "The Opportunity:" and other duties. - Requirements: maybe combine "Who You Are:" (mandatory) and "Preferred Qualifications:"? But we have separate headings Requirements and Qualifications. Could treat Requirements as mandatory qualifications, Qualifications as preferred? Or we could have Requirements for mandatory, Qualifications for preferred. Or we could have Requirements for education/experience, Qualifications for preferred. Let's follow: Requirements = mandatory (Who You Are). Qualifications = Preferred Qualifications. - Skills: maybe we could list tools proficiencies (Planisware, MS Office, Google Suite, Trello, LucidChart, Smartsheet, Jira, Azure DevOps, Agile best practices, SAFe). Those are skills. Could put under Skills. - Pay: salary range and bonus. - Schedule: hybrid expectation. We must not create sections with filler. Ensure each section has substantive content. Now format: Use

  for each heading. Then content: either

  for prose or

  • for lists. We need to decide what to list as
    • . For responsibilities, we have many items each with a bold heading. Could make each as
    • with the heading bold? But we cannot use markdown; we can use HTML inside
    • . That's fine. We'll produce something like:

      About the role

      At Roche you can show up as yourself, embraced for the unique qualities you bring. Our culture encourages personal expression, open dialogue, and genuine connections, where you are valued, accepted and respected for who you are, allowing you to thrive both personally and professionally. This is how we aim to prevent, stop and cure diseases and ensure everyone has access to healthcare today and for generations to come. Join Roche, where every voice matters. The Position A healthier future. It’s what drives us to innovate. To continuously advance science and ensure everyone has access to the healthcare they need today and for generations to come. Creating a world where we all have more time with the people we love. That’s what makes us Roche. As part of the Project Management Chapter, the Global Project Manager (GPM) plays a key role in optimized product delivery and is accountable for all project management aspects of various projects from simple to complex in nature. The GPM drives the project from the original concept through completion by developing and directing detailed work plans, schedules, project estimates, spending, resource plans, and status reports. As a trusted advisor, the GPM translates and drives projects into products and enables the organization to use energy and time effectively and efficiently while quickly responding to changing business needs across the portfolio.

      Then responsibilities:

      Responsibilities

      • Companion Diagnostics (CDx) Project Ownership: You will proactively drive, from conception to launch, the development activities for CDx Development projects in close collaboration with third-party Pharmaceutical partners.
      • Schedule Management: You will proactively own timeline creation and management during scoping and post-contract execution using industry-standard tools such as Planisware. You will analyze the project critical path to determine priorities and drive team discussions, resolve dependencies and roadblocks, and guide the team to achieve key CDx contract deliverables.
      • Resource Management: You will collaborate with project team members and key functional stakeholders to identify project resource needs, align functional leaders on resource availability, and continuously monitor usage and performance to optimize team allocation and proactively escalate concerns.
      • Budget Management: You will drive the project budget from initial scoping through post-contract execution. You will perform regular monitoring and maintenance of the budget with key functional stakeholders, prepare exception analyses for business and finance stakeholders, and track FTEs and project expenditures.
      • Scope & Change Management: You will define project objectives and establish scope baselines. You will proactively identify and address any deviations in scope, budget, timeline, and resources using our change management process, and conduct comprehensive impact assessments. You will review Pharma-driven change requests with senior project stakeholders to determine if project contract amendments are necessary.
      • Stakeholder & Communication Management: You will own project team meetings amongst internal members as well as with Pharma partners to ensure the delivery of CDx contract milestones. You will partner with the project team to engage stakeholders through appropriate channels, resolve conflicts, and secure acceptance from key project stakeholders.
      • Project Risk Management: You will proactively identify, evaluate, and prioritize project risks, engaging stakeholders to co-develop mitigation strategies and contingency plans. You will regularly review risks with your project team, and provide comprehensive risk reports to stakeholders to ensure informed decision-making.
      • Quality Management & Project Health: You will partner with Quality stakeholders to ensure project execution is in compliance with our Quality Management System (QMS) framework and regulatory guidelines. You will conduct lessons learned activities to drive continuous improvement and provide insights for future projects. You will maintain high project data quality to enable teams to recognize recurring issues, pinpoint their root causes, and promote ongoing learning and process optimization.
      • Partner & Vendor Management: You will facilitate effective collaboration, information flow, and decision-making with external Pharma entities. You will ensure all contract milestones are accurately tracked and status communicated to key internal stakeholders. You will own the communication of invoice forecasts to Pharma partners.
      • Methodology & Execution: You will select and apply appropriate project methodologies, including hybrid Agile practices and Scaled Agile Framework (SAFe) where applicable. You will manage WBS creation and closeout, oversee milestone and capacity reviews, and act as a trusted advisor with a 360° view to support holistic planning and optimized value delivery.
      • Other duties as assigned by leadership.
      Then Requirements (mandatory):

      Requirements

      • Bachelor’s degree, preferably in a Life Sciences field.
      • 4 years of experience in project management / engineering / business in the diagnostic, medical device, pharmaceutical or biotech industry leading product development and product care projects.
      • At least one year of experience in the following areas: clinical biomarker or In Vitro Diagnostic development, CDx development, analytical and clinical validations, regulatory submissions, instrument/systems development, or program management.
      • One year of experience in a regulated industry (e.g. FDA 21 CFR part 820, ISO 13485, ISO 9001).
      • Proficient and demonstrated experience using Planisware, MS Office, and Google Suite, and “know-how” of project management tools such as Trello, LucidChart, Smartsheet, Jira, Azure DevOps, etc.
      • Working knowledge on Agile best practices and Agile-at-Scale methodologies (e.g SAFe), and experience operating in hybrid Waterfall-Agile environments.
      Then Qualifications (preferred):

      Qualifications

      • Master's degree, preferably in a Life Sciences field, and 6 years project management / engineering / business experience in the diagnostic, medical device, pharmaceutical or biotech industry leading product development and product care projects. Alternatively, a Ph.D with 3 years project management experience in those areas.
      • 3 years of clinical biomarker or In Vitro Diagnostic development experience in CDx development, analytical and clinical validations and regulatory submissions or instrument development and program management.
      • Significant experience managing complex project team structures, including third-party external co-development partners.
      • Project Management Professional (PMP) and/or SAFe Agile certifications.
      Then Skills: maybe we could list tools and methodologies as skills. But we already included many in Requirements. Could still have a Skills section for technical proficiencies not covered. However to avoid duplication, maybe we skip Skills section because those are already in Requirements. But the instruction: prefer a few substantive sections over many thin ones. We could combine skills into Requirements or Qualifications. However we have a separate allowed heading Skills. If we include it, we must have substantive content not just repeating. Could list specific tools: Planisware, MS Office, Google Suite, Trello, LucidChart, Smarts