Senior HR & Onboarding Coordinator (Temporary)
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. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Must not create sections with filler like "commensurate with experience". Must not invent or summarize away detail.
We need to parse the posting.
Let's extract content.
The posting starts with "WHAT MAKES US EPIC?" then description about Epic, People Team, What We Do, What You'll Do (list of duties), What We're Looking For (requirements), EPIC JOB + EPIC BENEFITS = EPIC LIFE (benefits), About Us (company description), then EEO etc.
We need sections: maybe "About the role" (could be the description of role?), "Responsibilities" (What You'll Do), "Requirements" (What We're Looking For), "Skills" (maybe combine with requirements?), "Benefits" (EPIC JOB + EPIC BENEFITS = EPIC LIFE), "Pay" (not mentioned), "Schedule" (not mentioned). So we only include sections with actual content: About the role, Responsibilities, Requirements, Skills?, Benefits. Also maybe "About Us" could be "About the company" but not in list; we could put under "About the role"? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. We could include "About the role" for the role description (What You'll Do? Actually that is responsibilities). "About the role" could be a brief summary of the role from the posting: "Epic Games is searching for a Senior HR & Onboarding Coordinator to join the HR Operations team. You'll have dual responsibilities across the HR and Onboarding team to help us deliver a first class employee experience for our versatile businesses." That's from the posting.
Responsibilities: the bullet list under "What You'll Do". We need to convert to - . Must preserve all substantive info, not summarize away detail. So we need to list each duty as separate
- . The responsibilities are a long paragraph with semicolons and colon. We need to split into logical items. The text:
"You'll have dual responsibilities across the HR and Onboarding team to help us deliver a first class employee experience for our versatile businesses. In this role, you will HR partnership & employee lifecycle support: partner closely with assigned HR Partners to provide first-class support for both your HR Partner and the assigned business; supporting teams through employee lifecycle events and topics such as onboarding, departures, performance management, employee relations, and leads coachingPre-onboarding & compliance: support candidates post-offer across new hires, contract conversions, interns, acquisitions, and executives - partnering with IT, Recruiting, Payroll, Facilities, Immigration, Relocation, Legal, and Benefits to resolve issues. Initiate and monitor background checks through completion, manage Form I-9 compliance for U.S. hires and equivalent right-to-work verification in other regions, and ensure all Workday onboarding items are complete before each new hire's start dateOnboarding & Day 1 experience: manage Enboarder workflows end-to-end - communications, task/form completion, lead follow-up, and the vendor relationship. Monitor and respond to inquiries in the HR onboarding inbox and Slack channels. Schedule and facilitate new hire orientation (Americas, with EMEA support as needed), coordinate Day 1 location logistics, and ensure new hires are logged in and accounted forSystems, data & reporting: ensure accurate hiring data across Epic systems; complete Workday Hire Events; build and maintain Greenhouse and Airtable tracking for offers, pre-boarding tasks, and hire changes; and audit employment documents in WorkdayHR operations: complete administrative work within the global HR Coordinator team, including employee queries, HR Inbox, and necessary Workday updatesPolicies, projects & process improvement: provide guidance across our policies and procedures and help take these processes to the next level with your ideas; support defined People projects in partnership with our CoEs; and act as SME on cross-functional initiatives such as the Workday migration, executive onboarding, and onsite onboarding, identifying gaps and building improvementsAl-enabled ways of working: use Al tools and automation to streamline HR and onboarding workflows, surface insights and data issues faster, and improve accuracy and efficiency across your work"
We need to split into items: maybe each bold heading (HR partnership & employee lifecycle support, Pre-onboarding & compliance, Onboarding & Day 1 experience, Systems, data & reporting, HR operations, Policies, projects & process improvement, Al-enabled ways of working). Each with subitems separated by semicolons.
We'll produce
- for each main duty, and within each we can have nested
for subpoints? The instruction: Use - for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll produce top-level
with each duty as - , and inside each we can have
for subpoints.
Similarly for Requirements: "What We're Looking For" list: Solid prior experience in HR administration and or onboarding, in a global environmentAble to deliver results in a complex and fast paced, global organizationGood eye for detail and strong coordination and project management skillsExpertise in navigating within ambiguous, high-volume situations when neededExcellent communication and interpersonal skills, working in a virtual, cross-functional environmentComfort using Al tools and automation to streamline processes, reduce manual work, and improve data accuracyAbility to look for solutions and independently drive initiatives and process improvements as neededStrong networking skills and ambition to growStrong IT and HRIS skills (Workday, Greenhouse, Enboarder, Airtable, and related systems)
We need to split into items. They are concatenated without punctuation. We'll separate by capital letters after a lowercase? We'll manually split based on meaning:
- Solid prior experience in HR administration and/or onboarding, in a global environment
- Able to deliver results in a complex and fast-paced, global organization
- Good eye for detail and strong coordination and project management skills
- Expertise in navigating within ambiguous, high-volume situations when needed
- Excellent communication and interpersonal skills, working in a virtual, cross-functional environment
- Comfort using AI tools and automation to streamline processes, reduce manual work, and improve data accuracy
- Ability to look for solutions and independently drive initiatives and process improvements as needed
- Strong networking skills and ambition to grow
- Strong IT and HRIS skills (Workday, Greenhouse, Enboarder, Airtable, and related systems)
We'll produce - for each.
Skills: Could be separate from Requirements? The instruction includes Skills as possible heading. We could combine requirements and skills, but better to have separate sections if content distinct. The posting doesn't have a separate skills list; the requirements include skills. We could still have a Skills section listing the same items? That would be duplication. Better to not create a Skills section if no distinct content; but we could treat the requirements as skills. However instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Skills into one section called "Requirements" (or "Qualifications"). Since they gave examples: Requirements, Qualifications, Skills. We can choose to have Requirements (or Qualifications) and maybe Skills not needed. We'll include Requirements (or Qualifications) and maybe Skills if we want to split but risk thin. Let's make one section: "Requirements" containing the list.
Benefits: from "EPIC JOB + EPIC BENEFITS = EPIC LIFE". Content: "Our intent is to cover all things that are medically necessary and improve the quality of life. We pay 100% of the premiums for both you and your dependents. Our coverage includes Medical, Dental, a Vision HRA, Long Term Disability, Life Insurance & a 401k with competitive match. We also offer a robust mental well-being program through Modern Health, which provides free therapy and coaching for employees & dependents. Throughout the year we celebrate our employees with events and company-wide paid breaks. We offer unlimited PTO and sick time and recognize individuals for 7 years of employment with a paid sabbatical."
We need to put that as
- list. Could split each sentence as item.
About the role: we need a short paragraph summarizing role. Could be: "Epic Games is searching for a Senior HR & Onboarding Coordinator to join the HR Operations team. You'll have dual responsibilities across the HR and Onboarding team to help us deliver a first class employee experience for our versatile businesses." That's from the posting. We'll put that in
.
We must not include boilerplate: EEO, Note to Recruitment Agencies, etc. Also remove duplicated lines. Also remove "About Us" maybe? The instruction says use headings for sections like About the role, Responsibilities, etc. About Us is not in list; we could omit it or incorporate into About the role? Probably we should omit About Us as it's not required heading. However we must preserve ALL substantive information. About Us is substantive about company. But we don't have a heading for it; we could include it under About the role? Might be okay to add a paragraph about the company under About the role? But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to include About the role (role description) and maybe also include About the company under About the role? Could be considered part of role description. However the About Us section is separate from role. But we could incorporate it as a paragraph under About the role (makes sense: describing the company). The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can put About Us content into a
under About the role or as a separate
before sections? Probably better to have a section "About the role" that includes both role description and company overview. We'll include a
with role description and then another
with company overview.
Now produce HTML fragment:
About the role
Epic Games is searching for a Senior HR & Onboarding Coordinator to join the HR Operations team. You'll have dual responsibilities across the HR and Onboarding team to help us deliver a first class employee experience for our versatile businesses.
Epic Games is a leading interactive entertainment company. For over 30 years we've been making award-winning games and engine technology that empowers others to make visually stunning games and 3D content that bring environments to life like never before. Epic's award-winning Unreal Engine technology not only provides game developers the ability to build high-fidelity, interactive experiences for PC, console, mobile, and VR, it is also a tool being embraced by content creators across a variety of industries such as media and entertainment, automotive, and architectural design. As we continue to build our Engine technology and develop remarkable games, we strive to build teams of world-class talent.
Responsibilities
-
HR partnership & employee lifecycle support
- Partner closely with assigned HR Partners to provide first-class support for both your HR Partner and the assigned business
- Support teams through employee lifecycle events and topics such as on
- . Must preserve all substantive info, not summarize away detail. So we need to list each duty as separate
- . The responsibilities are a long paragraph with semicolons and colon. We need to split into logical items. The text:
"You'll have dual responsibilities across the HR and Onboarding team to help us deliver a first class employee experience for our versatile businesses. In this role, you will HR partnership & employee lifecycle support: partner closely with assigned HR Partners to provide first-class support for both your HR Partner and the assigned business; supporting teams through employee lifecycle events and topics such as onboarding, departures, performance management, employee relations, and leads coachingPre-onboarding & compliance: support candidates post-offer across new hires, contract conversions, interns, acquisitions, and executives - partnering with IT, Recruiting, Payroll, Facilities, Immigration, Relocation, Legal, and Benefits to resolve issues. Initiate and monitor background checks through completion, manage Form I-9 compliance for U.S. hires and equivalent right-to-work verification in other regions, and ensure all Workday onboarding items are complete before each new hire's start dateOnboarding & Day 1 experience: manage Enboarder workflows end-to-end - communications, task/form completion, lead follow-up, and the vendor relationship. Monitor and respond to inquiries in the HR onboarding inbox and Slack channels. Schedule and facilitate new hire orientation (Americas, with EMEA support as needed), coordinate Day 1 location logistics, and ensure new hires are logged in and accounted forSystems, data & reporting: ensure accurate hiring data across Epic systems; complete Workday Hire Events; build and maintain Greenhouse and Airtable tracking for offers, pre-boarding tasks, and hire changes; and audit employment documents in WorkdayHR operations: complete administrative work within the global HR Coordinator team, including employee queries, HR Inbox, and necessary Workday updatesPolicies, projects & process improvement: provide guidance across our policies and procedures and help take these processes to the next level with your ideas; support defined People projects in partnership with our CoEs; and act as SME on cross-functional initiatives such as the Workday migration, executive onboarding, and onsite onboarding, identifying gaps and building improvementsAl-enabled ways of working: use Al tools and automation to streamline HR and onboarding workflows, surface insights and data issues faster, and improve accuracy and efficiency across your work"
We need to split into items: maybe each bold heading (HR partnership & employee lifecycle support, Pre-onboarding & compliance, Onboarding & Day 1 experience, Systems, data & reporting, HR operations, Policies, projects & process improvement, Al-enabled ways of working). Each with subitems separated by semicolons.
We'll produce
- for each main duty, and within each we can have nested
- for subpoints? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll produce top-level
- with each duty as
- , and inside each we can have
- for subpoints.
Similarly for Requirements: "What We're Looking For" list: Solid prior experience in HR administration and or onboarding, in a global environmentAble to deliver results in a complex and fast paced, global organizationGood eye for detail and strong coordination and project management skillsExpertise in navigating within ambiguous, high-volume situations when neededExcellent communication and interpersonal skills, working in a virtual, cross-functional environmentComfort using Al tools and automation to streamline processes, reduce manual work, and improve data accuracyAbility to look for solutions and independently drive initiatives and process improvements as neededStrong networking skills and ambition to growStrong IT and HRIS skills (Workday, Greenhouse, Enboarder, Airtable, and related systems)
We need to split into items. They are concatenated without punctuation. We'll separate by capital letters after a lowercase? We'll manually split based on meaning:
- Solid prior experience in HR administration and/or onboarding, in a global environment
- Able to deliver results in a complex and fast-paced, global organization
- Good eye for detail and strong coordination and project management skills
- Expertise in navigating within ambiguous, high-volume situations when needed
- Excellent communication and interpersonal skills, working in a virtual, cross-functional environment
- Comfort using AI tools and automation to streamline processes, reduce manual work, and improve data accuracy
- Ability to look for solutions and independently drive initiatives and process improvements as needed
- Strong networking skills and ambition to grow
- Strong IT and HRIS skills (Workday, Greenhouse, Enboarder, Airtable, and related systems)
We'll produce
- for each.
Skills: Could be separate from Requirements? The instruction includes Skills as possible heading. We could combine requirements and skills, but better to have separate sections if content distinct. The posting doesn't have a separate skills list; the requirements include skills. We could still have a Skills section listing the same items? That would be duplication. Better to not create a Skills section if no distinct content; but we could treat the requirements as skills. However instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Skills into one section called "Requirements" (or "Qualifications"). Since they gave examples: Requirements, Qualifications, Skills. We can choose to have Requirements (or Qualifications) and maybe Skills not needed. We'll include Requirements (or Qualifications) and maybe Skills if we want to split but risk thin. Let's make one section: "Requirements" containing the list.
Benefits: from "EPIC JOB + EPIC BENEFITS = EPIC LIFE". Content: "Our intent is to cover all things that are medically necessary and improve the quality of life. We pay 100% of the premiums for both you and your dependents. Our coverage includes Medical, Dental, a Vision HRA, Long Term Disability, Life Insurance & a 401k with competitive match. We also offer a robust mental well-being program through Modern Health, which provides free therapy and coaching for employees & dependents. Throughout the year we celebrate our employees with events and company-wide paid breaks. We offer unlimited PTO and sick time and recognize individuals for 7 years of employment with a paid sabbatical."
We need to put that as
- list. Could split each sentence as item.
About the role: we need a short paragraph summarizing role. Could be: "Epic Games is searching for a Senior HR & Onboarding Coordinator to join the HR Operations team. You'll have dual responsibilities across the HR and Onboarding team to help us deliver a first class employee experience for our versatile businesses." That's from the posting. We'll put that in
. We must not include boilerplate: EEO, Note to Recruitment Agencies, etc. Also remove duplicated lines. Also remove "About Us" maybe? The instruction says use headings for sections like About the role, Responsibilities, etc. About Us is not in list; we could omit it or incorporate into About the role? Probably we should omit About Us as it's not required heading. However we must preserve ALL substantive information. About Us is substantive about company. But we don't have a heading for it; we could include it under About the role? Might be okay to add a paragraph about the company under About the role? But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to include About the role (role description) and maybe also include About the company under About the role? Could be considered part of role description. However the About Us section is separate from role. But we could incorporate it as a paragraph under About the role (makes sense: describing the company). The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can put About Us content into a
under About the role or as a separate
before sections? Probably better to have a section "About the role" that includes both role description and company overview. We'll include a
with role description and then another
with company overview. Now produce HTML fragment:
About the role
Epic Games is searching for a Senior HR & Onboarding Coordinator to join the HR Operations team. You'll have dual responsibilities across the HR and Onboarding team to help us deliver a first class employee experience for our versatile businesses.
Epic Games is a leading interactive entertainment company. For over 30 years we've been making award-winning games and engine technology that empowers others to make visually stunning games and 3D content that bring environments to life like never before. Epic's award-winning Unreal Engine technology not only provides game developers the ability to build high-fidelity, interactive experiences for PC, console, mobile, and VR, it is also a tool being embraced by content creators across a variety of industries such as media and entertainment, automotive, and architectural design. As we continue to build our Engine technology and develop remarkable games, we strive to build teams of world-class talent.
Responsibilities
-
HR partnership & employee lifecycle support
- Partner closely with assigned HR Partners to provide first-class support for both your HR Partner and the assigned business
- Support teams through employee lifecycle events and topics such as on
-
HR partnership & employee lifecycle support
- list. Could split each sentence as item.
About the role: we need a short paragraph summarizing role. Could be: "Epic Games is searching for a Senior HR & Onboarding Coordinator to join the HR Operations team. You'll have dual responsibilities across the HR and Onboarding team to help us deliver a first class employee experience for our versatile businesses." That's from the posting. We'll put that in
- for each.
Skills: Could be separate from Requirements? The instruction includes Skills as possible heading. We could combine requirements and skills, but better to have separate sections if content distinct. The posting doesn't have a separate skills list; the requirements include skills. We could still have a Skills section listing the same items? That would be duplication. Better to not create a Skills section if no distinct content; but we could treat the requirements as skills. However instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Skills into one section called "Requirements" (or "Qualifications"). Since they gave examples: Requirements, Qualifications, Skills. We can choose to have Requirements (or Qualifications) and maybe Skills not needed. We'll include Requirements (or Qualifications) and maybe Skills if we want to split but risk thin. Let's make one section: "Requirements" containing the list.
Benefits: from "EPIC JOB + EPIC BENEFITS = EPIC LIFE". Content: "Our intent is to cover all things that are medically necessary and improve the quality of life. We pay 100% of the premiums for both you and your dependents. Our coverage includes Medical, Dental, a Vision HRA, Long Term Disability, Life Insurance & a 401k with competitive match. We also offer a robust mental well-being program through Modern Health, which provides free therapy and coaching for employees & dependents. Throughout the year we celebrate our employees with events and company-wide paid breaks. We offer unlimited PTO and sick time and recognize individuals for 7 years of employment with a paid sabbatical."
We need to put that as
- , and inside each we can have
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll produce top-level
- for each main duty, and within each we can have nested