Senior Director, People Strategy & Transformation

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: 1. Company Description / About AbbVie - this is prose, should be a

or maybe a section with heading "About the company" but the rules say use

for section headings like "About the role". The company description is not a role description, but it's part of the posting. The rules say "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention "About the company". However, the company description is substantive content. I could include it as a section with heading "About AbbVie" or "Company Description". But the rules say "include a section ONLY when the posting has real, specific content for it". The company description is real content. I'll include it as a section with

About AbbVie

and then

for the prose. 2. Job Description / Position Summary - this is prose about the role. Could be "About the role" heading. 3. Key Responsibilities - this has multiple sub-sections: People Strategy, People Branding & Storytelling, HR Strategy & Annual Prioritization, Planning & Budgeting, HR Technology Strategy, Chief of Staff & Integration, HR Global Portfolio. Each is a list of bullet points. The rules say use

• for any list of duties/requirements/benefits. So I should create a "Responsibilities" section with subsections? The rules say use

  for section headings. Should I make each sub-responsibility a separate

  ? That might be too many headings. The example headings include "Responsibilities" as a section. I think I should have one

  Responsibilities

  and then within that, maybe use

  for each sub-area? But the rules only mention

  for section headings. It 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, maybe I should treat each sub-responsibility as a separate list under the main Responsibilities heading, but with bold labels? However, the rules say "use

  • for any list of duties/requirements/benefits". The responsibilities are lists of bullet points. I could create a single
    with all bullet points, but they are grouped by theme. The posting has clear subheadings. I think it's acceptable to use

    for sub-sections within Responsibilities, but the instruction says "use

    for section headings". It doesn't say we cannot use

    . But to be safe, I'll keep only

    for top-level sections. I'll create a "Responsibilities" section and then for each sub-area, I'll create a

    with a preceding

    People Strategy

    or something. But that might not be semantic. Alternatively, I could make each sub-area a separate

    ? That would be many headings: People Strategy, People Branding & Storytelling, etc. That might be okay because they are distinct responsibility areas. The rules say "Prefer a few substantive sections over many thin ones." But each of these has multiple bullet points, so they are substantive. However, the example headings don't include such granular headings. The example includes "Responsibilities" as a single heading. I think the best is to have one "Responsibilities" heading and then include all bullet points in a single list, but grouped with bold labels. But the rules say "use

    • for any list of duties/requirements/benefits". It doesn't say we cannot have multiple lists. I'll do:

      Responsibilities

      then for each sub-area, a

      People Strategy

      followed by
      • ... But that's not a list of duties, it's a list of sub-areas. Actually each sub-area has its own bullet points. I'll create a
        for each sub-area, with a heading-like label. Since we cannot use

        ? The instruction doesn't forbid it, but says "use

        for section headings". It doesn't say "only use

        ". I think using

        for sub-sections is fine. But to be safe, I'll use

        for each major responsibility area? That would be 7 headings. That might be too many. Let's see the posting: "Key Responsibilities" then subheadings. I'll treat "Key Responsibilities" as the section heading, and then each subheading as a

        ? But the output should be HTML fragment, no restrictions on heading levels. I'll use

        for the main sections: "About AbbVie", "About the role", "Responsibilities", "Qualifications", "Competencies", "Why People Experience at AbbVie", "Pay and Benefits". The "Additional Information" includes pay disclosure and benefits. That should be a "Pay" and "Benefits" section? The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states: "The compensation range described below is the range of possible base pay compensation..." but it doesn't give a specific range. It says "The compensation range described below is the range of possible base pay compensation that the Company believes in good faith it will pay for this role at the time of this posting based on the job grade for this position." But no actual numbers. It also says "We offer a comprehensive package of benefits including paid time off (vacation, holidays, sick), medical/dental/vision insurance and 401(k) to eligible employees. This job is eligible to participate in our long-term incentive programs." That is specific benefits content. So we should include a Benefits section. For Pay, since no specific range is given (just a statement that range exists but not disclosed), we should not create a Pay section because it's filler. The rules: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The pay disclosure is essentially "range not specified". So we should not include a Pay section. But we can include Benefits section with the listed benefits. Also "Qualifications" section has Required and Preferred. That's two lists. We'll make a "Qualifications" heading with two sub-lists. "Competencies" is a list of competencies. "Why People Experience At AbbVie" is prose. "Additional Information" includes pay disclosure and EEO boilerplate. We should remove EEO boilerplate (equal opportunity employer, etc.) as per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we drop the EEO lines. The pay disclosure is not boilerplate but it's not specific. We'll include the benefits part in Benefits section. Now, structure: - About AbbVie (company description) - About the role (position summary) - Responsibilities (with subsections) - Qualifications (Required and Preferred) - Competencies - Why People Experience at AbbVie - Benefits We need to ensure we don't repeat job title as heading. The job title is "Vice President, People Strategy & Transformation" (implied). The page already shows it, so we don't include. Now, write HTML. Let's start. First, About AbbVie: prose.

        About AbbVie

        AbbVie's mission is to discover and deliver innovative medicines and solutions that solve serious health issues today and address the medical challenges of tomorrow. We strive to have a remarkable impact on people's lives across several key therapeutic areas including immunology, oncology and neuroscience - and products and services in our Allergan Aesthetics portfolio. For more information about AbbVie, please visit us at www.abbvie.com. Follow @abbvie on LinkedIn, Facebook, Instagram, X and YouTube.

        About the role:

        About the role

        The role to lead the People Strategy & Transformation group is a critical leadership role within AbbVie's People Experience organization, serving as the primary architect of transformational change across the HR ecosystem. This leader is the strategic unlock to delivering on the broad, ambitious vision of the People Experience team — bringing together people strategy, HR planning and prioritization, technology strategy, experience story telling and communications, and portfolio management under a single, integrated leadership mandate. This role is for an enterprise-scale strategist and systems thinker who understands how to connect vision to execution, drive structural and cultural change across a complex global organization, and leverage technology and storytelling to reimagine how HR delivers value. This role will lead a team of highly specialized functions and will serve as a driving force behind AbbVie's next generation of HR transformation.

        Responsibilities: We'll create a section with subsections. I'll use

        Responsibilities

        then for each sub-area, a

        ? But the instruction says use

        for section headings. It doesn't say we can't use

        . I'll use

        for sub-sections to keep hierarchy. But the output is a fragment, so it's okay. However, the instruction might expect only

        headings. To be safe, I'll make each sub-area a separate

        ? That would be many

        s. The example says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the top-level sections. So "Responsibilities" is one section. The sub-areas are part of that section. I'll keep them as labeled lists within the Responsibilities section. I'll do:

        Responsibilities

        People Strategy

        • Define and champion an enterprise-wide people strategy that aligns with AbbVie's business priorities, workforce needs, and the long-term vision of the People Experience team.
        • Translate complex workforce trends, competitive intelligence, and organizational data into clear strategic direction for the PE organization, while supporting socialization with HR's senior stakeholders.
        • Partner with the VP of People Experience and PE Leadership Team to set the multi-year strategic agenda and ensure coherent prioritization across functions.
        • Serve as a forward-looking thought leader, anticipating shifts in the external talent and HR landscape and positioning AbbVie to stay ahead.

        People Branding & Storytelling

        • Lead AbbVie's People Branding strategy, shaping how the company's employee value proposition (EVP) and talent brand are articulated, activated, and experienced globally.
        • Build a compelling storytelling capability within the PE organization — translating the impact of People programs and initiatives into narratives that resonate with employees, candidates, leaders, and external stakeholders.
        • Partner with Corporate Communications, Marketing, and Business HR to ensure consistency and authenticity of AbbVie's people brand across all touchpoints.
        • Champion the PE team's own brand and visibility — elevating the strategic contribution of the People Experience function across the enterprise.
        ... and so on for each sub-area. That seems acceptable. Qualifications: Required and Preferred.

        Qualifications

        Required

        • Bachelor's degree in Human Resources, Business Administration, Organizational Development, or a related field.
        • Progressive HR leadership experience, with significant scope across