Systems Administrator
-
IT/Tech
Job Description & How to Apply Below
IT service delivery
Smart Suite for the Systems AdministratorThe Systems Administrator builds and maintains servers, networks and platforms: provisioning, patching, monitoring, backups and the operational tasks that keep infrastructure healthy. They respond to alerts and escalated incidents and document the environment they run.
Reports to:
IT Operations Director
The Systems Administrator builds and maintains servers, networks and platforms: provisioning, patching, monitoring, backups and the operational tasks that keep infrastructure healthy.
- Provision, configure and maintain servers, networks and platforms
- Apply patches and manage vulnerabilities on schedule
- Monitor infrastructure and respond to alerts
- Run backups, restores and DR tests
- Resolve escalated incidents and raise changes
- Document systems and keep configuration records current
Who this role reports to, who reports to them, and the peers they work with most.
Reports toIT Operations Director
Works closely with- Service Desk Analyst
- Dev Ops Engineer
- Security Analyst
- IT Asset Manager
- IT Disaster Recovery Lead
The Systems Administrator keeps servers, networks and platforms healthy, answering to the IT Operations Director for patches applied, alerts handled and an environment that is documented as it is. Smart Suite puts routed alerts, linked configuration items and remediation tasks in one place, so work is recorded as it is done and the CMDB stays true.
Keep infrastructure healthy, patched and documented Alerts that arrive with priority and contextEvent & Alert Management routes alerts to you with priority and the service and dependency context behind them, and the action you take is recorded on the event. On-Call Management decides who gets the page, not the group inbox.
Patch windows met on the recordPatch and vulnerability remediation tasks are assigned by system, routed by criticality and tracked to closure with the Security Analyst's verification, so the PCI DSS, NYDFS or BOD 22-01 patch window is met on the record, not by recollection.
Maintenance windows on a calendar everyone can seePlanned maintenance, outages, changes and releases sit on one operations calendar visible to stakeholders, with each window having an owner and a status, so the Dev Ops Engineer's release and your patch cycle do not land on the same night by accident.
Work with the desk, security, Dev Ops and asset management Starting on the fault, not the questionsIncidents escalated from the Service Desk Analyst arrive with the affected configuration item, the steps already taken and the user's contact, so you start on the fault rather than on the questions. Status flows back to the requester as you update.
CMDB updated as the change is madeConfiguration records are updated against the asset and the Configuration Management (CMDB) entry as part of the change, with lifecycle status and ownership kept current, so the IT Asset Manager's register and your running environment describe the same estate.
Changes raised with the impact already assessedOperational changes route through risk and impact review and approval when the dependency context says they need it, and audit-ready change history records who approved what and when. Raising a change is a form, not a negotiation.
Show the IT Operations Director what was done No Friday status report from memoryPlanned changes, outages, incident trends and operational KPIs are live dashboards over the same records you update, so the IT Operations Director sees what the team handled without a status report compiled from memory on a Friday.
Backups and DR tests on the recordBackups, restores and DR tests are recorded as operational events with outcomes, follow-ups and…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).
View / Apply for Jobs
Matching My Jurisdiction