Director, RDU IT Business Partner, Commercial - Alexion

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to preserve all substantive information. We need to parse the posting. Let's extract sections: - "WHY JOIN US?" is a section but not in list; we can maybe treat as About the role? Actually "WHY JOIN US?" is like an intro. Could be part of About the role? But we have "About the Role" heading later. We'll include "About the role" section with content from "WHY JOIN US?" and maybe "Introduction". The posting includes "WHY JOIN US?" paragraph about purpose, etc. Then "Hybrid Policy" paragraph about Boston, 3 days office. Then "Introduction" paragraph about role description. Then "About the Role" heading with description. We need to combine into About the role section. We must not create sections with filler. So we need to decide which sections have content. Responsibilities: There's a "Key Responsibilities" list with bullet points. Also there is "AI-Ready Business Partner Responsibilities" which seems like more responsibilities. So we can combine under Responsibilities. Requirements: There's "Essential Qualifications" and "Preferred Qualifications". Those could be Requirements and Qualifications? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have "Essential Qualifications" (list of bullet-like sentences). That could go under Requirements or Qualifications. Usually Requirements = essential qualifications. Qualifications = preferred qualifications? Or Skills = specific skills. We'll decide: - Requirements: Essential Qualifications (must-have). - Qualifications: Preferred Qualifications (nice-to-have). - Skills: maybe extract specific skills from responsibilities? But we could also put skills under Responsibilities? However we need to include Skills section only if there is real specific content. The posting mentions many skills: "Strong understanding of US Commercial business processes", "Working knowledge of Market Access, GTN", "Experience shaping or delivering data, analytics, digital, automation, AI, or technology-enabled transformation capabilities", "Experience with CRM and related commercial platforms such as Salesforce, Veeva", "Strong understanding of data products, analytics, reporting, commercial data foundations, SDLC, Agile practices, privacy, security, quality, compliance, and regulatory expectations", "Experience managing portfolio funding, business cases, risks, dependencies, vendor engagement, and executive-level reporting", "Ability to influence senior stakeholders, simplify complexity, drive alignment, communicate technology concepts in business language, and connect technology investments to business value, patient impact, efficiency, adoption, and risk reduction." Those could be considered Skills. We'll put them under Skills. But we must not duplicate content. We'll need to extract and maybe rephrase? We must preserve all substantive information, not invent or summarize away detail. So we need to keep the exact sentences? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not paraphrase or condense; we should keep the original text. However we can keep bullet points as

• . So we need to keep the content verbatim (or close). We can keep the sentences as they appear. Thus we need to extract the exact bullet points from "Key Responsibilities" and "AI-Ready Business Partner Responsibilities". Also the "Essential Qualifications" list (each line starts with a bold phrase? Actually they are sentences separated by periods). We'll need to format each as
• . Similarly for "Preferred Qualifications". For Skills, we need to extract skill statements; they are interspersed within Essential Qualifications and maybe elsewhere. But to avoid duplication, we could treat Skills as a separate section containing skill-related statements that are not already captured in Requirements/Qualifications. However that may cause duplication. The instruction says preserve ALL substantive information; we can include them in multiple sections? Might be okay but could be considered duplication. Better to follow the headings: Requirements = Essential Qualifications; Qualifications = Preferred Qualifications; Skills = maybe extract from the responsibilities? But responsibilities already contain skill-like statements. However we can still include them under Skills if they are distinct. Given the complexity, maybe we can simplify: Use only About the role, Responsibilities, Requirements (Essential Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay, Schedule. Skip Skills if not clearly separate. But the instruction says we can prefer a few substantive sections over many thin ones. So we could omit Skills if not clearly defined. However the posting does have skill statements; but we could incorporate them into Requirements or Responsibilities. Since we must preserve all info, we can keep them within Requirements (essential) and Qualifications (preferred). That would still preserve all info. So we can omit Skills section. Benefits: The posting mentions: "Benefits offered included a qualified retirement program [401(k) plan]; paid vacation and holidays; paid leaves; and, health benefits including medical, prescription drug, dental, and vision coverage in accordance with the terms and conditions of the applicable plans." Also "short-term incentive bonus opportunity; eligibility to participate in our equity-based long-term incentive program." Also maybe other benefits? That's enough. Pay: The posting includes: "The annual base pay for this position ranges from $153,018.40 - $200,836.65 USD. Base pay offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience." Schedule: Hybrid policy: "This role is based in Boston, MA, with employees expected to work from the office three days per week, creating opportunities for teams to connect, collaborate, and solve complex challenges together." Also "may require up to 20% travel." That's schedule info. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include headings with empty content. Ensure each section has content. Now we need to strip boilerplate: Remove "WHY JOIN US?" heading? We'll incorporate its content into About the role. Also remove "Hybrid Policy" heading but keep its content under Schedule. Remove "Introduction" heading but keep content under About the role. Remove "About the Role" heading but keep its content under About the role (maybe we keep heading as About the role). Remove "Key Responsibilities" heading but keep content under Responsibilities. Remove "AI-Ready Business Partner Responsibilities" heading but keep content under Responsibilities. Remove "Essential Qualifications" heading but keep content under Requirements. Remove "Preferred Qualifications" heading but keep content under Qualifications. Remove "SO, WHAT’S NEXT?" etc (application instructions) - remove. Remove "Where can I find out more?" etc - remove. Remove EEO statements etc - remove. Remove "Date Posted" and "Closing Date" maybe? Those are minor metadata; we can drop them per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can drop Date Posted and Closing Date. Now we need to format. We'll produce something like:

  About the role

  At Alexion, a division of AstraZeneca, we are driven by a shared purpose to transform the lives of people affected by rare and devastating diseases. By combining deep expertise in rare disease with the scale, science, and innovation of AstraZeneca, we are working to deliver meaningful advances for patients and families with significant unmet needs. Join us at an exciting time as we continue to evolve how technology, data, digital, and AI support our Commercial organization. You will have the opportunity to work closely with business and technology leaders, shape solutions that enable new product launches and commercial transformation, and help turn emerging technologies into measurable outcomes for patients and the business. Our culture is built on collaboration, innovation, and continuous learning. We encourage our people to challenge convention, explore new possibilities, and bring forward ideas that can improve how we work and how we serve patients. As part of Alexion, you will have the opportunity to make an impact in a highly specialized area of healthcare while benefiting from the capabilities and global reach of AstraZeneca.

  As Director, RDU IT Business Partner, US Commercial, you will serve as a senior business-facing technology partner, shaping and delivering technology, data, digital, and AI-enabled capabilities that support commercial priorities, launch readiness, commercial transformation, and improved patient outcomes. This position is based in Boston, MA, and may require up to 20% travel.

  The Director, RDU IT Business Partner, US Commercial will serve as a senior IT Business Partner for the US Commercial organization, with a defined portfolio spanning Commercial business functions, Commercial Training, Rare Disease Therapy Area teams, launch, Finance, Commercial Operations, Market Access, and enabling functions and AI-enabled transformation. This role will build trusted relationships with senior Commercial stakeholders, shape the multi-year technology and AI roadmap for assigned business areas, lead demand prioritization, steward portfolio health, and partner across IT, Digital, Data, AI, Architecture, Cybersecurity, Privacy, Compliance, Finance, Service Delivery, and external partners to deliver measurable business outcomes.

  But we need to avoid duplication: The "About the Role" paragraph repeats some of the earlier content. We'll combine but ensure we keep all substantive info. Might be okay to have some repetition but we should try not to repeat same sentences. However instruction says preserve ALL substantive information; duplication is okay if it's in original. But we can try to avoid obvious duplication by merging. Let's extract unique sentences: From WHY JOIN US?: - At Alexion, a division of AstraZeneca, we are driven by a shared purpose to transform the lives of people affected by rare and devastating diseases. - By combining deep expertise in rare disease with the scale, science, and innovation of AstraZeneca, we are working to deliver meaningful advances for patients and families with significant unmet needs. - Join us at an exciting time as we continue to evolve how technology, data, digital, and AI support our Commercial organization. - You will have the opportunity to work closely with business and technology leaders, shape solutions that enable new product launches and commercial transformation, and help turn emerging technologies into measurable outcomes for patients and the business. - Our culture is built on collaboration, innovation, and continuous learning. - We encourage our people to challenge convention, explore new possibilities, and bring forward ideas that can improve how we work and how we serve patients. - As part of Alexion, you will have the opportunity to make an impact in a highly specialized area of healthcare while benefiting from the capabilities and global reach of AstraZeneca. From Introduction: - As Director, RDU IT Business Partner, US Commercial, you will serve as a senior business-facing technology partner, shaping and delivering technology, data, digital, and AI-enabled capabilities that support commercial priorities, launch readiness, commercial transformation, and improved patient outcomes. - This position is based in Boston, MA, and may require up to 20% travel. From About the Role: - The Director, RDU IT Business Partner, US Commercial will serve as a senior IT Business Partner for the US Commercial organization, with a defined portfolio spanning Commercial business functions, Commercial Training, Rare Disease Therapy Area teams, launch, Finance, Commercial Operations, Market Access, and enabling functions and AI-enabled transformation. - This role will build trusted relationships with senior Commercial stakeholders, shape the multi-year technology and AI roadmap for assigned business areas, lead demand prioritization, steward portfolio health, and partner across IT, Digital, Data, AI, Architecture, Cybersecurity, Privacy, Compliance, Finance, Service Delivery, and external partners to deliver measurable business outcomes. We can combine these into About the role section, maybe as multiple

  paragraphs. Now Responsibilities: Need to combine Key Responsibilities and AI-Ready Business Partner Responsibilities. Key Responsibilities bullet points (as per text): - Serve as a senior IT Business Partner and trusted advisor for assigned US Commercial business areas, aligning