Associate Director, Commercial Data Science

We need to output HTML fragment with sections: About the role? Actually the posting includes mission description, then "Associate Director, Commercial Data Science" then "What you will do" etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Apply now..." etc. Also remove "In any materials you may redact..." etc. Also remove "Application deadline..." etc. Also remove "Sponsorship..." etc. Also remove "Amgen is an Equal Opportunity employer..." etc. We need to include sections only when posting has real specific content. So we need to extract content for each. Let's parse the posting. First paragraph: "Join Amgens Mission of Serving Patients At Amgen, if you feel like youre part of something bigger, its because you are. Our shared missionto serve patients living with serious illnessesdrives all that we do. Since 1980, weve helped pioneer the world of biotech in our fight against the worlds toughest diseases. With our focus on four therapeutic areas Oncology, Inflammation, General Medicine, and Rare Disease we reach millions of patients each year. Amgen is advancing a broad and deep pipeline of medicines to treat cancer, heart disease, inflammatory conditions, rare diseases, and obesity and obesity-related conditions. As a member of the Amgen team, youll help make a lasting impact on the lives of patients as we research, manufacture, and deliver innovative medicines to help people live longer, fuller happier lives. Our award-winning culture is collaborative, innovative, and science based. If you have a passion for challenges and the opportunities that lay within them, youll thrive as part of the Amgen team. Join us and transform the lives of patients while transforming your career." That's about the company/mission. Could be "About the role"? Actually "About the role" maybe about the position. But we have mission description; could be placed under "About the role" or maybe we treat as "About the role". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have "What you will do" which is responsibilities. So we can put that under

Responsibilities

. We have "What we expect of you" which includes basic qualifications, preferred qualifications. That could be split into Requirements and Qualifications and Skills. The posting lists Basic Qualifications (education/experience) and Preferred Qualifications (leadership, AI & Analytics Strategy, Commercial Business Acumen, Technical Leadership, Communication). Those could be considered Qualifications and Skills. We need to decide. We have "What You Can Expect Of Us" which includes benefits, salary range, total rewards plan. So we can put Benefits and Pay sections. We have "Flexible Commuter role to Thousand Oaks, CA office. You will work on-site a minimum of 2 days a week." That's schedule info. So we can put Schedule. We also have location maybe not needed. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. So we need to include the mission description maybe under About the role. Let's extract each piece. About the role: Could be the introductory paragraph about Amgen mission and culture. We'll put that as

About the role

with

containing that text. Responsibilities: The "What you will do" section includes bullet-like paragraphs. We need to convert to

• for any list of duties/requirements/benefits. The responsibilities are described in paragraphs with bold headings? Actually they have headings like "Strategic Leadership", "AI Product & Portfolio Leadership", etc. Each heading followed by sentences. We could treat each bullet as a list item. The instruction: Use
  • for any list of duties/requirements/benefits. So we should convert the responsibilities into a list. We'll extract each duty. From "What you will do": - Strategic Leadership: Execute on the Commercial AI and Advanced Analytics roadmap aligned with brand and enterprise priorities. Partner with Commercial leadership to identify high-value opportunities where AI and advanced analytics can accelerate growth, improve customer engagement, and enhance decision making. Prioritize the Commercial AI/ML portfolio based on business value, strategic alignment, organizational readiness, and expected return on investment. Translate evolving business challenges into scalable capabilities and data products. - AI Product & Portfolio Leadership: Lead a portfolio of AI, Machine Learning, Generative AI, and advanced analytics initiatives from business strategy through deployment and organizational adoption. Provide technical oversight for predictive modeling, customer targeting, next-best-action, causal inference, optimization, Generative AI, and other advanced analytical capabilities. Guide technical teams in the development of production-grade AI products while ensuring scalability, maintainability, and business impact. Partner with Data Engineering, Digital Technology, and external vendors to operationalize enterprise AI capabilities. - Business Partnership & Executive Influence: Build trusted partnerships with Brand, Marketing, Sales, Medical, Market Access, and Digital leaders. Communicate complex analytical concepts to executive audiences in a clear, compelling, and business-focused manner. Influence investment decisions by developing business cases, success metrics, and ROI assessments for AI initiatives. - Organizational Leadership: Lead, coach, and develop a high-performing team of data scientists while fostering a culture of innovation, collaboration, continuous learning, and business partnership. Establish technical standards, best practices, and governance for Commercial Data Science. Champion responsible AI principles, model governance, and ethical AI practices across Commercial. Build organizational capability by mentoring future leaders and developing technical talent. - Innovation & Thought Leadership: Continuously evaluate emerging AI technologies, industry trends, and external innovations to identify opportunities that create competitive advantage. Represent Commercial Data Science across enterprise initiatives and external collaborations. Foster experimentation while ensuring successful transition from proof-of-concept to enterprise-scale deployment. We'll put each as
  • . Requirements: The posting has "What we expect of you" includes Basic Qualifications and also "In addition to meeting at least one of the above requirements, you must have a minimum of 3 years experience directly managing people and/or leadership experience leading teams, projects, programs, or directing the allocation or resources." That's a requirement. Also maybe "Preferred Qualifications" are not requirements but preferred. So Requirements section could contain the basic qualifications and the managerial experience requirement. We need to decide if we separate Requirements and Qualifications. The instruction lists both as possible headings. We could put Basic Qualifications under Requirements, and Preferred Qualifications under Qualifications or Skills. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we have to follow instruction: Use headings only when posting has real specific content. We have content for both. Let's define: - Requirements: Basic Qualifications (education/experience combinations) plus the 3 years managerial experience requirement. - Qualifications: Preferred Qualifications (leadership, AI & Analytics Strategy, Commercial Business Acumen, Technical Leadership, Communication). Could be considered qualifications. - Skills: maybe we could extract specific skills from preferred qualifications (like Python, R, etc.) but they are already in preferred qualifications. Could put under Skills. But we might end up with many thin sections. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section called "Requirements" that includes both basic and preferred. Or we could have "Requirements" for basic qualifications and "Qualifications" for preferred. That's two sections, still okay. We also have Skills: maybe we can extract technical skills like Python, R, Scala, Java, etc. But they are within preferred qualifications. Could put under Skills. But we need to avoid duplication. Let's think: The posting includes "Preferred Qualifications" with subcategories: Leadership, AI & Analytics Strategy, Commercial Business Acumen, Technical Leadership, Communication. Each subcategory has bullet points. That's a lot of content; could be its own section "Qualifications". Then we could have "Skills" maybe not needed if we already covered under Qualifications. But we could still have Skills for technical skills like programming languages, MLOps, etc. However that would be thin. Better to have: About the role, Responsibilities, Requirements (basic qualifications + managerial experience), Qualifications (preferred qualifications), Benefits, Pay, Schedule. That's 6 sections. Might be okay. Now Benefits: From "What You Can Expect Of Us": "As we work to develop treatments that take care of others, we also work to care for your professional and personal growth and well-being. From our competitive benefits to our collaborative culture, well support your journey every step of the way." Then later: "In Addition To The Base Salary, Amgen Offers a Total Rewards Plan, Based On Eligibility, Comprising Of Health And Welfare Plans For Staff And Eligible Dependents, Financial Plans With Opportunities To Save Towards Retirement Or Other Goals, Work/life Balance, And Career Development Opportunities That May Include A comprehensive employee benefits package, including a Retirement and Savings Plan with generous company contributions, group medical, dental and vision coverage, life and disability insurance, and flexible spending accountsA discretionary annual bonus program, or for field sales representatives, a sales-based incentive planStock-based long-term incentivesAward-winning time-off plansFlexible work models where possible. Refer to the Work Location Type in the job posting to see if this applies." We need to preserve all substantive info. So we need to list benefits: health and welfare plans, financial plans (retirement savings), work/life balance, career development opportunities, comprehensive employee benefits package (Retirement and Savings Plan with generous company contributions, group medical, dental and vision coverage, life and disability insurance, flexible spending accounts), discretionary annual bonus program, stock-based long-term incentives, award-winning time-off plans, flexible work models. We should format as
    • for benefits. Pay: The posting says: "The expected annual salary range for this role in the U.S. (excluding Puerto Rico) is posted. Actual salary will vary based on several factors including but not limited to, relevant skills, experience, and qualifications." It does not give actual numbers. It says "is posted" but we don't have the range. Since we don't have the actual range, we cannot include Pay section because we would be inventing or summarizing away detail? The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states that the expected annual salary range is posted, but does not give the range in the text we have. Since we don't have the range, we cannot create a Pay section with actual numbers. However we could include a note that the salary range is posted (but not given). That might be considered filler? It says "The expected annual salary range for this role in the U.S. (excluding Puerto Rico) is posted." That's a statement that the range is posted elsewhere. It's not a specific number. Should we include Pay section? The instruction says never create Pay section unless posting actually states them. It does state that the salary range is posted, but not the actual range. This is ambiguous. I'd lean to not include Pay section because we don't have the actual range; including a vague statement might be considered filler. However we could include a

      stating that the expected annual salary range is posted (as per the posting). But that is not a specific number; it's still info. The instruction says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "is posted" is not exactly those placeholders but it's still not giving the range. Might be considered placeholder. Safer to omit Pay section