IT Support Manager

Role Purpose & Context

Role Summary

The Senior IT Support Manager is responsible for tackling the trickier IT issues that stump the rest of the team, ensuring our users stay productive and happy. You'll be the escalation point, the problem solver, and the mentor all rolled into one. This role sits right at the heart of our operations, bridging the gap between everyday user problems and the deeper technical solutions. You'll work closely with the junior team, helping them grow, and with other IT teams to sort out bigger system issues. When you do this well, our users get their problems sorted quickly and effectively, and our junior team members learn loads, making everyone more efficient. If it's not done well, simple issues can spiral, users get frustrated, and the business grinds to a halt. The challenge is balancing urgent user needs with the bigger picture of improving our IT systems. The reward? Seeing your team develop, knowing you've kept the business running smoothly, and solving those really tough, head-scratching problems.

Reporting Structure

• Reports to: IT Support Manager (L5)
• Direct reports: None (mentors 0-2 junior team members)
• Matrix relationships: Senior IT Support Engineer, Technical Support Lead, IT Systems Specialist (Senior), Service Desk Team Lead,

Key Stakeholders

Internal:

• L1/L2 IT Support Engineers (your mentees)
• IT Support Manager (your boss)
• Networking Team
• DevOps Team
• Internal Business Users (everyone from the CEO to the newest intern)
• Product Teams (when troubleshooting application issues)

External:

• Hardware and Software Vendors (when escalating issues to third-party support)
• Managed Service Providers (if we use them for specific functions)

Organisational Impact

Scope: This role is crucial for keeping our entire workforce productive. You're directly responsible for resolving complex technical roadblocks that stop people from doing their jobs. Your work ensures that our IT services are reliable, and that our support team is constantly improving, which frankly, saves the company a lot of money in lost productivity and keeps everyone sane.

Performance Metrics

Quantitative Metrics

1. Metric: SLA Adherence for Escalated Tickets
2. Desc: Ensuring that the more complex tickets you handle, or that your mentees escalate to you, are resolved within our agreed Service Level Agreements.
3. Target: >98% compliance on response and resolution SLAs for L2/L3 tickets.
4. Freq: Monthly, reviewed in 1-to-1s.
5. Example: If a P2 incident is assigned to you, you'll make sure it's acknowledged within 30 minutes and resolved within 4 hours, consistently hitting that target.
6. Metric: Ticket Escalation Rate Reduction
7. Desc: Reducing the number of tickets that need to be escalated to other, more specialised IT teams (like Networking or DevOps) by improving our internal knowledge and troubleshooting capabilities.
8. Target: Reduce escalations to other teams by 15% quarter-over-quarter.
9. Freq: Quarterly, based on ITSM platform data.
10. Example: If we escalated 100 tickets to the Networking team last quarter, your goal is to help the team resolve 15 of those types of issues internally this quarter, perhaps by creating a new runbook.
11. Metric: Knowledge Contribution & Quality
12. Desc: Actively creating, reviewing, and improving our internal knowledge base articles and runbooks, making it easier for everyone (especially junior staff) to solve problems.
13. Target: Author or approve >10 new or significantly updated KB articles per quarter.
14. Freq: Quarterly, tracked in Confluence/Knowledge Base platform.
15. Example: You'll write a detailed guide on 'Troubleshooting VPN Connectivity Issues on macOS' and review five articles written by junior engineers, ensuring they're clear and accurate.
16. Metric: Problem Management & RCA Completion
17. Desc: Successfully identifying the root cause of recurring incidents and ensuring that a permanent fix or workaround is implemented to prevent them from happening again.
18. Target: Lead and close out >3 Root Cause Analysis (RCA) investigations per quarter.
19. Freq: Quarterly, reviewed in problem management meetings.
20. Example: After a series of printer outages, you'll lead the RCA, identify a driver conflict, and work with the Endpoint Management team to deploy a fix, then document it.

Qualitative Metrics

1. Metric: Mentorship Effectiveness
2. Desc: How well you guide and develop junior IT Support Engineers, helping them grow their technical skills and problem-solving abilities.
3. Evidence: Feedback from junior team members (anonymous surveys or 1-to-1s), observed improvement in their ticket handling, their ability to take on more complex tasks, and their reduced need for direct supervision. Your manager will also look for your active participation in their development plans.
4. Metric: Incident Leadership & De-escalation
5. Desc: Your ability to take charge during P1 incidents, communicate calmly and clearly, and effectively de-escalate frustrated users or stakeholders.
6. Evidence: Post-incident review feedback, observations during 'war room' calls, positive comments from business users or other IT teams about your handling of stressful situations. The speed and clarity of your incident communications will also be key.
7. Metric: Process Improvement Impact
8. Desc: Your contributions to making our IT support processes more efficient, reliable, and user-friendly.
9. Evidence: Documented process changes you've initiated or championed, reduction in manual steps for common tasks, positive feedback from the team on new runbooks or workflows you've helped create, and observable improvements in team efficiency or user experience.

Primary Traits

• Trait: Calm Under Pressure (Operational)
• Manifestation: When the network's down and everyone's panicking, you're the one who takes a deep breath and starts methodically troubleshooting. You can handle an angry executive whose laptop just died before a big presentation, de-escalating the situation with a steady voice. You communicate clearly and concisely, even when systems are melting down around you, keeping everyone informed without adding to the chaos.
• Benefit: Let's be real, IT support can be stressful. Panic is contagious, and during a P1 incident, the team and the business look to you for leadership. Your composure sets the tone for the entire incident response, maintains stakeholder confidence, and frankly, helps everyone think straight to get things fixed faster. If you crumble when things get tough, the whole operation suffers.
• Trait: Empathetic (Client-facing)
• Manifestation: You actually listen to a frustrated user's full story without cutting them off, even if you already know the answer. You acknowledge the real business impact of their issue, saying things like, 'I completely understand this is stopping you from closing the month-end reports, let's get you sorted.' You're a wizard at translating tech jargon into simple, understandable terms for non-technical folks, making them feel heard and helped.
• Benefit: IT Support isn't just about fixing broken tech; it's about helping people who are often stressed and reliant on that tech. Empathy builds trust, reduces user frustration, and can turn a really negative experience into a positive interaction. This is absolutely critical for our CSAT scores and for making IT feel like a partner, not just a necessary evil. If you can't connect with people, you'll struggle to truly help them.
• Trait: Process-Minded (Operational)
• Manifestation: You're the one who insists on a ticket for every request, not because you're a bureaucrat, but because you know it ensures traceability and helps us spot trends. You're great at creating clear, step-by-step checklists (runbooks) for common, complex tasks, so anyone can follow them. You love digging into ticket data to spot trends that scream 'process failure' or 'recurring problem' and then you actually do something about it.
• Benefit: Truth is, repeatable processes create predictable, high-quality outcomes. A process-driven approach ensures consistency, reduces errors, makes onboarding new team members a breeze, and gives us the data we need for continuous improvement. Without it, we're just firefighting, and that's no way to run a support operation. If you hate documentation or think processes are 'red tape', this role won't be for you.

Supporting Traits

• Trait: Decisive
• Desc: You can make a quick, informed call on how to best allocate resources during a 'ticket swarm' or a major incident, even with incomplete information. You don't dither when a user is waiting.
• Trait: Patient
• Desc: You can walk a non-technical user through a complex procedure for the third time without showing any frustration. You understand that not everyone 'gets' tech as quickly as you do, and that's okay.
• Trait: Influential
• Desc: You can convince other IT teams (like Networking or DevOps) to prioritise a fix that's causing a flood of support tickets, even if it wasn't on their original roadmap. You're good at making your case.
• Trait: Curious
• Desc: You're innately driven to understand *why* something broke, not just how to slap a quick fix on it. You'll dig deeper, ask questions, and look for the underlying cause of recurring issues.

Primary Motivators

1. Motivator: Solving Complex Puzzles
2. Daily: You get a real kick out of taking on the trickiest, most obscure technical problems that have stumped everyone else. When a user has a weird, intermittent issue that defies all logic, you're the first to volunteer to dig in.
3. Motivator: Helping Others Grow and Succeed
4. Daily: You genuinely enjoy seeing junior team members 'get it' and become more capable. You're always ready to offer guidance, share knowledge, and patiently explain complex concepts, knowing it makes the whole team stronger.
5. Motivator: Making Systems More Efficient and Reliable
6. Daily: You're not content with just fixing things; you want to make sure they don't break again. You're always looking for ways to automate repetitive tasks, improve documentation, and streamline processes, so everyone's life is easier.

Potential Demotivators

Honestly, this role isn't for everyone. You'll rerun the same analysis three times because stakeholders keep changing the question. The 'urgent' request that disrupted your Thursday will get deprioritised on Friday. You'll build a beautiful model that never gets deployed because the business moved on. If you need to see every piece of work make it to production, you'll struggle here. If you're someone who needs constant, immediate gratification from every single task, you might find the pace of systemic improvement a bit slow. Also, if you can't stand explaining the same basic troubleshooting steps over and over, you'll find parts of this job frustrating.

Common Frustrations

1. The 'Reboot Lie': Spending 15 minutes troubleshooting only to discover the user never performed the first and most basic step: rebooting their machine. It's infuriating.
2. Being the 'Bearer of Bad News': Having to tell the business a critical application is down when the underlying infrastructure is managed by a different team that is slow to respond. You take all the heat.
3. 'Urgent' Ticket Fatigue: When every other ticket is marked 'Urgent' or 'High Priority' by users for non-urgent issues, completely devaluing the entire priority system.
4. Scope Creep from 'Shadow IT': Being asked to support a SaaS tool that a department purchased on a credit card, with no admin access, documentation, or training. It's a nightmare.
5. The Bottleneck Blame Game: Your team's MTTR metrics look terrible because you're waiting on the Networking or DevOps team for 80% of the resolution time, but your SLA is the one that breaches. It's not fair.

What Role Doesn't Offer

1. A quiet, solitary work environment with no interruptions – you'll be constantly interacting with people.
2. A clear, linear path where every problem has a simple, documented solution – you'll be dealing with ambiguity a lot.
3. A role where you can avoid documentation or process improvement – these are core to your success here.
4. An escape from direct user interaction – you're still very much on the front lines, just for tougher issues.

ADHD Positives

1. The fast-paced, varied nature of incident response and troubleshooting can be highly engaging for those with ADHD, offering constant novelty and problem-solving challenges.
2. The need to quickly context-switch between different problems and users can be a strength, as you'll be juggling multiple priorities.

ADHD Challenges and Accommodations

1. Maintaining focus on detailed documentation or lengthy Root Cause Analysis reports can be a challenge. We can use templates, checklists, and break down tasks into smaller, manageable chunks.
2. The constant interruptions from tickets and escalations might be overwhelming. We can explore tools for focus, dedicated 'deep work' blocks, or noise-cancelling headphones.
3. Organisational tools like advanced ITSM features, calendar blocking for specific tasks, and visual dashboards can help manage priorities and deadlines.

Dyslexia Positives

1. Strong problem-solving skills and the ability to see the 'big picture' in complex systems, often a strength for dyslexic individuals, are highly valuable in identifying root causes.
2. Excellent verbal communication skills, crucial for de-escalating users and mentoring junior staff, are often prominent.

Dyslexia Challenges and Accommodations

1. Reading and writing detailed technical documentation or incident reports can be time-consuming. We encourage the use of dictation software, grammar/spell checkers, and peer review for critical documents.
2. Complex forms within ITSM platforms might be difficult to navigate. Training can focus on visual cues and keyboard shortcuts, and we can explore customisable interfaces where possible.
3. Using tools like Grammarly, text-to-speech readers, and ensuring clear, concise formatting in all written communication will be supported.

Autism Positives

1. A methodical, logical approach to problem-solving and troubleshooting is a significant asset in IT support, especially for complex technical issues.
2. A strong focus on detail and accuracy, vital for Root Cause Analysis and maintaining system integrity, can be a major strength.
3. The ability to identify patterns and anomalies in data or system behaviour, which is key for predictive analysis and problem management.

Autism Challenges and Accommodations

1. Unpredictable social interactions with frustrated users or during high-stress incidents can be draining. We can provide clear communication templates, allow for 'cool-down' periods after intense calls, and offer quiet spaces.
2. Changes in routine or unexpected 'P1' incidents can be disruptive. Clear incident management protocols and pre-defined 'war room' structures can help provide predictability.
3. Ensuring clear, direct communication from colleagues and managers, avoiding ambiguity or unspoken expectations, will be a priority.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Senior (5-8 years)
2. Responsibilities: Act as the primary escalation point for complex, tricky technical issues that L1/L2 engineers can't crack. You'll jump in, diagnose, and resolve them, often under pressure.
3. Mentor and guide 0-2 junior IT Support Engineers. This means doing code reviews, unblocking them when they're stuck, sharing your knowledge, and helping them grow their troubleshooting skills.
4. Lead Root Cause Analysis (RCA) investigations for recurring incidents. You'll dig deep to find out *why* things keep breaking and work with other teams to implement permanent fixes.
5. Design, author, and review new knowledge base articles and detailed runbooks. Make sure our documentation is clear, accurate, and actually useful for the whole team.
6. Take charge during P1 (critical) incidents. You'll coordinate the response, communicate clearly to stakeholders, and make sure we get things back online as quickly as possible.
7. Work closely with other IT teams (Networking, DevOps, Security) to resolve cross-functional issues, acting as the bridge between support and specialist teams.
8. Proactively identify areas for process improvement within IT support. Spot inefficiencies, propose solutions, and help implement changes that make everyone's life easier.
9. Manage relationships with key hardware and software vendors, escalating issues to them when necessary and holding them accountable to their support contracts.
10. Supervision: You'll have bi-weekly check-ins with your IT Support Manager, but for the most part, you're expected to be autonomous on your day-to-day tasks and project work. You'll know when to flag something, but you won't be micro-managed.
11. Decision: You'll have full technical decision-making authority within the scope of your assigned incidents and problem investigations (e.g., choosing troubleshooting steps, recommending tool configurations). You can recommend minor budget spends (up to roughly £5K) for tools or training but won't have final approval. For anything strategic or impacting other teams, you'll consult with your manager.
12. Success: You're successful when complex tickets get resolved efficiently, junior team members are visibly growing in their capabilities, recurring problems are significantly reduced, and our knowledge base is a reliable, up-to-date resource. Essentially, you're making the whole support operation smarter and smoother.

Decision-Making Authority

• Type: Troubleshooting Steps for Complex Issue
• Entry: Follows documented steps; escalates when unsure.
• Mid: Chooses appropriate troubleshooting path from experience; escalates novel issues.
• Senior: Defines novel troubleshooting paths; makes real-time decisions during P1 incidents; rarely escalates for technical guidance.
• Type: Knowledge Base Article Creation/Update
• Entry: Suggests edits to existing articles; documents simple solutions.
• Mid: Creates articles for common, undocumented issues; gets manager approval.
• Senior: Designs and authors comprehensive new articles/runbooks; reviews and approves junior team's contributions; identifies knowledge gaps.
• Type: Prioritising Daily Workload
• Entry: Prioritises based on ticket queue order or supervisor guidance.
• Mid: Independently prioritises based on SLA and business impact for routine tickets.
• Senior: Strategically prioritises complex incidents, problem investigations, and mentorship activities, often reprioritising junior team's work during a 'ticket swarm'.
• Type: Vendor Escalation
• Entry: Provides information to senior team for vendor escalation.
• Mid: Initiates vendor support requests for known issues; follows up on existing tickets.
• Senior: Leads vendor escalation calls; holds vendors accountable to SLAs; influences vendor technical direction for specific issues.

Competency Requirements

Foundation Skills (Transferable)

Beyond the technical wizardry, being a Senior IT Support Manager means you've got to be brilliant with people and processes. These are the bedrock skills that let you lead incidents, mentor juniors, and keep everyone happy.

• Category: Communication & Interpersonal Skills
• Skills: De-escalation Techniques: Calming frustrated users and stakeholders during high-stress situations.
• Clear Technical Communication: Explaining complex IT issues in plain English to non-technical audiences.
• Active Listening: Genuinely understanding user problems and team challenges, not just hearing them.
• Mentorship & Coaching: Guiding junior team members, providing constructive feedback, and fostering their growth.
• Cross-functional Collaboration: Working effectively with other IT teams (Networking, DevOps) and business units to solve problems.
• Category: Problem-Solving & Critical Thinking
• Skills: Root Cause Analysis (RCA): Methodically identifying the underlying cause of recurring issues, not just the symptoms.
• Analytical Thinking: Breaking down complex problems into manageable parts and logically working through solutions.
• Troubleshooting Methodologies: Applying structured approaches to diagnose and resolve technical faults efficiently.
• Decision-Making Under Pressure: Making sound judgments quickly during P1 incidents with limited information.
• Category: Organisational & Adaptability
• Skills: Prioritisation & Time Management: Juggling multiple urgent tasks, project work, and mentorship responsibilities effectively.
• Process Improvement: Identifying inefficiencies and proposing practical, implementable solutions to streamline workflows.
• Adaptability to Change: Comfortably navigating evolving technical landscapes, new tools, and shifting business priorities.
• Documentation & Knowledge Management: Creating and maintaining clear, accurate, and accessible technical documentation.
• Category: Leadership & Initiative
• Skills: Incident Leadership: Taking charge during major outages, coordinating efforts, and driving resolution.
• Proactive Problem Identification: Spotting potential issues before they become widespread problems.
• Accountability: Taking ownership of outcomes, even when working with other teams.
• Influencing Stakeholders: Persuading others to adopt new processes or prioritise critical fixes.

Functional Skills (Role-Specific Technical)

Here's where your deep technical know-how comes into play. You'll need to be an expert in our core support tools and methodologies, capable of not just using them, but improving how we use them.

Technical Competencies

• Skill: ITIL Framework (v4) Application
• Desc: You won't just know the theory; you'll be applying ITIL's Guiding Principles and Service Value Chain daily. This means differentiating between an Incident, a Problem, and a Change Request under pressure, and knowing how to use these concepts to improve our support operations.
• Level: Advanced
• Skill: SLA & OLA Management
• Desc: You'll be actively involved in crafting, negotiating, and reporting on Service Level Agreements (SLAs) with the business and Operational Level Agreements (OLAs) with internal IT teams. Crucially, you'll know how to manage expectations and mitigate impact when an OLA breach is about to cause an SLA breach.
• Level: Advanced
• Skill: Root Cause Analysis (RCA) Leadership
• Desc: You'll be leading structured RCA methodologies like the '5 Whys' or Fishbone (Ishikawa) diagrams to move beyond fixing symptoms. Your goal is to identify the true underlying cause of recurring P1 incidents and ensure a permanent solution is put in place.
• Level: Expert
• Skill: Knowledge-Centered Service (KCS) Implementation
• Desc: You'll be championing and actively implementing KCS principles, where knowledge is created and curated as a byproduct of solving tickets. Your aim is to significantly improve First Call Resolution (FCR) and enable more self-service for our users.
• Level: Advanced
• Skill: IT Asset Lifecycle Management (ITAM) Contribution
• Desc: You'll contribute to managing the full lifecycle of hardware and software assets from procurement and deployment to maintenance, retirement, and disposal. This means ensuring compliance, optimising costs, and helping to shape our ITAM processes.
• Level: Intermediate
• Skill: Vendor Management & Accountability
• Desc: You'll be evaluating, negotiating with, and managing relationships with hardware and software vendors. A key part of this is holding them accountable to their support contracts and SLAs, ensuring we get the service we pay for.
• Level: Advanced

Digital Tools

• Tool: ITSM Platform (ServiceNow, Jira Service Management, Zendesk)
• Level: Expert
• Usage: You'll be configuring workflows, building custom reports and dashboards to track team performance, training new users on advanced features, and managing automation rules to streamline ticket handling. You're not just using it; you're shaping it.
• Tool: Endpoint Management (Microsoft Intune, Jamf Pro, Kandji)
• Level: Advanced
• Usage: You'll be creating and testing deployment packages for new software, building complex configuration profiles, and troubleshooting tricky policy conflicts across our fleet of devices. You'll ensure our devices are secure and correctly configured.
• Tool: Identity & Access Management (Okta, Azure Active Directory, JumpCloud)
• Level: Advanced
• Usage: You'll be managing group policies, troubleshooting complex SSO/MFA failures, and conducting regular user access reviews and audits. You're ensuring the right people have the right access, and no more.
• Tool: Remote Support Tools (BeyondTrust, TeamViewer, Splashtop)
• Level: Expert
• Usage: You'll be using advanced features like session recording for training purposes, troubleshooting connectivity issues with the tool itself, and ensuring secure, efficient remote access for complex problem resolution.
• Tool: Knowledge Base (Confluence, Guru, Notion)
• Level: Advanced
• Usage: You'll be authoring, reviewing, and publishing new KB articles and detailed runbooks. You'll also be analysing usage metrics to identify critical knowledge gaps and ensure our documentation is actually used and useful.
• Tool: Executive Dashboards (Power BI, Tableau)
• Level: Advanced
• Usage: You'll be connecting data sources (like the ITSM API) to build custom reports and dashboards on team performance, incident trends, and problem management effectiveness. You'll turn raw data into actionable insights.
• Tool: GRC Systems (ServiceNow GRC, OneTrust)
• Level: Basic
• Usage: You'll be providing evidence for IT controls during audits (e.g., access reviews, change logs) and understanding how our support processes contribute to overall compliance requirements.

Industry Knowledge

• Area: Cybersecurity Fundamentals
• Desc: Understanding common security threats (phishing, malware), basic incident response procedures, and the importance of data protection in a support context. You'll be the first line of defence for many security issues.
• Area: Cloud Computing Concepts (Azure/AWS/GCP)
• Desc: Basic understanding of cloud services, common architectures, and how they impact user access and application performance. You'll often be troubleshooting issues that touch our cloud infrastructure.
• Area: Networking Basics
• Desc: Solid grasp of TCP/IP, DNS, DHCP, and VPN concepts to diagnose connectivity issues before escalating to the Networking team. You'll know how to do initial triage effectively.
• Area: Operating Systems (Windows, macOS, Linux)
• Desc: Deep knowledge of multiple operating systems for advanced troubleshooting, configuration, and security hardening. You'll be comfortable working across different user environments.

Regulatory Compliance Regulations

• Reg: GDPR (General Data Protection Regulation)
• Usage: Ensuring all support activities, particularly those involving personal data, adhere to GDPR principles. You'll know how to handle data subject access requests and data breaches from a support perspective.
• Reg: ISO 27001 (Information Security Management)
• Usage: Understanding how our IT support processes contribute to the overall information security management system. You'll ensure our incident management and access control procedures align with ISO 27001 requirements.
• Reg: SOC 2 (Service Organisation Control 2)
• Usage: Providing necessary documentation and evidence during SOC 2 audits related to security, availability, processing integrity, confidentiality, and privacy for our IT support services.

Essential Prerequisites

• Proven ability to independently resolve complex, undocumented technical issues, demonstrating strong analytical and problem-solving skills.
• Experience taking ownership of tickets from initial contact through to resolution, including effective communication with users and internal teams.
• A track record of identifying recurring problems and proposing solutions, even if you didn't lead the full Root Cause Analysis.
• Demonstrated ability to work effectively with cross-functional teams and manage minor projects or initiatives within IT support.
• A solid foundation in all core IT support tools and methodologies, including advanced use of an ITSM platform and endpoint management solutions.

Career Pathway Context

To thrive as a Senior IT Support Manager, you'll need to have mastered the skills of an IT Support Engineer (Level 2). This means you're comfortable working independently, you're a solid problem-solver, and you've already shown initiative in improving things. We're looking for someone who's ready to step up, take on more complex challenges, and start guiding others.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: Prompt Engineering & LLM Integration
• Why: Critical within 6 months—this isn't future-gazing; it's happening now. Competitors are already using Large Language Models (LLMs) to draft incident reports in minutes that used to take hours. Support professionals who figure this out will outproduce peers significantly.
• Concepts: [{'concept_name': 'Context Windows & Token Limits', 'description': 'Understanding how much information an LLM can process at once and how to manage it for effective results.'}, {'concept_name': 'Temperature Settings', 'description': "Knowing how to adjust an LLM's creativity for different tasks, from factual summaries to drafting empathetic user communications."}, {'concept_name': 'RAG Architectures (Retrieval-Augmented Generation)', 'description': 'Learning how to connect LLMs to our internal knowledge bases and documentation for accurate, context-specific answers.'}, {'concept_name': 'Output Validation & Hallucination Detection', 'description': "Developing a critical eye to verify AI-generated content and spot when the model is 'making things up'."}, {'concept_name': 'Prompt Chaining for Complex Analysis', 'description': 'Breaking down multi-step tasks into a series of prompts to achieve more sophisticated outcomes, like full Root Cause Analysis drafts.'}]
• Prepare: This week: Set up GitHub Copilot (if coding) or a similar AI assistant. Use it for every piece of code or text you generate.
• This month: Build one automated report or draft one complex incident communication using an LLM API (e.g., OpenAI, Anthropic).
• Month 2: Experiment with integrating an LLM with a small segment of our internal documentation using RAG principles.
• Month 3: Document your productivity gains and share your findings and new workflows with the rest of the support team.
• QuickWin: Start using Claude or ChatGPT to draft email summaries, code comments, or initial troubleshooting steps today. No approval needed, immediate benefit. Just remember to always verify the output!
• Skill: Advanced Automation Scripting (PowerShell/Python)
• Why: Important within 12 months. The drive for 'shift-left' and 'self-healing' IT means more tasks will be automated. If you can write scripts to fix common problems or automate repetitive tasks, you'll be invaluable.
• Concepts: [{'concept_name': 'API Integration', 'description': 'Writing scripts to interact with our ITSM, Endpoint Management, and Identity platforms via their APIs.'}, {'concept_name': 'Error Handling & Logging', 'description': 'Building robust scripts that can gracefully handle failures and provide clear logs for debugging.'}, {'concept_name': 'Scheduled Tasks & Event Triggers', 'description': 'Automating scripts to run at specific times or in response to system events (e.g., a service stopping).'}, {'concept_name': 'Script Version Control', 'description': 'Using Git to manage and collaborate on automation scripts with the team.'}, {'concept_name': 'Security Best Practices for Scripting', 'description': 'Writing secure code, managing credentials, and understanding potential vulnerabilities.'}]
• Prepare: This week: Pick one repetitive, manual task you do daily and try to automate a small part of it with a simple script.
• This month: Complete an online course on PowerShell or Python scripting focused on IT automation.
• Month 2: Develop a script to automate a common user request (e.g., creating a shared mailbox) and get it reviewed by a peer.
• Month 3: Work with the Endpoint Management team to deploy a self-healing script for a known recurring issue on user machines.
• QuickWin: Start by automating your own daily reports or data exports. Even small scripts can save significant time and build your confidence.

Advancing Technical Skills

• Skill: Cloud Service Management & Optimisation
• Why: Critical within 12-18 months. More and more of our services are moving to the cloud. You'll need to understand how to support, monitor, and even help optimise costs for cloud-native applications and infrastructure.
• Concepts: [{'concept_name': 'Cloud Cost Management (FinOps)', 'description': 'Understanding basic principles of cloud cost optimisation and identifying areas where support can contribute to savings.'}, {'concept_name': 'Serverless Architectures', 'description': 'Basic understanding of how serverless functions work and how to troubleshoot applications built on them.'}, {'concept_name': 'Cloud Security Best Practices', 'description': 'Recognising common cloud security risks and how to apply security principles in a cloud environment.'}, {'concept_name': 'Monitoring & Alerting in Cloud', 'description': 'Using cloud-native monitoring tools (e.g., Azure Monitor, AWS CloudWatch) to proactively identify issues.'}, {'concept_name': 'Hybrid Cloud Support Challenges', 'description': 'Understanding the unique support complexities of environments spanning on-premise and multiple cloud providers.'}]
• Prepare: This week: Read up on the basics of our primary cloud provider (e.g., Azure Fundamentals or AWS Cloud Practitioner).
• This month: Complete an online course on cloud service management or a specific cloud platform's support features.
• Month 2: Shadow a member of the DevOps or Cloud Engineering team to understand how they manage cloud resources.
• Month 3: Take ownership of troubleshooting one recurring cloud-related support issue, working with relevant teams to resolve it permanently.
• QuickWin: Familiarise yourself with the dashboards and monitoring tools for our current cloud services. Just knowing where to look for logs is a great start.

Education Requirements

• Level: Minimum
• Req: A Bachelor's degree (or equivalent OFQUAL Level 6 qualification) in Information Technology, Computer Science, or a related technical field.
• Alts: We're pragmatic here. If you've got 8+ years of demonstrable, hands-on experience in a senior IT support role, with a strong track record of problem-solving and process improvement, we'll absolutely consider that as equivalent to a degree.
• Level: Preferred
• Req: A Bachelor's degree in a relevant technical field with a strong academic record, or a Master's degree in IT Management or a related discipline.
• Alts: Relevant industry certifications (see below) can often compensate for a lack of formal higher education, especially if combined with significant practical experience.

Experience Requirements

You'll need roughly 5-8 years of progressive experience in IT support roles, with at least 2-3 years spent at an 'IT Support Engineer' (Level 2) or equivalent mid-level position. This isn't your first rodeo; you'll have a proven track record of resolving complex technical issues, leading incident responses, mentoring junior colleagues, and actively contributing to process improvements. We're looking for someone who's seen a lot, fixed a lot, and learned even more.

Preferred Certifications

• Cert: ITIL v4 Practitioner/Manager
• Prod: AXELOS
• Usage: Demonstrates a deeper understanding and practical application of IT service management best practices, which is crucial for process improvement and problem management.
• Cert: Microsoft 365 Certified: Enterprise Administrator Expert
• Prod: Microsoft
• Usage: Shows advanced proficiency in managing and troubleshooting our core Microsoft ecosystem, including Azure AD, Intune, and M365 services, which are central to our operations.
• Cert: CompTIA A+ / Network+ / Security+
• Prod: CompTIA
• Usage: These certifications validate fundamental knowledge across hardware, networking, and security, providing a strong baseline for advanced troubleshooting and incident response.
• Cert: ServiceNow Certified System Administrator
• Prod: ServiceNow
• Usage: If you're already familiar with configuring and managing our ITSM platform, you'll hit the ground running and be able to contribute to platform optimisation immediately.

Recommended Activities

• Regularly attending industry webinars and conferences focused on IT service management, cybersecurity, and cloud technologies.
• Actively participating in online technical communities and forums (e.g., Reddit's r/sysadmin, specific vendor communities) to stay updated on emerging issues and solutions.
• Seeking out opportunities to lead internal projects that improve IT support tools or processes.
• Mentoring junior colleagues and actively engaging in knowledge sharing within the team.
• Undertaking advanced training in scripting languages like PowerShell or Python for automation.

Career Progression Pathways

Entry Paths to This Role

• Path: From IT Support Engineer (Level 2)
• Time: 2-3 years at Level 2
• Path: From System Administrator / Junior DevOps Engineer
• Time: 3-5 years in a sysadmin/devops role with strong user-facing experience
• Path: From Technical Specialist (e.g., Desktop Support Specialist)
• Time: 4-6 years in a specialist role, with broad exposure

Career Progression From This Role

• Pathway: Lead IT Support Manager (Level 4)
• Time: 3-5 years in this Senior IT Support Manager role
• Pathway: IT Support Manager (Level 5)
• Time: 4-6 years in this Senior IT Support Manager role (or from Lead IT Support Manager)

Long Term Vision Potential Roles

• Title: Director of IT Operations (Level 6)
• Time: 5-10 years from this role
• Title: Chief Information Officer (CIO) (Level 7)
• Time: 10-15+ years from this role
• Title: IT Service Management Consultant
• Time: 5-8 years from this role

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.