Senior Rendering Programmer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - Intro about Epic: "WHAT MAKES US EPIC?" etc. That's about company culture. Could be "About Us" but not required heading. We can include maybe "About the role" section? The posting includes "What You'll Do" which is responsibilities. Also "What We're Looking For" which is requirements/qualifications/skills. Also "EPIC JOB + EPIC BENEFITS = EPIC LIFE" which describes benefits. Also "About Us" at end. We need to avoid repeating job title as heading. No Job ID. We need to remove boilerplate: EEO, recruitment agency note, etc. We need to preserve all substantive info. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could be a brief description of the role: maybe from "What You'll Do" intro? Actually "What You'll Do" is responsibilities. "About the role" could be a summary: maybe from "The Fortnite Desktop team is seeking an experienced Senior Rendering Engineer..." That's role description. We'll put that in About the role. - Responsibilities: list of duties from "What You'll Do" bullet points (the long list). We'll extract each duty as

. - Requirements: maybe "What We're Looking For" includes strong C++ knowledge etc. Could be requirements. - Qualifications: maybe overlapping; but we can split: Requirements = technical skills, Qualifications = experience? However we need to avoid thin sections. Better to combine? But instructions: use headings only if posting has real specific content for it. We could have Requirements and Qualifications both with content. Let's see. "What We're Looking For" includes: - Strong C++ knowledge and multi-threaded programming techniques; ability to code and architect various core engine systems - Real-time rendering experience in the games industry or for the computer graphics industry: knowledge of at least one graphics API (DirectX 12 preferred) and a general understanding of modern graphics API architecture - Experience in profiling and optimizing a large codebase - Demonstrated ability to reason about and debug large, interacting systems from macro to micro level - Experience with OS-level systems, Windows APIs, and common frameworks is a plus These could be Requirements or Qualifications. We could put them under Requirements. Qualifications maybe empty; we should not create empty heading. So we omit Qualifications. Skills: maybe we could list specific skills like C++, multi-threaded, DirectX 12, profiling, debugging, OS-level, Windows APIs. Could be separate but we already have them in Requirements. Could create Skills section listing those. But we need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put same info in two sections, that's duplication but not invented. Might be okay but could be considered redundant. Better to have one section for requirements/qualifications/skills combined? But they ask to use those headings if content exists. We could assign: - Requirements: Strong C++ knowledge, multi-threaded programming, ability to code and architect core engine systems. - Qualifications: Real-time rendering experience, knowledge of graphics API (DirectX 12 preferred), understanding of modern graphics API architecture, experience profiling/optimizing large codebase, ability to reason/debug large interacting systems. - Skills: Experience with OS-level systems, Windows APIs, common frameworks (plus maybe others). But that seems splitting arbitrarily; but we have content for each. Alternatively, we could combine Requirements and Qualifications into one section called "Requirements" and omit Qualifications and Skills. But the instruction says to include a section ONLY when the posting has real, specific content for it. It doesn't forbid omitting some headings. So we can choose to include only those sections that have distinct content. Let's see what distinct content we have: - About the role: description of team and role. - Responsibilities: list of duties. - Requirements/Qualifications/Skills: all from "What We're Looking For". Could be split but we could just put all under "Requirements". That would capture all. Then we don't need Qualifications or Skills. - Benefits: from "EPIC JOB + EPIC BENEFITS = EPIC LIFE": medical, dental, vision HRA, long term disability, life insurance, 401k with match, mental well-being program, events, paid breaks, unlimited PTO and sick time, paid sabbatical after 7 years. - Pay: Not mentioned explicitly. No salary info. So we should NOT create Pay section. - Schedule: Not mentioned. No schedule info. So omit. Thus sections: About the role, Responsibilities, Requirements, Benefits. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive info; not invent or summarize away detail. So we need to include all details from the posting. Let's extract: About the role prose: Could be combination of first paragraphs: "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." Also maybe "ENGINEERING - UNREAL ENGINE What We Do Unreal-powered projects have been on the bleeding edge of real-time entertainment for over 20 years. Our team of engineering experts are always innovating to improve the tools and technology that empower content developers worldwide." That's about the team. Could be included. But we need to avoid duplication; we can put a concise prose summarizing the role: "The Fortnite Desktop team is seeking an experienced Senior Rendering Engineer to enhance the player experience on PC. You will work with other engineers and directly contribute to building and improving our Desktop platform support to an industry-leading state. This role is the perfect opportunity to work on the rendering systems that power Fortnite's visuals." That's from "What You'll Do" intro. That seems appropriate for About the role. Let's craft About the role

  containing that sentence plus maybe the earlier Epic culture description? The instruction: preserve ALL substantive information; we should not omit any. If we omit the Epic culture description, we lose substantive info. So we need to include that somewhere. Could be in About the role as well, or maybe we could add another section like "About Us" but not in allowed headings. Since only allowed headings are those list, we might need to fit the Epic culture description into About the role or Responsibilities etc. Probably About the role is appropriate to include company overview. Thus About the role

  could contain: Epic's success description, the engineering team description, and the role seeking sentence. We must not invent; just copy. Let's extract exact text blocks: From posting: "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. ENGINEERING - UNREAL ENGINE What We Do Unreal-powered projects have been on the bleeding edge of real-time entertainment for over 20 years. Our team of engineering experts are always innovating to improve the tools and technology that empower content developers worldwide. What You'll Do The Fortnite Desktop team is seeking an experienced Senior Rendering Engineer to enhance the player experience on PC. You will work with other engineers and directly contribute to building and improving our Desktop platform support to an industry-leading state. This role is the perfect opportunity to work on the rendering systems that power Fortnite's visuals." We can combine these into About the role. Now Responsibilities: The bullet list after "You will improve existing features and systems and design new ones to ensure the best player experience across a wide variety of hardware and software configurations. In this role, you will" then a list: - Analyze and resolve stability and performance problems of Fortnite on a wide range of PC hardware configurations; this includes identifying solutions in such areas as: - Solving device-specific CPU and GPU performance and compatibility issues - Rendering performance and device compatibility, including the shader pipeline - Improving rendering systems and optimizing their stability and performance across various graphics APIs - Improvements in low-level systems that interface with platform APIs, i.e., memory allocators (physical and virtual), file systems, and input systems - Monitor stability and performance data from Fortnite releases and improve Unreal Engine’s systems and applications in Fortnite-specific use cases - Work with GPU vendors and other partners to resolve technical issues and collaborate on improving underlying technologies, such as graphics drivers for Fortnite and Unreal Engine - Assess performance data across various hardware and improve Unreal Engine’s rendering systems and applications in Fortnite-specific use cases - Collaborate with a variety of other Epic teams, such as Unreal Engine’s Rendering Architecture team, to help them solve complex technical challenges in ways that move the stability and quality of Fortnite and our internal products forward We need to preserve all. We'll output as

  • each item. The first bullet "Analyze and resolve stability and performance problems..." is a top-level; then sub-items under it. We could flatten? The instruction: use
    • for any list of duties/requirements/benefits. Could nest lists but simpler to make each as separate
    • . We'll include all distinct duties. Thus list items: 1. Analyze and resolve stability and performance problems of Fortnite on a wide range of PC hardware configurations; this includes identifying solutions in such areas as: (maybe we keep as part of item, then sub-items separate? Could be confusing. Better to keep as separate items: "Analyze and resolve stability and performance problems of Fortnite on a wide range of PC hardware configurations" and then each sub-item as separate. But the sub-items are part of identifying solutions. We'll keep them separate for clarity. Thus: - Analyze and resolve stability and performance problems of Fortnite on a wide range of PC hardware configurations - Solve device-specific CPU and GPU performance and compatibility issues - Address rendering performance and device compatibility, including the shader pipeline - Improve rendering systems and optimize their stability and performance across various graphics APIs - Make improvements in low-level systems that interface with platform APIs, i.e., memory allocators (physical and virtual), file systems, and input systems - Monitor stability and performance data from Fortnite releases and improve Unreal Engine’s systems and applications in Fortnite-specific use cases - Work with GPU vendors and other partners to resolve technical issues and collaborate on improving underlying technologies, such as graphics drivers for Fortnite and Unreal Engine - Assess performance data across various hardware and improve Unreal Engine’s rendering systems and applications in Fortnite-specific use cases - Collaborate with a variety of other Epic teams, such as Unreal Engine’s Rendering Architecture team, to help them solve complex technical challenges in ways that move the stability and quality of Fortnite and our internal products forward - Improve existing features and systems and design new ones to ensure the best player experience across a wide variety of hardware and software configurations We also have "You will improve existing features and systems and design new ones to ensure the best player experience across a wide variety of hardware and software configurations." That's before the