Unreal Developer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About The Job (maybe "About the role"): The paragraph after "About The Job": "The Games Analytics team is looking for an Unreal Engine Developer to help grow our new division at SAS and prepare our projects for mature production and deployment pipelines. Join us in our quest to unlock the power of video game engines for analytics and digital twins, build specialized tools and connectors for publishers and studios, and develop new lines of business across the industry. This is a hands-on build role on a small team doing something unusual: real-time 3D in service of analytics. You will ship features into digital twin products used by industrial customers, work directly with the engineers who own the data and simulation layers, and grow your engine depth alongside senior developers who have shipped commercial titles and enterprise simulation software." That's about the role. - Responsibilities: The bullet list after "As a Unreal Engine Developer, You Will". It lists many responsibilities. We'll capture each as
or drop it. Location is minor metadata; we could include a short
maybe after heading? But we should not create a heading for it. Could include a
after the About the role heading? The instruction: "Prefer a few substantive sections over many thin ones." We could embed location in About the role paragraph. But we need to preserve all substantive information; location is substantive? It's location. Could include as a short
after the heading? But we shouldn't create a new heading for it. We could add a
with location after the About the role heading before the responsibilities. That seems okay. Also there is "Additional Information" about legal etc. That's boilerplate; we should remove. Also "Let's stay in touch! Join our Talent Community..." is boilerplate; remove. Also "#SAS #gaming" maybe remove. Now produce HTML:
About the role
Location: Remote in the US or Hybrid in Cary, NC? Actually "Remote in the US or Hybrid in Cary, NC". We'll phrase: "This position is remote within the United States or hybrid at the Cary, NC office." Then the paragraph about the Games Analytics team. Then
Responsibilities
- with each responsibility.
Then
- Build and extend photorealistic digital twin environments in Unreal Engine 5, implementing real-time simulation and visualization of industrial systems, robotic fleets and logistics operations against defined fidelity and performance targets.
- Work with IoT engineers, optimization experts and software architects to connect Unreal Engine visualizations to real-time telemetry, sensor inputs and machine learning output from SAS analytics pipelines.
- Develop and optimize Blueprints and C++ modules supporting simulation logic, physical system behavior and user interaction, including dynamic asset loading and level streaming.
- Integrate and extend Unreal Engine plugins, including our group's own SAS Connector and the third-party plugins used across our digital twin products.
- Profile, diagnose and resolve performance and stability issues using Unreal Insights and the engine's profiling tools, and document findings for the team.
- Follow and help improve team standards for pipeline management and version control (Perforce, Plastic SCM) as the division's practices mature.
- Be encouraged to participate in open-source projects on behalf of SAS.
- Ensure all applicable security policies and processes are followed to support the organization's secure software development goals.
- Embrace curiosity, passion, authenticity and accountability. These are our values and influence everything we do.
- Bachelor's degree in Computer Science or a related field.
Requirements
maybe "Required Qualifications". The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Requirements and Qualifications. Could combine? But we have separate sections: Required Qualifications and Additional Competencies... The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications headings if content exists. We'll put Required Qualifications under Qualifications
. And Additional Competencies... under Skills
. Also maybe Requirements could be same as Qualifications? But we have both; we can put Required Qualifications under Qualifications, and maybe Requirements could be empty; better not to create empty heading. So we will not include Requirements heading if we don't have separate content. We'll just have Qualifications and Skills.
Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits.
Now extract content precisely.
Responsibilities list (from "As a Unreal Engine Developer, You Will"):
- Build and extend photorealistic digital twin environments in Unreal Engine 5, implementing real-time simulation and visualization of industrial systems, robotic fleets and logistics operations against defined fidelity and performance targets.
- Work with IoT engineers, optimization experts and software architects to connect Unreal Engine visualizations to real-time telemetry, sensor inputs and machine learning output from SAS analytics pipelines.
- Develop and optimize Blueprints and C++ modules supporting simulation logic, physical system behavior and user interaction, including dynamic asset loading and level streaming.
- Integrate and extend Unreal Engine plugins, including our group's own SAS Connector and the third-party plugins used across our digital twin products.
- Profile, diagnose and resolve performance and stability issues using Unreal Insights and the engine's profiling tools, and document findings for the team.
- Follow and help improve team standards for pipeline management and version control (Perforce, Plastic SCM) as the division's practices mature.
- Be encouraged to participate in open-source projects on behalf of SAS.
- Ensure all applicable security policies and processes are followed to support the organization's secure software development goals.
- Embrace curiosity, passion, authenticity and accountability. These are our values and influence everything we do.
Note: last bullet is a bit different; still include.
Now Qualifications list:
- Bachelor's degree in Computer Science or a related field.
- Minimum 5 years of professional experience developing interactive 3D applications with Unreal Engine, including proficiency in both Blueprints and C++.
- Experience taking at least one real-time 3D or simulation project from prototype through to release.
- Working knowledge of integrating external data into real-time applications using JSON, REST, WebSocket or MQTT.
- Experience working in a team-based content pipeline under version control (Perforce, Plastic SCM or Git).
- Equivalent combination of related education, training and experience may be considered in place of the above qualifications.
Now Skills list (Additional Competencies, Knowledge And Skills):
- Technical/Professional Knowledge & Skills – Applies engine and programming expertise to complete work effectively, and keeps current with developments in real-time 3D.
- Collaborating – Works cooperatively with engineers, artists and analysts to help the team achieve its goals; communicates clearly about progress and blockers.
- Continuous Learning – Actively identifies new areas for learning, and applies newly gained knowledge and skill on the job.
- Experience with Unreal Engine server/client architecture and network replication.
- Exposure to digital twin, industrial simulation or enterprise visualization projects.
- Familiarity with analytics or streaming data concepts, or interest in learning SAS products such as CI360, Intelligent Decisioning or Event Stream Processing.
- Game industry experience, or a portfolio of shipped titles or interactive experiences.
Now Benefits list (World-class Benefits Highlights include...):
- Comprehensive medical, prescription, dental and vision plans.
- Medical plan options include:
- PPO with low annual deductible and copays.
- HDHP combined with a health savings account with a contribution from SAS (no access to on-site health care center).
- Onsite Health Care Center (HQ) that’s free to employees and family members enrolled in the PPO plan. There's a pharmacy too!
- Not local to HQ? The pharmacy will ship prescriptions for no additional charge!
- An industry-leading 401k plan.
- Tuition Assistance Program and programs and resources to support your development.
- Generous time away including vacation time, a variety of paid holidays, and our much-loved U.S. Winter Wellness Break between December 25 and January 1.
- Volunteer Time Off, parental leave and unlimited paid sick days.
- Generous childcare benefits for all full-time employees.
- You are welcome here. At SAS, it’s not about fitting into our culture – it’s about adding to it. We believe our people make the difference. Our inclusive workforce brings together unique talents and inspires teams to create amazing software that reflects the diversity of our users and customers.
We need to keep as list items. Some are sub-items; we can flatten.
Now location paragraph: We'll include a short
after About the role heading: "This position is remote within the United States or hybrid at the Cary, NC office." Now ensure we don't include any boilerplate like "We’re a leader in data and AI..." That's introductory fluff; maybe considered boilerplate? It's about company; but it's not specific to role. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The introductory paragraph about company might be considered boilerplate? It's not navigation/legal/EEO, but it's generic marketing. Might be considered not substantive to the job. However we need to preserve ALL substantive information; does that include company description? It's not directly about the job but could be considered fluff. The instruction says "Prefer a few substantive sections over many thin ones." The company description could be considered thin. I'd lean to omit it because it's not specific to the role. The "About The Job" section is the substantive description. So we can omit the initial fluff. Thus final HTML:
About the role
This position is remote within the United States or hybrid at the Cary, NC office.
The Games Analytics team is looking for an Unreal Engine Developer to help grow our new division at SAS and prepare our projects for mature production and deployment pipelines. Join us in our quest to unlock the power of video game engines for analytics and digital twins, build specialized tools and connectors for publishers and studios, and develop new lines of business across the industry. This is a hands-on build role on a small team doing something unusual: real-time 3D in service of analytics. You will ship features into digital twin products used by industrial customers, work directly with the engineers who own the data and simulation layers, and grow your engine depth alongside senior developers who have shipped commercial titles and enterprise simulation software.