layiq

/la·yiq/adjective

worthy; deserving; fitting; suitable.

A role, opportunity, or path that merits attention, time, and pursuit.

Professional Services Engineer at Network Right | LAYIQ

What You'll Support

End-to-end implementations:

Lead multiple concurrent projects from discovery through design, execution, validation, and client handoff

Hands-on technical leadership:

You are the primary technical authority on your projects. You make decisions and you execute them.

Delivery outcomes:

Projects land on time, in scope, and documented well enough that anyone can pick up where you left off

Client confidence:

Translate technical decisions into clear expectations, set realistic timelines, and build trust through consistent follow-through
Types of Projects You'll Lead
SaaS implementations and integrations
Identity and access management (SSO, MDM, directory setup)
Security tooling rollouts
Domain and email migrations
AV and conference room buildouts
Cross-platform environment standardization for Mac-first clients

Our clients run Mac-heavy environments, but Windows experience is very helpful. The tools you'll work in most: JAMF, Kandji, Okta, JumpCloud, Google Workspace, M365, SentinelOne, Slack, Zoom, 1Password.

What You'll Do (Day-to-Day)

Run intake and kickoff meetings to scope work, set expectations, and build a workback plan before a single thing is deployed
Lead and execute implementations, migrations, and integrations from the ground up
Context switch across simultaneous projects for different clients without things falling through the cracks
Troubleshoot complex issues during deployment rather than escalating them
Write and maintain documentation throughout every project: design docs, implementation notes, runbooks, SOPs, handoff materials. This is not optional.
Partner with project managers to align scope, timelines, and client communication
Identify risks early and solve them before they become client conversations

What We're Looking For

4+ years in IT, systems, infrastructure, or SaaS environments
Implementor, not administrator: You can point to multiple specific projects you built from scratch, end to end. If your examples sound more like oversight than execution, it might not be the best fit.
Strong tooling alignment: Hands-on experience with JAMF, Kandji, or Intune, Okta, JumpCloud, or Entra ID, Google Workspace, M365, or Slack & Zoom, SentinelOne, etc.
Multi-client project management: You've managed concurrent projects across entirely different client environments, not just multiple work-streams within one organization.
Documentation discipline: You write runbooks, SOPs, and handoff docs as a natural part of how you work, not as a task someone has to ask you for.
Client-facing confidence: You can explain tradeoffs, push back when needed, absorb feedback mid-project without getting defensive, and adjust course without losing momentum.
Nice to Haves, but don't let this stop you from applying!
MSP or startup IT background: You've worked in environments where you were building things for the first time, not maintaining what was already there. Corporate IT only backgrounds typically don't translate to our client stack, pace, or multi-project structure.

What Makes Someone Successful in This Role

You build structure into every project before anything is deployed: intake, workback calendar, milestone check-ins
You move toward problems proactively instead of waiting to be asked
You've operated in ambiguous environments and gotten comfortable there
You care about adoption and user experience, not just whether the technical implementation is correct
You leave environments cleaner, better documented, and easier to support than you found them

Professional Services Engineer

Employer job description

What We Do

About the Role

Compensation