Senior Technical QA

This is a contractor role through X-Team. You will join the client's centralized Unreal Engine team, which supports multiple internal game teams with shared engine tools, plugin compatibility and client-backend integrations. Because the team manages foundation-level technology for several connected titles, robust validation, fast engine-level debugging and automated regression testing keep things working for both developers and players. Embedded in the central engine domain, you will own quality validation gates for major Unreal Engine upgrades (UE4 and UE5), ensure shared plugin compatibility and validate client-server API integrations. You will troubleshoot cook and package failures, inspect call stacks and crash dumps, and integrate automated test suites into CI/CD pipelines.

Must have

• 5+ years of Technical QA or SDET experience inside Unreal Engine 4 and/or 5, with deep knowledge of modules, build systems, asset pipelines and cook/package execution.
• Able to read, debug and write C++ alongside Blueprints to troubleshoot low-level engine bugs.
• Direct experience building automated test suites with Unreal Automation Framework or Gauntlet, with CI/CD tools (Jenkins or GitHub Actions) and source control (Perforce or Git).
• Strong diagnostics: parsing call stacks, analyzing crash logs and profiling with tools such as Unreal Insights.
• Hands-on experience testing client-server systems, network replication and third-party REST API integrations, including the client's public game data APIs.
• Minimum 6 hours of daily overlap with US Pacific Time.

Nice to have

• Experience supporting central tech, platform or core engine teams serving multiple game projects at once.
• Multi-platform testing across consoles (Xbox Series X, PS5) and mobile (iOS, Android).
• Python or Bash scripting for custom build-validation tools.
• Exposure to live-service online gaming architectures and high-volume backend integrations.

Who does well here

• Thinks like a game developer and a defender of quality: cares whether the engine builds cleanly, and cares more about whether game teams can iterate without blockers.
• Runs toward broken builds. When a cook fails or an upgrade introduces a regression, pulls up the crash logs and fixes the actual problem.
• Prefers reliable automated tools, clean CI pipelines and shared knowledge over rigid manual gatekeeping.
• Stays grounded when complex C++ crashes and plugin bugs hit, treating them as practical puzzles.