Senior IT Engineer

The role
You are where things stop being stuck.

When our Senior Support Analysts cannot resolve something, it comes to you — and when you cannot resolve it, the question is no longer "who troubleshoots better," it is "what should the standard be." That is a design question for our Architect. Everything short of it is yours.

You are also the person who keeps our customer environments operable and conform ant to standard: correcting drift, executing the complex changes, and — importantly — holding the authority to stop something that would leave the team supporting a mess.

That halt authority is real here. If you can see that a deliverable will generate six months of support pain, we want you to say so and stop it.

What you will do
Keeping things running

Act as the terminal operational escalation point for the Services team

Take technical command during major incidents: direct diagnosis, decide actions, keep leadership informed

Execute complex change beyond established standards, safely, with rollback planned

Remediate environments back to standard and keep them there

Run post-incident reviews that actually change something — a standard, a runbook, an automation

Develop our Tier 2 analysts deliberately, not incidentally

Delivering change
(roughly 40–50% of your time, with a dedicated Implementation Engineer seat planned as this work grows)

Lead migrations, server and cloud transitions, and new customer onboardings

Implement our Workplace OS layers to defined standard

Validate that what gets built can be operated by the team, and hand it over properly

What you bring
Experience

Five or more years supporting and engineering Microsoft environments, with real time in a managed services or multi-customer setting

A track record of owning complex problems end to end, and of executing change in production without incident

Technical depth

Microsoft 365 in depth:
Exchange Online, Teams, SharePoint, Intune, Defender, Purview fundamentals

Entra  Active Directory in depth — hybrid identity, authentication flows, Conditional Access

Windows Server: AD, Group Policy, DNS, DHCP, file services, certificates

Azure infrastructure: virtual machines, networking, storage, backup, Site Recovery, governance and cost

Security in practice: MFA, Conditional Access, endpoint protection, patch and vulnerability management, Zero Trust, CIS familiarity

Networking to a genuine troubleshooting standard. Cisco Meraki and Barracuda are directly relevant.

Power Shell for administration and automation

Backup, continuity, and DR — designing it and proving it works

Valued certifications:
Microsoft endpoint and administrator paths, the SC series, AZ-104 / AZ-305 / AZ-500

How you work

Diagnostic rigour under pressure. Staying systematic when a customer is down and everyone is watching.

Design judgement with standards deference. You know what good looks like and you still choose the standard over your own preference. That combination is rarer than raw skill and matters more to us.

Risk calibration. Blast radius, rollback, and the discipline to stop.

Teaching by default. You leave the team more capable than you found it.

Plain-language translation. Explaining technical reality without condescension and without false comfort.

Interest in automation. You do not have to be a developer. You do have to notice repetition and want it gone.

Why this role, here, now
We are honest about our situation: this seat is currently open, and its absence is being felt. That means two things for you. The work is needed and you will see your impact immediately. And you are joining a team that has just redesigned how it operates specifically so that this role is not the impossible everything-seat it can become elsewhere — escalation and project delivery are explicitly bounded, and a…