Game Design Intern
Epic Games · Cary, NC · 1 mo ago
Art & CreativeFull-time
We need to output HTML fragment with sections only if there is real specific content. The posting includes: "WHAT MAKES US EPIC?" (intro), "DESIGN What We Do", "GAME DESIGN INTERN What You'll Do", "What We're Looking For", "This internship has a flexible start date in 2027...", "About Us". Also there is EEO and recruitment agency note which we should remove (boilerplate). Also we need to use for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must map content to these headings appropriately. The instructions: "use
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must map content to these headings appropriately. The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings? It says e.g., meaning examples. We should use those headings when appropriate. We need to decide which sections we have content for.
We have:
- About the role: could be description of what the intern will do (What You'll Do). That's responsibilities.
- Responsibilities: list of duties (the bullet points under "What You'll Do").
- Requirements / Qualifications: "What We're Looking For" list.
- Skills: maybe combine with requirements? Could list specific skills like Unreal Engine, Blueprints, etc.
- Benefits: Not mentioned besides maybe flexible start date? Not a benefit. No explicit benefits.
- Pay: Not mentioned.
- Schedule: Not mentioned (flexible start date maybe schedule? but not explicit schedule like hours). Probably we should not create Pay/Schedule/Benefits sections unless posting actually states them. It does not state pay, benefits, schedule. So we omit those.
- About the company: Could be "About Us" section. Could map to "About the role"? Actually "About the role" is about the role, not company. There's no explicit "About the company" heading in list, but we could use "About the role" for role description and maybe "About Us" not in list. 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 suggests using those. Safer to stick to those headings. So we can have sections: About the role (description), Responsibilities (list), Requirements (list), Qualifications (maybe same as Requirements?), Skills (list). Might be redundant. Better to combine: Use About the role for overview, Responsibilities for duties list, Requirements for qualifications list, Skills for specific technical skills list. But we must not repeat content. We need to preserve all substantive information.
Let's extract content:
Intro: "WHAT MAKES US EPIC? ..." This is boilerplate? It's about company culture. Might be considered "About the role"? Not exactly. Could be considered "About the role"? Actually it's about Epic. Might be considered "About the company". Since we don't have a heading for that, maybe we can include it under About the role? But it's not about the role. However we could treat it as part of About the role? 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 we should prefer those. However we need to preserve all substantive information. The intro about Epic's success, collaborative environment, etc. is substantive. We could put it under a heading like "About Epic" but not in list. Might be okay to add a custom heading? The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections, but we could also use other headings if needed? Safer to stick to those. We could incorporate the intro into About the role section as a brief description of the company/context. That might be acceptable.
Now "DESIGN What We Do" is a heading but not in list. Could be considered part of About the role? It's about design team. Might be considered part of About the role.
Then "GAME DESIGN INTERN What You'll Do" - this is the role title. We should not repeat job title as a heading. So we skip that heading.
Then bullet points under "What You'll Do": list of responsibilities.
Then "What We're Looking For": list of requirements/qualifications/skills.
Then "This internship has a flexible start date in 2027...": This is about schedule/start date. Could be considered Schedule? It's a flexible start date. The instruction says include Schedule section only if posting actually states them. It does state a flexible start date. So we could include a Schedule section with that info. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state flexible start date, so we can include Schedule.
But we need to check if "flexible start date in 2027" is considered schedule. It's about timing. We'll include Schedule.
Also "Recruitment will be ongoing until teams find an ideal match." That's metadata, could be dropped.
"Applicants must be legally authorized to work in the posting location for the duration of the internship." That's a requirement (legal). Could be included in Requirements.
"For more information about Epic’s Early Career Program, visit epicgames.com/earlycareers." That's application instruction? Actually it's a link for more info. Might be considered application instruction; we should remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop that line.
"This is going to be Epic!" is fluff, maybe drop.
"About Us" section: description of Epic Games. Could be considered About the role? Or we could add a custom heading "About the company". But not in list. However we could treat it as part of About the role? Might be okay to include as a paragraph under About the role.
"Epic Games deeply values diverse teams..." EEO boilerplate: remove.
"Note to Recruitment Agencies...": remove.
Thus we need to produce HTML with sections:
- About the role
: include intro paragraph about Epic's culture and design team, plus About Us description.
- Responsibilities
: - ... list items from "What You'll Do".
-
Requirements
: maybe combine "What We're Looking For" plus legal authorization.
- Skills
: maybe list specific technical skills: Unreal Engine, Blueprints, Gameplay Ability System, World Partition, Data Layers, Level Sequencer, multiplayer replication, troubleshooting, communication, collaboration, debugging, test plans.
But we must not duplicate content. If we put skills separate, we need to ensure we don't lose any info. Could instead put all under Requirements. But we have both Requirements and Skills headings available; we could split.
Better: Use Requirements for general qualifications (experience, interest, ability to work legally). Use Skills for technical proficiencies.
Let's extract:
From "What We're Looking For":
- Practical experience with Unreal Engine
- Proficiency with Blueprints and the Gameplay Ability System
- Portfolio of playable projects demonstrating experience across the video game production cycle, including student, indie, or freelance work
- Interest in Fortnite, particularly live events and ambitious, narrative-driven content
- Experience with level design systems such as World Partition and Data Layers, Level Sequencer, and basic multiplayer replication
- Ability to independently troubleshoot problems and use available resources to identify solutions to blocking issues
- Ability to clearly communicate needs, risks, ideas, scope, and progress to the team
- Ability to collaborate effectively across disciplines to safely implement content into a project
- Ability to debug systems and interactive gameplay issues and develop test plans that support both debugging and QA validation
Legal authorization: "Applicants must be legally authorized to work in the posting location for the duration of the internship."
Now responsibilities list:
- Help design and implement gameplay features for live events
- Learn how to prototype dynamic player experiences in a large scale client-server replicated environment and expand on those ideas
- Work within level sequences to help align keyframed event triggers, work with cinematic artists to manage structure and timing, and implement gameplay features into the event
- Participate in team playtests, providing and addressing feedback
- Collaborate with others and independently iterate on work based on feedback and evolving needs
- Clearly communicate updates, progress, and potential risks to relevant stakeholders
- Make and update documents for designs, technical adjustments, or reference materials
Now About the role paragraph: combine WHAT MAKES US EPIC? and DESIGN What We Do and About Us.
WHAT MAKES US EPIC? text: "At the core of Epic’s success are talented, passionate people. Epic prides itself on creating a collaborative, welcoming, and creative environment. Whether it’s building award-winning games or crafting engine technology that enables others to make visually stunning interactive experiences, we’re always innovating. Being Epic means being a part of a team that continually strives to do right by our community and users. We’re constantly innovating to raise the bar of engine and game development."
DESIGN What We Do: "Put your design skills to work at a cutting-edge company that challenges the norm. From character and level design to competitive gameplay and system design, help shape the future of interactive entertainment at Epic."
About Us: "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. Like what you hear? Come be a part of something Epic!"
We can combine into a few paragraphs.
Now Schedule: "This internship has a flexible start date in 2027. Recruitment will be ongoing until teams find an ideal match." The second sentence maybe metadata but still about schedule. We'll include flexible start date.
We should not include "Recruitment will be ongoing..." maybe it's okay but it's not schedule. Could keep as part of schedule.
Now we must not include any boilerplate like EEO, recruitment agency note, application instructions (the link to early careers). Also remove duplicated lines.
Now produce HTML fragment:
About the role
... paragraphs ...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Schedule
Flexible start date in 2027; recruitment ongoing until an ideal match is found.
Check that we didn't repeat job title. Good.
Now ensure we preserve all substantive information: Did we miss any? The "Portfolio of playable projects demonstrating experience across the video game production cycle, including student, indie, or freelance work" is included under Requirements or Skills? We'll put under Requirements maybe.
"Interest in Fortnite, particularly live events and ambitious, narrative-driven content" under Requirements.
"Ability to independently troubleshoot problems..." under Skills.
"Ability to clearly communicate needs, risks, ideas, scope, and progress to the team" under Skills.
"Ability to collaborate effectively across
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings. So we can have sections: About the role (description), Responsibilities (list), Requirements (list), Qualifications (maybe same as Requirements?), Skills (list). Might be redundant. Better to combine: Use About the role for overview, Responsibilities for duties list, Requirements for qualifications list, Skills for specific technical skills list. But we must not repeat content. We need to preserve all substantive information.
Let's extract content:
Intro: "WHAT MAKES US EPIC? ..." This is boilerplate? It's about company culture. Might be considered "About the role"? Not exactly. Could be considered "About the role"? Actually it's about Epic. Might be considered "About the company". Since we don't have a heading for that, maybe we can include it under About the role? But it's not about the role. However we could treat it as part of About the role? 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 we should prefer those. However we need to preserve all substantive information. The intro about Epic's success, collaborative environment, etc. is substantive. We could put it under a heading like "About Epic" but not in list. Might be okay to add a custom heading? The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections, but we could also use other headings if needed? Safer to stick to those. We could incorporate the intro into About the role section as a brief description of the company/context. That might be acceptable.
Now "DESIGN What We Do" is a heading but not in list. Could be considered part of About the role? It's about design team. Might be considered part of About the role.
Then "GAME DESIGN INTERN What You'll Do" - this is the role title. We should not repeat job title as a heading. So we skip that heading.
Then bullet points under "What You'll Do": list of responsibilities.
Then "What We're Looking For": list of requirements/qualifications/skills.
Then "This internship has a flexible start date in 2027...": This is about schedule/start date. Could be considered Schedule? It's a flexible start date. The instruction says include Schedule section only if posting actually states them. It does state a flexible start date. So we could include a Schedule section with that info. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state flexible start date, so we can include Schedule.
But we need to check if "flexible start date in 2027" is considered schedule. It's about timing. We'll include Schedule.
Also "Recruitment will be ongoing until teams find an ideal match." That's metadata, could be dropped.
"Applicants must be legally authorized to work in the posting location for the duration of the internship." That's a requirement (legal). Could be included in Requirements.
"For more information about Epic’s Early Career Program, visit epicgames.com/earlycareers." That's application instruction? Actually it's a link for more info. Might be considered application instruction; we should remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop that line.
"This is going to be Epic!" is fluff, maybe drop.
"About Us" section: description of Epic Games. Could be considered About the role? Or we could add a custom heading "About the company". But not in list. However we could treat it as part of About the role? Might be okay to include as a paragraph under About the role.
"Epic Games deeply values diverse teams..." EEO boilerplate: remove.
"Note to Recruitment Agencies...": remove.
Thus we need to produce HTML with sections:
- About the role
: include intro paragraph about Epic's culture and design team, plus About Us description.
- Responsibilities
: - ... list items from "What You'll Do".
-
Requirements
: maybe combine "What We're Looking For" plus legal authorization.
- Skills
: maybe list specific technical skills: Unreal Engine, Blueprints, Gameplay Ability System, World Partition, Data Layers, Level Sequencer, multiplayer replication, troubleshooting, communication, collaboration, debugging, test plans.
But we must not duplicate content. If we put skills separate, we need to ensure we don't lose any info. Could instead put all under Requirements. But we have both Requirements and Skills headings available; we could split.
Better: Use Requirements for general qualifications (experience, interest, ability to work legally). Use Skills for technical proficiencies.
Let's extract:
From "What We're Looking For":
- Practical experience with Unreal Engine
- Proficiency with Blueprints and the Gameplay Ability System
- Portfolio of playable projects demonstrating experience across the video game production cycle, including student, indie, or freelance work
- Interest in Fortnite, particularly live events and ambitious, narrative-driven content
- Experience with level design systems such as World Partition and Data Layers, Level Sequencer, and basic multiplayer replication
- Ability to independently troubleshoot problems and use available resources to identify solutions to blocking issues
- Ability to clearly communicate needs, risks, ideas, scope, and progress to the team
- Ability to collaborate effectively across disciplines to safely implement content into a project
- Ability to debug systems and interactive gameplay issues and develop test plans that support both debugging and QA validation
Legal authorization: "Applicants must be legally authorized to work in the posting location for the duration of the internship."
Now responsibilities list:
- Help design and implement gameplay features for live events
- Learn how to prototype dynamic player experiences in a large scale client-server replicated environment and expand on those ideas
- Work within level sequences to help align keyframed event triggers, work with cinematic artists to manage structure and timing, and implement gameplay features into the event
- Participate in team playtests, providing and addressing feedback
- Collaborate with others and independently iterate on work based on feedback and evolving needs
- Clearly communicate updates, progress, and potential risks to relevant stakeholders
- Make and update documents for designs, technical adjustments, or reference materials
Now About the role paragraph: combine WHAT MAKES US EPIC? and DESIGN What We Do and About Us.
WHAT MAKES US EPIC? text: "At the core of Epic’s success are talented, passionate people. Epic prides itself on creating a collaborative, welcoming, and creative environment. Whether it’s building award-winning games or crafting engine technology that enables others to make visually stunning interactive experiences, we’re always innovating. Being Epic means being a part of a team that continually strives to do right by our community and users. We’re constantly innovating to raise the bar of engine and game development."
DESIGN What We Do: "Put your design skills to work at a cutting-edge company that challenges the norm. From character and level design to competitive gameplay and system design, help shape the future of interactive entertainment at Epic."
About Us: "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. Like what you hear? Come be a part of something Epic!"
We can combine into a few paragraphs.
Now Schedule: "This internship has a flexible start date in 2027. Recruitment will be ongoing until teams find an ideal match." The second sentence maybe metadata but still about schedule. We'll include flexible start date.
We should not include "Recruitment will be ongoing..." maybe it's okay but it's not schedule. Could keep as part of schedule.
Now we must not include any boilerplate like EEO, recruitment agency note, application instructions (the link to early careers). Also remove duplicated lines.
Now produce HTML fragment:
About the role
... paragraphs ...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Schedule
Flexible start date in 2027; recruitment ongoing until an ideal match is found.
Check that we didn't repeat job title. Good.
Now ensure we preserve all substantive information: Did we miss any? The "Portfolio of playable projects demonstrating experience across the video game production cycle, including student, indie, or freelance work" is included under Requirements or Skills? We'll put under Requirements maybe.
"Interest in Fortnite, particularly live events and ambitious, narrative-driven content" under Requirements.
"Ability to independently troubleshoot problems..." under Skills.
"Ability to clearly communicate needs, risks, ideas, scope, and progress to the team" under Skills.
"Ability to collaborate effectively across
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections, but we could also use other headings if needed? Safer to stick to those. We could incorporate the intro into About the role section as a brief description of the company/context. That might be acceptable.
Now "DESIGN What We Do" is a heading but not in list. Could be considered part of About the role? It's about design team. Might be considered part of About the role.
Then "GAME DESIGN INTERN What You'll Do" - this is the role title. We should not repeat job title as a heading. So we skip that heading.
Then bullet points under "What You'll Do": list of responsibilities.
Then "What We're Looking For": list of requirements/qualifications/skills.
Then "This internship has a flexible start date in 2027...": This is about schedule/start date. Could be considered Schedule? It's a flexible start date. The instruction says include Schedule section only if posting actually states them. It does state a flexible start date. So we could include a Schedule section with that info. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state flexible start date, so we can include Schedule.
But we need to check if "flexible start date in 2027" is considered schedule. It's about timing. We'll include Schedule.
Also "Recruitment will be ongoing until teams find an ideal match." That's metadata, could be dropped.
"Applicants must be legally authorized to work in the posting location for the duration of the internship." That's a requirement (legal). Could be included in Requirements.
"For more information about Epic’s Early Career Program, visit epicgames.com/earlycareers." That's application instruction? Actually it's a link for more info. Might be considered application instruction; we should remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop that line.
"This is going to be Epic!" is fluff, maybe drop.
"About Us" section: description of Epic Games. Could be considered About the role? Or we could add a custom heading "About the company". But not in list. However we could treat it as part of About the role? Might be okay to include as a paragraph under About the role.
"Epic Games deeply values diverse teams..." EEO boilerplate: remove.
"Note to Recruitment Agencies...": remove.
Thus we need to produce HTML with sections:
- About the role
: include intro paragraph about Epic's culture and design team, plus About Us description.
- Responsibilities
: - ... list items from "What You'll Do".
-
Requirements
: maybe combine "What We're Looking For" plus legal authorization.
- Skills
: maybe list specific technical skills: Unreal Engine, Blueprints, Gameplay Ability System, World Partition, Data Layers, Level Sequencer, multiplayer replication, troubleshooting, communication, collaboration, debugging, test plans.
But we must not duplicate content. If we put skills separate, we need to ensure we don't lose any info. Could instead put all under Requirements. But we have both Requirements and Skills headings available; we could split.
Better: Use Requirements for general qualifications (experience, interest, ability to work legally). Use Skills for technical proficiencies.
Let's extract:
From "What We're Looking For":
- Practical experience with Unreal Engine
- Proficiency with Blueprints and the Gameplay Ability System
- Portfolio of playable projects demonstrating experience across the video game production cycle, including student, indie, or freelance work
- Interest in Fortnite, particularly live events and ambitious, narrative-driven content
- Experience with level design systems such as World Partition and Data Layers, Level Sequencer, and basic multiplayer replication
- Ability to independently troubleshoot problems and use available resources to identify solutions to blocking issues
- Ability to clearly communicate needs, risks, ideas, scope, and progress to the team
- Ability to collaborate effectively across disciplines to safely implement content into a project
- Ability to debug systems and interactive gameplay issues and develop test plans that support both debugging and QA validation
Legal authorization: "Applicants must be legally authorized to work in the posting location for the duration of the internship."
Now responsibilities list:
- Help design and implement gameplay features for live events
- Learn how to prototype dynamic player experiences in a large scale client-server replicated environment and expand on those ideas
- Work within level sequences to help align keyframed event triggers, work with cinematic artists to manage structure and timing, and implement gameplay features into the event
- Participate in team playtests, providing and addressing feedback
- Collaborate with others and independently iterate on work based on feedback and evolving needs
- Clearly communicate updates, progress, and potential risks to relevant stakeholders
- Make and update documents for designs, technical adjustments, or reference materials
Now About the role paragraph: combine WHAT MAKES US EPIC? and DESIGN What We Do and About Us.
WHAT MAKES US EPIC? text: "At the core of Epic’s success are talented, passionate people. Epic prides itself on creating a collaborative, welcoming, and creative environment. Whether it’s building award-winning games or crafting engine technology that enables others to make visually stunning interactive experiences, we’re always innovating. Being Epic means being a part of a team that continually strives to do right by our community and users. We’re constantly innovating to raise the bar of engine and game development."
DESIGN What We Do: "Put your design skills to work at a cutting-edge company that challenges the norm. From character and level design to competitive gameplay and system design, help shape the future of interactive entertainment at Epic."
About Us: "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. Like what you hear? Come be a part of something Epic!"
We can combine into a few paragraphs.
Now Schedule: "This internship has a flexible start date in 2027. Recruitment will be ongoing until teams find an ideal match." The second sentence maybe metadata but still about schedule. We'll include flexible start date.
We should not include "Recruitment will be ongoing..." maybe it's okay but it's not schedule. Could keep as part of schedule.
Now we must not include any boilerplate like EEO, recruitment agency note, application instructions (the link to early careers). Also remove duplicated lines.
Now produce HTML fragment:
About the role
... paragraphs ...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Schedule
Flexible start date in 2027; recruitment ongoing until an ideal match is found.
Check that we didn't repeat job title. Good.
Now ensure we preserve all substantive information: Did we miss any? The "Portfolio of playable projects demonstrating experience across the video game production cycle, including student, indie, or freelance work" is included under Requirements or Skills? We'll put under Requirements maybe.
"Interest in Fortnite, particularly live events and ambitious, narrative-driven content" under Requirements.
"Ability to independently troubleshoot problems..." under Skills.
"Ability to clearly communicate needs, risks, ideas, scope, and progress to the team" under Skills.
"Ability to collaborate effectively across
Requirements
: maybe combine "What We're Looking For" plus legal authorization. -Skills
: maybe list specific technical skills: Unreal Engine, Blueprints, Gameplay Ability System, World Partition, Data Layers, Level Sequencer, multiplayer replication, troubleshooting, communication, collaboration, debugging, test plans. But we must not duplicate content. If we put skills separate, we need to ensure we don't lose any info. Could instead put all under Requirements. But we have both Requirements and Skills headings available; we could split. Better: Use Requirements for general qualifications (experience, interest, ability to work legally). Use Skills for technical proficiencies. Let's extract: From "What We're Looking For": - Practical experience with Unreal Engine - Proficiency with Blueprints and the Gameplay Ability System - Portfolio of playable projects demonstrating experience across the video game production cycle, including student, indie, or freelance work - Interest in Fortnite, particularly live events and ambitious, narrative-driven content - Experience with level design systems such as World Partition and Data Layers, Level Sequencer, and basic multiplayer replication - Ability to independently troubleshoot problems and use available resources to identify solutions to blocking issues - Ability to clearly communicate needs, risks, ideas, scope, and progress to the team - Ability to collaborate effectively across disciplines to safely implement content into a project - Ability to debug systems and interactive gameplay issues and develop test plans that support both debugging and QA validation Legal authorization: "Applicants must be legally authorized to work in the posting location for the duration of the internship." Now responsibilities list: - Help design and implement gameplay features for live events - Learn how to prototype dynamic player experiences in a large scale client-server replicated environment and expand on those ideas - Work within level sequences to help align keyframed event triggers, work with cinematic artists to manage structure and timing, and implement gameplay features into the event - Participate in team playtests, providing and addressing feedback - Collaborate with others and independently iterate on work based on feedback and evolving needs - Clearly communicate updates, progress, and potential risks to relevant stakeholders - Make and update documents for designs, technical adjustments, or reference materials Now About the role paragraph: combine WHAT MAKES US EPIC? and DESIGN What We Do and About Us. WHAT MAKES US EPIC? text: "At the core of Epic’s success are talented, passionate people. Epic prides itself on creating a collaborative, welcoming, and creative environment. Whether it’s building award-winning games or crafting engine technology that enables others to make visually stunning interactive experiences, we’re always innovating. Being Epic means being a part of a team that continually strives to do right by our community and users. We’re constantly innovating to raise the bar of engine and game development." DESIGN What We Do: "Put your design skills to work at a cutting-edge company that challenges the norm. From character and level design to competitive gameplay and system design, help shape the future of interactive entertainment at Epic." About Us: "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. Like what you hear? Come be a part of something Epic!" We can combine into a few paragraphs. Now Schedule: "This internship has a flexible start date in 2027. Recruitment will be ongoing until teams find an ideal match." The second sentence maybe metadata but still about schedule. We'll include flexible start date. We should not include "Recruitment will be ongoing..." maybe it's okay but it's not schedule. Could keep as part of schedule. Now we must not include any boilerplate like EEO, recruitment agency note, application instructions (the link to early careers). Also remove duplicated lines. Now produce HTML fragment:About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Schedule
Flexible start date in 2027; recruitment ongoing until an ideal match is found.
Check that we didn't repeat job title. Good. Now ensure we preserve all substantive information: Did we miss any? The "Portfolio of playable projects demonstrating experience across the video game production cycle, including student, indie, or freelance work" is included under Requirements or Skills? We'll put under Requirements maybe. "Interest in Fortnite, particularly live events and ambitious, narrative-driven content" under Requirements. "Ability to independently troubleshoot problems..." under Skills. "Ability to clearly communicate needs, risks, ideas, scope, and progress to the team" under Skills. "Ability to collaborate effectively across