Engineering & Technology - IT
IT Systems Engineer
IC / Practitioner
Independently auditedKeeps the company's people productive and its corporate systems secure. Owns a defined area of the function and the outcomes it produces.
Audited package
Built, independently audited role package. Everything on this page is written for this seat.
Your Stack (Swappable)
This role works against whatever tools you already run. We list the tool categories the role operates in, never a named vendor, so you are never asked to replace a system that works.
- Identity & Access (SSO/IAM)
- Endpoint & Device (MDM/UEM)
- Cloud Infrastructure & IaC
- Automation / scripting
- IT Ops (RMM/Asset/Backup)
- Observability & Monitoring
- ITSM / Service Desk
Deliverables
- Support resolutions and runbooks
- Access review evidence
- Asset and licence records
- IT standards and policies
Responsibilities
- Build, configure, and maintain internal systems - servers, virtualization, directory / identity, endpoints, and core internal services - to a defined quality standard, and close the loop on dependencies, decisions, and corrective work
- Produce access-provisioning workflows (joiner-mover-leaver) and automation scripts with explicit acceptance criteria, owners, and review dates, provisioning to least privilege
- Maintain the identity platform and endpoint / device management (MDM) as reliable operating records - correcting stale ownership, missing evidence, and configuration drift
- Run patch and configuration management across the estate on a tested, staged cadence with a rollback path, treating every patch as a change that can break
- Own backups and recovery - and prove them by restoring, not by assuming; keep recovery objectives (RPO / RTO) honest
- Monitor system uptime, ticket-resolution time, and automation coverage, and investigate a change far enough to name the cause, the affected workflow, and the required action
- Take escalations from IT support that exceed frontline break/fix, and hand back runbooks so support can self-serve next time
- Coordinate with employees, the security team, application owners, and IT support on inputs, decisions, and handoffs so configurations complete without avoidable rework
The essence of this seat
The IT Systems Engineer owns internal systems administration, automation, and reliable employee technology services - the builder who keeps the company's own IT running at scale.
Signature move
Build it so another engineer can rebuild it. The first move on any build or fix is to make it repeatable and documented - a scripted / golden-image / infrastructure-as-code path plus a runbook - not a hand-configured snowflake; if it only lives in your head, it is not done
What good looks like
runs JML as a lifecycle to least privilege (group/role-based, [SCIM]-driven), treats the mover as a re-baseline not an append, fully deprovisions leavers (sessions/tokens/licenses/leftovers), automates with an approval gate on high-blast-radius steps, and routes policy exceptions rather than granting them
Decision rights
- - system-configuration standards and build quality, access provisioning and deprovisioning executed within policy, routine patch scheduling and the staged rollout, the automation and scripts you build, runbooks and documentation, and troubleshooting / root-cause fixes on the systems you own
Working vocabulary
What this role does
The IT Systems Engineer owns internal systems administration, automation, and reliable employee technology services - the builder who keeps the company's own IT running at scale. Core ownership is system configurations, access-provisioning workflows, and automation scripts, delivered across the standard identity, endpoint, virtualization, and support stack. This is an individual-contributor seat reporting to an IT Manager or Head of IT, with end-to-end ownership of the systems it builds and close partnership with employees, the security team, and IT support. It is not the frontline IT Support / Helpdesk Technician who sits the ticket queue and does end-user break/fix (the systems engineer builds and owns the systems and takes the escalations, but does not staff the queue), not the generalist IT Engineer (this seat is defined by systems-engineering depth - infrastructure, identity, virtualization, automation - not broad generalist IT), not the Security Engineer who owns the security program and its controls (the systems engineer implements hardening and patches and partners with security), and not a cloud / SRE engineer running the customer-facing production platform (the focus here is internal corporate IT). Performance is visible in system uptime, ticket-resolution time on escalated systems issues, and automation coverage, so better judgment produces measurable business impact. What separates great from average is building systems that run reliably without the builder standing next to them: a server or service that is configured to a repeatable standard and documented so another qualified engineer can rebuild it, identity and access provisioned to least privilege and cleaned up when people move or leave, patches and backups that are actually tested rather than assumed, and the repetitive work automated with a human-review model. A mediocre engineer builds a snowflake only they understand and fights the same fire every month; a great one removes the class of fire.
Best-fit customer
IT teams managing a growing estate without a growing headcount
Need more than one role?
Buying the whole team or the complete department lowers your effective cost per role at every tier of the ladder.