Senior IT Systems Engineer
Senior IT Systems Engineer · Scape
ScapeWorld Entertainment · Remote
We are recruiting in the EEA, the UK and Switzerland only.
About us
We are Scape, a Swedish game studio of about 30 people, fully remote by choice. We are launching Gravity on Steam Early Access later this year: a precision climbing game where 100 players share one server, one tower, and one long way down. Gravity is the first game inside Scape, a growing platform of multiplayer games where a player's identity carries across all of them; Scape itself follows. Our senior team has shipped and run live games at studios including Arrowhead (Helldivers 2), Avalanche Studios, and Ubisoft.
Our IT is moving to code, piece by piece, and we are looking for the person who drives that with us and still answers when someone is locked out.
The role
Let us start with what IT looks like here. There is no office and no server room. Nearly everything is SaaS, everything signs in through one identity, and we are moving the estate to code: groups, guests, app registrations, DNS and Zero Trust policies increasingly live in Terraform and change through a reviewed pull request, with automation reverting what is changed by hand. Some of it is already there, some is still clickops, some will move and some will stay. Our goal is to automate as much as we can and to bring AI into more and more of our workflows. You look after IT for the whole company, including the team building Lemur, our proprietary multiplayer engine, though nearly everyone you work with day to day is on Scape.
You are the first hire into IT, and you own it. Our technical leadership is your main stakeholder for changes, and where IT overlaps with the rest of management you work it out with them. You report to the Technical Director.
The other half of the job is people. A colleague cannot get into Jira. A new hire starts Monday and needs everything on day one. A partner needs guest access to a board. Those arrive as Teams messages from a fully remote team, and they need someone who reads the problem behind the message, fixes it, and then fixes the reason it happened. If that half of the job is beneath you, this is the wrong seat. If you like it, read on.
In practice, it comes down to three things:
You build. Terraform, PowerShell, pipelines and pull requests are your daily tools. You bring the next piece of clickops under code without breaking what runs, and you look for the manual step that a script or an automation can take over.
You run the desk. Access, onboarding, guests, mailboxes, admin rights, all remote, all through Teams. Fast, friendly, and closed properly, with the cause fixed and not just the symptom.
You keep the admin straight. Every subscription, seat, renewal and invoice is accounted for, on time, in the register. Nothing lapses, nothing is paid twice, and nobody has to chase you.
What you will own
Our IT as code: Terraform and PowerShell, every change a reviewed pull request, drift reverted rather than argued with, the documentation kept true in the same change, and what is still clickops brought under code one deliberate change at a time
Microsoft 365 and Entra ID day to day: accounts set up when HR hands a new starter over to IT, groups, guests, mailboxes and aliases, and the Exchange side the provider cannot reach
All our domains and websites: DNS across every zone, registrations and redirects, and the mail records that decide whether our mail is trusted
Zero Trust through Cloudflare: Access applications, tunnels and device profiles, and who reaches what from where
SSO and integrations: every app signing in through one identity, SAML and SCIM where a tool supports them, and app registrations and admin consent for anything that asks for organisation data. User consent is off by design, so all of it lands with you
Automation and AI in our workflows: finding the manual step, scripting it, wiring the tool in, and pushing what we do with AI further, one workflow at a time
The security posture in practice: multi-factor authentication with no exceptions, credentials only in the vault, and a leaver closed out the same day across every system, tokens included