Register your interest - Human Resources (HR) Graduate Scheme (UFLP) - UK & Ireland
targetjobs UK · Hull, TX · 1 mo ago
OTHRFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive information.
We need to parse the posting: It's about Unilever Futures Programme HR. Content includes:
- Intro about Unilever (company description) maybe "About the role"? Actually "About the role" could be description of role and program.
- "What do we look for?" - list of attributes.
- "The role: Human Resources (HR)" - description.
- "What will the programme involve?" - details: three-year leadership development programme, promotion after completing, CIPD training, 4 placements of 9 months each, areas: HR Business Partnering, HR in Factories, HR Expertise (Reward, Learning, Talent, Organisation Development & People Analytics), People Experience.
- "All rotations present responsibility and accountability from day one..."
- "You'll have the opportunity to shape your career adventure..."
- "What could your day-to-day role include (depending on your role)?" - list: driving culture change, managing employee relations, developing talented leaders, improving team performance, building skills and capabilities, etc. Also list of positions you could be allocated to: HR Business partner BG/BU People Partner Global Learning Specialist Reward Specialist.
- "Skills Required Include Business Acumen Stakeholder Management Design thinking Digital Technology Awareness Microsoft Office skills (Excel, Outlook, Word, PowerPoint)" plus note about development.
- "Our Application Process Involves" - steps: Online Application, Profile Assessment, Digital Interview, Discovery Centre. However instructions say remove application instructions. So we should omit the application process steps? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we must remove application instructions. So we should not include the steps.
- "What Can Unilever offer YOU?" - includes Competitive Salary £35,000, Benefits Envelope (notional value 25% of pensionable earnings), pension Scheme, Annual Bonus, discounted staff shop, Subsidised Gym Memberships (availability varies by site), Shares, Relocation support through a £5000 tax free loan, 25 days of holiday allowance.
- Diversity statement etc. Might be considered boilerplate? It's about inclusion networks etc. Might be considered substantive? It's about diversity and inclusion; maybe keep as part of Benefits? But it's not a benefit per se. Could be considered "About the role" or separate section? The instruction: include a section ONLY when posting has real, specific content for it. Diversity statement is specific content about inclusion networks. Could be a section "Diversity and Inclusion". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot add new headings beyond those. So we must fit content into those headings. Diversity statement could go under Benefits? Not exactly. Could be under About the role? Might be okay to include as a paragraph under About the role.
- "What support will you receive?" - includes buddy, career sponsor, line manager, bespoke L&D plan, opportunities to gain leadership experience outside rotations. This could be under Benefits or maybe under About the role? Could be considered part of Benefits (support). But Benefits heading is for benefits like salary, pension, etc. Support could be considered part of Benefits? Might be okay to include under Benefits as additional support.
- "Do you require any adjustments..." is about accommodations; could be considered part of Benefits? Not really. Might be considered boilerplate? It's about accessibility; maybe we keep as a short paragraph under Benefits? But it's more about application adjustments; could be considered part of Application Process (which we removed). Might be considered boilerplate? It's not EEO but about accommodations. Might be considered relevant but not in allowed headings. Could be omitted? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. Since we cannot add new headings, we could put it under Benefits as a paragraph about support for adjustments. Or under About the role.
- "Applications Open 21st September 2026 Location: Hybrid working with a minimum of 3 days required weekly at one of our offices – Port Sunlight, Kingston, Blackfriars, Leeds, Crumlin, Colworth, Burton. Travel Required Approximately 10-25% of your time, depending on your functional rotation. Closing Date This is a rolling deadline, so we encourage you to apply as soon as possible to avoid disappointment in case applications close early. Start Date September 2027" This is metadata: location, schedule, start date, etc. We have headings Pay, Schedule, Benefits. So we can put location and hybrid working under Schedule? Schedule heading could include work pattern, location, travel. Start date maybe also under Schedule? Or we could put under About the role? But we have Schedule heading for schedule details. So we can include location, hybrid working, travel %, start date maybe.
- Pay: Competitive Salary £35,000.
- Benefits: Benefits Envelope (notional value 25% of pensionable earnings), pension Scheme, Annual Bonus, discounted staff shop, Subsidised Gym Memberships (availability varies by site), Shares, Relocation support through a £5000 tax free loan, 25 days of holiday allowance, plus support (buddy, career sponsor, line manager, bespoke L&D plan, opportunities to gain leadership experience outside rotations), plus adjustments/accessibility.
- Requirements: maybe "What do we look for?" list of attributes: future HR leaders motivated by passion for people, trusted partners, drive performance using data and insight, think of new ways, dissatisfaction with status quo, people skills, mindful and responsive to contexts and audiences, inspired to develop colleagues and capabilities, enthusiasm, interest in how businesses operate, bravery to offer creative insights and execute change, build relationships, collaborate, data-driven mindset, strong influencing and negotiation abilities, remaining constantly curious and keen to learn, demonstrating agility, think differently in different contexts.
- Qualifications: The posting says "Whilst people skills are critical for the Unilever Futures Programme in HR, there are no specific qualifications necessary." So we could include a Qualifications section stating that no specific qualifications are required. But 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. For Qualifications, stating "no specific qualifications necessary" is specific content, not filler. So we can include Qualifications heading with that statement.
- Responsibilities: Could be "What could your day-to-day role include" list, plus "What will the programme involve?" maybe responsibilities. We'll create Responsibilities section with bullet list of duties: driving culture change, managing employee relations, developing talented leaders, improving team performance, building skills and capabilities, etc. Also maybe include rotations responsibilities? But we can keep.
- Skills: list: Business Acumen, Stakeholder Management, Design thinking, Digital Technology Awareness, Microsoft Office skills (Excel, Outlook, Word, PowerPoint). Also note that these are skills good to have at beginning but will be developed.
- About the role: Could include company description, program overview, purpose, vision, etc. We'll include a paragraph about Unilever and the HR Futures Programme vision.
We must not include application instructions (steps). So we will omit the "Our Application Process Involves" steps.
We must not include boilerplate like EEO, scam warning, etc. So we will remove the diversity statement? Actually diversity statement is not EEO but about inclusion networks; maybe we keep as part of Benefits or About the role. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The diversity statement is not exactly EEO but it's about inclusion networks; it's not legal boilerplate. It's substantive about diversity. We'll keep it maybe under Benefits or About the role.
We must not repeat the job title as a heading. The job title is "Human Resources (HR)" maybe? We'll not use that as heading.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment, no /, no markdown.
We'll structure:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive information.
We need to parse the posting: It's about Unilever Futures Programme HR. Content includes:
- Intro about Unilever (company description) maybe "About the role"? Actually "About the role" could be description of role and program.
- "What do we look for?" - list of attributes.
- "The role: Human Resources (HR)" - description.
- "What will the programme involve?" - details: three-year leadership development programme, promotion after completing, CIPD training, 4 placements of 9 months each, areas: HR Business Partnering, HR in Factories, HR Expertise (Reward, Learning, Talent, Organisation Development & People Analytics), People Experience.
- "All rotations present responsibility and accountability from day one..."
- "You'll have the opportunity to shape your career adventure..."
- "What could your day-to-day role include (depending on your role)?" - list: driving culture change, managing employee relations, developing talented leaders, improving team performance, building skills and capabilities, etc. Also list of positions you could be allocated to: HR Business partner BG/BU People Partner Global Learning Specialist Reward Specialist.
- "Skills Required Include Business Acumen Stakeholder Management Design thinking Digital Technology Awareness Microsoft Office skills (Excel, Outlook, Word, PowerPoint)" plus note about development.
- "Our Application Process Involves" - steps: Online Application, Profile Assessment, Digital Interview, Discovery Centre. However instructions say remove application instructions. So we should omit the application process steps? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we must remove application instructions. So we should not include the steps.
- "What Can Unilever offer YOU?" - includes Competitive Salary £35,000, Benefits Envelope (notional value 25% of pensionable earnings), pension Scheme, Annual Bonus, discounted staff shop, Subsidised Gym Memberships (availability varies by site), Shares, Relocation support through a £5000 tax free loan, 25 days of holiday allowance.
- Diversity statement etc. Might be considered boilerplate? It's about inclusion networks etc. Might be considered substantive? It's about diversity and inclusion; maybe keep as part of Benefits? But it's not a benefit per se. Could be considered "About the role" or separate section? The instruction: include a section ONLY when posting has real, specific content for it. Diversity statement is specific content about inclusion networks. Could be a section "Diversity and Inclusion". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot add new headings beyond those. So we must fit content into those headings. Diversity statement could go under Benefits? Not exactly. Could be under About the role? Might be okay to include as a paragraph under About the role.
- "What support will you receive?" - includes buddy, career sponsor, line manager, bespoke L&D plan, opportunities to gain leadership experience outside rotations. This could be under Benefits or maybe under About the role? Could be considered part of Benefits (support). But Benefits heading is for benefits like salary, pension, etc. Support could be considered part of Benefits? Might be okay to include under Benefits as additional support.
- "Do you require any adjustments..." is about accommodations; could be considered part of Benefits? Not really. Might be considered boilerplate? It's about accessibility; maybe we keep as a short paragraph under Benefits? But it's more about application adjustments; could be considered part of Application Process (which we removed). Might be considered boilerplate? It's not EEO but about accommodations. Might be considered relevant but not in allowed headings. Could be omitted? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. Since we cannot add new headings, we could put it under Benefits as a paragraph about support for adjustments. Or under About the role.
- "Applications Open 21st September 2026 Location: Hybrid working with a minimum of 3 days required weekly at one of our offices – Port Sunlight, Kingston, Blackfriars, Leeds, Crumlin, Colworth, Burton. Travel Required Approximately 10-25% of your time, depending on your functional rotation. Closing Date This is a rolling deadline, so we encourage you to apply as soon as possible to avoid disappointment in case applications close early. Start Date September 2027" This is metadata: location, schedule, start date, etc. We have headings Pay, Schedule, Benefits. So we can put location and hybrid working under Schedule? Schedule heading could include work pattern, location, travel. Start date maybe also under Schedule? Or we could put under About the role? But we have Schedule heading for schedule details. So we can include location, hybrid working, travel %, start date maybe.
- Pay: Competitive Salary £35,000.
- Benefits: Benefits Envelope (notional value 25% of pensionable earnings), pension Scheme, Annual Bonus, discounted staff shop, Subsidised Gym Memberships (availability varies by site), Shares, Relocation support through a £5000 tax free loan, 25 days of holiday allowance, plus support (buddy, career sponsor, line manager, bespoke L&D plan, opportunities to gain leadership experience outside rotations), plus adjustments/accessibility.
- Requirements: maybe "What do we look for?" list of attributes: future HR leaders motivated by passion for people, trusted partners, drive performance using data and insight, think of new ways, dissatisfaction with status quo, people skills, mindful and responsive to contexts and audiences, inspired to develop colleagues and capabilities, enthusiasm, interest in how businesses operate, bravery to offer creative insights and execute change, build relationships, collaborate, data-driven mindset, strong influencing and negotiation abilities, remaining constantly curious and keen to learn, demonstrating agility, think differently in different contexts.
- Qualifications: The posting says "Whilst people skills are critical for the Unilever Futures Programme in HR, there are no specific qualifications necessary." So we could include a Qualifications section stating that no specific qualifications are required. But 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. For Qualifications, stating "no specific qualifications necessary" is specific content, not filler. So we can include Qualifications heading with that statement.
- Responsibilities: Could be "What could your day-to-day role include" list, plus "What will the programme involve?" maybe responsibilities. We'll create Responsibilities section with bullet list of duties: driving culture change, managing employee relations, developing talented leaders, improving team performance, building skills and capabilities, etc. Also maybe include rotations responsibilities? But we can keep.
- Skills: list: Business Acumen, Stakeholder Management, Design thinking, Digital Technology Awareness, Microsoft Office skills (Excel, Outlook, Word, PowerPoint). Also note that these are skills good to have at beginning but will be developed.
- About the role: Could include company description, program overview, purpose, vision, etc. We'll include a paragraph about Unilever and the HR Futures Programme vision.
We must not include application instructions (steps). So we will omit the "Our Application Process Involves" steps.
We must not include boilerplate like EEO, scam warning, etc. So we will remove the diversity statement? Actually diversity statement is not EEO but about inclusion networks; maybe we keep as part of Benefits or About the role. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The diversity statement is not exactly EEO but it's about inclusion networks; it's not legal boilerplate. It's substantive about diversity. We'll keep it maybe under Benefits or About the role.
We must not repeat the job title as a heading. The job title is "Human Resources (HR)" maybe? We'll not use that as heading.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment, no /, no markdown.
We'll structure:
About the role
... company description and program overview ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
No specific qualifications are required for the Unilever Futures Programme in HR; people skills are critical.
Skills
- Business Acumen
- Stakeholder Management
- Design thinking
- Digital Technology Awareness
- Microsoft Office skills (Excel, Outlook, Word, PowerPoint)
These skills are beneficial to have at the start but will be developed throughout the programme.
Benefits
- Competitive Salary of £35,000
- Benefits Envelope with a notional value of 25% of pensionable earnings (can be used to save for pension, get extra taxable pay, or both)
- Pension Scheme
- Annual Bonus
- Discounted staff shop
- Subsidised Gym Memberships (availability varies by site)
- Shares
- Relocation support through a £5,000 tax‑free loan
- 25 days of holiday allowance
- Support: dedicated buddy for onboarding, dedicated Career Sponsor, experienced Line Manager for each rotation, bespoke Learning & Development Plan, opportunities to gain leadership experience outside functional rotations
- Accessibility adjustments available on request (e.g., extra time for timed assessments, magnifying glass, font/size/colour changes, screen ruler, screen mask)
Schedule
Hybrid working with a minimum of 3 days per week required at one of Unilever’s offices (Port Sunlight, Kingston, Blackfriars, Leeds, Crumlin, Colworth, Burton). Travel required approximately 10‑25% of time, depending on functional rotation. Programme start date: September 2027.
We need to ensure we didn't include Pay heading separately; we included salary in Benefits list. But we also have a Pay heading possible. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We have salary info; we could create a Pay heading with salary. But we already put salary in Benefits. However we could separate Pay and Benefits. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Pay into Benefits is okay. But we have a Benefits heading that includes salary; that's okay. However we might want to separate Pay heading for clarity. But we have to avoid many thin sections. Having both Pay and Benefits might be thin if each only has one item. But we have many benefits items, so Benefits is substantive. Pay could be just salary; but we could still include Pay heading with salary and then Benefits heading with other benefits. That would be two sections, each substantive enough? Pay would have just salary line; that's still substantive (specific). It's not filler. So we could have both. Let's decide: We'll create Pay