Sr Director, Supply Chain

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting starts with company description about Gilead, then "Job Description Head of Global Supply Chain Digital Technology (Senior Director)" - this is the job title, which I should not repeat as a heading. Then there's a paragraph describing the role: "We are seeking a highly motivated individual to join the Global Supply Chain Strategy and Operations team as Senior Director of Digital Technology..." Then there are several sections with headings: - "Job Description Strategy and Roadmap Development" - this seems like a section heading - "Innovation, Change Leadership, and Continuous Improvement" - "Program Delivery and Vendor Coordination" - "Collaboration and Influence" - "Leadership & People Development" - "Qualifications Domain Knowledge & Experience" - "Digital & Systems Fluency" - "Technical & Strategic Skills" - "Leadership & Soft Skills" - "People Leader Accountabilities" Then salary range: "$243,100.00 - $314,600.00" and benefits info. Then lots of boilerplate: EEO, polygraph protection, FMLA, pay transparency, etc. - these should be removed. Also "For Current Gilead Employees And Contractors Please apply via the Internal Career Opportunities portal in Workday." - application instructions, remove. I need to structure this into semantic HTML with appropriate sections. Let me think about the sections: 1. About the role - the introductory paragraph describing the role 2. Responsibilities - the various duty sections (Strategy and Roadmap Development, Innovation/Change Leadership, Program Delivery, Collaboration, Leadership & People Development) 3. Qualifications - the qualifications sections (Domain Knowledge, Digital & Systems Fluency, Technical & Strategic Skills, Leadership & Soft Skills) 4. People Leader Accountabilities - this is a specific section 5. Pay - salary range is given 6. Benefits - benefits are described I should combine the responsibility sections into one "Responsibilities" section with sub-lists or just a combined list. The instructions say use

  • for any list of duties/requirements/benefits. The responsibilities are listed as bullet points under each sub-heading. I could either keep the sub-headings as part of the list items or create nested lists. Since the rule says use

    for section headings, and these are sub-sections of responsibilities, I could make them

    but the rule only mentions

    for section headings. The rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels, but to keep it simple, I'll use

    for main sections and maybe

    for sub-sections? But the instruction says "use

    for section headings" and gives examples. It doesn't say I cannot use other headings. However, to be safe, I'll use

    for the main sections only, and within Responsibilities, I'll list the duties as bullet points, perhaps grouping them under the sub-headings as bold text or something. But the rule says "Use

    • for any list of duties/requirements/benefits, and

      for prose." So I can have a

      with
      • items that include the sub-heading as bold text followed by the bullet points. Alternatively, I could create separate

        for each responsibility area? But the examples given are "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So "Responsibilities" is one section. I'll make one Responsibilities section with a list of all duties, perhaps organized with the sub-headings as part of the list items. Similarly for Qualifications: there are multiple sub-sections. I'll make a Qualifications section with a list of all qualification items. Let me parse the content: **About the role**: The paragraph after the job title: "We are seeking a highly motivated individual to join the Global Supply Chain Strategy and Operations team as Senior Director of Digital Technology. The successful candidate will lead the digital strategy, implementation roadmap, and cross-functional coordination to transform processes through innovative digital solutions. Candidate will oversee implementation of emerging technologies (including AI), and champion data-driven, digitally empowered ways of working. The Head of GSC Digital Technology will report to the Executive Director of Global Supply Chain Strategy and Operations and partner closely with Global Supply Chain leadership, Information Technology, Manufacturing, Quality and the broader Gilead digital ecosystem." **Responsibilities**: - Strategy and Roadmap Development: - Continuously refine a Global Supply Chain Digital Enablement roadmap aligned to organizational priorities and enterprise platforms. - Translate Global Supply Chain-specific digital needs into business cases for enterprise-level investments. - Lead the business case development and ROI analysis for new digital investments, effectively communicating trade-offs between speed, cost, and scope to leadership. - Innovation, Change Leadership, and Continuous Improvement: - Articulate a compelling vision for digital transformation within Global Supply Chain. - Leverage data science AI models to transform the ways of working and accelerate supply chain. - Drive strategic data-centric solutions to enable product supply to patients. - In partnership with IT, scan the digital landscape for emerging tools applicable for supply chain from supply planning, production planning, logistics and distribution. - Lead change management, including upskilling, communication planning, and user adoption. - Partner with GSC and PDM operational excellence in designing, digitizing, and automating processes. - Partner with broader Global Supply Chain community to identify areas where digital can remove friction or enable leapfrog innovation. - Program Delivery and Vendor Coordination: - In partnership with IT, identify, evaluate, and create strategic partnerships with established and emerging technology providers to bring cutting-edge solutions and expertise into the organization. - In partnership with key stakeholders, drive digital pilots and implementations. - Foster relationships with internal partners (e.g., IT, Quality, Manufacturing) and external vendors. - Collaboration and Influence: - Serve as a bridge between Global Supply Chain and PDM digital governance groups. - Represent Global Supply Chain in PDM Digital and Data Program committees and structured content working groups. - Align efforts with data governance, structured data initiatives, and broader PDM digital programs. - Leadership & People Development: - Create a collaborative and inclusive work environment, promoting teamwork and effective communication. - Lead, mentor, and develop a high-performing team of data scientists. **Qualifications**: - Domain Knowledge & Experience: - Requires a PhD OR MS with 10+ years of relevant professional experience, OR BS with 12+ years of relevant professional experience. - Proven experience integrating data and digital tools. - Training or certification in data science, informatics and digital transformation preferred. - Comprehensive understanding of the biopharmaceutical industry, R&D, and product commercialization, including the regulatory framework. - Digital & Systems Fluency: - Experience designing, selecting, and implementing digital tools such as planning tools, SAP, reporting and analytics, and AI. - Understanding of structured content, automation, and enterprise knowledge systems. - Technical & Strategic Skills: - Demonstrated enterprise mindset with ability to align Global Supply Chain needs to enterprise platforms and solutions, ensuring scalability, interoperability, and long-term business value. - Proven success leading digital initiatives from strategy through implementation. - Established data acumen, understanding of advanced analytics, data architecture, and data engineering. - Strong AI fluency with experience deploying both everyday AI tools for general use and custom AI and digital solutions in a technical environment. - Knowledge of data governance principles, systems integrations, and metadata management is a plus. - Leadership & Soft Skills: - Visionary leader who can define and execute a digital and data strategy for global supply chain. - Excellent collaborator with scientists, engineers, IT, manufacturing and others. - Change agent with the ability to inspire adoption and build digital fluency across teams. - Track record of building and managing high-performing, multidisciplinary teams. **People Leader Accountabilities**: - Create Inclusion - knowing the business value of diverse teams, modeling inclusion, and embedding the value of diversity in the way they manage their teams. - Develop Talent - understand the skills, experience, aspirations and potential of their employees and coach them on current performance and future potential. They ensure employees are receiving the feedback and insight needed to grow, develop and realize their purpose. - Empower Teams - connect the team to the organization by aligning goals, purpose, and organizational objectives, and holding them to account. They provide the support needed to remove barriers and connect their team to the broader ecosystem. **Pay**: The salary range for this position is: $243,100.00 - $314,600.00. Gilead considers a variety of factors when determining base compensation, including experience, qualifications, and geographic location. These considerations mean actual compensation will vary. This position may also be eligible for a discretionary annual bonus, discretionary stock-based long-term incentives (eligibility may vary based on role), paid time off, and a benefits package. **Benefits**: Benefits include company-sponsored medical, dental, vision, and life insurance plans*. For Additional Benefits Information, Visit https://www.gilead.com/careers/compensation-benefits-and-wellbeing. Eligible employees may participate in benefit plans, subject to the terms and conditions of the applicable plans. Now, I need to output HTML fragment with these sections. I'll use

        for each main section: About the role, Responsibilities, Qualifications, People Leader Accountabilities, Pay, Benefits. For Responsibilities, I'll create a

        with each duty as a
        • . Since there are many, I'll include the sub-heading as bold text within the list item, then maybe a nested list? But the rule says use
          • for any list of duties. I could make a flat list with each bullet being a duty, prefixed by the category. Or I could use nested lists:
            • Strategy and Roadmap Development
              • ...
            ... That would be more semantic. The rule doesn't forbid nested lists. I'll do nested lists for clarity. Similarly for Qualifications. For People Leader Accountabilities, it's a list of three items with descriptions. For Pay, it's prose with salary range and details. For Benefits, prose with list of benefits. I'll also include the company description? The posting starts with "At Gilead, we’re creating a healthier world..." That's company boilerplate. The rule says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Company description might be considered boilerplate? But it's part of the job posting. The instruction says "Preserve ALL substantive information". The company description is substantive? It's generic company mission. Might be considered boilerplate. However, the user said "