AlignLayerNine (ALN) is a managed IT and security provider with teams in Glenview, Naples, London and Santiago. The CORE team is the engineering group behind our managed services: it owns the systems, identity, endpoint and security platforms that every client environment runs on, and it is where the L1 help desk escalates.
Each Systems Engineer II owns specific systems, assigned and reviewed by the CORE Team Lead, and is accountable for their configuration, health and standards across client environments. Other engineers in the same role provide cross support. When not doing direct system configuration work, this role takes tickets escalated upstream from the L1 help desk and client escalation requests routed through the Technology Alignment Manager and the Owner. We also work as one team: everyone picks up regular help desk tickets on occasion, based on inflow and service metrics.
This is an engineering role, not an administration role. A systems administrator keeps one environment running; a systems engineer at ALN builds a standard once, automates it, documents it and applies it across dozens of client environments. The ideal candidate has strong hands-on administration depth and wants to work that way: fixing the root cause, scripting the repeatable parts and leaving every environment closer to the ALN baseline than they found it.
Key Working Relationships
- CORE Team Lead: Direct manager; assigns and reviews system ownership, sets priorities and standards
- Owner / Head of Solutions: Routes client escalation requests to this role; sets solution direction and standards for the stack
- Technology Alignment Manager (TAM): Routes client escalation requests to this role; partners on aligning client environments to ALN standards
- Fellow Systems Engineers: Peers in the same role; provide cross support and backup coverage on each other's assigned systems
- Engineer III, Network (Santiago): Senior escalation point and primary partner on network, firewall and infrastructure issues that cross into systems
- Infrastructure / Project Engineer: Partners on project delivery, hardware refreshes and site buildouts
- L1 Help Desk Technicians (Chicago and Santiago): Takes their upstream escalations, returns fixes with documentation, and pitches in on regular tickets when inflow calls for it
- Field Services Technicians: Provides remote engineering support for on-site work; hands off physical tasks
- Project Manager: Receives scoped project tasks; reports status, risks and hours
- GRC Lead: Implements technical controls behind compliance work (NIST 800-171, CMMC) and supplies evidence
- Client IT contacts (co-managed): Works alongside internal IT teams with clear lines on who owns what
- External Partners: After-hours NOC/TAC partner, distributors, Microsoft and platform vendors' support
Key Responsibilities
Approximate time allocation is shown for each area and will shift with system assignments, client load and project schedule. Areas 1–3 are the pool that assigned systems are drawn from; a given engineer may own some and cross-support others.
1. Microsoft 365, Identity & Endpoint Management (~20%)
- Configure and maintain Entra ID, Exchange Online, SharePoint, Teams and Intune across client tenants; support Google Workspace tenants
- Maintain conditional access, MFA, device compliance and baseline policies, deployed consistently across tenants through ALN's policy management tooling
- Run user and device lifecycle: onboarding, offboarding, licensing, Autopilot and application deployment
- Support the move to privileged access management and just-in-time admin access; no shared admin credentials
2. Servers, Virtualization, Backup & Continuity (~20%)
- Build, patch and maintain Windows Server, Active Directory, DNS, DHCP, Group Policy and file services
- Operate virtualization and cloud workloads (Hyper-V, VMware, Azure)
- Own backup and BCDR health for assigned systems: daily verification, scheduled restore tests and recovery during incidents
- Plan and execute maintenance windows with change notes and rollback plans
3. Security Stack Operations (~15%)
- Operate ALN's security platforms day to day: application allowlisting and elevation control, MDR, SIEM and identity threat detection, email security and SaaS backup
- Triage and act on security alerts with the MDR provider; contain, remediate and document
- Remediate vulnerability scan findings and investigate rogue or unknown devices
- Implement the technical controls behind client and internal compliance programs, working with the GRC Lead
4. Escalations & Help Desk Support (~25%)
- When not doing direct system configuration work, take tickets escalated upstream from the L1 help desk and own them through to resolution
- Handle client escalation requests routed through the Technology Alignment Manager and the Owner
- Diagnose to root cause rather than symptom, and fix the underlying standard when the same issue appears across clients
- Pick up regular help desk tickets alongside the rest of the team when inflow and service metrics call for it
- Work tickets in Autotask with accurate time entries, clear client-facing notes and status that reflects reality
- Provide cross support and backup coverage for systems owned by other engineers
5. Projects & Client Onboarding (~10%)
- Deliver the systems workstream of projects: tenant and mail migrations, server replacements, Intune rollouts, identity redesigns
- Onboard new clients onto the ALN baseline: agents, policies, documentation and backup
- Scope effort honestly, flag risks early and hit committed dates
6. Automation, Standards & Documentation (~10%)
- Write and maintain PowerShell scripts and RMM components; all scripts live in GitHub with a named owner, with peer review for anything multi-client, scheduled or touching security, identity or backup
- Keep IT Glue documentation current for every environment touched
- Contribute to internal knowledge-sharing sessions and mentor Technician I/II staff
First-Year Priorities
- First 30 Days: Complete ALN onboarding and tool access; learn the stack, ticket flow and escalation paths; shadow CORE engineers; begin taking L1 escalations with a senior engineer as backstop
- First 90 Days: First assigned systems owned independently, with a completed ownership review; documentation current for those systems; first script or RMM component published to GitHub; 90-day review completed
- By End of Year 1: Recognized owner of assigned systems and reliable cross support for peers; led the systems workstream on at least [two] projects or onboardings; measurable drop in repeat escalations; certification progress on the ALN career ladder toward Engineer III
How Success Will Be Measured
- Health, standards compliance and review outcomes for assigned systems
- Time to resolution and SLA attainment on escalated tickets
- Reopen rate and repeat-incident rate
- Share of escalations returned to L1 with documentation that lets them solve it next time
- Backup success rate and completed restore tests
- Patch compliance and time to remediate critical and high vulnerability findings
- Documentation completeness for assigned systems
- Project tasks delivered on schedule and within scoped hours
- Client satisfaction on tickets and projects
- Utilization and time-entry accuracy
Qualifications
Required
- 4–6 years of hands-on IT experience, including at least 2 years as a systems administrator or systems engineer responsible for production environments
- Strong Microsoft 365 and Entra ID administration: Exchange Online, conditional access, MFA, Intune and device compliance
- Solid Windows Server and Active Directory skills, including Group Policy, DNS, DHCP and file services
- Experience with virtualization (Hyper-V or VMware) and with backup and recovery, including real restores
- Working PowerShell: able to read, adapt and write scripts for routine administration
- Sound networking fundamentals (TCP/IP, VLANs, VPN, firewalls) sufficient to troubleshoot across the systems and network boundary
- Security-first habits: least privilege, MFA everywhere, change control and clean documentation
- Clear written and verbal communication with non-technical clients and with peers
- Able to manage a queue of competing priorities across multiple environments
Preferred
- Experience at an MSP or MSSP, or in internal IT supporting multiple sites or business units
- Microsoft certifications (MS-102, MD-102, AZ-104, SC-300) or CompTIA Security+ / Server+
- Experience with RMM and PSA platforms and with IT documentation systems
- Experience with application allowlisting, MDR/SIEM and identity threat detection tools
- Azure infrastructure experience
- Google Workspace administration
- Background in healthcare, nonprofit or regulated environments (NIST 800-171, CMMC, HIPAA)
- Spanish language skills, for work with the Santiago team
Platforms & Tools
Working knowledge of, or ability to quickly learn: Microsoft 365, Entra ID, Intune and Microsoft 365 Lighthouse; Google Workspace; Windows Server, Hyper-V, VMware and Azure; Datto RMM and Datto BCDR; Autotask PSA; IT Glue; ThreatLocker; Huntress; GitHub.
Competencies
- Engineer mindset. Solves the class of problem, not just the ticket; builds the standard and automates it
- Ownership. Takes an issue from escalation to verified fix and closes the loop with the client and the team
- Client-first judgment. Weighs business impact, communicates plainly and picks the right time for a change
- Documentation discipline. If it is not documented, it is not done
- Team multiplier. Makes the help desk better by teaching, not just by taking the ticket
- Continuous learner. Pursues certifications and keeps current on Microsoft and security platform changes
Working Conditions
- Assigned to the Glenview, IL office
- Hybrid week: 2 days in office (currently Wednesday and Friday, subject to change), 1 day in person at a client site, 2 days remote; office space is available for anyone who prefers to be in more often
- Standard shift is 8 paid hours plus a 30-minute unpaid lunch, during Chicago business hours. Start time is flexible and set around what works best for the employee, as long as it stays consistent; an early start (7:30–8:00 am) is preferred
- No on-call rotation; ALN support is staffed 24x7. Planned maintenance windows may occasionally fall outside normal hours
- Works daily with the Santiago team; handoff meetings three times a week
- Local travel to client sites; valid driver's license required
- Access to client systems requires a background check