Hiring the Right People

Introduction

In IT Services / Managed IT, hiring isn’t just staffing—it’s risk control and customer experience. Every new tech you bring on affects your response times, ticket quality, and the stability of managed clients’ networks. If you hire fast to “stop the bleeding,” you often end up with more outages, more rework, and more owner time spent fixing what should never have slipped through.

That’s why you want a Talent Funnel. Think of hiring like a pipeline: you attract the right people, train them into your way of delivering managed services, and repel candidates who will struggle in your environment. When it works, you reduce churn, lower escalation frequency, and build a team that can deliver SLAs without constant supervision.

Concept

Your Talent Funnel for Managed IT has three parts:

#

Hiring

Hiring is the front door. In Managed IT, your job ad must do two jobs at once: (1) clearly describe the work, and (2) filter for people who can handle it.

Instead of “IT Support Technician,” write a role that reflects the reality: ticket-driven support, documentation expectations, escalation discipline, and working within your managed stack (e.g., RMM, PSA, ticket queues). Specify what success looks like—like resolving tickets end-to-end, documenting fixes, and following change rules.

Real-World Managed IT Example: You’re hiring for a Level 1/2 Support Technician. Your ad says you’ll be working in a ticket system all day, using an RMM tool to monitor alerts, and performing resets, patching, and user troubleshooting under documented processes. You explicitly mention that you must be comfortable with after-hours rotation and that “good enough” documentation won’t pass.

This attracts candidates who want process and stability, not just a one-off “break/fix” life.

#

Training

Once the right person is in, training is where you turn “a tech” into “your delivery team.” Managed IT is built on repeatable playbooks: onboarding new clients, handling alerts, running standard changes, and resolving tickets without reinventing the wheel.

Your training must include both technical competency and your service operating system:
- How to triage tickets fast (and what gets escalated)
- How to communicate with clients (what you say, when you say it)
- How to document in your PSA/RMM so your knowledge base stays usable
- How to follow change control and avoid risky shortcuts

Real-World Managed IT Example: A new technician starts with a 2-week onboarding plan: day-by-day shadowing, then supervised ticket work, then a short certification on your RMM monitoring rules (what alerts matter, what alerts can be ignored, and how to escalate). By the end of week two, they run a checklist to onboard a sample workstation and demonstrate they can document the outcome in the PSA.

#

The Repellent Job Ad

The Repellent Job Ad repels people who will churn, cause quality issues, or create extra owner work.

In Managed IT, common “bad fit” signals include: refusing after-hours rotation, not wanting documentation, blaming customers instead of troubleshooting, or skipping process “because they can do it faster.” Your ad should quietly test for these traits.

A repellent job ad doesn’t need gimmicks. It needs truth plus a filter.

Real-World Managed IT Example: In the application instructions, you require the candidate to include a short example of how they handled a recurring issue using documentation (not just “I fixed it”). You also include a line that states: “This role follows documented SOPs and uses PSA/RMM workflows. If you prefer improvising during escalations, do not apply.” Only candidates who actually want managed service work will respond.

Conclusion

Hiring the right people in Managed IT is not luck—it’s a funnel. Build a job ad that matches the real work, use training to transfer your delivery system into the new hire’s hands, and use a Repellent Job Ad to filter out candidates who won’t thrive in your operational style. When you do this, you spend less time firefighting, your clients get steadier service, and your team scales without constant owner intervention.