Senior Software Engineer
Light & Wonder · Raleigh-Durham-Chapel Hill Area · 3 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes Position Summary and Essential Job Functions (list of duties). Also Qualifications (Training and/or Experience, Knowledge, Skills and Abilities). No explicit Benefits, Pay, Schedule. So we should not include those sections. Also we need to avoid repeating job title as heading (not present). Remove boilerplate like EEO statement. Also remove application instructions (none). So we need sections: About the role (maybe from Position Summary?), Responsibilities (Essential Job Functions), Qualifications (Training and/or Experience), Skills (Knowledge, Skills and Abilities). Could also combine Qualifications and Skills? The instruction says use headings for those categories if content exists. We have both Qualifications and Skills sections. So we will output:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes Position Summary and Essential Job Functions (list of duties). Also Qualifications (Training and/or Experience, Knowledge, Skills and Abilities). No explicit Benefits, Pay, Schedule. So we should not include those sections. Also we need to avoid repeating job title as heading (not present). Remove boilerplate like EEO statement. Also remove application instructions (none). So we need sections: About the role (maybe from Position Summary?), Responsibilities (Essential Job Functions), Qualifications (Training and/or Experience), Skills (Knowledge, Skills and Abilities). Could also combine Qualifications and Skills? The instruction says use headings for those categories if content exists. We have both Qualifications and Skills sections. So we will output:
About the role
Design, code, integrate, test, and debug game software for slot machines. Demonstrate a strong understanding of the platform hardware, libraries, and operating system. Provide input on game design and scheduling as it relates to software implementation. Effectively communicate technical requirements to team members. Collaborate with software quality assurance engineers to ensure regulatory compliance and timely product release. Cultivate, maintain, and disseminate internal systems knowledge while providing feedback on platform and tools implementation. Mentor junior engineers in related studios and throughout Game Development. Create or update documentation related to new features, interfaces, and usage. Contribute to in-house development toolset and engineering support. Maintain up-to-date knowledge on new programming methods and technologies. Use Claude Code and Cowork intentionally as part of daily engineering work - coding, debugging, test writing, and documentation. Apply healthy skepticism to AI-generated output: check for invented APIs or methods, subtly incorrect logic, and missed edge cases before work moves to review. Set the standard for how the team verifies AI-assisted work; help others recognize and work around common AI shortcomings rather than taking output at face value. Take a leading role evaluating and adopting agentic coding workflows as they mature, weighing fit against our regulatory constraints.
But we might split responsibilities into list. The Essential Job Functions are a list of duties. So we could put them under Responsibilities as- ... each bullet. Let's extract each bullet:
- Design, code, integrate, test, and debug game software for slot machines.
- Demonstrate a strong understanding of the platform hardware, libraries, and operating system.
- Provide input on game design and scheduling as it relates to software implementation.
- Effectively communicate technical requirements to team members.
- Collaborate with software quality assurance engineers to ensure regulatory compliance and timely product release.
- Cultivate, maintain, and disseminate internal systems knowledge while providing feedback on platform and tools implementation.
- Mentor junior engineers in related studios and throughout Game Development.
- Create or update documentation related to new features, interfaces, and usage.
- Contribute to in-house development toolset and engineering support.
- Maintain up-to-date knowledge on new programming methods and technologies.
- Use Claude Code and Cowork intentionally as part of daily engineering work - coding, debugging, test writing, and documentation.
- Apply healthy skepticism to AI-generated output: check for invented APIs or methods, subtly incorrect logic, and missed edge cases before work moves to review.
- Set the standard for how the team verifies AI-assisted work; help others recognize and work around common AI shortcomings rather than taking output at face value.
- Take a leading role evaluating and adopting agentic coding workflows as they mature, weighing fit against our regulatory constraints.
We can put these under Responsibilities.
About the role could be a brief summary: maybe the Position Summary line: "Position Summary Essential Job Functions:" but we can treat About the role as a short paragraph summarizing role: maybe "Design, code, integrate, test, and debug game software for slot machines." But we already have that as first bullet. To avoid duplication, we could keep About the role as a brief overview: maybe "The role involves designing, coding, integrating, testing, and debugging game software for slot machines, collaborating with QA, mentoring junior engineers, and driving AI-assisted development practices." But we must not invent or summarize away detail; we must preserve ALL substantive information. So we cannot create new summary that omits details. However we can keep the Position Summary as a paragraph and then list responsibilities separately. The Position Summary is: "Position Summary Essential Job Functions: Design, code, integrate, test, and debug game software for slot machines...." Actually the given text: "Position Summary Essential Job Functions: Design, code, integrate, test, and debug game software for slot machines.Demonstrate a strong understanding of the platform hardware, libraries, and operating system.Provide input on game design and scheduling as it relates to software implementation.Effectively communicate technical requirements to team members.Collaborate with software quality assurance engineers to ensure regulatory compliance and timely product release.Cultivate, maintain, and disseminate internal systems knowledge while providing feedback on platform and tools implementation.Mentor junior engineers in related studios and throughout Game Development.Create or update documentation related to new features, interfaces, and usage.Contribute to in-house development toolset and engineering support.Maintain up-to-date knowledge on new programming methods and technologies.Use Claude Code and Cowork intentionally as part of daily engineering work - coding, debugging, test writing, and documentation.Apply healthy skepticism to AI-generated output: check for invented APIs or methods, subtly incorrect logic, and missed edge cases before work moves to review.Set the standard for how the team verifies AI-assisted work; help others recognize and work around common AI shortcomings rather than taking output at face value.Take a leading role evaluating and adopting agentic coding workflows as they mature, weighing fit against our regulatory constraints."
Thus the Position Summary includes all those items. So we could treat the whole block as About the role (paragraph) and not repeat them as list. But the instruction says use
- for any list of duties/requirements/benefits. The duties are a list; we could either keep them as paragraph or list. Better to make list under Responsibilities. Then About the role could be a short summary like "The role focuses on developing game software for slot machines, ensuring regulatory compliance, mentoring junior engineers, and leading AI-assisted development practices." However that would be summarizing and potentially losing detail. But we already have the detail in Responsibilities list, so About the role can be a brief overview without losing detail because details are elsewhere. That's acceptable: we preserve all substantive information either in About the role or Responsibilities. So we can have About the role as a short paragraph summarizing the role (maybe one or two sentences) and then Responsibilities list with all items. That preserves all info.
Qualifications: Training and/or Experience: 5+ years of professional experience in a software development team; 2D and 3D graphics programming experience (Unity or Godot experience is preferred); Gaming industry experience is preferred, but not required.
Knowledge, Skills and Abilities: Proficient in C# or C++ with a strong understanding of object-oriented design concepts; High degree of comfort with software development tools such as IDEs/compilers, debuggers, profilers, and version control systems; Familiarity with working in a Windows programming environment, including Unity and Visual Studio; Enjoy working in a creative environment; Strong multi-tasking skills; Excellent written and verbal communication skills; Ability to work well with others in a team environment; Practical, daily experience with AI coding assistants, with the judgment to catch common failure modes - confident-but-wrong answers, hallucinated functions, outdated patterns - and work around them.; Track record of using AI tools to take on higher-complexity work while maintaining rigorous verification habits; able to coach others on catching AI mistakes early.
We can put Training/Experience under Qualifications heading, and Knowledge, Skills and Abilities under Skills heading. Or combine? The instruction says use headings for those categories if content exists. So we will have:
Qualifications
- 5+ years of professional experience in a software development team
- 2D and 3D graphics programming experience (Unity or Godot experience is preferred)
- Gaming industry experience is preferred, but not required
Skills
- Proficient in C# or C++ with a strong understanding of object-oriented design concepts
- High degree of comfort with software development tools such as IDEs/compilers, debuggers, profilers, and version control systems
- Familiarity with working in a Windows programming environment, including Unity and Visual Studio
- Enjoy working in a creative environment
- Strong multi-tasking skills
- Excellent written and verbal communication skills
- Ability to work well with others in a team environment
- Practical, daily experience with AI coding assistants, with the judgment to catch common failure modes - confident-but-wrong answers, hallucinated functions, outdated patterns - and work around them
- Track record of using AI tools to take on higher-complexity work while maintaining rigorous verification habits; able to coach others on catching AI mistakes early
About the role
This position focuses on developing game software for slot machines, collaborating with QA, mentoring junior engineers, and driving AI-assisted development practices while ensuring regulatory compliance.
Responsibilities
- Design, code, integrate, test, and debug game software for slot machines.
- Demonstrate a strong understanding of the platform hardware, libraries, and operating system.
- Provide input on game design and scheduling as it relates to software implementation.
- Effectively communicate technical requirements to team members.
- Collaborate with software quality assurance engineers to ensure regulatory compliance and timely product release.
- Cultivate, maintain, and disseminate internal systems knowledge while providing feedback on platform and tools implementation.
- Mentor junior engineers in related studios and throughout Game Development.
- Create or update documentation related to new features, interfaces, and usage.
- Contribute to in-house development toolset and engineering support.
- Maintain up-to-date knowledge on new programming methods and technologies.
- Use Claude Code and Cowork intentionally as part of daily engineering work - coding, debugging, test writing, and documentation.
- Apply healthy skepticism to AI-generated output: check for invented APIs or methods, subtly incorrect logic, and missed edge cases before work moves to review.
- Set the standard for how the team verifies AI-assisted work; help others recognize and work around common AI shortcomings rather than taking output at face value.
- Take a leading role evaluating and adopting agentic coding workflows as they mature, weighing fit against our regulatory constraints.
Qualifications
- 5+ years of professional experience in a software development team
- 2D and 3D graphics programming experience (Unity or Godot experience is preferred)
- Gaming industry experience is preferred, but not required
Skills
- Proficient in C# or C++ with a strong understanding of object-oriented design concepts
- High degree of comfort with software development tools such as IDEs/compilers, debuggers, profilers, and version control systems
- Familiarity with working in a Windows programming environment, including Unity and Visual Studio
- Enjoy working in a creative environment
- Strong multi-tasking skills
- Excellent written and verbal communication skills
- Ability to work well with others in a team environment
- Practical, daily experience with AI coding assistants, with the judgment to catch common failure modes - confident-but-w
- for any list of duties/requirements/benefits. The duties are a list; we could either keep them as paragraph or list. Better to make list under Responsibilities. Then About the role could be a short summary like "The role focuses on developing game software for slot machines, ensuring regulatory compliance, mentoring junior engineers, and leading AI-assisted development practices." However that would be summarizing and potentially losing detail. But we already have the detail in Responsibilities list, so About the role can be a brief overview without losing detail because details are elsewhere. That's acceptable: we preserve all substantive information either in About the role or Responsibilities. So we can have About the role as a short paragraph summarizing the role (maybe one or two sentences) and then Responsibilities list with all items. That preserves all info.
Qualifications: Training and/or Experience: 5+ years of professional experience in a software development team; 2D and 3D graphics programming experience (Unity or Godot experience is preferred); Gaming industry experience is preferred, but not required.
Knowledge, Skills and Abilities: Proficient in C# or C++ with a strong understanding of object-oriented design concepts; High degree of comfort with software development tools such as IDEs/compilers, debuggers, profilers, and version control systems; Familiarity with working in a Windows programming environment, including Unity and Visual Studio; Enjoy working in a creative environment; Strong multi-tasking skills; Excellent written and verbal communication skills; Ability to work well with others in a team environment; Practical, daily experience with AI coding assistants, with the judgment to catch common failure modes - confident-but-wrong answers, hallucinated functions, outdated patterns - and work around them.; Track record of using AI tools to take on higher-complexity work while maintaining rigorous verification habits; able to coach others on catching AI mistakes early.
We can put Training/Experience under Qualifications heading, and Knowledge, Skills and Abilities under Skills heading. Or combine? The instruction says use headings for those categories if content exists. So we will have: