Onboarding Engineer

About the role

In this role you take new client environments from unknown to documented: access, licensing, network, endpoints, backups and the gaps to fix first.

This is one of the roles Velocity Technologies recruits for year-round. The job may be with Velocity, or with an organization in the Phoenix area that we recruit for. Most positions are hybrid. We confirm the employer, pay, schedule and benefits with you before any interview.

What you'll do

• Collect and check access, licensing, vendor, network, endpoint, server, backup and Microsoft 365 details for new clients.
• Document each environment so the help desk, NOC, engineers and vCIO work from reliable information.
• Find urgent gaps in MFA, backups, admin access, endpoint coverage, patching and firewall ownership.
• Coordinate onboarding tasks, client communication and handoffs.
• Write up first-month findings for standards work and roadmap planning.

You're probably right for this if

• You have documented technical environments and coordinated several people to get it done.
• You have working knowledge of Microsoft 365, Entra ID, Active Directory, endpoint management, networking and backups.
• You can raise gaps without alarming the client or confusing coworkers.
• You work from checklists and hand work off cleanly.

Useful but not required: MSP onboarding or client transitions; access transfer, vendor coordination, firewall review, Intune and backup validation; Microsoft 365 Administrator, Network+ or Security+. Equivalent experience counts.

Pay

$70,000 to $95,000 a year.

The hiring organization sets the exact pay within this range. Benefits depend on the employer, and we confirm them with you before any interview.

How hiring works

1. A phone call with Velocity about your experience, the role and the pay.
2. If it looks like a fit, we tell you who the employer is and confirm pay, schedule and benefits.
3. Interviews with the hiring organization, which may be Velocity.

On the first call, expect to talk through questions like these:

• What has to be captured before a new client can be supported responsibly.
• How you handle missing admin access during onboarding.
• What you would tackle first in the first week of a messy transition.