At Charged Monkey, we are a team of talented and experienced game makers. Our ambitions are huge, and only a world-class team could achieve them. To date, we’ve built a team of incredibly talented individuals from all over the world, who together are bringing industry-defining games to life.

We are seeking an experienced Senior UNITY Systems Engineer to join a Developer Experience team.
This position is based in Prague or Bratislava on a hybrid or remote basis. Candidates from other countries are also welcome, however relocation to one of our employing entities is required. 

In partnership with SCOPELY, one of the biggest gaming studios worldwide (known for IPs like Star Trek™ Fleet Command, MONOPOLY GO!, etc.), we are in the early stages of development on an ambitious, unannounced, cross-platform Strategy/MMO title.

A project of this scale needs more than great game engineers. It needs someone making sure those engineers can actually work. We have a small Developer Experience team focused on exactly that: remove friction, reduce cognitive burden, make doing the right thing easy. We want you on this team, focused entirely on Unity.

Our project is big. Hundreds of assemblies, complex package trees, a content pipeline that never stops growing. When domain reloads creep up, when a package upgrade quietly breaks half the project, when the editor stutters and nobody knows why, you’re the person who digs in and untangles it.

This is not a gameplay role. You won’t be building combat systems or UI. You’ll be making it possible for a large team to iterate faster, encounter fewer surprises, and spend their time on the game instead of fighting the editor.

What You Will Do  

• Hunt down and fix the things that slow people down in Unity: domain reload time, import performance, asset pipeline bottlenecks, editor startup, anything that makes developers wait.
• Steward the project’s Unity configuration: assembly definitions, package dependencies, scripting backend settings, editor preferences. Catch problems before they cascade across the team.
• Spot regressions and surface patterns from Unity’s log files and diagnostics. Build tooling to catch issues before a human notices.
• Build tools and automation: project structure validation, bad-pattern detection, environment health checks, dependency untangling.
• Talk to developers. Understand their real workflows, not just the ones in the wiki. Document what you learn so the team doesn’t keep rediscovering the same traps.
• Anticipate problems. When a Unity upgrade is coming or a new package is being adopted, you’re already thinking about what might break and how to test it first.

• Deep experience with Unity’s internals: asset pipeline, domain reload, assembly definitions, package manager, serialization, scripting backends (Mono, IL2CPP). You’ve diagnosed the problems most people work around – mysterious recompile loops, import thrashing, broken asmdef graphs, editor slowdowns nobody can reproduce on their own machine.
• C# and Unity’s scripting ecosystem, including editor scripting and custom tooling.
• Scripting and automation skills (Python, Bash, or similar) for building tools that other engineers actually use.
• Clear written communication. Your documentation, announcements, and commit messages are detailed and actionable.
• A service-oriented mindset. Motivated by making others productive. Would rather teach someone to diagnose a problem than just fix it for them.
• 6+ years in game development or a similarly complex production environment.

Seniority here is about depth of judgment, not just tenure.