IT Manager / IT Administrator (SMB) Hiring Guide
Responsibilities, must-have skills, 30-minute assessment, 6 interview questions, and a scoring rubric for this role.
Role Overview
Function: Oversee and maintain all information technology systems and services for the organization. The IT Manager/Administrator ensures that networks, servers, hardware, and software are operating securely and efficiently to support business operations. This role manages dayto-day IT activities (e.g. user support, system maintenance) while also planning long-term IT strategy.
Core Focus: Align technology with business needs and reliability. The IT Manager is responsible for more than just troubleshooting they shape the IT strategy, implement robust security measures, and drive innovation to improve business processes. A core focus is bridging the gap between technical systems and business objectives, ensuring IT investments deliver value. They prioritize protecting data (cybersecurity, backups) and minimizing downtime, since even minor glitches could escalate into major disruptions without their expertise
Typical SMB Scope: In small-to-medium businesses (10400 employees), this is a hands-on mid-level role often covering all IT functions. The IT Manager may be the sole IT professional or lead a very small team, wearing multiple hats from helpdesk support to network administrator. They handle the entire IT infrastructure (workstations, networks, cloud services, business apps) and vendor relationships for things like internet, software, and equipment. SMB IT Managers must be adaptable generalists one day installing updates or fixing Wi-Fi, the next day evaluating a new SaaS tool or planning an office move. They ensure technology reliably supports day-to-day operations and growth, often under tight budgets and limited resources. Security is a key emphasis, as SMBs are frequent cyber targets despite limited IT staff. The role is typically hybrid (mix of on-site and remote work) given the need to support office infrastructure and remote users.
Core Responsibilities
Manage and maintain all IT infrastructure Oversee all hardware, software, networks, and cloud services to ensure reliable daily operations. This includes servers (on-prem or cloud), network devices, user endpoints, and peripherals. Monitor system performance and uptime, proactively addressing issues to minimize disruptions.
Implement security measures and data protection Develop, enforce, and update IT security policies (firewalls, antivirus, access controls) to safeguard company data. Maintain regular data backups and a disaster recovery plan to protect against data loss. Continuously monitor for security breaches or vulnerabilities and respond to incidents in line with best practices and compliance requirements.
Oversee IT support and user services Manage the IT help desk function, ensuring prompt response to technical support tickets and incidents. Troubleshoot and resolve hardware/software issues for employees in a timely, customer-friendly manner. Provide training or guidance to staff on
using technology tools securely and effectively. Ensure all employees have the IT resources and access needed to do their jobs (accounts, devices, software).
Plan and execute IT projects and upgrades Lead projects such as deploying new systems, implementing software upgrades, or setting up IT for new office locations. Define project scope/ timelines, coordinate resources (including any external vendors or consultants), and ensure projects are delivered on time and within budget. Manage changes (e.g. major system updates, cloud migrations) to minimize disruption, including communication and training around those changes.
Develop and manage IT budgets and vendors Forecast IT needs and prepare the IT budget, balancing cost-effectiveness with business requirements. Track IT spending and optimize costs
(e.g. negotiating contracts or choosing cost-efficient solutions). Evaluate and manage vendor relationships for services like internet, software subscriptions, managed services, and equipment procurement. Ensure the company is getting best-value services and that vendors meet agreed service levels.
Align IT strategy with business goals Work with leadership and other departments to identify technology needs or improvements that will enhance productivity, efficiency, or growth Propose and implement solutions that support business strategies (for example, introducing a CRM system to improve sales tracking, or enabling remote work capabilities). Conduct cost-benefit analyses for major tech initiatives
and advise management on IT opportunities and risks in business terms.
Maintain IT documentation and compliance Keep detailed documentation of IT assets (inventory of hardware/software), network diagrams, configurations, and standard operating procedures. Document support resolutions for future reference. Develop and enforce IT policies (acceptable use, password policy, etc.) and ensure compliance with any industry regulations or data protection laws relevant to the business. Regularly review and update policies/procedures to reflect changes in technology or compliance requirements.
(If applicable) Lead and mentor IT staff If the SMB has additional IT support staff or technicians, provide leadership and direction to the IT team. Delegate tasks effectively, ensure IT staff follow best practices, and foster a culture of continuous improvement and customer service. Conduct performance evaluations, identify training needs, and mentor junior team members in developing their skills. (Note: In many SMBs, the IT Manager might be an individual contributor with outsourced support; in those cases this responsibility would shift to coordinating external IT support contractors or MSPs.)
Must-Have Skills
Hard Skills
Network administration: Strong understanding of networking (TCP/IP, DNS, DHCP, routing, switching, Wi-Fi) to manage LAN/WAN connectivity and troubleshoot network issues. Ability to configure routers, firewalls, VPNs and ensure network security and performance.
System administration (Windows/Linux): Experience administering operating systems and servers
(e.g. Windows Server with Active Directory, Linux servers) including user account management, group policies, file permissions, and basic scripting for automation. Familiarity with Microsoft 365 administration (Exchange/Outlook, SharePoint, Teams) or Google Workspace in an SMB context is expected.
Cloud services & virtualization: Hands-on knowledge of cloud platforms or services common to SMBs for example, managing Microsoft Azure AD/Intune or AWS resources, and SaaS applications.
Experience with virtualization (VMware, Hyper-V) for managing virtual servers or desktops is often required
Cybersecurity practices: Solid understanding of IT security fundamentals firewalls, anti-malware, patch management, encryption, and access control. Ability to implement security policies and educate users on security (phishing awareness, proper data handling). Should be up to date on the latest threats relevant to SMBs and mitigation strategies (given ~43% of cyber attacks target small businesses).
Backup and disaster recovery: Proficient in setting up and managing data backup solutions (on-site and cloud backup), and in restoring data or systems from backups. Understands disaster recovery planning e.g. creating redundant systems or plans to quickly recover critical services after outages.
Hardware & software troubleshooting: Keen diagnostic skills to resolve a range of IT issues from a failed PC or printer to a server performance problem. Can systematically troubleshoot hardware failures, software errors, network drops, etc., and identify root causes quickly. Familiar with using monitoring tools or error logs to pinpoint issues.
IT support and ITIL basics: Knowledge of IT service management processes (incident, change management) appropriate to an SMB environment. Able to prioritize and handle a queue of support tickets efficiently. Provides excellent customer service to internal users, understanding that clear communication and patience are as important as technical fixes
Project management (IT projects): Ability to plan and execute IT projects (e.g. a hardware refresh, office 365 migration, implementing a new tool). Skills include defining requirements, creating a project plan, coordinating tasks, managing timelines and stakeholders, and adjusting plans as needed. Certifications like PMP are not required but the role demands project leadership capability to ensure successful implementations.
Scripting/automation (nice-to-have): Basic scripting ability (PowerShell, Bash or Python) to automate routine tasks or manage configurations can be very useful in an SMB setting where efficiency is key. While not every SMB IT Manager codes, being able to write a simple script (for example to batch-create users or automate a backup check) is a plus.
Relevant certifications: While not always mandatory, having certifications like CompTIA A+ or Network+, Microsoft Certified (e.g. Azure or M365), Cisco CCNA, or ITIL Foundation can validate the knowledge areas above and are often viewed favorably. These indicate a commitment to professional development and a solid baseline of skills.
Soft Skills
Communication: Excellent written and verbal communication skills are critical. Must be able to explain technical concepts in plain language to non-technical colleagues and management. Whether writing an IT policy or coaching a user through a problem, communication should be clear, patient, and tailored to the audience.
Problem-solving & Analytical thinking: A natural troubleshooter who approaches problems methodically. Able to analyze complex issues (Why is the network intermittently dropping How can we reduce support tickets) and break them into root causes and solutions. Uses data and logical reasoning to make decisions, and can think creatively to find workarounds or improvements when faced with constraints.
Organization & Time management: Capable of juggling multiple priorities and tasks in a fast-paced SMB environment. Uses ticketing systems or task lists to keep track of ongoing issues and projects, ensuring nothing falls through the cracks. Excellent at managing time, especially when
wearing many hats (can switch from urgent support mode to focusing on an upgrade project and back).
Leadership & Teamwork: Even if the IT Manager is a team of one, they frequently coordinate with others and may lead vendors or cross-functional project teams. Needs leadership skills to drive initiatives and possibly supervise junior IT staff. Equally important is collaboration working well with colleagues in other departments, being receptive to input, and guiding end-users or junior staff constructively.
Customer service orientation: A helpful, user-focused attitude is essential. Treats internal users like valued customers listens to their issues, empathizes, and strives to solve problems with a positive demeanor. Remains calm and courteous under pressure (such as when an executives system is down) and works to restore productivity quickly.
Adaptability: Comfortable with change and able to quickly learn new technologies or adjust to new business needs. SMB environments evolve, and the IT Manager should handle sudden shifts (like a quick pivot to remote work) or new challenges without being rattled. Embraces continuous learning to stay current on tech trends that could benefit the company.
Hiring for Attitude
Ownership & Accountability: Takes responsibility for outcomes, good or bad. Doesn or make excuses when issues occur instead, owns the problem and drives it to resolution Shows reliability and follows through on commitments, which is crucial when overseeing critical systems.
Continuous learning & Curiosity: Passionate about keeping skills up-to-date and learning new technologies or better ways to do things. In an SMB (with no large specialist team), the IT Manager must be a lifelong learner to adapt to new challenges. They seek out training, experiment with new tools in safe ways, and stay informed about IT trends impacting small businesses
Service-minded attitude: Truly enjoys helping people and solving problems. Exhibits patience, empathy, and a positive demeanor when dealing with frustrated users. Views the IT role as a support function to empower colleagues, not as a gatekeeper of technology.
Integrity and Trustworthiness: Handles sensitive data (employee records, financial info, passwords) and system access with the utmost integrity. Can be trusted to do the right thing, follow security policies themselves, and maintain confidentiality. If a mistake is made, they are honest about it (no cover-ups) because trust is paramount.
Proactiveness: A forward-thinking, proactive approach to identify and prevent problems before they occur. For example, doesnt wait for a system to fail they monitor logs and health metrics to address issues in advance, and they schedule maintenance in off-hours to prevent outages. Brings up ideas to improve IT and business operations without being asked.
Adaptability & Flexibility: Willingness to stretch beyond a fixed job description to get things done common in the SMB culture. One day they might be unboxing and setting up 10 laptops, the next day negotiating a contract with a telecom provider. They handle shifting priorities with grace and can adjust plans when business needs change suddenly.
Team and Culture Fit: A cooperative style that meshes with the companys culture. In a small company, every hire has amplified impact on culture. The IT Manager should be seen as a team player who collaborates well, respects others expertise, and can influence good practices without alienating colleagues. They should also exhibit leadership humility confident in their domain but not arrogant, willing to listen and explain rather than dictate.
Tools & Systems
Systems / Artifacts
Common Software/Tools Used:
Productivity & Collaboration: Microsoft 365 (Exchange Online, Office apps, Teams) or Google Workspace for email, calendars, documents, and collaboration are typically central tools. Also messaging platforms like Slack or Microsoft Teams for day-to-day communication.
Operating Systems & Endpoint Management: Windows (Windows 10/11 on desktops, Windows Server for AD/file servers) is most common in SMBs, often alongside some Mac or Linux devices. Tools like Microsoft Active Directory and Group Policy for user/device management, and endpoint management solutions such as Microsoft Intune, SCCM, or third-party RMM (Remote Monitoring & Management) tools to oversee PCs, laptops, and mobile devices.
Network & Security: Network devices (routers, switches, Wi-Fi access points) from SMB-friendly vendors (e.g. Cisco/Meraki, Ubiquiti, Fortinet). Firewall/UTM appliances for security (e.g. a SonicWall or PfSense firewall). VPN solutions for remote access. Network monitoring tools (like Pingdom, PRTG, or built-in router dashboards) to watch uptime and performance. Endpoint protection software (antivirus/anti-malware or EDR solutions such as Symantec, CrowdStrike, etc.) on all endpoints. Possibly a password management tool (or enforcing usage of one) to maintain credential security.
Servers & Cloud Services: If on-prem servers: virtualization platforms like VMware vSphere or Microsoft Hyper-V to host multiple virtual servers. If in cloud: managing cloud instances or services in AWS/Azure, or using a managed services providers cloud. Common services might include file storage (NAS or SharePoint/OneDrive), phone/VoIP system management, and possibly databases (SQL Server or cloud databases for business apps).
IT Support & Ticketing: A help desk ticketing system to track issues could range from dedicated tools like Jira Service Management, Zendesk, Freshservice, Spiceworks or even just an email-based ticket system or Teams channel in a very small setup. Monitoring and remote support tools like TeamViewer or Remote Desktop for assisting users and servers.
Backup Solutions: Software/services for regular backups, such as Veeam, Acronis, cloud-backup services, or even built-in Windows Backup for smaller setups. If using cloud SaaS (M365/Google), third-party cloud-to-cloud backup services might be used to back up email/Drive/SharePoint data.
Business Applications: The IT Manager typically administers key business systems (though specifics vary by company). Examples: CRM or ERP systems if used (e.g. Salesforce, QuickBooks, SAP Business One), the company website or e-commerce platform, and any industry-specific applications. They
coordinate with vendors for these systems but should be capable of basic admin tasks like adding users or managing integrations.
Other Tools: Device imaging or deployment tools (e.g. WDS/MDT for Windows or third-party imaging tools) for setting up new machines. Software deployment and patch management utilities. Possibly scripting environments (PowerShell) for automation. And standard IT utilities (diagnostic tools, network scanners, etc.).
What to Assess
Situational Judgment Scenarios
The following are realistic dilemmas an SMB IT Manager might face, useful for situational judgment tests. Each scenario provides context that reveals on-the-job decision-making and attitude.
1. Multiple Priority Meltdown: Its Monday morning and three critical issues hit at once: the CEOs home internet is down during a crucial Zoom call, a ransomware alert pops up on one employees PC, and the company CRM system is offline. Youre the only IT person available. Context: All 2.
3.
4.
5.
6.
7.
stakeholders are demanding immediate attention the CEO is calling you repeatedly, the infected PC user is panicking, and Sales is frantic about the CRM. Dilemma: How do you prioritize and handle communication The scenario tests balancing critical issues, triaging security vs. executive support, and keeping calm under pressure.
Security vs. Convenience: A department head insists on using an old software tool that IT deems insecure and which violates company security policy. They argue its essential for their teams productivity and have even hinted they might install it themselves if IT wont. Context: The business unit is pressuring for an exception, but the software has known vulnerabilities (e.g., its out of support). Dilemma: Do you stick to security policy or bend to business convenience The situation examines the IT Managers ability to educate stakeholders, propose alternatives, and uphold crucial security standards without alienating the department.
The Unplanned Outage Communication: An offices network goes down for 2 hours due to a misconfigured switch after an upgrade you implemented. Its now resolved. Context: Employees experienced downtime and some work was lost. The COO is upset and demands an explanation. Dilemma: How do you handle the post-outage communication and accountability This scenario looks at whether the IT Manager transparently communicates the cause and remediation, takes responsibility, and outlines prevention steps versus deflecting blame or downplaying the issue.
Rogue IT Request: An employee from Finance asks for local admin rights on their work laptop to install some special tools and claims its urgent. Company policy restricts admin privileges to IT only. They have their managers backing, citing that IT processes are too slow. Context: Granting the request would violate policy and potentially introduce risk, but denying it might upset leadership in that department. Dilemma: How do you respond The scenario tests integrity to follow policy, negotiation skills (perhaps finding a secure way to meet the need), and the ability to handle pressure from higher-ups for exceptions.
Vendor Showdown: The internet service provider for your office has been unreliable lately, causing several outages. The CEO wants this fixed now. Youre considering whether to switch vendors or negotiate with the current ISP. Context: The current contract still has 6 months left. Switching would be disruptive and possibly costly, but continuing means risk of more downtime. Dilemma: How do you approach the situation and present options to leadership This scenario examines business-savvy and problem-solving do you gather data on downtime and push the vendor for SLA compliance, propose a backup line, or rush into a new contract The right approach balances immediate needs with long-term implications.
Confidential Data Dilemma: You discover that a member of the HR team has been routinely saving employee data spreadsheets to a personal Google Drive account for backup, which is against policy. Context: They likely meant no harm but are exposing confidential data externally. Confronting this could cause inter-department tension. Dilemma: What do you do The scenario tests the IT Managers approach to enforcing data policies ideally educating the employee and securing the data immediately and gauges their tact and firmness in handling sensitive policy violations by a colleague.
Overworked and Understaffed: Its quarter-end and every department seems to have urgent IT needs at once Finance needs a report from the system, Marketings design software license
expired, and Ops has a new hire starting tomorrow with no equipment ready. Youre drowning. Context: The company has grown, but IT staffing hasnt. Overtime and stress are mounting. Dilemma: How do you communicate and set expectations across the company This scenario checks how the IT Manager manages time and expectations whether theyll ask management for prioritization help or help from an MSP, or just over-promise and likely under-deliver. It reveals attitude toward self-management and seeking help when needed.
8.
Ethical Software Shortcut: A department requests an expensive software tool for a short-term project. Buying enough licenses properly will bust the budget. A team member suggests We can just install one license on multiple machines theyll never know. Context: The team is under deadline pressure and sees compliance as a hurdle. Dilemma: Do you enforce proper licensing and find a compliant solution, or look the other way to quickly accommodate the team This scenario tests integrity (software compliance, ethics) and creativity in solving budget vs. need e.g. negotiating a short-term license or finding an alternative tool, rather than piracy.
9.
Subpar Performer on the Team: (If the IT Manager has reports) One of your IT support technicians has had several user complaints about unprofessional communication and unresolved tickets. Context: Youve coached them before, but issues persist and are now affecting ITs reputation. Dilemma: How do you address this situation The scenario looks at leadership and attitude whether the IT Manager will actively address performance through training or corrective action, and how they balance being supportive vs. ensuring quality service.
10.
BYOD Security Risk: Several employees started using personal tablets and phones to access company email and files, which increases risk if not managed (no MDM in place). Context: Employees enjoy the convenience, and no formal BYOD program exists yet at the company. Dilemma: What steps do you take The scenario evaluates whether the IT Manager is proactive to create a BYOD policy and implement controls (or training) to secure company data on personal devices, while navigating employee privacy and convenience considerations.
Assessment Tasks
Attention to Detail Tasks
These tasks assess the candidates ability to catch errors, inconsistencies, or important details in typical IT-related data. Each task should have a clear, deterministic correct answer to objectively mark.
1. Identify the Email Address Error: You have a list of new employee email addresses. All company emails should follow the format firstname.lastname@company.com. Identify which one of the following email addresses is formatted incorrectly:
a.
john.smith@company.com
b.
emily.jones@company.com
c.
alex_chen@company.com
d.
sarah.davis@company.com
Expected Answer: c. alex_chen@company.com is incorrect, because it uses an underscore instead of a dot. The standard format is firstname.lastname, so the correct format would be alex.chen@company.com. The other addresses conform to the firstname.lastname format.
1. Duplicate Asset ID Check: Below is an excerpt from an IT asset inventory for company laptops. Each device should have a unique Asset ID. Find the duplicate Asset ID in the list:
Asset ID Device Name Assigned User
Expected Answer: LT-020 is duplicated. Asset ID LT-020 appears twice (for Laptop-Beta and Laptop-Delta), which is an error since each asset should have a unique identifier. The candidate should spot LT-020 repeating. (In a real test, we would accept LT-020 as the answer.)
1. Log File Anomaly: You are reviewing a backup log snippet. All nightly backups should complete with a Success status. Identify which dates backup failed or had an issue:
[Jan 10 02:00] Backup Job 245 -Status: Success [Jan 11 02:00] Backup Job 246 -Status: Success [Jan 12 02:00] Backup Job 247 -Status: Failure (Disk Full) [Jan 13 02:00] Backup Job 248 -Status: Success
Expected Answer: January 12 had the failed backup. The log line for Jan 12 explicitly shows Failure (Disk Full) whereas all other dates show Success. The correct identification is Jan 12. (The candidate might answer Jan 12 or the backup on 12th failed due to disk full which are equivalent recognition of the error.)
1. Inconsistency in a Notification: Youre proofreading an email draft to all employees about a scheduled maintenance:
Planned Downtime: Our servers will be offline for maintenance on Saturday, July 14, 2026 from 8:00 PM to 10:00 PM. Please save your work in advance. (Note: July 14 is a Sunday.)
Find the error in the announcement.
Expected Answer: The date and day dont match July 14, 2026 is a Tuesday (not a Saturday). This inconsistency (saying Saturday but giving a date that is not Saturday) is the error. The candidate should point out the mismatch, indicating a detail oversight. The correct combination would need to be fixed (either the day or the date).
(Each of these tasks has an objective answer. Scoring is straightforward: the candidate either identifies the correct error/inconsistency or not. These simulate tasks like checking data entries, reviewing logs, or proofreading IT communications where attention to detail is crucial.)
The following prompts simulate real workplace communication scenarios an IT Manager might handle. Candidates would be instructed to draft responses (emails or messages). These tasks assess clarity, tone, and appropriateness of communication. Scoring would be based on inclusion of key points and professional tone.
1.
Maintenance Announcement Email: Prompt: Draft an email to all employees informing them of a scheduled network maintenance this weekend. Include the timing, which services will be affected (e.g., internet, VPN, servers), and any actions employees should take (such as saving work or logging off). The tone should be informative and reassure staff that IT is taking care to minimize disruption.
2.
Expectation (Key points to cover): The email should clearly state when the downtime will occur (date and start/end time), what systems or services are impacted (e.g. internet and internal systems will be unavailable), and if any preparation is needed by employees (e.g. please save your work and log off before 8 PM). It should use a polite, appreciative tone (e.g. Thank you for your understanding). It might also provide a point of contact for questions and an apology for inconvenience. The language must be non-technical enough for all staff to understand.
3.
Scoring notes: Full points if the draft includes all critical details (when, what, action needed) and has a professional, clear tone. Minor deductions if something is missing (e.g. no mention of what to do or missing end time). Major deduction if tone is inappropriate (too abrupt or too much jargon) or info is incorrect.
4.
Responding to an Upset User (Email): Prompt: You receive an email from an employee who is frustrated that their laptop has had recurring issues and wasnt fixed after multiple support requests. They say, This is unacceptable, I keep losing work! Draft a reply email as the IT Manager to acknowledge the frustration, outline what steps will be taken to resolve the issue permanently, and re-establish confidence.
5.
Expectation: The reply should start by acknowledging the users frustration and apologizing for the inconvenience (Im sorry youve experienced these ongoing issues). It should then state a plan of action for example, that you will personally investigate or assign a senior technician, ensure the problem is fixed, and possibly offer a solution like a loaner device or checking for hardware replacement if needed. The tone must be empathetic, not defensive. It should assure the user that their concerns are taken seriously and maybe give a timeframe or next steps (I will contact you by end of day with an update or we will schedule a time to swap out your laptop).
6.
Scoring notes: Look for empathy in the opening, a clear commitment to resolve (not just generic well try), and a professional tone. A top answer also avoids blaming the user and doesnt make excuses instead it focuses on solution and prevention of further issues. Points off if the response sounds dismissive or doesnt actually propose a concrete next step.
7.
8.
9.
10.
11.
12.
Explaining an IT Policy on Chat (IM): Prompt: A manager pings you on Slack/Microsoft Teams: Why cant my team just use Dropbox instead of the company file server Its easier for them. In a chat response, briefly explain the companys policy (assuming external cloud storage like Dropbox is against policy for security reasons) and suggest a compliant solution, all in a friendly, informative tone.
Expectation: The IM reply should politely explain the reason behind the policy (e.g. For security and compliance, we need all files on approved systems external cloud services like Dropbox arent vetted for company data security). It should avoid simply saying because its policy; instead, offer understanding and an alternative: perhaps using the companys approved cloud (OneDrive/Google Drive or VPN to the file server) and offering to help the team set that up. Tone: courteous and helpful (I understand Dropbox seems convenient... however, our policy exists to protect client data. We do have [alternative] which is secure. Id be happy to help your team get set up if needed.).
Scoring notes: Full credit if the answer balances enforcement with helpfulness i.e., it communicates why the policy is important (security) and demonstrates customer service by offering a path forward. If the response is too authoritarian (Because I said so, no Dropbox, end of story) or too lax (implying the manager could just do it anyway), thats a negative.
Incident Report to Management (Email): Prompt: Write a brief email to the COO summarizing a major IT incident that occurred (e.g., email server outage for 2 hours yesterday). Include what happened, how it was resolved, and steps to prevent it recurring. Keep it concise and factual, as this may be forwarded to the CEO.
Expectation: A concise recap: an opening line stating the incident and timeframe (Yesterday from 3:005:00 PM, the email server was down for all users). Then a sentence on cause (Root cause was an overloaded database that triggered a crash) if known, or that its under investigation if not fully known. Next, state resolution (Service was restored at 5:00 PM after restarting the database and removing a stuck process). Finally, preventive measures (To prevent this in future, we are implementing an alert for high database load and will schedule a memory upgrade this weekend). Tone should be professional and reassuring, showing IT has it under control. No overly technical jargon assume the reader is a non-IT executive.
Scoring notes: Check for inclusion of the three main parts: what/when, resolution, future prevention. Clarity is key if an executive can understand it easily. Points off for unnecessary technical detail (e.g. stack traces or jargon) or for omitting one of the parts. Bonus points if the tone takes responsibility appropriately and is proactive about next steps, demonstrating accountability.
(Evaluation of communication tasks will consider whether the candidates response is clear, correct, appropriately toned, and addresses the prompt. While multiple phrasings can be acceptable, the presence of essential information and a service-oriented tone are the deterministic scoring factors.)
Tasks
These tasks present scenarios requiring the candidate to outline their approach or process step-by-step. The goal is to test practical know-how in troubleshooting and IT procedures. Each has an expected solution path for scoring.
1.
New Employee Onboarding IT Setup: Task: Outline the steps you (as IT Manager) would take to onboard a new employee from an IT perspective. Assume their first day is next Monday. Include account setup, equipment preparation, and any access or orientation steps.
2.
Expected Step-by-Step Answer:
1.
Accounts & Access: Create the new users accounts in relevant systems ahead of time e.g. Active Directory account or Google Workspace account, company email address, and add them to appropriate groups/distribution lists (for access to shared drives, email lists). Also set up accounts in any key apps (CRM, Slack/Teams, etc.) as per their role.
2.
Equipment Preparation: Prepare their laptop/desktop. This includes installing the standard OS image or configuring a new machine with required software, applying updates and security settings. Set up their phone or other devices if provided. Ensure the computer is tagged (asset ID) and recorded in inventory.
3.
Credentials: Generate initial login credentials (temporary password/PIN) and ensure its ready to hand over securely on day one (often the user will be prompted to change password on first login).
4.
Workspace Setup: If on-site, set up their desk with docking station, monitors, peripherals, and test that everything (network connection, phone extension if any) is working. If remote, prepare shipping of equipment or ensure VPN accounts are set.
5.
Welcome and Orientation: On start day, either meet with the employee (or send instructions if remote) to hand over equipment, provide their login info, and guide them through first login, email setup on phone (if applicable), and introduction to how to get IT help (explain ticketing system or contact).
6.
Security Briefing: Brief the new hire on IT policies and security practices (acceptable use, password policy, MFA setup, phishing awareness training link, etc.). Make sure they enroll in any required security systems (like multi-factor authentication enrollment on their accounts).
7.
Verify Access: Double-check the new hire can access shared drives, email groups, and essential software for their role. Be available for any troubleshooting on their first day.
(Scoring: The candidate should mention creating accounts, setting up hardware/software, and covering security/policy orientation. They might list 57 steps similar to above. Full points if all major areas are covered in a logical order. Minor omissions (e.g. not mentioning policy training) could be partial credit. The sequence and thoroughness can be evaluated.)
3. Troubleshoot: Office Internet is Down: Task: Your entire office suddenly cant access the internet. Describe the step-by-step troubleshooting process you would take to diagnose and resolve the outage.
4. Expected Step-by-Step Answer:
1.
Verify the Scope: Check whether the issue is truly office-wide. For example, confirm that multiple devices (your own PC and others) cannot reach external sites. Determine if internal network resources are accessible (if internal is up but external down, that points to the ISP).
2.
Check Physical Connections/Power: Look at the network infrastructure is the main router/ firewall up Check the lights on the modem, router, and switches. Ensure no cable is unplugged and that equipment has power (perhaps someone accidentally knocked out a plug or a power strip tripped).
3.
ISP/Modem Status: If the modem/router has status indicators for internet link, check those. Log in to the routers admin console if possible see if it shows connection to ISP. If theres an outage notification from the ISP (some routers show this or you might have an external 4G to test ISP connectivity).
4.
Internal Network Check: Ensure the internal network is functioning: e.g. can computers talk to the router (ping the gateway IP) If not, maybe internal networking is the issue (e.g. a switch failure). If internal is fine, focus on external path.
5.
ISP Contact: If it appears to be an external connectivity issue (and quick tests like rebooting the modem dont fix it), contact the internet service provider to report the outage or get details. Often, widespread internet outage resolution is on the ISP side.
6.
Temporary Mitigation: While troubleshooting, communicate with the office (Were aware of the internet outage and troubleshooting it). If you have a backup internet link (like a secondary WAN or a hotspot), consider activating it for critical users.
7.
Resolution: Implement the fix if it was internal (e.g. a failed router), replace or reset that equipment. If ISP restored service, verify internet is back. After connectivity returns, do a quick test on critical services (VPN, etc.).
8.
Post-mortem: Identify the root cause if possible (ISP issue vs hardware failure). Document what happened and any improvements (maybe you realize you need a redundant link or better monitoring).
(Scoring: A good answer will start with checking basics (scope, hardware) and not jump straight to complex steps. They should mention contacting ISP if needed and communicating to users. Full credit if the steps are logical and cover both internal and external possibilities. Points off if they miss obvious initial steps (like checking if the router is powered) or if they dont mention communicating status during the outage.)
5.
Responding to a Malware Infection: Task: One employee reports that they opened an email attachment and now their computer is acting strangely a possible malware infection. Outline the steps you take in response to this security incident.
6.
Expected Step-by-Step Answer:
1.
Isolate the Machine: Immediately instruct the user to disconnect from the network (unplug Ethernet or turn off Wi-Fi). If they are in the office, go there and physically disconnect it. This prevents potential spread of malware.
2.
Assess & Calm User: Tell the user not to panic and not to use the machine further. Get details on what they observed (error messages, ransomware note, etc.), but minimize interaction with the infected system for now.
3.
Secure Credentials: If theres any chance credentials might be compromised (e.g. they entered a password after malware ran), advise them to change those passwords from a
different safe machine. If the machine was logged into critical accounts, consider those creds potentially stolen and respond accordingly (force password resets, etc.).
4.
Scan and Identify Malware: Run an antivirus/anti-malware scan using a trusted boot disk or in safe mode. Alternatively, remove the drive and scan it externally, or use EDR tools centrally if available. Determine the nature of the malware (virus, ransomware, etc.).
5.
Remove Threat & Recover Machine: Attempt cleaning using security tools. Often it might involve quarantining or removing infected files. If cleaning fails or system integrity is suspect, plan to reimage the PC and restore data from backups.
6.
Restore Data: If files were encrypted or damaged and you have backups, start restoring critical files once the system is clean or reimaged. If no backups and its ransomware, escalate according to company policy (do not pay ransom; involve management and possibly law enforcement).
7.
Update and Patch: Ensure the machine (and all others) have latest security patches and antivirus definitions to prevent this exploit.
8.
Communication & Education: Inform other staff if needed (e.g. IT detected a malware incident, please be vigilant with email attachments). Check if others received similar phishing emails. Use this as a teachable moment maybe send a security reminder company-wide about not opening suspicious attachments.
9.
Post-Incident Analysis: Document the incident: how it happened, what was impacted, how it was resolved. If needed, update security measures (maybe this incident shows a need for better email filtering or additional training).
(Scoring: Strong answers isolate the threat first, protect data/credentials, then remediate. A candidate should absolutely mention disconnecting the machine and scanning. Not mentioning containment (isolation) would be a major miss. Also, expecting mention of communication and learning to demonstrate a complete security mindset. Full credit if steps align with standard incident response: contain, eradicate, recover, communicate.)
7.
Routine Backup Test Restoration: Task: Describe how you would periodically test your backups to ensure data can be restored (describe one cycle of a test restore process).
8.
Expected Steps:
1.
Select Backup Set to Test: Choose a recent backup (for example, last weeks full backup of a critical server or a random file from user backups) as the target for a restoration test.
2.
Prepare Test Environment: Never overwrite production data for a test instead, prepare a safe location to restore to. This could be a test server, a spare machine, or a different directory path on the server, so as not to interfere with live data.
3.
Perform Restore: Using the backup software, perform a restore of the selected data to the test location. If its a file backup, restore a sample of files; if its a system backup, perhaps spin up a VM and attempt a full system restore there.
4.
Verify Integrity: After restoration, verify the files or system work correctly. For files, ensure they open and are the expected versions. For system images, verify the system boots and applications run. Check for any errors reported during the restore process.
5.
Document Results: Record the outcome of the test: e.g. Backup from Oct 1 restored successfully to test server in 22 minutes; verified key files X, Y, Z were intact. If any issues arose (corrupted archive, slower than expected, etc.), note them and take corrective action (maybe need to fix the backup job or adjust retention policies).
6.
Frequency & Improvement: State that you would do such test restores regularly (e.g. monthly for critical systems, quarterly for others). Use the tests to improve confidence and
tweak processes (for example, if a test took too long, maybe plan for a different backup strategy).
(Scoring: This task expects the candidate to show understanding that a backup is only good if it can be restored. Full credit if they mention a separate test environment and verifying the data. Points off if they say something risky like restoring directly over production to test which wouldnt be realistic. Also, mentioning documentation of the test is a plus indicating thoroughness.)
Already have an account? Use template directly
Recommended Interview Questions
- 1
How do you prioritize and handle communication The scenario tests balancing critical issues, triaging security vs. executive support, and keeping calm under pressure.
- 2
How do you handle the post-outage communication and accountability This scenario looks at whether the IT Manager transparently communicates the cause and remediation, takes responsibility, and outlines prevention steps versus deflecting blame or downplaying the issue.
- 3
How do you respond The scenario tests integrity to follow policy, negotiation skills (perhaps finding a secure way to meet the need), and the ability to handle pressure from higher-ups for exceptions.
- 4
How do you approach the situation and present options to leadership This scenario examines business-savvy and problem-solving do you gather data on downtime and push the vendor for SLA compliance, propose a backup line, or rush into a new contract The right approach balances immediate needs with long-term implications.
- 5
What do you do The scenario tests the IT Managers approach to enforcing data policies ideally educating the employee and securing the data immediately and gauges their tact and firmness in handling sensitive policy violations by a colleague.
- 6
How do you communicate and set expectations across the company This scenario checks how the IT Manager manages time and expectations whether theyll ask management for prioritization help or help from an MSP, or just over-promise and likely under-deliver. It reveals attitude toward self-management and seeking help when needed.
Already have an account? Use flow directly
Scoring Guidance
Full points if the draft includes all critical details (when, what, action needed) and has a professional, clear tone. Minor deductions if something is missing (e.g. no mention of what to do or missing end time). Major deduction if tone is inappropriate (too abrupt or too much jargon) or info is incorrect.
Look for empathy in the opening, a clear commitment to resolve (not just generic well try), and a professional tone. A top answer also avoids blaming the user and doesnt make excuses instead it focuses on solution and prevention of further issues. Points off if the response sounds dismissive or doesnt actually propose a concrete next step.
Full credit if the answer balances enforcement with helpfulness i.e., it communicates why the policy is important (security) and demonstrates customer service by offering a path forward. If the response is too authoritarian (Because I said so, no Dropbox, end of story) or too lax (implying the manager could just do it anyway), thats a negative.
Check for inclusion of the three main parts: what/when, resolution, future prevention. Clarity is key if an executive can understand it easily. Points off for unnecessary technical detail (e.g. stack traces or jargon) or for omitting one of the parts. Bonus points if the tone takes responsibility appropriately and is proactive about next steps, demonstrating accountability.
The candidate should mention creating accounts, setting up hardware/software, and covering security/policy orientation. They might list 57 steps similar to above. Full points if all major areas are covered in a logical order. Minor omissions (e.g. not mentioning policy training) could be partial credit. The sequence and thoroughness can be evaluated.)
A good answer will start with checking basics (scope, hardware) and not jump straight to complex steps. They should mention contacting ISP if needed and communicating to users. Full credit if the steps are logical and cover both internal and external possibilities. Points off if they miss obvious initial steps (like checking if the router is powered) or if they dont mention communicating status during the outage.)
Strong answers isolate the threat first, protect data/credentials, then remediate. A candidate should absolutely mention disconnecting the machine and scanning. Not mentioning containment (isolation) would be a major miss. Also, expecting mention of communication and learning to demonstrate a complete security mindset. Full credit if steps align with standard incident response: contain, eradicate, recover, communicate.)
This task expects the candidate to show understanding that a backup is only good if it can be restored. Full credit if they mention a separate test environment and verifying the data. Points off if they say something risky like restoring directly over production to test which wouldnt be realistic. Also, mentioning documentation of the test is a plus indicating thoroughness.)
Red Flags
Disqualifiers
When evaluating candidates for this IT Manager/Administrator role, watch out for the following red flags that could indicate a poor fit or potential problems:
Superficial Technical Knowledge: The candidate talks in buzzwords or lists many tools but cannot clearly explain how they used them to achieve results. For example, they mention we implemented AWS and Kubernetes but cant articulate the challenges or outcomes. Shaky grasp of fundamental concepts (networking basics, backup vs. archive, etc.) beneath resume keywords is a major red flag.
Poor Attitude Toward Users: Any hint of condescension or lack of empathy when discussing end-users is concerning. If the candidate refers to user requests as dumb or seems irritated by basic support tasks, thats a bad sign. An IT Manager in an SMB must have a service mindset; dismissive language or an unwillingness to help non-technical colleagues would be disqualifying.
Blame-Shifting or Lack of Ownership: In behavioral answers, if the person never takes accountability and always blames others (previous coworkers, stupid management decisions, users) for issues, it indicates poor ownership. An IT Manager needs to be solutions-focused and own problems. Frequent use of they failed vs. heres what I could have done is a red flag.
Resistance to Learning or Feedback: A candidate who is stuck in their way of doing things (Ive always done it this way and it works, why change) or who gets defensive when confronted with new ideas is problematic. The IT field changes rapidly; someone not interested in learning new technologies or who brushes off the need for ongoing development will fall behind and may not adapt in an SMB environment.
Overemphasis on Enterprise Scale Only: If the candidates experience and answers all revolve around having large teams or siloed duties, and they express reluctance or disdain for hands-on work (In my last job I had a team to do that, I wouldnt personally fix a printer), it could signal a poor fit for an SMB. In a 200-person company, the IT Manager has to be willing to roll up their sleeves. A hint of that task is beneath me is a red flag.
Communication Red Flags: Pay attention to how the candidate communicates in answers and any written exercise. Red flags include very disorganized explanations, excessive use of jargon when asked to simplify (indicating inability to adjust to audience), or rambling off-topic answers. Since communication is key, an inability to convey thoughts clearly or a pattern of misunderstanding questions might disqualify the person. Additionally, unprofessional tone (especially in written tasks
e.g. replying curtly or impolitely) is a serious concern.
Negativity About Past Employers/Teams: If the candidate bad-mouths previous employers, colleagues, or clients at length, it reflects poorly on their attitude. While some constructive critique is fine, an overly negative tone or lack of any positive lessons learned suggests potential interpersonal issues. Also watch for signals they had conflicts they didnt resolve constructively.
Ethical Lapses or Security Indifference: Any suggestion that they would take unethical shortcuts
(e.g. use unlicensed software, hack something in production without approval) or would ignore security/privacy policies to make things easier is a glaring red flag. For instance, joking that they sometimes used a single admin password for all systems to save time is grounds for elimination. Similarly, if in SJT scenarios they choose clearly irresponsible actions (like hiding an incident), thats disqualifying.
Lack of Attention to Detail: If the candidate makes many careless mistakes in the assessment (such as significant typos in the writing tasks, or failing to notice obvious errors in the accuracy tasks), it indicates poor attention to detail. An IT Manager dealing with configurations and contracts needs to be detail-oriented; multiple mistakes or inconsistent information in their responses would be concerning.
Frequent Job Hopping without Insight: While many IT careers involve several jobs, a pattern of very short stints (e.g. <1 year in multiple roles) combined with weak explanations can be a red flag. It might indicate performance issues or lack of commitment. If they left several jobs quickly and blame the employer in each case, thats even worse. (This can be verified via resume review rather than the assessment, but its something to note as a disqualifier unless well explained.)
(Any one of these red flags, especially in combination or unmitigated by other factors, should weigh heavily in the hiring decision. The presence of red flags in critical areas like security, attitude, or fundamental knowledge would typically mean a no-go for the candidate.)
10) Assessment Blueprint (30 minutes, 5 sections)
A structured 30-minute assessment is designed, covering five key areas. Each section, time allocation, and example content are outlined below. All questions/tasks are meant to be deterministic i.e., they have correct answers or clear rating criteria for objective scoring. Answer keys and scoring notes are provided for each part.
A. Cognitive (5 min) 4 Questions
Format: Multiple-choice or short-answer questions assessing logic, basic math, and reasoning in an IT context. These are quick questions to gauge general cognitive ability relevant to the role (like problem-solving, basic numerical reasoning, attention to simple logic).
1. Quantitative Reasoning: Question: The IT budget for the year is $120,000. Approximately what is
the average spending per month 2. a. $8,000 3. b. $10,000 4. c. $12,000
5. d. $15,000 Correct Answer: b. $10,000. (Calculation: $120,000/12 months = $10,000 per month.) Scoring: 1 point for correct selection. (Tests basic division and understanding of budgets; wrong answers show difficulty with straightforward math.)
6.
Logical Sequence: Question: A server backup starts at 11:00 PM and takes 2.5 hours to complete. At approximately what time should it finish
7.
a. 1:30 AM
8.
b. 2:30 AM
9.
c. 12:30 AM
10.
d. 2:00 AM Correct Answer: a. 1:30 AM. (11:00 PM + 2.5 hours = 1:30 AM.) Scoring: 1 point for correct answer. (Ensures candidate can handle time addition, relevant for scheduling tasks.)
11.
Pattern Recognition: Question: Which of the following IP addresses does NOT belong in the same network, assuming a subnet mask of 255.255.255.0 (/24) for 192.168.5.0 network
12. a. 192.168.5.45 13. b. 192.168.5.200 14. c. 192.168.6.10
15. d. 192.168.5.150 Correct Answer: c. 192.168.6.10. (All others start with 192.168.5.X which is the 192.168.5.0/24 network. The address with 192.168.6. is in a different subnet.) Scoring: 1 point for c. (Tests basic understanding of IP ranges or pattern odd-one-out; a technically relevant logic pattern.)
16. Basic Problem-Solving: Question: If 30 employees each have 2 devices connected to the network (e.g., a desktop and a phone) and 10 employees have only 1 device, how many total devices are on the network
17. a. 40 18. b. 50 19. c. 70 20. d. 90
Correct Answer: d. 90. (Calculation: 30 employees with 2 devices = 60 devices, plus 10 employees with 1 device = 10, total 70. Wait, check the math: Actually 302 = 60 and 101 = 10, sum = 70, so option c. Need to correct the question or answer.) Scoring: 1 point for correct answer. (This question checks basic arithmetic and translating a scenario into numbers. The correct answer is 70, which corresponds to option c, not d. We should correct the options: likely the intended total was 70. We'll adjust accordingly.)
Correction: Let's adjust the numbers to match the intended correct answer or vice versa. Perhaps they meant 20 employees have 2 devices and 10 have 1: that would be 202 + 101 = 40 + 10 = 50. Or if we keep 30
and 10, answer should be 70. Probably better to make it 70 devices, matching option c. So: 30 employees with 2 devices (60) + 10 employees with 1 (10) = 70. So correct answer is 70 (c).
I'll rewrite that question properly:
Revised Q4: If 30 employees each have 2 devices connected to the network, and another 10 employees each have 1 device, how many total devices are connected Options: a. 40, b. 60, c. 70, d. 80. Correct: c. 70. (Then explanation.)
We must ensure the final answer is correct. Good catch that 60+10=70. I'll present as correct....
What is the Role of an IT Manager 10 Responsibilities | Binary Blue
Do IT Managers Fit in an SMB -Cortavo by Aventis Systems
Example Interview Guide for IT Manager
IT Manager Job Description | LinkedIn Talent Solutions
IT Manager Job Description [Updated for 2026]
Identifying IT Candidate Red Flags: A Hiring Managers Guide to Better Technical Hires Refactor Talent
The Evolution of IT Help Desk: What SMBs Should Expect
When to Use This Role
IT Manager / IT Administrator (SMB) is a senior-level role in Engineering. Choose this title when you need someone focused on the specific responsibilities outlined above.
How it differs from adjacent roles:
- IT Support Specialist / Help Desk Technician: Function: The IT Support Specialist (Help Desk Technician) serves as the first line of technical support for a companys employees, ensuring that users can effectively use the organizations hardware, software, and network services in their daily work.
Related Roles
Deploy this hiring playbook in your pipeline
Every answer scored against a deterministic rubric. Full audit log included.