Expert Engine Engineer - Treyarch - Los Angeles, CA

We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Let's parse. Job Title: Expert Engine Engineer - Treyarch - Los Angeles, CA (but we don't repeat title as heading). We'll not include title. We have sections: - About the role: The description includes "Treyarch, the studio behind ... is seeking an Expert Engine Engineer to join our Core Engine team. This is an opportunity to help shape the technology..." Also includes location and work schedule: "This role can be based in either our Playa Vista, CA or our Vancouver, BC office and follows an onsite work schedule of four days per week." Also mention "Work arrangements may change..." That's about role. - Responsibilities: The "What You’ll Do…" bullet list. - Requirements/Qualifications/Skills: The "To succeed you should have…" list and "We’d love it if you also have..." list. Could split into Requirements (must-have) and Qualifications/Skills (nice-to-have). But we need to decide sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple of those if content exists. We must not create empty sections. We have: - Requirements: 10+ years experience, deep C++, etc. That's specific. - Qualifications: maybe the "We’d love it if you also have..." could be Qualifications or Skills. Could treat as Skills. - Benefits: The "PS, we’ve also got some pretty amazing office perks and benefits..." plus later "Rewards Requirements" section describing benefits. So we have benefits content. - Pay: The "In the U.S., the standard base pay range for this role is $124,000.00 - $229,400.00 Annual." That's specific pay range. - Schedule: The role mentions "onsite work schedule of four days per week." That's schedule info. Thus we can include sections: About the role, Responsibilities, Requirements, Skills (or Qualifications), Benefits, Pay, Schedule. We must not repeat job title as heading. Also not include Job ID/requisition numbers. We must remove boilerplate: EEO, legal, accommodation, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions. Also remove "Not sure you meet all qualifications? Let us decide!" etc. Also remove "We love hearing from anyone..." etc. Also remove "The videogame industry..." etc. Also remove "About Treyarch" maybe? That's about the studio, could be considered About the role? Actually "About Treyarch" is separate but could be considered part of About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "About Treyarch" is not exactly "About the role". But we could treat that as About the role content (company overview). It's substantive. We'll include it under About the role. We must not include "We are an Equal Opportunity Employer..." etc. Remove. We must not include "General employment questions cannot be accepted..." etc. We must not include "To learn more about our studio..." etc (maybe that's navigation). Remove. We must not include "PS, we’ve also got some pretty amazing office perks and benefits..." but that's benefits, we keep. We must not include the link to benefits site? It's okay to keep as part of benefits description? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we can keep the description of benefits and the link? The link is a URL; it's substantive? Might be considered navigation but it's part of benefits. I'd keep the description but maybe drop the URL as it's just a link. However preserving all substantive info: the URL is info but maybe not essential. Safer to keep the description but maybe drop the URL. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The URL is detail; removing it could be summarizing away. But it's a link; could be considered navigation. I'd keep it as plain text? Might be okay. But we can keep it as part of benefits description. Similarly for Pay: we have the range and note about incentive compensation. Keep. Schedule: we have "onsite work schedule of four days per week." Also mention "Work arrangements may change at the company's discretion to meet business needs." That's schedule-related. Now we need to format lists: Use

• for any list of duties/requirements/benefits. So responsibilities list: bullet points after "What You’ll Do…". Also requirements list: the "To succeed you should have…" list (numbered). We need to convert to
  • . Similarly the "We’d love it if you also have..." list. Benefits: The benefits description includes a list after "Subject to eligibility requirements, the Company offers comprehensive benefits including:" then a long list separated by semicolons. We need to turn that into
    • . Also the later list of paid holidays etc. Could combine? Might be easier to treat the whole benefits paragraph as prose? But instruction: Use
      • for any list of duties/requirements/benefits. So we need to identify lists. The benefits section includes multiple items separated by semicolons. We'll split into list items. Also the "PS, we’ve also got some pretty amazing office perks and benefits, like 20 vacation days and 16 holidays, 10 weeks of family leave, free lunches and snacks at our office, comprehensive healthcare, and more!" That's also a list-ish. Could incorporate. We'll produce sections:

        About the role

        ... (combined description from initial paragraph and About Treyarch)

        Responsibilities

        • Design, implement, refactor, optimize, and debug core runtime engine systems across a large, established C++ codebase.
        • Improve game performance, stability, memory usage, streaming, multithreading, and platform-specific behavior.
        • Profile and optimize runtime systems across supported platforms, including PC and consoles.
        • Investigate complex bugs, crashes, performance issues, and low-level engine problems.
        • Work closely with pipeline, graphics, tools and other engineering teams to deliver robust engine technology.
        • Participate in technical design, code reviews, performance reviews, and long-term engine roadmap discussions.
        • Mentor engineers and provide technical guidance on architecture, debugging, optimization, and best practices.

        Requirements

        • 10+ years of professional software engineering experience, with significant experience in game engine, core systems, or runtime development.
        • Deep C++ expertise and proven ability to work effectively in a large, established codebase.
        • Strong experience designing, debugging, and optimizing core engine or runtime systems.
        • Solid understanding of computer architecture, memory systems, CPU performance, data-oriented optimization, and multithreaded programming.
        • Excellent debugging, profiling, performance analysis, and optimization skills.
        • Experience shipping AAA console and PC titles across multiple platforms.
        • Ability to independently research, prioritize, and solve complex technical problems.
        • Excellent communication and collaboration skills across engineering teams.
        • Passion for writing clean, efficient, reliable, and maintainable code.

        Skills

        • Experience contributing to a proprietary or bespoke internal game engine.
        • Experience with runtime memory systems, streaming technology, asset loading, or platform-level systems.
        • Experience with low-level systems such as I/O, memory management, job systems, task scheduling, or platform abstraction.
        • Strong 3D math and linear algebra skills.
        • Experience with game networking, animation systems, physics, build infrastructure, distributed systems, or async programming.
        • Graphics programming experience on console or PC, including rendering APIs, GPU architecture, or graphics performance analysis.
        • Experience mentoring senior engineers or helping guide technical direction across a team.
        • Multiple shipped AAA titles.

        Benefits

        PS, we’ve also got some pretty amazing office perks and benefits, like 20 vacation days and 16 holidays, 10 weeks of family leave, free lunches and snacks at our office, comprehensive healthcare, and more!

        • Medical, dental, vision, health savings account or health reimbursement account, healthcare spending accounts, dependent care spending accounts, life and AD&D insurance, disability insurance
        • 401(k) with Company match
        • Tuition reimbursement
        • Charitable donation matching
        • Paid holidays and vacation, paid sick time, floating holidays, compassion and bereavement leaves, parental leave
        • Mental health & wellbeing programs, fitness programs, free and discounted games, and a variety of other voluntary benefit programs like supplemental life & disability, legal service, ID protection, rental insurance, and others
        • If the Company requires that you move geographic locations for the job, then you may also be eligible for relocation assistance

        Eligibility to participate in these benefits may vary for part time and temporary full-time employees and interns with the Company. You can learn more by visiting https://www.benefitsforeveryworld.com/

        Pay

        In the U.S., the standard base pay range for this role is $124,000.00 - $229,400.00 Annual. These values reflect the expected base pay range of new hires across all U.S. locations. Ultimately, your specific range and offer will be based on several factors, including relevant experience, performance, and work location. Your Talent Professional can share this role’s range details for your local geography during the hiring process. In addition to a competitive base pay, employees in this role may be eligible for incentive compensation. Incentive compensation is not guaranteed. While we strive to provide competitive offers to successful candidates, new hire compensation is negotiable.

        Schedule

        This role can be based in either our Playa Vista, CA or our Vancouver, BC office and follows an onsite work schedule of four days per week. Work arrangements may change at the company's discretion to meet business needs.

        We need to ensure we didn't include any boilerplate like EEO, legal, etc. We removed those. Check for any leftover boilerplate: The "About Treyarch" paragraph we included? We included only a brief snippet? Actually we didn't include the About Treyarch paragraph explicitly; we only used the initial description. We could add a bit about Treyarch from the "About Treyarch" section. But we might consider that as part of About the role. It's substantive. Let's incorporate a concise version: "Founded in 1996, Treyarch is a videogame studio whose purpose is to create awesome games for the world to enjoy. With this purpose in mind, we crafted the award winning Call of Duty: Black Ops series and pioneered the fan favorite Zombies mode. At Treyarch, we empower the team to be individually driven to innovate on our games, processes, and culture." That's from About Treyarch. We'll add to About the role paragraph. Thus About the role paragraph will combine: "Treyarch, the studio behind the best-selling Call of Duty: Black Ops