Build And Release Engineer

Job Details:

Role Name : Build Reliability Engineer

Type : Contract – Inside IR35

Location : Atherstone, UK

Hybrid/Remote : Remote (Need onsite while onboarding)

Start Date : ASAP

Duration : 18 months

Job Description:

Role Overview

The Build Reliability Engineer (Operational / Support Focused) is a front line, operational role responsible for monitoring and supporting the health of the build farm. This role acts as the first point of contact when builds fail, focusing on triage, investigation, and clear communication rather than designing or rebuilding CI/CD systems.

The emphasis is on observing build outputs, identifying failure patterns, diagnosing issues, and feeding actionable insights back to engineering teams so problems can be resolved quickly and efficiently. This is a hands on support role, not a CI/CD pipeline engineering position.

This role is:

• Operational and support oriented

• Focused on monitoring, triage, investigation, and reporting

• Embedded in the build farm day to day

• Front line support for developers across disciplines

This role is NOT:

• A CI/CD engineer role

• Responsible for designing or rebuilding pipelines

• Continuously driving large scale CI/CD improvements

• A senior or architectural position

Skills & Experience Required

• Ideally 3–5 years experience in a build support, build engineering, or operational reliability role

• Strong understanding of how build farms and build pipelines operate

• Experience monitoring and triaging build failures

• Comfortable analysing logs and build outputs

• Familiarity with automated builds and basic testing concepts

• Some exposure to debugging and coding (C# and/or C++) to understand failure causes

• Strong analytical and problem solving skills

• Able to communicate issues clearly to both technical and non technical audiences

• Comfortable operating in a support driven, fast response environment

Tools & Technologies

(Experience in any 2 of the following is sufficient)

• CI / Build Systems: TeamCity (monitoring and operational usage, not pipeline ownership)

• Source Control: Perforce

• Game Engines: Unreal Engine 4 / 5

• Deep CI/CD configuration or pipeline design experience is not required.

What Success Looks Like

• Build failures are identified and triaged quickly

• Clear, actionable information is provided back to engineering teams

• Recurring issues are spotted early through pattern recognition

• Developers trust the build support function

• Build stability improves through operational insight rather than system redesign

Thanks.