Associate Cloud Support Assistant

Role Purpose & Context

Role Summary

The Associate Cloud Support Assistant is here to make sure our customers feel heard and helped when their cloud services hit a snag. You'll be the initial responder, diving into tickets, gathering information, and following our trusty runbooks to sort out common issues. This role sits right at the front line, connecting our customers with our technical teams. You'll be translating customer problems into clear, actionable information that our Cloud Support Analysts can use to fix things properly. When you do this well, customers get quick, clear answers and feel supported, which keeps them happy and sticking with us. If things go wrong, customers get frustrated, and our senior team gets swamped with basic issues. The tricky part is often figuring out what the customer *actually* means when they say 'it's broken'. The reward? Honestly, it's the satisfaction of helping someone out of a bind and seeing your knowledge grow every single day.

Reporting Structure

• Reports to: Cloud Support Assistant Manager
• Direct reports: 0
• Matrix relationships: Junior Cloud Operations Technician, Entry-Level Cloud Helpdesk Analyst, Cloud Support Trainee, Technical Support Assistant (Cloud),

Key Stakeholders

Internal:

• Cloud Support Analysts (L2/L3)
• Cloud Support Manager
• Internal Engineering Teams (for escalations)
• Customer Success Team

External:

• Our Customers (end-users experiencing issues)

Organisational Impact

Scope: You're essentially the first line of defence, filtering and resolving the simpler issues so the more experienced engineers can focus on the big, hairy problems. Your quick, accurate initial responses directly affect customer satisfaction and our ability to meet service level agreements (SLAs). Get it right, and our customers feel supported and our internal teams can work efficiently. Get it wrong, and you'll create a backlog of frustrated customers and unnecessary escalations.

Performance Metrics

Quantitative Metrics

1. Metric: First Response Time (FRT)
2. Desc: How quickly you acknowledge an incoming customer ticket.
3. Target: <90 minutes for non-critical tickets
4. Freq: Weekly, reviewed in 1:1s
5. Example: You pick up a new 'low-priority' ticket at 10:00 and send an initial 'we're on it' message by 10:45. That's a 45-minute FRT, well within target.
6. Metric: Mean Time to Resolution (MTTR) for L1 Tickets
7. Desc: The average time it takes you to fully resolve basic, well-documented issues.
8. Target: <4 hours for L1 tickets
9. Freq: Monthly
10. Example: You resolve 10 password reset requests and 5 'how-to' questions, all within 2 hours each. Your average MTTR for these L1 tickets would be 2 hours.
11. Metric: Customer Satisfaction (CSAT)
12. Desc: Feedback from customers on your helpfulness and the resolution of their issue.
13. Target: >90% positive feedback on resolved tickets
14. Freq: Monthly (based on post-resolution surveys)
15. Example: Out of 50 tickets you close, 46 customers give you a 'satisfied' or 'very satisfied' rating. That's 92% CSAT, hitting the target.
16. Metric: Runbook Adherence Rate
17. Desc: How consistently you follow established step-by-step guides for common issues.
18. Target: >95% adherence (no critical steps missed)
19. Freq: Quarterly (via peer review and manager spot checks)
20. Example: When investigating a 'server unreachable' alert, you correctly check network connectivity, security group rules, and instance status in the AWS console, exactly as the runbook specifies, before escalating.

Qualitative Metrics

1. Metric: Quality of Initial Triage
2. Desc: How well you understand the customer's problem, gather necessary information, and categorise the ticket before escalating or resolving.
3. Evidence: Tickets you handle have clear problem statements, all required diagnostic information attached (e.g., screenshots, error codes, timestamps), and are correctly assigned. Senior colleagues find your escalations easy to pick up and act on. You're not just passing the buck; you're doing the legwork.
4. Metric: Proactive Learning & Engagement
5. Desc: Your willingness to learn new systems, ask questions, and contribute to team knowledge.
6. Evidence: You regularly ask thoughtful questions during team meetings or to your mentor. You actively review new runbooks and suggest minor improvements. You're keen to shadow senior colleagues on complex issues. You're not just waiting to be told what to do; you're seeking out opportunities to grow.
7. Metric: Professional Communication
8. Desc: Your ability to communicate clearly, calmly, and empathetically with customers and internal teams, even when things are stressful.
9. Evidence: Your written responses to customers are clear, polite, and easy to understand, even for non-technical users. You keep a calm tone on calls. You summarise issues concisely for escalations. You avoid jargon where possible, or explain it when necessary. No one's scratching their head after reading your updates.

Primary Traits

• Trait: Methodical Problem-Solver
• Manifestation: When a customer says 'it's broken', you don't panic. Instead, you'll reach for the diagnostic checklist, asking about recent changes, specific error messages, and what they were trying to do. You'll follow the steps in the runbook, one by one, rather than jumping straight to a wild guess. You can tell the difference between 'the system is slow because of a network issue' and 'the system is slow because someone uploaded a 50GB file to S3'.
• Benefit: This isn't about being a genius; it's about being thorough. If you skip steps or make assumptions, you'll waste everyone's time, including your own. Proper initial investigation means we either fix it quickly or escalate it to the right person with all the necessary info. It prevents that annoying 'ticket tennis' where issues bounce around for days.
• Trait: Calm Under Pressure
• Manifestation: Imagine a customer is shouting down the phone because their website is offline, or an internal team is demanding answers in a 'war room' chat. You'll be the one who keeps a steady, professional tone, focusing on the next logical step rather than getting flustered or defensive. You can reassure a panicked customer and get the information you need, even when they're stressed.
• Benefit: During a Sev-1 incident, chaos is the enemy. Your ability to remain calm helps de-escalate situations and creates a better environment for everyone, especially the engineers who are trying to fix the actual problem. It builds trust with customers and helps your colleagues focus. Panicking just makes everything worse, honestly.
• Trait: Precise Communicator
• Manifestation: You'll write ticket summaries that are clear and to the point, leaving no room for misunderstanding. When you send an email or an internal message, you'll double-check it for typos or ambiguity. If you're documenting an incident, you'll make sure the timeline is accurate and every detail is correct. You know that a missing screenshot or an incorrect error code can completely derail an investigation.
• Benefit: In cloud support, a single typo in a command or a misremembered detail in an escalation can lead to hours of wasted time, or worse, further outages. Precision is the bedrock of trust, both with our customers and with your colleagues. It means the right information gets to the right people, quickly, leading to faster resolutions.

Supporting Traits

• Trait: Empathetic Listener
• Desc: You can genuinely understand a user's frustration and articulate it back to them, even if the problem isn't technically complex. It's about putting yourself in their shoes and acknowledging their pain, not just solving the technical puzzle.
• Trait: Patient Explainer
• Desc: You're willing to walk non-technical users through complex steps, sometimes repeatedly, without getting annoyed. You can break down technical jargon into plain English so anyone can understand what's happening.
• Trait: Naturally Curious
• Desc: You've got a genuine desire to understand how systems work under the hood. When you see an error, you don't just want to fix it; you want to know *why* it happened. This curiosity drives you to learn new technologies and dig deeper.
• Trait: Reliable Contributor
• Desc: When you say you'll do something, your team knows it'll get done. You take ownership of your tasks and follow through, meaning colleagues can count on you to handle your part of the workload correctly and on time.

Primary Motivators

1. Motivator: Solving Puzzles & Helping People
2. Daily: You get a real kick out of figuring out why something isn't working and then guiding a customer to a solution. That 'aha!' moment when you connect the dots, or the 'thank you!' from a relieved customer, really makes your day.
3. Motivator: Continuous Learning & Growth
4. Daily: You're excited by the idea of constantly learning new cloud technologies and diagnostic techniques. Every new ticket is a chance to expand your knowledge, and you actively seek out opportunities to understand complex systems.
5. Motivator: Being Part of a Team
6. Daily: You enjoy collaborating with colleagues, sharing knowledge, and knowing you're part of a crew that's got each other's backs. You're happy to ask for help when stuck and offer it when you can.

Potential Demotivators

Honestly, this job isn't for everyone. You'll get vague tickets like 'the app is slow' that force you to play detective for ages before you even understand the problem. The on-call pager might go off at 3 AM for something that could have waited until morning, and sometimes you'll feel like a 'human shield', taking the heat from frustrated customers for issues caused by bugs the engineering team hasn't fixed yet. If you need perfect documentation for every single issue, you'll struggle, because sometimes you'll be supporting new features with zero runbooks. There's also that constant tension between hitting quick SLA targets and taking the time to find the *actual* root cause. And yes, you'll get a lot of 'can you just...?' requests via Slack that completely derail your focus from high-priority tickets. If these things sound like they'd drive you absolutely mad, this might not be the right fit.

Common Frustrations

1. Receiving tickets with summaries like 'The app is slow' or 'It's broken' – you'll spend the first 30 minutes just trying to understand the actual problem.
2. The anxiety of the pager going off at 3 AM for a non-critical alert that could have waited until morning.
3. Being the 'human shield' – taking the heat from frustrated customers or internal stakeholders for an outage caused by a bug the engineering team hasn't fixed for months.
4. Lack of documentation – trying to support a new feature that was deployed with zero runbooks or knowledge base articles from the development team.
5. The constant stream of 'quick questions' via Slack that derail your focus from high-priority tickets.

What Role Doesn't Offer

1. A perfectly predictable, routine workday – expect curveballs and urgent requests.
2. Complete autonomy over technical architecture or strategic direction – that comes later.
3. An environment where every single issue has a clear, documented solution readily available.
4. A role where you only interact with technology and never deal with people's frustrations.

ADHD Positives

1. The fast-paced nature of incident response and the constant variety of incoming tickets can be quite stimulating and engaging, preventing boredom. You'll rarely do the exact same thing for hours on end.
2. The need for quick problem-solving and rapid context switching can play to strengths in adaptability and hyperfocus when something truly critical comes in.
3. The clear, step-by-step nature of runbooks provides a structured framework, which can be helpful for task initiation and execution.

ADHD Challenges and Accommodations

1. Maintaining focus on a single, complex ticket for an extended period might be challenging. We can help by breaking down larger tasks, encouraging frequent check-ins, and using visual cues to track progress.
2. Organising and prioritising a queue of diverse tickets can be overwhelming. We use Jira Service Management with clear prioritisation flags and provide regular coaching on queue management techniques.
3. Distractions in an open-plan office environment can be tricky. We offer noise-cancelling headphones, quiet zones for focused work, and flexibility for remote work days where possible.

Dyslexia Positives

1. Strong problem-solving and pattern recognition skills, often seen in dyslexic individuals, are incredibly valuable for diagnosing complex cloud issues and spotting anomalies in logs.
2. Excellent verbal communication and empathy can shine when de-escalating customer situations and clearly explaining technical concepts on calls.
3. The visual nature of cloud consoles (AWS, Azure, GCP) and monitoring dashboards (Grafana, Datadog) can be more intuitive than purely text-based interfaces.

Dyslexia Challenges and Accommodations

1. Reading and writing detailed incident reports or knowledge base articles can be time-consuming. We encourage the use of dictation software, provide templates with clear headings, and offer proofreading support from colleagues.
2. Distinguishing between similar-looking commands or log entries might require extra focus. We use syntax highlighting in our tools and encourage double-checking with a peer before executing critical commands.
3. Processing large amounts of text-based documentation can be tiring. We prioritise visual aids in our knowledge base, use tools with text-to-speech functionality, and encourage verbal knowledge transfer during handovers.

Autism Positives

1. A strong adherence to logical processes and runbooks is a huge asset in support roles, ensuring consistency and accuracy in troubleshooting.
2. The ability to focus intensely on details and spot subtle patterns in data (like log entries or metric graphs) can be invaluable for root cause analysis.
3. Direct, clear communication, often preferred by autistic individuals, is highly valued in technical support, especially during incident 'war rooms' where ambiguity is the enemy.

Autism Challenges and Accommodations

1. Navigating ambiguous customer requests or unspoken social cues can be difficult. We provide training on active listening and asking clarifying questions, and encourage escalating unclear situations to a manager or senior colleague.
2. Unexpected changes or urgent interruptions, common in support, can be disruptive. We try to provide as much predictability as possible with shift patterns and offer 'focus time' blocks where interruptions are minimised.
3. Sensory overload from a busy office or constant notifications. We offer noise-cancelling headphones, the option to work in quieter areas, and encourage customising notification settings to reduce sensory input.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Entry Level (0-2 years)
2. Responsibilities: Respond to incoming customer support tickets and chat requests, making sure every customer feels heard and understood from the get-go.
3. Perform initial triage on reported issues, which means figuring out the basic problem, its urgency, and gathering all the necessary details (error messages, timestamps, affected services) before escalating.
4. Follow established runbooks and step-by-step guides to resolve common, well-documented cloud issues, like password resets, basic access problems, or checking service statuses in the AWS/Azure/GCP console.
5. Document every step you take and every piece of information you find in our ticketing system (Jira Service Management), keeping the ticket history clear and concise for anyone else who might pick it up.
6. Monitor pre-configured dashboards in Datadog or Grafana, acknowledging alerts and following the escalation path if something looks off. You'll be the eyes and ears for potential problems.
7. Learn, learn, learn! You'll be spending time understanding our cloud architecture, our services, and our internal processes. Ask questions, read documentation, and soak it all up.
8. Participate in daily team stand-ups, sharing what you're working on, any blockers you're facing, and what you've learned. It's about being a part of the team, honestly.
9. Supervision: You'll have daily check-ins with your manager or a senior team member. All of your work, especially resolutions and escalations, will be reviewed. Think of it as having a safety net while you learn.
10. Decision: No independent decisions on customer-facing resolutions or system changes. You'll follow runbooks strictly. Any deviation or anything outside a runbook needs immediate escalation to a senior colleague or your manager. If a customer asks for something you're not sure about, you'll say 'Let me just check with a senior colleague to make sure we get this right for you'.
11. Success: You're successfully onboarding when you're consistently hitting your First Response Time targets, accurately triaging tickets, and resolving common L1 issues by following runbooks. Your documentation is clear, and you're actively asking thoughtful questions and contributing to team discussions. Basically, you're showing up, learning, and making a positive impact on customer experience.

Decision-Making Authority

• Type: Customer Issue Resolution
• Entry: Follow runbook for known issues; escalate anything outside of documented steps to a senior analyst.
• Mid: Independently resolve most L1/L2 issues; consult with senior staff for complex or undocumented problems.
• Senior: Resolve complex L3 issues and act as an escalation point; make technical decisions on resolution approach for critical incidents.
• Type: System Changes/Configuration
• Entry: No authority. Only perform read-only checks in cloud consoles. Any suggested change must be escalated.
• Mid: Perform approved, low-risk changes (e.g., restarting instances, adjusting security group rules) under strict guidelines. Escalate anything beyond that.
• Senior: Propose and execute approved changes to improve supportability or resolve recurring problems. Consult with engineering on significant changes.
• Type: Communication with Customers
• Entry: Draft responses based on templates; all critical communications or de-escalations should be reviewed by a senior colleague before sending.
• Mid: Independently communicate with customers, including updates and resolutions. Escalate sensitive customer interactions to a manager.
• Senior: Lead customer communication during major incidents; handle difficult customer conversations and manage expectations directly.
• Type: Knowledge Base Contribution
• Entry: Suggest improvements to existing runbooks or documentation. Learn from and use the knowledge base.
• Mid: Create and update runbooks and knowledge base articles for common issues, with peer review.
• Senior: Lead the creation of new documentation standards and ensure knowledge is captured and shared effectively across the team.

Competency Requirements

Foundation Skills (Transferable)

These are the bedrock skills you'll need to hit the ground running. They're not just about knowing things; they're about how you approach problems, communicate, and learn. Think of them as your toolkit for navigating the day-to-day challenges of cloud support.

• Category: Communication & Collaboration
• Skills: Active Listening: Really hearing what a customer is saying (and not saying) to understand their problem.
• Clear Written Communication: Writing concise, unambiguous ticket updates and emails, even under pressure.
• Verbal De-escalation: Keeping a calm, reassuring tone on calls, especially with frustrated customers.
• Team Collaboration: Working effectively with colleagues, asking for help, and sharing information.
• Category: Problem Solving & Analysis
• Skills: Structured Troubleshooting: Following a logical, step-by-step process to diagnose issues.
• Information Gathering: Knowing what questions to ask and where to look for relevant data (logs, error messages).
• Pattern Recognition: Spotting recurring issues or common error messages that point to a known problem.
• Attention to Detail: Noticing small discrepancies that can make a big difference in troubleshooting.
• Category: Learning & Adaptability
• Skills: Curiosity: A genuine desire to understand how systems work and why things break.
• Self-Directed Learning: Taking the initiative to read documentation, watch tutorials, and expand your knowledge.
• Adaptability: Being comfortable with changing priorities and learning new tools or processes quickly.
• Feedback Absorption: Actively seeking and acting on feedback to improve your skills and performance.

Functional Skills (Role-Specific Technical)

These are the specific technical and domain-specific skills you'll be using every day. You won't be expected to be an expert from day one, but a basic understanding and a willingness to master them are crucial for this role.

Technical Competencies

• Skill: ITIL Framework (Incident Management)
• Desc: Understanding the core principles of Incident Management – how to log, categorise, prioritise, and escalate issues according to best practices. You'll learn *why* we have these processes, not just follow them blindly.
• Level: Basic
• Skill: Triage & Escalation
• Desc: The ability to quickly assess an issue's impact and urgency, gather essential diagnostic data, and know exactly when and who to escalate to without 'crying wolf'. It's about getting the right information to the right people at the right time.
• Level: Intermediate
• Skill: Cloud Fundamentals (IaaS/PaaS/SaaS)
• Desc: A foundational grasp of what Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) actually mean. You'll understand the basic building blocks of cloud computing and how our services fit into them.
• Level: Basic
• Skill: Core Networking Concepts
• Desc: Understanding basic networking terms like IP addresses, DNS, firewalls, and subnets. You'll need to know enough to follow a runbook for network connectivity issues or security group configurations.
• Level: Basic
• Skill: Knowledge-Centered Service (KCS)
• Desc: While you won't be writing complex articles yet, you'll understand the importance of our knowledge base. You'll use it constantly to find solutions and learn to suggest improvements when you spot gaps.
• Level: Basic

Digital Tools

• Tool: Jira Service Management / ServiceNow
• Level: Intermediate
• Usage: You'll live in this. Logging new tickets, updating existing ones, adding comments, changing statuses, and assigning issues. It's how we track everything.
• Tool: AWS Console (EC2, S3, CloudWatch)
• Level: Basic
• Usage: Navigating for read-only tasks: checking service status, viewing basic logs, confirming instance configurations, and looking at simple metrics on dashboards.
• Tool: Azure Portal (VMs, Blob Storage)
• Level: Basic
• Usage: Similar to AWS, you'll use it for read-only tasks: checking virtual machine status, looking at storage accounts, and viewing resource health.
• Tool: GCP Console (Compute Engine)
• Level: Basic
• Usage: Again, read-only: checking Compute Engine instance status, looking at storage buckets, and verifying basic configurations.
• Tool: Datadog / Grafana / Prometheus
• Level: Intermediate
• Usage: Monitoring pre-configured dashboards. You'll acknowledge alerts, understand what basic metrics mean (CPU usage, network traffic), and follow escalation paths based on what you see.
• Tool: Splunk / ELK Stack (Kibana)
• Level: Basic
• Usage: Performing simple keyword searches in logs to find specific error messages or timestamps related to an incident. It's like being a detective with a magnifying glass.
• Tool: Slack / MS Teams
• Level: Intermediate
• Usage: Active use for internal incident communication, asking quick questions to colleagues, and participating in 'war room' channels during major issues.
• Tool: Confluence / Notion
• Level: Intermediate
• Usage: Consuming and following documentation, runbooks, and knowledge base articles. You'll be reading these constantly to learn and resolve issues.

Industry Knowledge

• Area: Customer Service Best Practices
• Desc: Understanding how to manage customer expectations, provide clear updates, and maintain a professional demeanour, even when dealing with difficult situations. It's about making the customer feel valued.
• Area: Basic IT Security Concepts
• Desc: A basic awareness of common security threats (e.g., phishing, malware) and the importance of strong passwords and access control. You'll know when to flag something as a potential security risk.

Regulatory Compliance Regulations

• Reg: General Data Protection Regulation (GDPR)
• Usage: You'll know the basics of handling customer data responsibly, understanding that certain information is sensitive and how to protect it. You won't be making legal decisions, but you'll know when to escalate a data privacy concern.
• Reg: Internal Security Policies
• Usage: Following our company's rules on data access, password management, and incident reporting. This is non-negotiable; it keeps our customers' data safe and our systems secure.

Essential Prerequisites

• A genuine interest in technology and cloud computing – you don't need to be an expert, but you should be excited to learn.
• Basic computer literacy, including navigating operating systems (Windows/Linux), using web browsers, and common office applications.
• Some prior experience in a customer-facing role (e.g., retail, hospitality, call centre) where you've had to solve problems and deal with people, or equivalent experience.
• The ability to communicate clearly and calmly in English, both verbally and in writing.
• A strong work ethic and a willingness to ask questions when you don't know something (which will be often, and that's absolutely fine!).

Career Pathway Context

We're not looking for someone who knows everything about the cloud yet. We're looking for someone with the right attitude, a curious mind, and a solid foundation in problem-solving and communication. We'll teach you the cloud specifics. Think of these prerequisites as the raw ingredients; we'll provide the recipe and the kitchen.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: Effective Prompt Engineering (for Support)
• Why: AI tools like ChatGPT and Claude are already here, and they're getting better at helping with customer queries, drafting responses, and summarising complex information. Knowing how to ask the right questions to these AIs will be critical within the next 6-12 months.
• Concepts: [{'concept_name': 'Clear & Specific Prompts', 'description': 'How to write prompts that give AI enough context to provide useful answers, rather than vague ones.'}, {'concept_name': 'Iterative Prompting', 'description': 'Refining your questions to AI based on its initial responses to get closer to the solution.'}, {'concept_name': 'Output Validation', 'description': "Knowing when to trust an AI's answer and when to recognise a 'hallucination' or incorrect information."}, {'concept_name': 'Role-Playing Prompts', 'description': "Asking AI to act as a 'cloud expert' or 'customer' to get different perspectives or help draft specific types of communication."}]
• Prepare: This week: Start using a free AI tool (like ChatGPT or Claude) to summarise long emails or articles.
• This month: Experiment with using AI to draft initial responses to simple customer queries (don't send them yet!).
• Month 2: Try using AI to help you troubleshoot a known issue by asking it diagnostic questions.
• Month 3: Share your experiences and any cool 'prompts' you've discovered with your team during stand-ups.
• QuickWin: Use AI today to help you rephrase complex technical explanations into simpler language for customers, or to generate ideas for troubleshooting steps when you're stuck on a common problem. It's a free learning tool.
• Skill: AI-Assisted Diagnostics & Monitoring
• Why: Our monitoring and logging tools are getting smarter, using AI to spot anomalies and suggest root causes before humans even see them. Understanding how these systems work and how to interpret their AI-generated insights will be important within the next 12-18 months.
• Concepts: [{'concept_name': 'Anomaly Detection', 'description': 'Understanding how AI flags unusual behaviour in metrics or logs that might indicate a problem.'}, {'concept_name': 'Correlation Engines', 'description': 'How AI connects seemingly unrelated events across different systems to identify a single underlying issue.'}, {'concept_name': 'Predictive Alerting', 'description': 'Recognising when AI is predicting a potential outage before it actually happens, based on current trends.'}, {'concept_name': 'Interpreting AI Explanations', 'description': "Learning to understand the 'why' behind an AI's suggestion, not just accepting it at face value."}]
• Prepare: This week: Pay extra attention to any 'AI-generated insights' or 'anomaly alerts' in our current monitoring tools.
• This month: Ask senior colleagues how they use AI features in Datadog or Splunk for troubleshooting.
• Month 2: Take an online course on basic machine learning concepts (e.g., what is a 'model', 'training data').
• Month 3: Propose a small project to your manager on how we could better use AI features in our existing tools.
• QuickWin: Whenever you're looking at a dashboard or logs, actively look for any 'smart' features or AI-generated summaries. Click them, explore them, and try to understand what they're telling you. It's free learning, honestly.

Advancing Technical Skills

• Skill: Deeper Cloud Platform Knowledge (AWS/Azure/GCP)
• Why: As you progress, you'll need to move beyond read-only access. Understanding how to provision resources, configure networking, and manage identity and access in a multi-cloud environment will become crucial for more advanced troubleshooting and support tasks.
• Concepts: [{'concept_name': 'IAM Policies & Roles', 'description': 'Understanding how access control works and how to troubleshoot permission issues.'}, {'concept_name': 'Virtual Private Clouds (VPCs) & Subnets', 'description': 'Deeper knowledge of cloud networking to diagnose connectivity problems.'}, {'concept_name': 'Managed Services (e.g., RDS, Lambda, AKS)', 'description': 'Understanding the common managed services and how they interact.'}, {'concept_name': 'Cost Management Basics', 'description': 'An awareness of how cloud resources are billed and how to spot potential cost anomalies.'}]
• Prepare: This week: Focus on one cloud provider (e.g., AWS) and explore its documentation beyond the services you usually touch.
• This month: Complete an AWS Cloud Practitioner or Azure Fundamentals certification (we'll support you!).
• Month 2: Ask to shadow a senior analyst who is working on a complex multi-service issue.
• Month 3: Start experimenting with a free-tier account to build small projects yourself, like a simple web server.
• QuickWin: Whenever you encounter a new cloud service in a ticket, take 10 minutes to read its overview documentation. Understanding the basics of what it does will help you connect the dots later.
• Skill: Basic Scripting for Automation (Bash/PowerShell)
• Why: As you identify repetitive diagnostic tasks, learning to write simple scripts will save you (and the team) loads of time. It's about 'automating away the toil' and making your job more efficient.
• Concepts: [{'concept_name': 'Variables & Conditionals', 'description': 'Basic programming logic to make scripts dynamic.'}, {'concept_name': 'Command Line Interface (CLI)', 'description': 'Using AWS CLI, Azure CLI, or gcloud CLI to interact with cloud services via scripts.'}, {'concept_name': 'Error Handling', 'description': 'Making scripts robust enough to handle unexpected outcomes gracefully.'}, {'concept_name': 'Version Control (Git Basics)', 'description': 'Understanding how to store and manage your scripts collaboratively.'}]
• Prepare: This week: Learn basic Linux/PowerShell commands – things like 'ls', 'cd', 'grep', 'Get-Service'.
• This month: Find a simple, repetitive task you do daily and try to write a 5-line script to automate part of it.
• Month 2: Take an online tutorial on Bash scripting or PowerShell basics.
• Month 3: Contribute a small, simple script to our internal automation repository (with review, of course).
• QuickWin: Instead of manually checking 10 servers for disk space, write a simple loop in Bash or PowerShell to do it for you. It's a small step, but a massive time saver.

Education Requirements

• Level: Minimum
• Req: A-Levels (or equivalent vocational qualifications like a BTEC in IT)
• Alts: We're pretty flexible here. If you've got relevant professional experience (e.g., 1-2 years in a technical helpdesk role, or even a customer service role with a strong technical component) and can show us you're a quick learner, that absolutely counts as equivalent. We value practical skills and a curious mind over just a piece of paper.
• Level: Preferred
• Req: A degree in Computer Science, IT, or a related technical field
• Alts: While a degree is great, it's not a deal-breaker. If you've got a strong portfolio of personal projects, relevant certifications, or proven experience in a technical role, we'd love to hear from you. Experience can often trump formal education in our world.

Experience Requirements

We're looking for roughly 0-2 years of experience. This could be anything from a technical apprenticeship, a helpdesk role, or even just a genuine passion for tinkering with computers and cloud services in your spare time. The key is demonstrating a foundational understanding of IT concepts, a knack for problem-solving, and a customer-first attitude. If you've had to explain complex technical things to non-technical people before, that's a huge plus.

Preferred Certifications

• Cert: CompTIA A+
• Prod: CompTIA
• Usage: Shows a foundational understanding of hardware, software, networking, and troubleshooting. It's a great baseline for any IT role.
• Cert: AWS Certified Cloud Practitioner
• Prod: Amazon Web Services (AWS)
• Usage: Demonstrates a basic understanding of AWS cloud concepts, services, security, architecture, and pricing – really useful for our multi-cloud environment.
• Cert: Microsoft Certified: Azure Fundamentals (AZ-900)
• Prod: Microsoft
• Usage: Similar to the AWS practitioner, this shows you grasp the core concepts of Azure, which is another key cloud platform we use.
• Cert: ITIL 4 Foundation
• Prod: AXELOS
• Usage: A great certification for understanding IT service management best practices, especially incident and problem management, which is what you'll be doing daily.

Recommended Activities

• Regularly engage with online learning platforms like A Cloud Guru, Pluralsight, or Coursera to deepen your cloud knowledge.
• Participate in relevant online forums or communities (e.g., Reddit's r/sysadmin, r/cloud) to learn from others' experiences.
• Attend webinars or virtual conferences on cloud computing and technical support trends.
• Seek out mentorship opportunities within the team – our senior analysts are always happy to share their wisdom.
• Work on personal cloud projects in a free-tier account to get hands-on experience (e.g., setting up a small web server, deploying a simple application).

Career Progression Pathways

Entry Paths to This Role

• Path: Technical Apprenticeship Programme
• Time: 1-2 years
• Path: General IT Helpdesk / Service Desk Role
• Time: 1-2 years
• Path: Self-Taught Enthusiast / Personal Projects
• Time: Varies (can be 0-2 years of focused learning)

Career Progression From This Role

• Pathway: Cloud Support Assistant (L2)
• Time: 18-36 months

Long Term Vision Potential Roles

• Title: Senior Cloud Support Analyst (L3)
• Time: 3-5 years from entry
• Title: Cloud Operations Engineer (L4/L5)
• Time: 5-8 years from entry
• Title: Cloud Support Manager (L5)
• Time: 7-10 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.