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.