Job Details

Job Description

We are hiring a senior IT Operations Lead to own and mature day-to-day IT operations in a modern, cloud-first environment. This is not a junior systems administrator, helpdesk lead, or people manager.

This role requires autonomy, judgment, and accountability. The right candidate reduces escalation and chaos; they do not add to it.

We Are Looking For Someone Who:

• Operates comfortably in under-defined environments
• Self-prioritizes without needing constant direction
• Identifies gaps and fixes them without being asked
• Thinks in systems, lifecycle, and downstream impact
• Documents, standardizes, and improves as a natural reflex
• Is comfortable being accountable for outcomes, not just tasks
• Knows what "good" looks like and will run through walls to get there
• This person has likely been doing "more than their title" in previous roles.

Candidates We Are Rejecting:

• Technically capable but passive and task-driven
• "Operations-oriented" without the technical depth to truly own environments
• Career helpdesk leads
• Candidates who wait for instructions
• Tool-centric resumes without ownership stories
• People whose experience is limited to "keeping the lights on"

Candidates Must Have Hands-On Experience With:

• Microsoft 365 - Mandatory Experience
• Entra ID (cloud-only identity)
• (No hybrid Active Directory-only backgrounds)
  Intune
• Policy-driven endpoint management and compliance
  Autopilot
• Modern device provisioning workflows
• Mobile Application Management (MAM)
• App protection policies and BYOD-aware controls
• Candidates whose experience is primarily on-prem AD with limited M365 exposure are not a fit.
• Security & Identity Awareness (Operational Level)
• This role is not a security engineer role, but candidates cannot be security-naïve.

Must Be Comfortable Operating In Environments With:

• MFA enforcement
• Conditional Access
• Least-privilege access concepts
• Understanding how identity, devices, and access intersect operationally
• Endpoint & Lifecycle Ownership

Candidates Should Have Personally Owned:

• User onboarding and offboarding at scale
• Device standards and replacement cycles
• Inventory accuracy and cleanup
• Operational hygiene in messy or inherited environments
• We value people who have fixed broken lifecycle processes, not just followed them.

Operational Responsibilities (Framed As Ownership:
This role owns:

• Day-to-day IT operational health
• Endpoint, identity, and access lifecycle discipline
• Documentation and operational clarity
• Practical business continuity (making common failures non-events)

It Also Supports Growth By:

• Participating in IT due diligence for acquisitions
• Assessing inherited infrastructure and telecom
• Supporting service transitions and standardization
• Network Awareness (Baseline Required)

This role does not require a network engineer, but candidates cannot be ignorant of networking.

Candidates Must Understand:

• Basic LAN/WAN concepts
• Office and multi-site connectivity
• How cloud services, identity, and endpoints interact with networks
• When to troubleshoot vs. when to escalate
• Environmental Experience (Strong Preference)

Ideal Candidates Have Worked In:

• Multi-location or distributed organizations
• Mixed corporate and non-desk populations
• Environments undergoing standardization or modernization
• Co-managed IT models involving MSPs or vendors
• They should understand what to own internally vs. what to hold partners accountable for.

We Do Not Screen For:

• Specific ticketing tools
• Certifications without applied ownership
• Narrow specialization without operational accountability
• What Success Looks Like (Very Important)

Within 3-6 Months, This Role Is Expected To:

• Bring visibility and order to IT operations (assets, access, endpoints, documentation)
• Reduce reactive firefighting and leadership escalations
• Establish clear operational ownership and decision-making
• Identify root causes of recurring issues and begin resolving them

Within 6-12 Months, Success Looks Like:

• IT operations are predictable, not reactive
• Device, identity, and access lifecycles are well-defined and consistently executed
• Documentation exists and is trusted
• Leadership confidence in IT operations has materially improved with consistent "roll up" reporting provided
• The IT leadership team is spending less time filling operational gaps
• The right person will make the environment feel calmer, clearer, and more intentional.