How to Hire Your First Internal IT Person: Job Description, Interview Scenarios, and 90-Day Plan

Your first internal IT hire should match the work that happens every day, which for most growing businesses means a support technician or systems administrator, not an IT director. Define the role from real support demand, give the person working tools and someone senior to escalate to, interview with realistic scenarios, and onboard with a 90-day plan.

The most common mistake is hiring one person and expecting them to be the help desk, network engineer, security team, and IT strategist at once. That person is rare, expensive, and hard to replace. A clear role, backed by the right support, lets you hire a capable earlier-career person and grow them.

Key takeaways

• Hire for the work you have: daily support usually comes first, strategy later.
• Write the job description from real requests and responsibilities, not a generic template with every product you own.
• Interview with realistic situations and a short writing task. Judgment and communication matter more than product trivia.
• Decide before day one who handles security, senior escalation, and after-hours coverage.

Is it time for your first IT hire?

Signs that a dedicated person would pay off:

• Staff wait days for laptops, accounts, or simple fixes.
• An office manager or operations lead has become the accidental IT person.
• You want someone on site who knows your people, even if you keep an outside provider.
• Your outside provider's response times or distance are causing real friction.

If you are replacing a managed service provider entirely, read what to know before you leave your MSP first. If you are unsure whether you need senior leadership, see do you need an IT director?

Which role should you hire first?

Role	Best fit when	Owns	Still needs from elsewhere
IT support technician	Lots of everyday employee, device, and account requests	Tickets, onboarding, devices, accounts, basic troubleshooting, inventory	Security, network engineering, senior escalation, planning
Systems administrator	Cloud, identity, device management, and backups need hands-on care	Microsoft 365 or Google Workspace, devices, patching, backups, networks	Architecture, security governance, compliance, executive planning
IT manager	Several IT staff, many vendors, competing projects	Priorities, vendors, budget, policies, reporting, team leadership	Specialist engineering, after-hours coverage, security operations

Headcount alone does not decide it. A 100-person accounting firm and a 100-person manufacturer can need very different first hires.

What to settle before you post the job

• The work. Pull a few months of support requests, if you have them, and list what the role will own every week.
• The tools. A ticket system, device management, documentation, a password vault, and backups the company controls. If an outside provider owns these today, plan what changes. Our internal IT tool stack guide lists the essentials.
• The senior layer. Who handles security monitoring, network design, major incidents, and after-hours coverage? It can be a partner, but it has to be someone.
• Decision limits. What the new hire can change alone and what needs approval.

Job description template

Copy this outline and fill it in with your own details.

Interview scenarios that show real judgment

Ask candidates to talk through situations like these:

1. A new employee starts tomorrow, but the manager only just sent the request.
2. A senior executive cannot get into email and asks you to switch off multi-factor authentication for them.
3. Several employees report a strange Microsoft 365 sign-in page.
4. A software vendor asks for a shared administrator password to fix their application.
5. A laptop fails and the employee says important files were only saved on it.
6. The same printer problem has created ten tickets this month.
7. You hit a network problem beyond what you know.

Listen for a clear troubleshooting process, sensible urgency, security awareness, documentation, kind communication, and a willingness to escalate. Strong candidates do not pretend to know everything. Add a short writing task: ask them to write a two-paragraph update to staff about an outage. Clear writing prevents a lot of support work.

Candidate scorecard

Area	What good looks like
Troubleshooting	Asks questions, narrows the problem, tests one change at a time
Security judgment	Will not bypass controls or share admin passwords, and explains why kindly
Communication	Plain-English explanations, clear written updates
Documentation	Writes down fixes and procedures without being asked
Escalation	Knows when to ask for help and what information to bring
Service attitude	Patient with stressed users, follows through

Score each area 1 to 5 for every candidate, and decide the minimum you will accept before interviews start.

A 30, 60, and 90 day onboarding plan

Days 1 to 30: learn and stabilize

• Meet department leaders, key vendors, and your escalation partner.
• Learn the ticket system, documentation, device management, and backups.
• Handle supervised support work, and write down questions and gaps instead of making unreviewed changes.

Days 31 to 60: own defined work

• Own routine tickets, onboarding, departures, devices, and accounts.
• Improve documentation as work gets done.
• Spot recurring problems and propose one or two fixes.

Days 61 to 90: improve and report

• Report on ticket patterns, open risks, and documentation gaps.
• Lead a small, well-defined project.
• Review performance against the scorecard and set the next goals.

What this looks like in practice

After a ransomware attack, a healthcare facility with more than 120 users rebuilt how it ran IT. With our help it hired one internal IT professional, and Spot On Tech took on the senior work behind that person: the security program, the ticketing operation, escalations, and projects. The new hire stays close to staff and daily work without carrying the whole environment alone. Read the healthcare case study.

How Compass helps you hire

Compass helps New York and New Jersey businesses define the role from real support demand, write the job description and scorecard, find and evaluate candidates, sit in on technical interviews, and build the 90-day plan. We can also run the tools, security, and senior support behind your new hire for as long as you want, which is what makes an earlier-career hire safe.

Frequently asked questions

What should my first IT hire be?
For most growing businesses, a support technician or systems administrator who handles everyday employee, device, and account needs, backed by senior support for security and complex problems.

What should an IT job description include?
Business context, the main goal of the role, what the person owns, decision limits, who backs them up, required and trainable skills, how success is measured, and where the role can grow.

What questions should I ask an IT candidate?
Realistic scenarios, such as an executive asking to bypass multi-factor authentication or a vendor asking for a shared admin password. Listen for judgment, security awareness, communication, and willingness to escalate.

Can we hire a junior IT person?
Yes, when the tools, documentation, and senior escalation are already in place. The risk is making a junior person the only authority on security and infrastructure.

Do we still need outside IT support after hiring?
Usually yes, for security monitoring, senior escalation, after-hours coverage, and projects. That arrangement is called co-managed IT.