Co-Managed Services Engineer

You've built real infrastructure depth across Intune, Entra, hybrid identity, virtualization, and Windows Server. Your current environment probably isn't fully using the extent of your expertise. This one will.

The model

Every customer already has internal IT staff. End-user support goes elsewhere. What reaches you are the backend problems their team couldn't solve.

Think:

• A Commvault job failing because of a VMware snapshot conflict

• A conditional access policy breaking authentication for the wrong group

• A cloud-hosted Linux server that needs someone who actually knows what they're looking at

You're the escalation layer and a project engineer. Not a ticket-taker.

Because every customer is at a different stage of modernization, you stay current across the full Microsoft ecosystem. New Intune features, Entra policy patterns, hybrid identity, virtualization modernization. The variety keeps your skills sharp in ways a single internal environment rarely does.

The work

M365 / Intune / Entra Conditional access design and troubleshooting, tenant administration, on-prem AD to hybrid migrations. You understand what's happening underneath the portal: identity flows, policy conflicts, log-level diagnostics. This is real engineering, not surface-level M365 admin work.

Backup / Commvault Setup, restores, failed job troubleshooting. The real skill is diagnosing whether the root cause is Windows Server, VMware, storage, or networking. Backup here is platform-level problem solving, not button-clicking.

Virtualization VMware and Nutanix are the backbone. HyperV and Azure Stack are in the mix. Deep in one hypervisor, able to apply that knowledge to the next one. You'll touch multiple platforms, not get stuck in one.

Windows Server Still the core of most customer environments. Solid here is non-negotiable, and you'll stay sharp because every environment is different.

Networking You're not the network engineer, but you can't tap out when the problem points toward Fortinet or Meraki. You know enough to isolate variables and move the issue forward.

Linux (nice to have) Not required, but a real differentiator. Permissions, directories, updates, basic Bash scripting. If two candidates are close, this decides it.

Why engineers choose this role

• You stay hands-on across the full Microsoft ecosystem

• You solve real problems, not repetitive tickets

• You work across multiple environments, not one stagnant stack

• You stay relevant: hybrid identity, Intune, virtualization, backup, scripting

• Internal IT handles the basics. You handle the engineering.

What they're hiring for

Not a niche specialist. A broad engineer who goes deep where it counts and doesn't freeze outside their lane.

The interview is practical. Walk me through a problem you had and exactly how you solved it. They're listening for logs, pivots, dead ends, and how you reason. Not memorized answers.

Their internal word for it is curiosity. Engineers who thrive here say "here's how I'd figure that out." Engineers who don't say "I haven't worked with that."

You're a fit if:

• 10+ years hands-on infrastructure, MSP or lean internal IT background preferred

• Strong in at least two of: Intune/Entra, Commvault, VMware/Nutanix, Windows Server

• Your hands are still on the keyboard, not just managing people

• Comfortable at the command line

• East Coast availability

Not a fit if:

• You want to stay in a narrow specialty: networking, Citrix, DevOps, or cloud architecture

• You prefer the pace of a single internal environment

• You avoid troubleshooting outside your lane