Senior Mobile Programmer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
First, "WHAT MAKES US EPIC?" paragraph: 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.
That's about company culture; could be "About Us" maybe but we have "About Us" later. This could be part of "About the role"? Not exactly. Might be considered "About Us". But we only have sections defined; we could put this under "About the role" or maybe "About Us" not in list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. The intro could go under "About the role". Or we could have a separate "About Us" but not allowed. Probably put under "About the role".
Next: "ENGINEERING - GAMES What We Do Unreal projects have been leading the pack of real-time entertainment with our constantly growing team of engineering experts. We’re always improving on the tools and technology that empower content developers worldwide." This is also about role/team. Could be part of About the role.
Then "What You'll Do The Fortnite Technology Team is looking for an experienced Mobile Platform Engineer passionate about creating world-class, industry leading game engine technologies, targeting the full spectrum of the Android and IOS platforms. You'll work with the latest in Unreal software and mobile hardware offerings to design and implement platform APIs, guide cross-platform API development, and create robust platform support as required by the demands of Fortnite as we continue to grow in this market. If you're an experienced engineer looking for an opportunity to grow and contribute to our engine and feature development, we want to talk to you!" This is also role description.
Then "In this role, you will" bullet list:
- Collaborate with a wide variety of Fortnite engineering and content creation teams to solve complex technical challenges in ways that move the stability and quality of Fortnite forward
- Implement and improve various low-level systems that interface with platform APIs, i.e. memory allocators (physical and virtual), file systems, input systems, graphics APIs (Metal and Vulkan), shader compilers, etc.
- Analyze and continuously strive to solve and optimize problems related to a modern game engine (load times, memory usage and platform specific performance issues) and the wide range of content delivered within Fortnite
- Make improvements to platform toolchains, i.e. compiler/linker support, deployment to device, SDK upgrades, platform specific data management tools, debugger integration, crash reporting, etc.
- Help us embrace, support, extend, and enhance our engine for future hardware
These are responsibilities.
Then "What We're Looking For" bullet list:
- Strong programming background and C++ knowledge
- Experience with a broad range of engineering areas in shipping games or real-time visualization systems, with special attention given to low-level code and deep optimization
- Experience developing for Android or IOS-based systems
- Well-versed in software engineering principles
- Familiarity with an existing game engine with an understanding of engine and editor concepts
- Familiarity with development tools and profiling on modern systems, including frame capture and profiling with engine-level and platform-specific tooling
- Experience developing in a large codebase at a fast pace, making trade-offs between usability, performance, and power
- Prior shipped projects with Unreal Engine is a plus
These could be Requirements, Qualifications, Skills. We need to decide mapping.
We have sections: Requirements, Qualifications, Skills. The instruction says prefer a few substantive sections over many thin ones. So we could combine into maybe Requirements (or Qualifications) and Skills. But we need to avoid thin sections.
We could put "What We're Looking For" as Requirements (or Qualifications). Then maybe Skills could be derived from same list? Might be redundant. Better to have one section for Requirements/Qualifications/Skills combined? But we need to follow allowed headings; we can omit sections if no specific content. So we could have only Requirements (or Qualifications) and Skills if we split.
But we need to preserve all substantive information; we can't lose detail. If we combine into one section, we need to choose a heading that fits. Perhaps "Requirements" is appropriate for the list of what they're looking for. Then we could have "Skills" maybe for specific technical skills like C++, Android/iOS, profiling tools, etc. But the list already includes those.
Alternatively, we could have "Qualifications" for education/experience, and "Skills" for technical abilities. But we don't have explicit education.
Given the instruction to prefer few substantive sections, maybe we just have Requirements (or Qualifications) and Skills, and maybe Benefits.
But we also have "About Us" later: "About Us Epic Games is a leading interactive entertainment company..." That could be part of About the role or maybe a separate "About Us" but not allowed. Could be included in About the role.
We also have "EPIC JOB + EPIC BENEFITS = EPIC LIFE" paragraph describing benefits.
We need to output sections: About the role, Responsibilities, Requirements, Benefits. Possibly also Skills if we split.
Let's decide:
- About the role: include introductory paragraphs about Epic, engineering team, what we do, what you'll do (maybe summary). But we already have responsibilities separate. So About the role could be a brief description of the team and role purpose.
- Responsibilities: the bullet list under "In this role, you will".
- Requirements: the bullet list under "What We're Looking For". Could be considered requirements.
- Benefits: the benefits paragraph.
We could also include Skills as separate if we want to highlight technical skills like C++, Android/iOS, profiling, etc. But the requirements list already includes those; splitting might be thin.
Thus we will output:
About the role
... (combined intro)
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
We must not include Pay or Schedule.
Now we need to extract exact prose for About the role without losing detail.
Let's gather the relevant paragraphs:
From start:
"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."
Then "ENGINEERING - GAMES What We Do Unreal projects have been leading the pack of real-time entertainment with our constantly growing team of engineering experts. We’re always improving on the tools and technology that empower content developers worldwide."
Then "What You'll Do The Fortnite Technology Team is looking for an experienced Mobile Platform Engineer passionate about creating world-class, industry leading game engine technologies, targeting the full spectrum of the Android and IOS platforms. You'll work with the latest in Unreal software and mobile hardware offerings to design and implement platform APIs, guide cross-platform API development, and create robust platform support as required by the demands of Fortnite as we continue to grow in this market. If you're an experienced engineer looking for an opportunity to grow and contribute to our engine and feature development, we want to talk to you!"
We could combine these into About the role paragraph(s). Should we keep them as separate elements? Probably each paragraph as
. The instruction: use
for prose. So we can have multiple
under About the role.
Thus:
About the role
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.
ENGINEERING - GAMES What We Do Unreal projects have been leading the pack of real-time entertainment with our constantly growing team of engineering experts. We’re always improving on the tools and technology that empower content developers worldwide.
What You'll Do The Fortnite Technology Team is looking for an experienced Mobile Platform Engineer passionate about creating world-class, industry leading game engine technologies, targeting the full spectrum of the Android and IOS platforms. You'll work with the latest in Unreal software and mobile hardware offerings to design and implement platform APIs, guide cross-platform API development, and create robust platform support as required by the demands of Fortnite as we continue to grow in this market. If you're an experienced engineer looking for an opportunity to grow and contribute to our engine and feature development, we want to talk to you!
But note: The phrase "What You'll Do" maybe belongs to Responsibilities, but we already have responsibilities list. However the paragraph includes a summary of role; we could keep it in About the role. It's okay.
Now Responsibilities: list from "In this role, you will". We'll output each as - .
We need to keep the exact text:
- Collaborate with a wide variety of Fortnite engineering and content creation teams to solve complex technical challenges in ways that move the stability and quality of Fortnite forward
- Implement and improve various low-level systems that interface with platform APIs, i.e. memory allocators (physical and virtual), file systems, input systems, graphics APIs (Metal and Vulkan), shader compilers, etc.
- Analyze and continuously strive to solve and optimize problems related to a modern game engine (load times, memory usage and platform specific performance issues) and the wide
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First, "WHAT MAKES US EPIC?" paragraph: 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. That's about company culture; could be "About Us" maybe but we have "About Us" later. This could be part of "About the role"? Not exactly. Might be considered "About Us". But we only have sections defined; we could put this under "About the role" or maybe "About Us" not in list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. The intro could go under "About the role". Or we could have a separate "About Us" but not allowed. Probably put under "About the role". Next: "ENGINEERING - GAMES What We Do Unreal projects have been leading the pack of real-time entertainment with our constantly growing team of engineering experts. We’re always improving on the tools and technology that empower content developers worldwide." This is also about role/team. Could be part of About the role. Then "What You'll Do The Fortnite Technology Team is looking for an experienced Mobile Platform Engineer passionate about creating world-class, industry leading game engine technologies, targeting the full spectrum of the Android and IOS platforms. You'll work with the latest in Unreal software and mobile hardware offerings to design and implement platform APIs, guide cross-platform API development, and create robust platform support as required by the demands of Fortnite as we continue to grow in this market. If you're an experienced engineer looking for an opportunity to grow and contribute to our engine and feature development, we want to talk to you!" This is also role description. Then "In this role, you will" bullet list: - Collaborate with a wide variety of Fortnite engineering and content creation teams to solve complex technical challenges in ways that move the stability and quality of Fortnite forward - Implement and improve various low-level systems that interface with platform APIs, i.e. memory allocators (physical and virtual), file systems, input systems, graphics APIs (Metal and Vulkan), shader compilers, etc. - Analyze and continuously strive to solve and optimize problems related to a modern game engine (load times, memory usage and platform specific performance issues) and the wide range of content delivered within Fortnite - Make improvements to platform toolchains, i.e. compiler/linker support, deployment to device, SDK upgrades, platform specific data management tools, debugger integration, crash reporting, etc. - Help us embrace, support, extend, and enhance our engine for future hardware These are responsibilities. Then "What We're Looking For" bullet list: - Strong programming background and C++ knowledge - Experience with a broad range of engineering areas in shipping games or real-time visualization systems, with special attention given to low-level code and deep optimization - Experience developing for Android or IOS-based systems - Well-versed in software engineering principles - Familiarity with an existing game engine with an understanding of engine and editor concepts - Familiarity with development tools and profiling on modern systems, including frame capture and profiling with engine-level and platform-specific tooling - Experience developing in a large codebase at a fast pace, making trade-offs between usability, performance, and power - Prior shipped projects with Unreal Engine is a plus These could be Requirements, Qualifications, Skills. We need to decide mapping. We have sections: Requirements, Qualifications, Skills. The instruction says prefer a few substantive sections over many thin ones. So we could combine into maybe Requirements (or Qualifications) and Skills. But we need to avoid thin sections. We could put "What We're Looking For" as Requirements (or Qualifications). Then maybe Skills could be derived from same list? Might be redundant. Better to have one section for Requirements/Qualifications/Skills combined? But we need to follow allowed headings; we can omit sections if no specific content. So we could have only Requirements (or Qualifications) and Skills if we split. But we need to preserve all substantive information; we can't lose detail. If we combine into one section, we need to choose a heading that fits. Perhaps "Requirements" is appropriate for the list of what they're looking for. Then we could have "Skills" maybe for specific technical skills like C++, Android/iOS, profiling tools, etc. But the list already includes those. Alternatively, we could have "Qualifications" for education/experience, and "Skills" for technical abilities. But we don't have explicit education. Given the instruction to prefer few substantive sections, maybe we just have Requirements (or Qualifications) and Skills, and maybe Benefits. But we also have "About Us" later: "About Us Epic Games is a leading interactive entertainment company..." That could be part of About the role or maybe a separate "About Us" but not allowed. Could be included in About the role. We also have "EPIC JOB + EPIC BENEFITS = EPIC LIFE" paragraph describing benefits. We need to output sections: About the role, Responsibilities, Requirements, Benefits. Possibly also Skills if we split. Let's decide: - About the role: include introductory paragraphs about Epic, engineering team, what we do, what you'll do (maybe summary). But we already have responsibilities separate. So About the role could be a brief description of the team and role purpose. - Responsibilities: the bullet list under "In this role, you will". - Requirements: the bullet list under "What We're Looking For". Could be considered requirements. - Benefits: the benefits paragraph. We could also include Skills as separate if we want to highlight technical skills like C++, Android/iOS, profiling, etc. But the requirements list already includes those; splitting might be thin. Thus we will output:
About the role
... (combined intro)
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
elements? Probably each paragraph as
. The instruction: use
for prose. So we can have multiple
under About the role. Thus:
About the role
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.
ENGINEERING - GAMES What We Do Unreal projects have been leading the pack of real-time entertainment with our constantly growing team of engineering experts. We’re always improving on the tools and technology that empower content developers worldwide.
What You'll Do The Fortnite Technology Team is looking for an experienced Mobile Platform Engineer passionate about creating world-class, industry leading game engine technologies, targeting the full spectrum of the Android and IOS platforms. You'll work with the latest in Unreal software and mobile hardware offerings to design and implement platform APIs, guide cross-platform API development, and create robust platform support as required by the demands of Fortnite as we continue to grow in this market. If you're an experienced engineer looking for an opportunity to grow and contribute to our engine and feature development, we want to talk to you!
But note: The phrase "What You'll Do" maybe belongs to Responsibilities, but we already have responsibilities list. However the paragraph includes a summary of role; we could keep it in About the role. It's okay. Now Responsibilities: list from "In this role, you will". We'll output each as