GBPO, Core HR Processes

We need to output HTML fragment with sections: headings

for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: - "YOUR ROLE" description: could be "About the role". We'll put that as

About the role

with paragraphs. - Responsibilities: bullet list. - Requirements? There's "YOUR BACKGROUND" which is qualifications/requirements. Also "Qualifications" section later. So we need to decide: maybe combine "Requirements" and "Qualifications"? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if posting has real specific content. We have content for About the role (YOUR ROLE). Responsibilities (list). Requirements? The "YOUR BACKGROUND" could be considered Requirements. Also there is a separate "Qualifications" heading later with bullet list. So we can have both Requirements and Qualifications sections. Skills? Not explicitly listed; maybe we can infer from qualifications but better not to create a Skills section unless explicit. So we skip Skills. Benefits: there is "Your Benefits" list. So include Benefits. Pay: not mentioned. So skip Pay. Schedule: not mentioned. Skip Schedule. Also we may include a short paragraph for metadata like location, reports to etc. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a

for "Reports to Global Head of HR Operations Troy, Michigan". Also maybe include "Global Business Process Owner, Core HR Processes (People Operations Transformation Leader)" as the job title but we should not repeat as heading; we can include it in a

maybe. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to remove the "APPLY TODAY!" paragraph, the "Versigent spun out..." paragraph, the Privacy Notice, EEO statement. Also remove "Why join us?" maybe? It's not boilerplate but it's promotional; but it's substantive? It's about why join us; could be considered part of Benefits? But it's not a specific benefit; it's more marketing. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why join us?" is not explicitly listed to remove, but it's more of a marketing blurb. However we might keep it as part of About the role? But we already have About the role; we could incorporate that as a paragraph under About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "Why join us?" is substantive but maybe not required to be a separate section; we could include it as a paragraph under About the role or as a separate section like "Why Join Us?" but that's not in the allowed headings list. Since we only allowed those headings, we should not create a heading for it. We could incorporate its content into a paragraph under About the role or Benefits? It's about growth, purpose, impact, support. Could be considered part of Benefits? Not exactly. Safer to include as a paragraph under About the role (since it's about the role). But we must not lose that info. We'll add a paragraph after the role description. Now we need to format lists: Use

• for any list of duties/requirements/benefits. Let's extract content. About the role: The paragraph starting "YOUR ROLE" includes sentences: "You own the global standard for the core employee lifecycle, from hire to retire. You design it end to end with the countries, in the plant and on the line, and you make sure it runs one streamlined way in Workday across every site." That's the core. We'll keep that as a paragraph. Then we could add the "Why join us?" paragraph after that. Responsibilities: The bullet list after "Responsibilities". Let's extract each line: - Field design: value stream mapping the real process in-country, then connecting it to the global standard so each site runs one streamlined process, not two stitched together - Functional design and policy for the lifecycle, built into Workday as the system of record - The specifics the HRIS team needs: clear, documented requirements for what to change in the system to make the process work in each country - Standard operating procedures, controls, and the governance that keeps local variation to what the law or a clear business case requires - The functional integrity of the organizational structure in the system of record - Process performance: the KPIs that show the lifecycle is adopted, clean, and improving - Training and adoption on the standard - You will design in the room with the country, in the plant and on the line, not on paper from a desk - You will value stream map the real local process, then connect it to the global standard so the site ends up with one better process, not a global one bolted on top - You will come back with specifics: what the HRIS team must change to make the process run in that country - You will influence the people who run the process every day without holding their reporting line - You will judge yourself by whether the lifecycle runs clean, the same way everywhere, and better for the site than what it replaced We need to preserve all. We'll put each as
• . Requirements: The "YOUR BACKGROUND" bullet list: - Hands-on Lean process design: you value stream map the real process where the work happens, on the line, not on paper from a desk - Workshop facilitation in the plant and in the country: you sit with local teams, design in the room, and leave with an agreed process and a specific change list - Deep command of the hire-to-retire lifecycle and how it is built in a modern HR system - A record of standardizing processes across many countries, ideally including a large, high-volume or manufacturing workforce - Authority through influence: you set the standard and hold it without owning the people who run it day to day - A builder who is steady in ambiguity, credible from the plant floor to the top of the house, and comfortable on a plane across cultures and time zones We'll put as
  • . Qualifications: The later "Qualifications" bullet list: - About 10+ years in HR operations or core HR process, several of them setting and holding a global standard. - Consulting or in-house process-design background, provided it is floor-tested: real value stream mapping in the operation, not desk theory - Carve-out, spin-off, or tenant-separation experience - Workday preferred, especially the core HCM lifecycle - A formal Lean or Six Sigma credential preferred - English language fluency. Bilingual skills, a plus - Local resident of Metro Detroit with ability to work on site - Valid U.S. Passport with ability to travel globally (up to 70%) Note: The line "English language fluency. Bilingual skills, a plus" is two sentences; we keep as is. We'll put as
    • . Benefits: The list under "Your Benefits": - Private health care effective day 1 of employment - Life and accident insurance - Paid Time Off (Holidays, Vacation, Designated time off, Parental leave) - Relocation assistance may be available - Learning and development opportunities - Discount programs with various manufacturers and retailers - Recognition for innovation and excellence - Opportunities to give back to the community - Tuition Reimbursement - Adoption Assistance - Fertility Coverage We'll put as
      • . We also need to include the short metadata paragraph: maybe combine "Reports to Global Head of HR Operations Troy, Michigan" and the job title line? The job title is already known; we can include a paragraph: "

        Reports to Global Head of HR Operations. Based in Troy, Michigan.

        " Also maybe include "Global Business Process Owner, Core HR Processes (People Operations Transformation Leader)" as a paragraph? But we should not repeat the job title as heading; we can include it as a

        before the sections. We must not include any boilerplate like "Versigent spun out..." etc. Now produce HTML fragment: start with maybe a

        for job title and reports, then

        About the role

        with paragraphs (maybe two paragraphs: role description and why join us). Then

        Responsibilities

        with
        . Then

        Requirements

        with
        . Then

        Qualifications

        with
        . Then

        Benefits

        with
        . No other sections. Check that we didn't miss any substantive info: The "DELIVERABLES IN YEAR ONE" section is also substantive. It lists deliverables. Should we include that? It's not covered by existing headings; maybe could be part of Responsibilities or a separate section like "Deliverables". But allowed headings list does not include Deliverables. However we could incorporate it into Responsibilities or About the role? The instruction: "Prefer a few substantive sections over many thin ones." We could add a section for Deliverables if we treat it as part of Responsibilities? But it's distinct. However we are limited to the headings list; we cannot create a heading not in that list unless we think it's necessary. The list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No Deliverables. So we must fit deliverables somewhere else, maybe under Responsibilities as additional bullet points? But they are not responsibilities; they are outcomes. Could be considered part of "About the role" or "Requirements"? Might be okay to add them as a paragraph under About the role? But that would be mixing. However we must preserve all substantive information; we cannot drop them. So we need to include them somewhere. Perhaps we can add a section "Deliverables" as an

        even though not in the list? The instruction says: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list? It says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings when appropriate, but we could also use other headings if needed? However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings. The examples are just typical sections. So we could add a

        Deliverables

        if we have content. That seems reasonable. The instruction didn't say we cannot use other headings; just gave examples. So we can add Deliverables. Similarly, we might add a section "Why Join Us?" but we already incorporated that into About the role. Thus we will include Deliverables section. Let's extract Deliverables: - A single, documented hire-to-retire standard adopted across the sites in scope, designed with the countries, not handed to them - Structural and organizational changes built and sustained cleanly in the system of record - Clean, repeatable transactions, with fewer exceptions and workarounds - Country variants reduced to those the law or a clear business case requires - A first set of process KPIs in use, so performance is measured, not asserted We'll put as
        • . Now we need to ensure we didn't include any boilerplate like "Versigent spun out..." etc. We removed