IT System Administrator

Project Description
We are looking for a sys admin to cover the US time zone. Working hours: 7 PM to 3 AM.
IT System Administrator (Evening/Night Shift, 7 PM 3 AM)
Responsibilities:
Device fleet: set up, maintain, and update Windows and macOS machines; handle hardware onboarding and offboarding.
User access: manage accounts, roles, permissions, MFA, password resets, and access revocation for departing employees.
Endpoint updates and security: apply OS and software patches, manage antivirus/EDR, enforce disk encryption (BitLocker, FileVault) and security policies.
Monitoring: track device health and corporate services, respond to alerts during the shift.
Backups: oversee backups of workstations and user data.
Troubleshooting: resolve OS, software, network, VPN, and peripheral issues.
Developer support: configure local environments (Docker, SDKs, IDEs, repository and VPN access), perform initial diagnosis of deployment issues, and escalate to DevOps.
Tickets: handle user requests, maintain documentation, and prepare shift handovers.
Requirements:
Experience: 2+ years as an IT Administrator or IT Support (L2).
Windows: solid administration of Windows 10/11, including Group Policy.
macOS: hands-on experience supporting and configuring macOS.
MDM: Microsoft Intune, Jamf, Kandji, or similar.
Identity and access: Entra ID (Azure AD) or Active Directory, Google Workspace or Microsoft 365, SSO (Okta, JumpCloud, etc.).
Networking (end-user level): DNS, DHCP, Wi-Fi, VPN.
Scripting: PowerShell and Bash/zsh for automating routine tasks.
Ticketing systems: Jira Service Management, Freshservice, or similar.
English: B1 or higher.
Nice to Have
Basic understanding of Docker, Git, and CI/CD to communicate effectively with DevOps.
Experience with EDR tools (CrowdStrike, SentinelOne, Defender for Endpoint).
Basic AWS or Azure knowledge at the access-management level (IAM).
Certifications: Microsoft (MD-102), Apple (ACSP), CompTIA A+/Network+.
Familiarity with ITIL processes.
Night Shift Specifics
Autonomy: able to resolve user issues independently without team backup.
Escalation: clear judgment on when to escalate an incident to on-call DevOps and when it can wait until morning.
Communication: clear written handovers for the day shift.
Schedule: consistent availability from 7 PM to 3 AM with an agreed rotation of days off.