Staff IT Product Lead - Enterprise Platforms-Discovery and Translational Medicine

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate: EEO, legal, accommodation email? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the accommodation email line? It's part of application instructions? It says "If you have a disability and need an accommodation in relation to the recruiting process, please email us at: ApplicantAccommodations@exelixis.com." That's an application instruction/accommodation, so remove. Also remove disclaimer about job description, equal opportunity employer, etc. Also remove "Working Conditions" maybe not a required heading; but we can include if content present? It's not one of the allowed headings; we should not create extra headings. So we should either omit or incorporate into existing sections? Probably omit as not requested heading. Also remove "Supervisory Responsibilities" etc. We need to preserve substantive info: Summary/Job Purpose, Essential Duties/Responsibilities (with subparts), Education/Experience/Knowledge/Skills & Abilities (including education, experience, required knowledge, skills, abilities), Travel Requirements, Environmental Requirements, Compensation (Pay), Benefits, maybe Schedule? Not present. No schedule info. So we should not create Schedule section. We need sections: About the role (maybe from Summary/Job Purpose). Responsibilities (Essential Duties/Responsibilities). Requirements (maybe Education/Experience). Qualifications (maybe same as Requirements? But we need to decide). The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections; we should not repeat similar content. We need to map content. We have: Summary/Job Purpose -> About the role. Essential Duties/Responsibilities -> Responsibilities. Education/Experience/Knowledge/Skills & Abilities -> could be split into Requirements (education/experience), Qualifications (maybe knowledge/skills), Skills (maybe specific skills). But we have overlapping. We need to avoid duplication. Perhaps we can have Requirements covering education and experience; Qualifications covering required knowledge, skills and abilities; Skills maybe not needed if covered. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we could combine into Requirements and Qualifications and Skills as needed. Let's extract: Education: Bachelor’s degree in related discipline and 6 years of related experience; or Master's degree in mathematics or statistics or engineering and 5 years of related experience. Equivalent combination. Experience: Minimum of 4 years of experience supporting enterprise-wide platforms. Minimum of 6+ years of progressive experience in IT, focused on digital workplace or product management. Proven experience in leading product development teams in an agile/product-centric operating model is essential. Demonstrated success in defining and delivering complex digital products that drive significant business value. Experience with one of the mentioned specific technologies or platforms as relevant to the specific role, [e.g., SaaS platforms (Veeva, Microsoft) or cloud solutions (AWS, Azure). Experience with regulatory frameworks and compliance. Experience with enterprise platforms and technologies relevant to the role, e.g., SaaS platforms (Revvity Signals, Schrodinger LiveDesign, Benchling) or cloud solutions (AWS, Azure). Required Knowledge, Skills and Abilities: Solid strategic thinking and problem-solving abilities, with a data-driven approach to decision-making. Strong communication, presentation, and interpersonal skills, with the ability to influence and collaborate effectively at all levels of the organization. Understanding of product management methodologies (e.g., Agile, Scrum, Kanban) and product lifecycle management. Strong technical acumen with the ability to understand complex IT architectures and development processes. Ability to manage multiple priorities in a fast-paced, dynamic environment. Travel Requirements: 5% Occasional travel may be required to other company sites, conferences, or vendor locations. Environmental Requirements: Primarily working indoors in an office environment. Compensation: base pay range $148,000 - $209,500 annually. Base pay may take into account geographic region, etc. Also mention total rewards: 401k, medical, dental, vision, life/disability, FSA, discretionary annual bonus, opportunity to purchase company stock, long-term incentives, 15 accrued vacation days first year, 17 paid holidays including company-wide winter shutdown in December, up to 10 sick days. Benefits: that list. We should not include "Working Conditions" etc. We need to output HTML with headings

and content

or

• . For lists, use
  • . For prose,

    . We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep details like specific numbers, percentages, etc. We must not include headings with filler like "commensurate with experience". Not present. We need to decide sections: - About the role: from Summary/Job Purpose paragraph(s). Could be multiple paragraphs; we can combine into one

    or multiple

    . Probably one

    . - Responsibilities: list of duties. The responsibilities have subheadings: Product Strategy & Roadmap, Product Development & Delivery, Stakeholder Management & Cross-Functional Collaboration, Operational Excellence, Quality & Compliance. We could make each as a

    ? But only allowed headings are

    for section headings. We could keep responsibilities as a

    with items that include the subheadings as bold text? But we must not invent headings. Could we use

    for each subheading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

    for section headings. It might be okay to use

    for main sections only; subheadings could be or

    . Safer to not add extra headings; just list responsibilities as

    • each duty. We can include the subheading text as part of the li. Thus responsibilities list items: each bullet can contain the subheading and details. We need to preserve all details: e.g., "Assist in executing the vision, strategy, and roadmap for digital products within Enterprise Platforms job family (e.g., Communication, Content Management, Collaboration, Enterprise Productivity, Data and Analytics etc.)." etc. We'll create
      with
      • for each bullet. Similarly for Education/Experience/Knowledge/Skills & Abilities: we can split into Requirements (education/experience) and Qualifications (knowledge, skills, abilities). Or combine into Requirements and Qualifications. Let's define: - Requirements: Education and Experience (including minimum years, degrees, equivalent combo). We'll list as
        . - Qualifications: Required Knowledge, Skills and Abilities (strategic thinking, communication, product mgmt methodologies, technical acumen, manage multiple priorities). Also maybe include "Proven experience in leading product development teams..." but that's experience; we already covered. But we also have "Experience with one of the mentioned specific technologies..." etc. That's also experience. Could be part of Requirements. We'll put all experience bullets under Requirements. Qualifications: the Required Knowledge, Skills and Abilities list. Skills: maybe not needed; but we could have Skills section for specific technical skills (SaaS platforms, cloud solutions, regulatory frameworks). However those are already in experience. To avoid thin sections, we could omit Skills. Benefits: list of benefits. Pay: base pay range and note about geographic region. Schedule: not present, so omit. Travel Requirements: we could include under a section? Not in allowed headings list but we could incorporate into Requirements or a separate section? The allowed headings include Schedule but not Travel. However we could put Travel under Requirements? Or maybe we create a section "Travel" but not allowed heading. Better to incorporate into Requirements or maybe a separate

        under Requirements? The instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exhaustive; we could still use other headings? It says use

        for section headings (e.g. ...). It implies those are the allowed headings; we should stick to those. So we should not create a Travel heading. We can include travel info in Responsibilities? Not appropriate. Could include in Requirements as a note? Or maybe we can put it under Requirements as a

        . But it's not really a requirement; it's a travel requirement. Could be part of Responsibilities? Not really. Perhaps we can include it under Requirements as a bullet: "Travel: 5% occasional travel may be required..." That seems okay. Environmental Requirements: could also be included under Requirements as a bullet. Thus Requirements section will contain education, experience, travel, environmental. Now Benefits: we need to list all benefits: 401k plan with generous company contributions, group medical, dental and vision coverage, life and disability insurance, flexible spending accounts, discretionary annual bonus program, opportunity to purchase company stock, receive long-term incentives, 15 accrued vacation days in first year, 17 paid holidays including a company-wide winter shutdown in December, up to 10 sick days throughout the calendar year. We should keep as

        . Pay: base pay range $148,000 - $209,500 annually. Also note that base pay may take into account geographic region, candidate's geographic region, job-related knowledge, skills, experience and internal equity, among other factors. We'll include that as prose. Now we need to ensure we don't repeat info. Let's craft HTML. Start with

        About the role

        then

        with summary. Summary/Job Purpose text: "The Staff IT Product Lead – Enterprise Platforms plays a critical role in supporting digital workplace solutions that drive enterprise productivity, collaboration, communication and content management. This role supports execution of platform capabilities that enhance user experience, operational efficiency, and cross-functional integration. As an individual contributor, the Staff IT Product Lead partners closely with business and IT stakeholders to define scalable, secure, and user-centric solutions aligned with Exelixis' digital workplace vision. This role requires technical expertise, product thinking, and the ability to work collaboratively with cross-functional teams." We'll put that as one

        . Next Responsibilities:

        Responsibilities

        then
        with
        • items. We need to break down the responsibilities into items. From the text: Product Strategy & Roadmap (Product-Centric Focus) - Assist in executing the vision, strategy, and roadmap for digital products within Enterprise Platforms job family (e.g., Communication, Content Management, Collaboration, Enterprise Productivity, Data and Analytics etc.). - Work with senior product leads and business stakeholders to gather user needs and translate them into actionable product requirements and user stories. - Participate in market research and technology assessments to support product planning and identify areas for innovation. - Help evaluate and prioritize product initiatives based on business impact, technical feasibility, and compliance considerations. - Collaborate with architecture and engineering teams to support the design and development of secure, scalable digital solutions. Product Development & Delivery (Agile/Product Team Support) - Contribute to product development activities across the lifecycle—from ideation to launch and post-launch optimization—using Agile methodologies (e.g., Scrum, Kanban). - Assist in writing user stories, defining acceptance criteria, and refining product specifications in alignment with business goals. - Work closely with engineering, architecture, and QA teams to support timely delivery of high-quality digital applications. - Help coordinate with external vendors and service providers to ensure alignment with product delivery timelines