IT Support Specialist

Role Purpose & Context

Role Summary

The IT Support Specialist is here to make sure our team can actually do their jobs without technology getting in the way. Day-to-day, you'll be troubleshooting issues, answering questions, and generally being a hero to anyone whose computer decides to have a bad day. You'll sit right at the heart of our operations, acting as the bridge between our colleagues and the complex IT systems that power everything we do. When you do this well, our people feel supported, productive, and happy, which means they can focus on their own work without tech headaches. When things aren't going so well, well, let's just say productivity grinds to a halt, and frustration levels climb pretty quickly. The challenge here is that every problem feels urgent to the person experiencing it, so you'll need to juggle priorities and keep a cool head. The reward? Honestly, it's the immediate gratitude you get when you fix someone's problem and see them get back on track. It's a real buzz, that.

Reporting Structure

• Reports to: Systems Administrator or Senior Systems Engineer
• Direct reports:
• Matrix relationships: Helpdesk Technician, Junior Systems Administrator, Desktop Support Engineer, Service Desk Analyst,

Key Stakeholders

Internal:

• All our colleagues across every department (Sales, Marketing, Finance, Product, etc.)
• Your immediate IT team members (Systems Administrators, Engineers)
• Departmental managers who need updates on their team's issues

External:

• Software vendors (e.g., Microsoft, Adobe) for basic support queries
• Hardware suppliers (e.g., Dell, HP) for warranty claims or troubleshooting

Organisational Impact

Scope: This role directly impacts the daily productivity and morale of every single person in the company. If you keep everyone's tech running smoothly, the whole business runs smoothly. If you don't, well, nothing gets done. It's foundational work, really, and it's absolutely vital for keeping the lights on and our people working effectively.

Performance Metrics

Quantitative Metrics

1. Metric: Ticket Resolution Time (P3/P4)
2. Desc: How long it takes you to close out routine, lower-priority support tickets.
3. Target: Resolve 90% of P3/P4 tickets within 8 business hours.
4. Freq: Weekly and Monthly reviews.
5. Example: If a user reports a slow internet connection (P3) at 9 AM, you'd aim to have it fixed or escalated by 5 PM that same day.
6. Metric: First Contact Resolution (FCR) Rate
7. Desc: The percentage of issues you fix on the very first interaction with the user, without needing to pass it on or follow up later.
8. Target: Achieve a 70% FCR rate for common issues like password resets or basic software installs.
9. Freq: Monthly, based on ticket categorisation.
10. Example: A user calls about a forgotten password, and you reset it and confirm access during that initial call. That's an FCR win.
11. Metric: User Satisfaction (CSAT)
12. Desc: How happy our colleagues are with the support they receive from you, usually measured by a quick survey after a ticket is closed.
13. Target: Maintain an average CSAT score of 4.5 out of 5.
14. Freq: Ongoing, with monthly reporting.
15. Example: After you fix someone's email issue, they get a survey and rate your help as 'Excellent' (5/5).
16. Metric: Runbook Adherence
17. Desc: How closely you follow the documented, step-by-step guides for common tasks and incident responses. This is crucial for consistency and learning.
18. Target: Adhere to established runbooks for 95% of routine tasks and incidents.
19. Freq: Reviewed during weekly 1-to-1s with your manager.
20. Example: When setting up a new laptop, you follow every step in the 'New User Onboarding' runbook, ensuring all software and security settings are correctly applied.

Qualitative Metrics

1. Metric: Learning & Development
2. Desc: Your proactive effort to learn new systems, processes, and troubleshooting techniques. It's about showing you're keen to grow.
3. Evidence: Asking thoughtful questions during team meetings, completing assigned training modules on time, taking notes during shadowing sessions, showing improvement in handling recurring issues over time.
4. Metric: Team Collaboration & Communication
5. Desc: How well you work with your immediate team, sharing knowledge, asking for help when you need it, and keeping everyone in the loop.
6. Evidence: Actively participating in daily stand-ups, clearly documenting your ticket notes for others to understand, offering to help colleagues during busy periods, giving constructive feedback during code reviews (when you get there!).
7. Metric: Problem Documentation Quality
8. Desc: How well you document the issues you resolve, the steps you took, and any new solutions you discover. This helps everyone else in the future.
9. Evidence: Clear, concise, and complete ticket notes; updating knowledge base articles with new solutions (under guidance); ensuring all relevant information is captured for future reference or escalation.
10. Metric: Proactive Issue Identification
11. Desc: Spotting potential problems before they become big ones, or noticing patterns in user complaints that suggest an underlying issue.
12. Evidence: Flagging a recurring issue to your manager, noticing that three different users have the same obscure software bug and bringing it to the team's attention, suggesting an improvement to a process you've identified as inefficient.

Primary Traits

• Trait: The Calm Problem Solver
• Manifestation: When someone's panicking because their presentation won't load, you're the one who takes a deep breath and systematically goes through the steps. You don't get flustered when things go wrong; instead, you focus on what you can do to fix it. You can follow a runbook step-by-step, even when there's a bit of pressure.
• Benefit: In IT support, every problem feels like a P1 to the person experiencing it. If you panic, they panic. We need someone who can stay cool, think clearly, and apply the right solution, or at least the right escalation path, to get things sorted. Keeping calm under pressure means issues get resolved faster and users feel reassured.
• Trait: The Clear Communicator
• Manifestation: You can explain a complex technical issue in plain English to someone who barely knows how to turn on a computer. You're patient, you listen carefully to what people are actually saying (not just what you think they're saying), and you make sure they understand your instructions. You're not afraid to ask for clarification if something's unclear.
• Benefit: A huge part of IT support isn't just fixing the tech, it's fixing the communication. If you can't understand the user's problem, or if they can't understand your solution, then nothing gets resolved. Being able to translate 'tech-speak' into 'human-speak' builds trust and gets everyone back to work quicker. It also means fewer repeat calls.

Supporting Traits

• Trait: Curious Learner
• Desc: You're genuinely interested in how things work and why they break. You'll ask 'why?' and try to understand the underlying cause, not just apply a quick fix. You're eager to pick up new skills and aren't afraid to admit when you don't know something, then go find the answer.
• Trait: Organised & Methodical
• Desc: You like following a process. You'll keep your ticket queue tidy, make sure your notes are clear, and you won't skip steps in a troubleshooting guide. This means fewer mistakes and more consistent results, which is vital in IT.
• Trait: Empathetic Listener
• Desc: You can put yourself in the user's shoes. You understand that a slow computer isn't just an inconvenience; it can be genuinely frustrating and impact someone's ability to do their job. You'll show patience and understanding, even when the user is stressed.

Primary Motivators

1. Motivator: Solving Tangible Problems
2. Daily: You get a real kick out of taking a broken thing and making it work again. The satisfaction of closing a ticket, knowing you've helped someone out, is what gets you through the day.
3. Motivator: Continuous Learning & Skill Building
4. Daily: You're always keen to learn something new, whether it's a new piece of software, a different troubleshooting technique, or understanding how a system actually fits together. You see every new problem as a chance to expand your knowledge.
5. Motivator: Being a Go-To Resource for Others
6. Daily: You enjoy being the person people come to when they're stuck. You like feeling helpful and being able to provide answers or solutions that make a real difference to someone's day.

Potential Demotivators

Honestly, this role isn't for everyone. If you're someone who needs every day to be completely different, or if you get easily frustrated by repetitive tasks, you might struggle a bit here. You'll often be solving the same problems over and over again, just for different people. Also, if you can't handle a bit of pressure when systems go down, or if you prefer working in isolation without much interaction, this probably isn't the right fit.

Common Frustrations

1. Dealing with users who haven't read the instructions you sent them five times.
2. Solving the same 'printer isn't working' issue for the tenth time this week.
3. When a 'quick fix' turns into a two-hour deep dive into a system you've never seen before.
4. Having to explain basic computer concepts repeatedly.
5. The occasional 2 AM phone call for a 'critical' issue that turns out to be someone's forgotten password.

What Role Doesn't Offer

1. Full autonomy to make strategic technical decisions (not yet, anyway).
2. A quiet, solitary work environment (you'll be talking to people constantly).
3. Guaranteed 9-to-5 hours every single day (sometimes things break outside of office hours).
4. The chance to build complex, new systems from scratch (you're maintaining and fixing existing ones).

ADHD Positives

1. The varied nature of incoming support tickets can provide novelty and stimulation, preventing boredom.
2. The immediate feedback loop of solving a problem and seeing a user's relief can be very motivating.
3. The need to quickly context-switch between different issues can be a strength for those with hyperfocus capabilities.

ADHD Challenges and Accommodations

1. Managing a busy ticket queue and prioritising can be overwhelming; using visual task boards (like Kanban) and clear prioritisation frameworks can help.
2. Detailed documentation can feel tedious; breaking it into smaller, manageable chunks or using templates can make it easier.
3. Potential for distraction in an open-plan office; noise-cancelling headphones or a quiet space for focused work can be arranged.

Dyslexia Positives

1. Strong practical, hands-on problem-solving skills are highly valued, often compensating for challenges with text-heavy tasks.
2. Excellent spatial reasoning can be a huge asset when visualising network layouts or hardware configurations.
3. Often brings a different perspective to troubleshooting, finding solutions others might miss.

Dyslexia Challenges and Accommodations

1. Reading and writing detailed technical documentation or long emails can be challenging; using spell-check/grammar tools, dictation software, or having a colleague proofread important communications can help.
2. Interpreting complex written instructions might require more time; providing verbal explanations or visual diagrams alongside written guides is beneficial.
3. Note-taking during calls or meetings can be difficult; recording meetings (with consent) or using structured templates can assist.

Autism Positives

1. A methodical and logical approach to troubleshooting, following procedures precisely, is a huge strength in IT support.
2. Strong focus on detail can help catch subtle issues that others might overlook.
3. Preference for clear, direct communication can be very effective in resolving technical problems efficiently.

Autism Challenges and Accommodations

1. Unexpected changes in routine or sudden urgent issues can be unsettling; providing as much warning as possible and clear, actionable steps during crises helps.
2. Interpreting social cues from frustrated users can be difficult; focusing on the technical problem and using structured communication scripts can be helpful.
3. Sensory overload in a busy office environment; offering a quieter workspace, noise-cancelling headphones, or flexible working arrangements can be considered.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Entry Level (0-2 years)
2. Responsibilities: Answer incoming support requests via phone, email, and our ITSM platform (ServiceNow) with a friendly, helpful attitude. This is usually the first point of contact for our colleagues.
3. Troubleshoot common IT issues like password resets, account lockouts, software installation problems, and basic network connectivity issues. You'll use our runbooks for this, of course.
4. Set up new hardware for incoming staff, including laptops, monitors, and peripherals. That means making sure everything's correctly configured and ready to go on day one.
5. Install and configure standard software applications (e.g., Microsoft Office, Adobe Creative Suite) on user devices, following our licensing guidelines.
6. Escalate more complex or unusual technical problems to the Systems Administrator or Senior Systems Engineer, making sure you provide all the relevant details you've gathered.
7. Keep our IT asset inventory up-to-date. This involves tracking who has what laptop, when it was issued, and when it needs replacing. Yes, it's boring, but it's essential.
8. Create and update documentation for common troubleshooting steps and FAQs. Future-you (and everyone else) will be grateful for clear notes.
9. Supervision: You'll have daily check-ins with your direct manager or a senior team member. All your work, especially on critical systems, will be reviewed. Think of it as close guidance to help you learn and grow quickly.
10. Decision: You won't be making independent technical or financial decisions. Any deviation from established procedures, or any issue you can't resolve with a runbook, needs to be escalated. For example, you can't authorise a software purchase or a major system change.
11. Success: Success here means consistently resolving routine tickets quickly and politely, learning from every interaction, and accurately documenting your work. It's also about showing initiative to learn new things and asking for help when you need it, rather than struggling in silence.

Decision-Making Authority

• Type: Troubleshooting a user's laptop issue
• Entry: Follow established runbooks; escalate if the issue isn't covered or if you're stuck after 30 minutes.
• Mid: Independently diagnose and resolve most common and some uncommon issues; consult senior on complex, novel problems.
• Senior: Diagnose and resolve all but the most obscure issues; provide guidance to junior staff; make decisions on replacement hardware if needed.
• Type: Installing new software for a user
• Entry: Install only approved software from the standard catalogue; escalate requests for unapproved software.
• Mid: Install approved software; evaluate and recommend new software for approval based on user needs and security policies.
• Senior: Approve or deny software requests based on policy and business need; manage software licensing and deployment strategy.
• Type: Ordering new IT equipment (e.g., a new mouse)
• Entry: Request new equipment through your manager, providing justification.
• Mid: Order standard equipment within a pre-approved budget (e.g., up to £100 per item) following procurement processes.
• Senior: Approve equipment purchases up to £5K; manage vendor relationships for standard hardware.

Competency Requirements

Foundation Skills (Transferable)

These are the core abilities that underpin everything you'll do. Think of them as your toolkit for interacting with people and solving problems, not just with computers.

• Category: Communication & Interpersonal Skills
• Skills: Active Listening: Really hearing what users are saying, not just waiting for your turn to speak. This helps you get to the root of the problem faster.
• Clear Verbal Communication: Explaining technical steps in a way that anyone can understand, without jargon. Being patient and polite, even when someone's frustrated.
• Written Communication: Writing clear, concise ticket notes and emails. No rambling, just the facts and the solution.
• Empathy & Patience: Understanding that not everyone is tech-savvy and that a broken computer is genuinely stressful for some people. Keeping a calm, helpful tone.
• Category: Problem Solving & Critical Thinking
• Skills: Logical Troubleshooting: Following a step-by-step process to diagnose issues, eliminating possibilities until you find the cause. It's like being a detective.
• Resourcefulness: Knowing where to look for answers—whether it's our internal knowledge base, a runbook, or asking a senior colleague.
• Attention to Detail: Noticing small clues that might point to a bigger problem, or making sure you've followed every step in a process correctly.
• Prioritisation: Figuring out which urgent request actually needs your attention first, especially when everything feels like a P1.
• Category: Adaptability & Learning Agility
• Skills: Openness to Feedback: Being able to take constructive criticism and use it to improve your work. We're all here to learn.
• Quick Learner: Picking up new software, systems, and troubleshooting techniques relatively quickly. IT changes fast, so you need to keep up.
• Flexibility: Being able to switch between different tasks and priorities as new issues come in. Sometimes your day won't go as planned, and that's okay.

Functional Skills (Role-Specific Technical)

These are the specific technical skills and knowledge you'll need to hit the ground running. Don't worry if you're not an expert in everything; we're looking for a solid foundation and a willingness to learn.

Technical Competencies

• Skill: Operating System Fundamentals
• Desc: A good grasp of Windows 10/11 and macOS basics. You should know how to navigate settings, manage files, install applications, and troubleshoot common OS-level issues.
• Level: Intermediate
• Skill: Network Basics
• Desc: Understanding of fundamental networking concepts like IP addresses, DNS, Wi-Fi, and how to troubleshoot basic connectivity problems (e.g., 'no internet').
• Level: Basic
• Skill: Hardware Troubleshooting
• Desc: Ability to diagnose and resolve common hardware issues with laptops, desktops, printers, and peripherals. Knowing when something needs to be replaced vs. fixed.
• Level: Intermediate
• Skill: Microsoft 365 / Google Workspace Administration
• Desc: Familiarity with user management (password resets, account unlocks) and basic troubleshooting for applications like Outlook, Teams, Word, Excel, or their Google equivalents.
• Level: Intermediate
• Skill: ITIL Framework (Foundational)
• Desc: A basic understanding of IT service management principles, especially Incident Management (how to log, prioritise, and resolve issues) and Service Request Management.
• Level: Basic

Digital Tools

• Tool: ServiceNow / Jira Service Management
• Level: Intermediate
• Usage: Logging, updating, and resolving support tickets; searching the knowledge base for solutions; managing your personal queue.
• Tool: Microsoft Intune / Jamf Pro
• Level: Intermediate
• Usage: Enrolling new devices; deploying standard application packages; checking device compliance; basic remote troubleshooting.
• Tool: AWS Console / Azure Portal
• Level: Basic
• Usage: Checking service health dashboards; managing user permissions (IAM/Entra ID) for basic tasks; pulling billing data for specific services (under guidance).
• Tool: Okta / Azure AD (Entra ID)
• Level: Intermediate
• Usage: Handling user provisioning/de-provisioning; password resets; assigning users to application groups; troubleshooting SSO issues.
• Tool: Datadog / SolarWinds
• Level: Basic
• Usage: Monitoring pre-configured dashboards for alerts; acknowledging issues; performing initial triage based on runbooks.
• Tool: Jira / Asana
• Level: Intermediate
• Usage: Updating tasks; tracking progress on assigned tickets; participating in sprint planning or Kanban boards for IT projects.

Industry Knowledge

• Area: IT Security Awareness
• Desc: Understanding basic security principles like strong passwords, phishing recognition, and the importance of data privacy. Knowing when to escalate a potential security incident.
• Area: Basic Vendor Interaction
• Desc: Knowing how to contact software or hardware vendors for support, provide them with necessary information, and follow up on cases.

Regulatory Compliance Regulations

• Reg: GDPR (General Data Protection Regulation)
• Usage: Understanding the importance of protecting personal data, knowing not to share sensitive information, and following procedures for data handling and access requests.
• Reg: Internal Security Policies
• Usage: Strictly following company policies on password management, device security, acceptable use, and incident reporting. You'll be trained on these, of course.

Essential Prerequisites

• A genuine interest in technology and problem-solving. You should enjoy tinkering with computers and figuring out why things aren't working.
• Some prior experience (even informal) in a customer service or support role. This could be retail, hospitality, or even helping friends and family with their tech.
• Basic computer literacy beyond just using a web browser—you should be comfortable with file systems, installing software, and understanding basic settings.
• A proactive attitude towards learning. We don't expect you to know everything, but we do expect you to be keen to learn and ask questions.
• The ability to work effectively in a team environment, sharing knowledge and supporting colleagues.

Career Pathway Context

These prerequisites are what we believe will set you up for success in this entry-level role. They're the building blocks for a long and rewarding career in IT. We're looking for potential and a solid foundation, not necessarily years of formal IT experience. If you've got the right attitude and a keen mind, we can teach you the rest.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: AI-Assisted Troubleshooting & Automation
• Why: AI isn't just for data scientists anymore; it's becoming a powerful tool for IT support. It'll help you diagnose issues faster, automate routine tasks, and even predict problems before they happen. Those who embrace it will be far more efficient.
• Concepts: [{'concept_name': 'Natural Language Processing (NLP) for ticket analysis', 'description': 'How AI understands and categorises the text in support tickets to route them correctly.'}, {'concept_name': 'Predictive analytics for common failures', 'description': 'Using data to anticipate when a hard drive might fail or a system might slow down.'}, {'concept_name': 'Basic chatbot interaction for self-service', 'description': 'Understanding how users interact with AI-powered chatbots for simple requests.'}, {'concept_name': 'Prompt engineering for AI assistants', 'description': 'Learning how to ask AI tools the right questions to get the best troubleshooting advice or documentation.'}]
• Prepare: This month: Start using our internal AI tools (like the smart knowledge base search) for every ticket you work on.
• Next quarter: Take an online course on 'Introduction to AI for IT Professionals' (we'll cover the cost).
• Month 4-6: Experiment with using public LLMs (like ChatGPT or Claude) to help draft troubleshooting steps or user communications (ensuring no sensitive data is used).
• Month 7-9: Work with your manager to identify one small, repetitive task that could potentially be automated with a simple script or AI tool.
• QuickWin: Start using AI to summarise long emails or draft initial responses to common support queries today. It's a low-risk way to get familiar with it.
• Skill: Cloud Service Management Basics
• Why: More and more of our systems are moving to the cloud (AWS, Azure, Google Cloud). Even at an entry level, you'll need to understand how these services work, how to monitor them, and how to troubleshoot connectivity or access issues related to them. It's the future of infrastructure.
• Concepts: [{'concept_name': 'Cloud vs. On-Premise differences', 'description': 'Understanding the fundamental differences in how services are hosted and managed.'}, {'concept_name': 'Basic cloud service models (IaaS, PaaS, SaaS)', 'description': 'Knowing what each means and how it applies to the tools we use.'}, {'concept_name': 'Cloud identity and access management (IAM)', 'description': 'How user permissions are managed in cloud environments like Azure AD or AWS IAM.'}, {'concept_name': 'Cloud monitoring dashboards', 'description': 'Learning to read and understand the health and performance metrics of cloud services.'}]
• Prepare: This month: Spend an hour each week exploring our AWS/Azure console, focusing on the dashboards and basic user management sections.
• Next quarter: Complete the 'AWS Cloud Practitioner Essentials' or 'Azure Fundamentals' free online course.
• Month 4-6: Shadow a Systems Administrator when they're working on a cloud-related task, asking questions about what they're doing.
• Month 7-9: Take ownership of a small, defined task related to cloud access or monitoring, under supervision.
• QuickWin: Familiarise yourself with the status pages for major cloud providers (e.g., status.aws.amazon.com) so you know where to check for outages.

Advancing Technical Skills

• Skill: Advanced Operating System Management
• Why: You'll move beyond basic troubleshooting to understanding the deeper configuration and optimisation of Windows and macOS, including scripting for automation and advanced diagnostics.
• Concepts: [{'concept_name': 'PowerShell/Bash scripting for automation', 'description': 'Writing simple scripts to automate repetitive tasks like user setup or log collection.'}, {'concept_name': 'Group Policy Objects (GPOs) / MDM profiles', 'description': 'Group Policy Objects (GPOs) / MDM profiles'}, {'concept_name': 'Advanced registry/plist editing and troubleshootin', 'description': 'Advanced registry/plist editing and troubleshooting'}, {'concept_name': 'Performance monitoring and optimisation tools (e.g', 'description': 'Performance monitoring and optimisation tools (e.g., Process Monitor)'}, {'concept_name': 'Disk imaging and deployment strategies', 'description': 'Disk imaging and deployment strategies'}]
• Prepare: This quarter: Start learning basic PowerShell or Bash scripting (there are loads of free tutorials online).
• Next quarter: Ask to shadow a Systems Administrator during a more complex OS deployment or configuration task.
• Month 7-9: Propose a small automation script for a task you do regularly.
• Month 10-12: Work towards a Microsoft Certified: Windows Client or Apple Certified Support Professional certification.
• QuickWin: Write a simple script to clear temporary files on your own machine. It's a small start, but it builds confidence.
• Skill: Network & Server Infrastructure Fundamentals
• Why: To effectively troubleshoot, you'll need to understand the underlying network and server infrastructure. This means moving beyond 'is the Wi-Fi working?' to 'what's causing this latency on the VPN?'
• Concepts: [{'concept_name': 'TCP/IP and common network protocols (DNS, DHCP)', 'description': 'Understanding how devices communicate on a network.'}, {'concept_name': "Router and switch basics (what they do, how they'r", 'description': "Router and switch basics (what they do, how they're configured)"}, {'concept_name': 'Virtualisation concepts (VMware, Hyper-V) and what', 'description': 'Virtualisation concepts (VMware, Hyper-V) and what a server actually is'}, {'concept_name': 'Basic firewall rules and network security principl', 'description': 'Basic firewall rules and network security principles'}, {'concept_name': 'VPN troubleshooting and connectivity issues', 'description': 'VPN troubleshooting and connectivity issues'}]
• Prepare: This quarter: Read a good 'Networking for Dummies' type book or complete an online 'Network Fundamentals' course.
• Next quarter: Ask to observe network changes or server maintenance, even if you're just watching.
• Month 7-9: Start using network diagnostic tools (like ping, tracert, ipconfig) more confidently to pinpoint issues.
• Month 10-12: Work towards a CompTIA Network+ certification.
• QuickWin: Learn to use 'ping' and 'tracert' commands effectively to diagnose basic internet connectivity issues.

Education Requirements

• Level: Secondary Education
• Req: GCSEs (or equivalent) in Maths and English at Grade C/4 or above.
• Alts: Relevant BTEC Level 3 qualification in IT or Computing, or demonstrable equivalent practical experience.
• Level: Further Education (Preferred but not essential)
• Req: A-Levels (or equivalent) in a STEM subject.
• Alts: A recognised IT apprenticeship completion, or a relevant Level 4 qualification.

Experience Requirements

We're looking for roughly 0-2 years of experience. This could be formal experience in a helpdesk or desktop support role, or even extensive informal experience helping friends, family, or a small business with their IT issues. What really counts is your enthusiasm, your problem-solving mindset, and your ability to communicate clearly. If you've spent your spare time building PCs, troubleshooting home networks, or setting up smart home tech, tell us about it – that absolutely counts!

Preferred Certifications

• Cert: CompTIA A+
• Prod: CompTIA
• Usage: This is a fantastic foundational certification for IT support, covering hardware, software, networking, and security basics. It shows you've got a solid understanding of the fundamentals.
• Cert: ITIL 4 Foundation
• Prod: AXELOS
• Usage: Gives you a great understanding of IT service management best practices, helping you understand how our IT department operates and how your role fits into the bigger picture.
• Cert: Microsoft Certified: Fundamentals (e.g., Azure Fundamentals, Microsoft 365 Fundamentals)
• Prod: Microsoft
• Usage: Demonstrates basic knowledge of Microsoft's cloud services, which are increasingly important for almost every business. It's a great stepping stone.

Recommended Activities

• Participating in online forums and communities (e.g., Reddit's r/sysadmin, Spiceworks) to learn from others and stay updated on common issues.
• Attending local IT meet-ups or webinars (many are free!) to network and pick up new ideas.
• Subscribing to relevant tech blogs or newsletters to keep abreast of industry trends and security alerts.
• Taking advantage of internal training programmes and shadowing opportunities with more senior team members.
• Building a small home lab (even a virtual one) to experiment with different operating systems, network configurations, or software deployments.

Career Progression Pathways

Entry Paths to This Role

• Path: IT Apprenticeship Programme
• Time: 1-2 years
• Path: Entry-Level Helpdesk / Desktop Support Role (External)
• Time: 1-2 years
• Path: Informal Tech Support / Self-Taught Enthusiast
• Time: Varies (often 0-2 years formal experience)

Career Progression From This Role

• Pathway: Systems Administrator (Level 2)
• Time: After 2-3 years in the IT Support Specialist role.

Long Term Vision Potential Roles

• Title: Senior Systems Engineer (Level 3)
• Time: 5-8 years from entry
• Title: IT Manager (Level 4)
• Time: 8-12 years from entry
• Title: Cloud Architect / Security Engineer (Specialist Paths)
• Time: 8-12 years from entry

How Zavmo Delivers This Role's Development

DISCOVER Phase: Skills Gap Analysis

Zavmo maps your current competencies against all requirements in this job description through conversational assessment. We evaluate your foundation skills (communication, strategic thinking), functional skills (CRM expertise, negotiation), and readiness for career progression.

Output: Personalised skills gap heat map showing strengths and priorities, estimated time to competency, neurodiversity accommodations.

DISCUSS Phase: Personalised Learning Pathway

Based on your DISCOVER results, Zavmo creates a personalised learning plan prioritised by impact: foundation skills first, then functional skills. We adapt to your learning style, pace, and neurodiversity needs (ADHD, dyslexia, autism).

Output: Week-by-week schedule, each module linked to specific job responsibilities, checkpoints and milestones.

DELIVER Phase: Conversational Learning

Learn through conversation, not boring modules. Zavmo uses 10 conversation types (Socratic dialogue, role-play, coaching, case studies) to build competence. Practice difficult QBR presentations, negotiate tough renewals, and handle churn conversations in a safe AI environment before facing real clients.

Example: "For 'Stakeholder Mapping', Zavmo will guide you through analysing a complex enterprise account, identifying key decision-makers, and building an engagement strategy."

DEMONSTRATE Phase: Competency Assessment

Zavmo automatically builds your evidence portfolio as you learn. Every conversation, practice scenario, and application example is captured and mapped to NOS performance criteria. When ready, your portfolio supports OFQUAL qualification claims and demonstrates competence to employers.

Output: Competency matrix, evidence portfolio (downloadable), qualification readiness, career progression score.