Product Management Intern
for section headings. Use - for lists. Use
for prose.
We need to decide sections:
- About the role: could combine the introductory description about Epic and product management intern role? The posting has "WHAT MAKES US EPIC?" and then description of Epic, then "PRODUCT MANAGEMENT What We Do" and then "PRODUCT MANAGEMENT INTERN What You'll Do". That's role description. So we can put that under About the role.
- Responsibilities: bullet list under "What You'll Do" (the list starting with Define scoped product improvements...). That's responsibilities.
- Requirements / Qualifications: bullet list under "What We're Looking For". Could be Requirements.
We could also have a section "About the company" maybe not required but we could include as 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. So we should map content to those headings.
Thus we need About the role: description of role and company.
Responsibilities: bullet list.
Requirements: bullet list (maybe combine Requirements and Qualifications). Could we have both Requirements and Qualifications sections? The posting has "What We're Looking For" which includes both qualifications and skills. Could split into Requirements (education/experience) and Skills (technical aptitude, communication). But we can just put all under Requirements (or Qualifications). Safer to have one section: Requirements.
We should not create Skills section unless we have specific skills list; we could extract skills from bullet list: technical aptitude, communication, problem-solving, etc. But we could also just put them in Requirements.
We must not create empty sections.
Thus output:
About the role
... prose ...
Then Responsibilities
- ... each bullet ...
Then Requirements
- ... each bullet ...
We need to preserve all substantive information: include the intro paragraphs about Epic, product management, etc. Also include the note about flexible start date 2027, recruitment ongoing, legal authorization, link to early careers? That's maybe application instruction; we should remove. But the instruction says remove application instructions. The line "For more information about Epic’s Early Career Program, visit epicgames.com/earlycareers." is more like info; but could be considered application instruction. Safer to remove.
Also remove the EEO policy line and note to recruitment agencies.
Also remove duplicated lines? Not seeing duplicates.
We need to preserve the sentence: "This internship has a flexible start date in 2027. Recruitment will be ongoing until teams find an ideal match. Applicants must be legally authorized to work in the posting location for the duration of the internship." This is substantive info about internship logistics; not exactly application instruction but could be considered. It's not boilerplate; it's details about the internship. Should we keep? Probably yes, as it's substantive. It's not a heading; we can put it in About the role paragraph.
Also preserve "About Us" description of Epic. That's also substantive.
Thus About the role paragraph will include:
- WHAT MAKES US EPIC? 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.
- PRODUCT MANAGEMENT What We Do Product Management partners with game development, publishing, marketing, and platform teams to provide a data and market-driven view of product strategy that aligns with business goals. As part of Epic’s Growth Team, we use our product expertise to identify and drive growth levers to grow our player base and business.
- PRODUCT MANAGEMENT INTERN What You'll Do We are building Discover Publish Tooling to help our creators and partners manage and publish their content. As a Technical Product Manager Intern, you will help define and ship improvements to this tooling and get hands-on experience taking a product idea from problem definition through delivery. You'll work closely with engineers, the product lead, and the operators who use the tool every day to understand problems, write clear requirements, make scope tradeoffs, and test what gets built. Along the way, you'll learn from an experienced product manager and gain hands-on experience with the tools, processes, and practices used to build high-quality products. By the end of the internship, you'll have shipped a real product improvement that our partners use.
- Then the internship logistics: flexible start date 2027, recruitment ongoing, legal authorized.
- About Us: Epic Games is a leading interactive entertainment company... etc.
We need to ensure we don't repeat the job title as a heading (the page already shows it). So we don't add a heading for "Product Management Intern". Good.
Now format.
We need to ensure we don't include any markdown fences.
Let's craft the HTML.
First, About the role: combine paragraphs into maybe multiple tags. It's okay to have multiple
under same heading.
We'll output:
About the role
WHAT MAKES US EPIC? 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.
PRODUCT MANAGEMENT What We Do Product Management partners with game development, publishing, marketing, and platform teams to provide a data and market-driven view of product strategy that aligns with business goals. As part of Epic’s Growth Team, we use our product expertise to identify and drive growth levers to grow our player base and business.
PRODUCT MANAGEMENT INTERN What You'll Do We are building Discover Publish Tooling to help our creators and partners manage and publish their content. As a Technical Product Manager Intern, you will help define and ship improvements to this tooling and get hands-on experience taking a product idea from problem definition through delivery. You'll work closely with engineers, the product lead, and the operators who use the tool every day to understand problems, write clear requirements, make scope tradeoffs, and test what gets built. Along the way, you'll learn from an experienced product manager and gain hands-on experience with the tools, processes, and practices used to build high-quality products. By the end of the internship, you'll have shipped a real product improvement that our partners use.
This internship has a flexible start date in 2027. Recruitment will be ongoing until teams find an ideal match. Applicants must be legally authorized to work in the posting location for the duration of the internship.
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! Epic Games deeply values diverse teams and an inclusive work culture, and we are proud to be an Equal Opportunity employer.
But note we should remove EEO boilerplate. The last sentence includes "Epic Games deeply values diverse teams and an inclusive work culture, and we are proud to be an Equal Opportunity employer." That's EEO related; might be considered boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove that sentence. Also remove "Learn more about our Equal Employment Opportunity (EEO) Policy here." which we already didn't include. So we need to cut the EEO sentence.
Thus About Us paragraph ends before that sentence. We can end at "Like what you hear? Come be a part of something Epic!" That's fine.
Now Responsibilities: list the bullet points under What You'll Do after the paragraph. The bullet points are:
- Define scoped product improvements for Discover by writing clear requirements, user flows, and acceptance criteria with guidance from the product lead
- Take a scoped product improvement from problem definition through build, testing, and delivery, with support from an experienced product mentor
- Talk to the operators and partners who use our solutions to understand their workflows and turn pain points into actionable requirements
- Use data such as usage metrics, dashboards, and spreadsheet or SQL analysis to size problems, inform prioritization, and measure whether shipped features work
- Test features before release, give structured feedback to engineers, and help coordinate and communicate releases to stakeholders
- Learn and apply team product practices, tools, and processes
We need to preserve all. So - each.
Now Requirements: bullet list under What We're Looking For:
- Currently enrolled in, or recently graduated from, a
for prose. We need to decide sections: - About the role: could combine the introductory description about Epic and product management intern role? The posting has "WHAT MAKES US EPIC?" and then description of Epic, then "PRODUCT MANAGEMENT What We Do" and then "PRODUCT MANAGEMENT INTERN What You'll Do". That's role description. So we can put that under About the role. - Responsibilities: bullet list under "What You'll Do" (the list starting with Define scoped product improvements...). That's responsibilities. - Requirements / Qualifications: bullet list under "What We're Looking For". Could be Requirements. We could also have a section "About the company" maybe not required but we could include as 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. So we should map content to those headings.
Thus we need About the role: description of role and company.
Responsibilities: bullet list.
Requirements: bullet list (maybe combine Requirements and Qualifications). Could we have both Requirements and Qualifications sections? The posting has "What We're Looking For" which includes both qualifications and skills. Could split into Requirements (education/experience) and Skills (technical aptitude, communication). But we can just put all under Requirements (or Qualifications). Safer to have one section: Requirements.
We should not create Skills section unless we have specific skills list; we could extract skills from bullet list: technical aptitude, communication, problem-solving, etc. But we could also just put them in Requirements.
We must not create empty sections.
Thus output:
About the role
... prose ...
ThenResponsibilities
- ... each bullet ...
Requirements
- ... each bullet ...
tags. It's okay to have multiple
under same heading. We'll output:
About the role
WHAT MAKES US EPIC? 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.
PRODUCT MANAGEMENT What We Do Product Management partners with game development, publishing, marketing, and platform teams to provide a data and market-driven view of product strategy that aligns with business goals. As part of Epic’s Growth Team, we use our product expertise to identify and drive growth levers to grow our player base and business.
PRODUCT MANAGEMENT INTERN What You'll Do We are building Discover Publish Tooling to help our creators and partners manage and publish their content. As a Technical Product Manager Intern, you will help define and ship improvements to this tooling and get hands-on experience taking a product idea from problem definition through delivery. You'll work closely with engineers, the product lead, and the operators who use the tool every day to understand problems, write clear requirements, make scope tradeoffs, and test what gets built. Along the way, you'll learn from an experienced product manager and gain hands-on experience with the tools, processes, and practices used to build high-quality products. By the end of the internship, you'll have shipped a real product improvement that our partners use.
This internship has a flexible start date in 2027. Recruitment will be ongoing until teams find an ideal match. Applicants must be legally authorized to work in the posting location for the duration of the internship.
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! Epic Games deeply values diverse teams and an inclusive work culture, and we are proud to be an Equal Opportunity employer.
But note we should remove EEO boilerplate. The last sentence includes "Epic Games deeply values diverse teams and an inclusive work culture, and we are proud to be an Equal Opportunity employer." That's EEO related; might be considered boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove that sentence. Also remove "Learn more about our Equal Employment Opportunity (EEO) Policy here." which we already didn't include. So we need to cut the EEO sentence. Thus About Us paragraph ends before that sentence. We can end at "Like what you hear? Come be a part of something Epic!" That's fine. Now Responsibilities: list the bullet points under What You'll Do after the paragraph. The bullet points are: - Define scoped product improvements for Discover by writing clear requirements, user flows, and acceptance criteria with guidance from the product lead - Take a scoped product improvement from problem definition through build, testing, and delivery, with support from an experienced product mentor - Talk to the operators and partners who use our solutions to understand their workflows and turn pain points into actionable requirements - Use data such as usage metrics, dashboards, and spreadsheet or SQL analysis to size problems, inform prioritization, and measure whether shipped features work - Test features before release, give structured feedback to engineers, and help coordinate and communicate releases to stakeholders - Learn and apply team product practices, tools, and processes We need to preserve all. So- each. Now Requirements: bullet list under What We're Looking For: - Currently enrolled in, or recently graduated from, a