The Systems Administrator

a.k.a. IT Administrator · Systems Manager · Platform Administrator

Owns core systems reliability and access.

Health check

Coffee at the kitchen island, laptop tethered to the phone hotspot. Opens the systems dashboard — overnight backups green, dispatch integration last sync 3 a.m., one alert from the billing connector that retried twice and recovered. Two access-request tickets queued from HR's orientation cohort.

Drive in

Quiet drive, audiobook on. Mentally queues the day — three new-hire access provisions before lunch, the Data Analyst's webhook ticket from the dispatch update, and the field-tablet vendor call at 2 p.m.

Triage

At the desk. Walks the ticket queue: two CSR access requests, one install helper, the analyst's webhook payload bug, and a tech who can't log into the tablet at a customer site. Tablet ticket jumps the line — pulls the user, sees a stale MFA enrollment, walks him through re-enrollment on the phone in four minutes.

Access provisioning

Provisions the three new hires from HR's orientation. Role-based groups, not individual permissions — CSR template for two, install-helper template for one. No admin rights, on principle. Sends each a welcome email with the SSO setup steps and confirms with HR they have full access well inside the 24-hour SLA.

Webhook investigation

Pulls the failing dispatch payload the Data Analyst attached to the ticket. Traces it to a field rename in Friday's vendor update — the integration was reading `job_id`, vendor moved it to `dispatch_job_id`. Patches the integration mapping in staging, runs a test payload, then promotes to production behind a feature flag.

Lunch

Leftover chili in the break room. Reads ten minutes of a homelab forum on his phone — the small ritual that keeps the brain warm without burning it.

Documentation

Writes up the webhook fix in the runbook before he forgets — the field rename, the mapping change, the test payload, the rollback path. Future-him will thank him at 2 a.m. when the next vendor update breaks something.

Vendor call

Thirty minutes with the field-tablet vendor on next month's firmware rollout. Pushes back on the proposed Friday-evening window — Saturday morning calls are the company's busiest. Negotiates a Sunday 2 a.m. deploy with a documented rollback, gets it in writing in the follow-up email.

Permissions audit

Quarterly access review. Pulls every account with admin or elevated permissions — finds two former employees still active in the billing system (offboarded by HR but the integration didn't sweep), one tech with a role he no longer holds. Disables all three, files the audit log, and emails HR the gap in the offboarding workflow.

Backup verification

Doesn't just check the green light — restores a sample database snapshot to the staging environment and runs a query against it. Backups that don't restore aren't backups. Logs the test and tears down the staging instance.

Close-out

Closes the day's tickets — three access requests done, webhook fix in production, MFA tablet user back online, vendor window negotiated. Two former-employee accounts disabled and emailed to HR. Sets the on-call pager and packs up.

One last look

Phone on the nightstand. Glances at the systems dashboard — all green, last sync within window. Plugs the pager in and turns the light off.

No mapped predecessors yet.