Cloud Administrator

Role Purpose & Context

Role Summary

The Cloud Administrator is responsible for the day-to-day operational health of our cloud platforms, mainly AWS and Azure. This means you'll be responding to alerts, squashing bugs, and making sure our systems are up and running for our customers. You'll work closely with the Senior Cloud Administrators and our development teams, translating their needs into stable, working cloud infrastructure. When you do this well, our applications stay online, customers are happy, and our developers can focus on building new features without worrying about the underlying platform. If things go wrong, well, that's when the phones start ringing and everyone feels the pressure. The challenge here is the sheer pace of change in cloud tech and the need to be constantly learning. The reward? Seeing your work directly impact the business and knowing you're keeping the lights on for thousands of users.

Reporting Structure

• Reports to: Senior Cloud Administrator
• Direct reports:
• Matrix relationships: Cloud Operations Engineer, Systems Administrator (Cloud), DevOps Administrator,

Key Stakeholders

Internal:

• Development Teams (Software Engineers, QA)
• Product Management
• Cyber Security Team
• IT Support Desk
• Technical Leadership

External:

• AWS and Azure Support
• Third-party tool vendors (e.g., Datadog, Terraform)

Organisational Impact

Scope: This role directly underpins the stability and performance of our core applications and services. Getting it right means happy customers and productive developers. Getting it wrong means outages, lost revenue, and a lot of frustrated people. You're essentially the backbone of our digital operations.

Performance Metrics

Quantitative Metrics

1. Metric: Alert Response Time
2. Desc: How quickly you acknowledge and begin working on critical system alerts.
3. Target: 90% of P1/P2 alerts acknowledged within 15 minutes
4. Freq: Weekly via monitoring system reports
5. Example: An alert for an EC2 instance being down comes in. You're on it, investigating, and updating the incident within 10 minutes.
6. Metric: Incident Resolution Rate
7. Desc: The percentage of assigned incidents (P2/P3) that you resolve within their defined Service Level Agreements (SLAs).
8. Target: 95% of P2/P3 incidents resolved within SLA
9. Freq: Monthly via ITSM tool reports
10. Example: You pick up 10 P3 tickets this week, and successfully close 9 of them before their SLA clock runs out.
11. Metric: System Uptime Contribution
12. Desc: Your direct contribution to the overall uptime of the services you manage.
13. Target: Maintain 99.9% uptime for assigned services
14. Freq: Monthly via cloud provider dashboards and monitoring tools
15. Example: The database you look after has been up for 29 days straight this month, with no unexpected downtime due to your actions (or inactions).
16. Metric: Patching & Maintenance Compliance
17. Desc: Ensuring that the cloud resources you're responsible for are kept up-to-date with security patches and routine maintenance.
18. Target: 99%+ of managed instances patched within 30 days of release
19. Freq: Quarterly via vulnerability scanning and patch management reports
20. Example: You've made sure all your Windows VMs in Azure have applied their critical security updates from last month, leaving only a couple of non-critical ones outstanding.

Qualitative Metrics

1. Metric: Proactive Issue Identification
2. Desc: Spotting potential problems before they become full-blown incidents.
3. Evidence: You're regularly flagging unusual log patterns, resource spikes, or upcoming certificate expirations to your Senior Admin. You might even propose a fix before anyone else notices there's an issue brewing. We'll see this in your contributions during team stand-ups and in your tickets.
4. Metric: Documentation Quality
5. Desc: How clear, accurate, and up-to-date your operational documentation and runbooks are.
6. Evidence: Other team members can easily follow your runbooks to resolve common issues. Your post-mortems are detailed and helpful. When a new joiner asks 'how do I do X?', you can point them to a clear, current document you've written or updated. This is about making sure future-you (and everyone else) isn't guessing.
7. Metric: Collaboration & Communication
8. Desc: How effectively you work with other teams, especially developers, and communicate technical information.
9. Evidence: Developers come to you for advice on cloud configurations. You explain complex issues clearly to non-technical colleagues without resorting to jargon. You're good at asking for help when you need it and offering it when others are stuck. We'll notice this in how smoothly projects run and how few misunderstandings there are.

Primary Traits

• Trait: Forensic Problem-Solver
• Manifestation: When something breaks, you don't just restart it and hope. You'll methodically trace a request from the user's browser, through our load balancer, to the application server, then into the database logs. You're not guessing; you're using every tool at your disposal – logs, metrics, network traces – to prove your hypothesis. You stay calm and logical even when production is down and everyone's panicking.
• Benefit: A vague 'the website is slow' report needs someone who can dig through layers of cloud abstraction to find the actual root cause. This trait is what separates someone who just fixes symptoms from someone who solves the underlying problem, which is how we prevent the same outages from happening again and again. It's about getting to the 'why'.
• Trait: Deliberately Precise
• Manifestation: You're the kind of person who always uses `--dry-run` or `--what-if` flags before applying any infrastructure change. You double-check the target environment in your terminal prompt before running a potentially destructive command. You'll document changes in a ticket *before* you even think about making them. For you, 'close enough' isn't good enough when it comes to infrastructure.
• Benefit: Honestly, a single typo in a Terraform variable can delete a production database. A misconfigured firewall rule can expose sensitive customer data. Precision isn't just a nice-to-have; it's your primary defence against catastrophic, career-limiting mistakes. We need people who treat every change with the respect it deserves.
• Trait: Relentless Learner
• Manifestation: You probably have a personal sandbox account where you're always experimenting with new cloud services. You might spend evenings on A Cloud Guru or KodeKloud, just because you're curious. You can explain the difference between AWS's 15 different container services because you've actually read the documentation and tried them out. You enjoy figuring out how things work, even if it's not directly related to your current task.
• Benefit: The cloud landscape changes weekly, sometimes daily. The 'best practice' from 18 months ago is often legacy now. Without a deep-seated curiosity and a genuine drive to learn, your skills will become obsolete, and our infrastructure will become vulnerable and inefficient. We need people who actively want to keep up, not just react when they're told to.

Supporting Traits

• Trait: Process-Oriented
• Desc: You get why change management and documentation aren't just bureaucracy; they're essential for stability and avoiding chaos. You appreciate a good runbook.
• Trait: Pragmatically Skeptical
• Desc: You'll politely question if a developer *really* needs admin access to the production database, or if there's a more secure way to achieve their goal. It's not about being difficult, it's about being secure.
• Trait: Calm Under Fire
• Desc: You can think clearly and communicate effectively when systems are failing and people are panicking. You're the steady hand in a crisis, which is invaluable.
• Trait: Helpful & Collaborative
• Desc: You're happy to jump in and help a colleague or a developer who's stuck, even if it's not strictly 'your' problem. You understand that we're all in this together.

Primary Motivators

1. Motivator: Solving Tricky Puzzles
2. Daily: You get a real kick out of debugging a complex cloud issue, tracing it through multiple services until you find the obscure configuration error that caused it all. It's like being a detective for infrastructure.
3. Motivator: Keeping Things Running Smoothly
4. Daily: You feel a sense of accomplishment when you see dashboards showing 100% uptime for the services you manage. There's a quiet pride in knowing you're the one making sure everything is stable and reliable.
5. Motivator: Continuous Learning & Growth
6. Daily: You're always looking for new cloud services, features, or automation techniques to try out. You enjoy learning new things and applying them to make our systems better, faster, or more secure.

Potential Demotivators

Honestly, this role isn't for everyone. If you need every day to be perfectly structured, or if you dislike being the 'bad guy' when it comes to security, you might find it tough.

Common Frustrations

1. Developer Entitlement: Constantly pushing back against developers who demand root access or overly permissive IAM roles in production, forcing you to be the 'bad guy' to prevent security disasters. It's exhausting.
2. Alert Fatigue: Drowning in a sea of low-priority, non-actionable alerts from poorly configured monitoring, making it mentally exhausting to spot the one alert that actually signals a major outage.
3. Cost Optimization Whack-a-Mole: Spending hours each week hunting down untagged S3 buckets or oversized EC2 instances spun up by other teams, only to have new ones appear the next day. It feels like an endless battle.
4. The 'It Works on My Machine' Black Hole: Wasting days debugging why a container fails in the production Kubernetes cluster when the developer insists it runs perfectly on their laptop, often due to subtle environment or networking differences. It's infuriating.
5. On-Call Creep: The unspoken expectation that you're always available to jump on an issue, even when you're not the one officially on call, leading to burnout if you don't set boundaries.

What Role Doesn't Offer

1. A predictable 9-to-5 schedule every single day. Incidents don't care about your plans.
2. Complete autonomy over strategic architectural decisions (that comes later).
3. A quiet, uninterrupted work environment all the time (alerts can be noisy).
4. The ability to avoid difficult conversations about security or best practices.

ADHD Positives

1. The fast-paced nature of incident response can be engaging and stimulating, providing varied challenges.
2. Opportunities for hyperfocus when deeply debugging complex cloud issues, leading to rapid problem resolution.
3. The constant need to learn new technologies and adapt to change keeps things fresh and avoids monotony.

ADHD Challenges and Accommodations

1. Managing alert fatigue and prioritising multiple incoming requests can be tough; clear prioritisation frameworks and tools are essential.
2. Documentation can feel tedious; using AI tools for drafting or having structured templates can help.
3. Maintaining focus during long, routine maintenance tasks might be difficult; breaking tasks into smaller chunks or using 'body doubling' techniques can assist.

Dyslexia Positives

1. Strong visual-spatial reasoning often excels in understanding complex cloud architecture diagrams and network flows.
2. Excellent problem-solving skills, especially for non-linear issues, are highly valued in cloud operations.
3. Practical, hands-on work with cloud consoles and command-line interfaces can be more accessible than heavy text-based tasks.

Dyslexia Challenges and Accommodations

1. Extensive reading of logs and documentation can be challenging; using screen readers, text-to-speech tools, or AI summarisation can help.
2. Writing detailed post-mortems or runbooks might require extra time; using templates, dictation software, or peer review for grammar/spelling can be beneficial.
3. Careful attention to syntax in code (Terraform, YAML) is critical; robust IDEs with auto-completion and linting are a must.

Autism Positives

1. A strong preference for logical, systematic problem-solving is perfect for debugging cloud infrastructure.
2. Attention to detail and precision, especially in configuration management and security, is a significant asset.
3. Ability to focus deeply on technical tasks for extended periods, leading to thorough analysis and resolution.

Autism Challenges and Accommodations

1. Unpredictable incidents and urgent requests can be disruptive; clear communication protocols and incident management structures help manage this.
2. Navigating social dynamics during high-pressure incidents might be challenging; focusing on clear, factual communication is encouraged.
3. Sensory overload from constant alerts or open-plan office environments; noise-cancelling headphones or quiet spaces can be helpful.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Mid-Level Professional
2. Responsibilities: Independently respond to and resolve P1/P2/P3 alerts from our monitoring systems (Datadog, New Relic) for assigned cloud services. This means you'll be the first responder, diagnosing the issue and getting things back online.
3. Take ownership of routine cloud administration tasks, like managing user access (IAM), patching virtual machines, and ensuring backup schedules are running successfully. Yes, it's often repetitive, but it's crucial.
4. Implement standard changes to our AWS and Azure infrastructure using existing Terraform modules and Ansible playbooks. You'll be running `terraform apply` and `ansible-playbook` on a regular basis.
5. Identify and troubleshoot common cloud networking issues, such as misconfigured security groups, route table problems, or VPN connectivity failures. You'll be using tools like `traceroute` and `nslookup` a lot.
6. Contribute to incident post-mortems by providing clear timelines and technical details of what happened and what you did to fix it. We're blameless here, but we need to learn from every incident.
7. Maintain and update operational documentation and runbooks for the services you manage. If you fix something, document it. Future-you will thank you.
8. Perform basic cost optimisation tasks, like identifying idle resources or ensuring correct tagging, under the guidance of a Senior Admin. Every penny saved helps the business.
9. Supervision: You'll have weekly check-ins with your Senior Cloud Administrator to discuss ongoing work, any blockers, and to review more complex issues. For routine tasks, you're expected to work independently, but don't hesitate to ask for help when you hit a wall—that's what the team's for.
10. Decision: You'll make routine operational decisions within established guidelines, like restarting a service, adjusting a scaling group, or approving a standard access request. Anything outside of these guidelines, or any change that could impact multiple services or incur significant cost, needs to be escalated to your Senior Cloud Administrator for review and approval.
11. Success: You're successful when the services you manage are stable, incidents are resolved quickly and effectively, and your documentation is clear enough for others to follow. Basically, you're making life easier for everyone else.

Decision-Making Authority

• Type: Incident Response (P1/P2)
• Entry: Escalate immediately, follow runbook with close supervision.
• Mid: Independently diagnose and resolve using established runbooks; escalate if runbook fails or issue is novel.
• Senior: Lead incident response, coordinate multiple teams, make on-the-fly technical decisions, define new runbooks.
• Type: Infrastructure Changes
• Entry: Execute pre-approved changes using existing scripts under direct supervision.
• Mid: Implement standard changes using existing IaC modules; propose minor modifications to modules for review.
• Senior: Design and implement new infrastructure patterns, author new IaC modules, approve changes from junior team members.
• Type: Access Management
• Entry: Process user access requests following strict guidelines; escalate any deviations.
• Mid: Manage user and role permissions within defined policies; identify and report overly permissive access.
• Senior: Define and audit IAM policies, implement least privilege principles, design secure access patterns.
• Type: Tool Selection
• Entry: No input on tool selection.
• Mid: Research and propose specific features of existing tools; suggest minor utility scripts.
• Senior: Evaluate and recommend new tools for specific problem areas; lead PoCs for new technologies.

Competency Requirements

Foundation Skills (Transferable)

These are the fundamental ways you'll think and interact. They're not about specific tools, but about how you approach problems and work with people. Getting these right is just as important as your technical chops.

• Category: Communication & Collaboration
• Skills: Clear Technical Explanations: You can explain complex cloud issues to a developer without oversimplifying, and to a non-technical manager without jargon. It's about tailoring your message.
• Active Listening: You actually hear what people are saying, especially during an incident or when a developer is describing a problem. This helps you get to the root cause faster.
• Teamwork: You're happy to jump in and help a colleague who's stuck, and you know when to ask for help yourself. We're a team, not a collection of individuals.
• Written Documentation: Your runbooks, incident reports, and internal emails are clear, concise, and easy to follow. No one wants to decipher cryptic notes.
• Category: Problem-Solving & Critical Thinking
• Skills: Systematic Debugging: You approach issues methodically, forming hypotheses and testing them, rather than just guessing. Think like a detective.
• Root Cause Analysis: You don't just fix the symptom; you dig deeper to find out *why* something broke, preventing it from happening again.
• Prioritisation: You can quickly assess the urgency and impact of multiple incoming requests and decide what needs attention first. Not everything is a P1.
• Adaptability: The cloud changes fast. You're comfortable learning new things on the fly and adapting to new tools or processes.
• Category: Attention to Detail & Reliability
• Skills: Precision in Execution: You double-check your work, especially before making changes in production. A misplaced comma can cause chaos.
• Thoroughness: You don't cut corners on security, patching, or documentation. You understand that the little things matter.
• Accountability: You take ownership of your tasks and see them through to completion, even when they're challenging. If you say you'll do it, you do it.

Functional Skills (Role-Specific Technical)

These are the specific technical skills and knowledge you'll need to do the job well. We're looking for practical experience here, not just theoretical understanding.

Technical Competencies

• Skill: Cloud Security Best Practices
• Desc: You'll understand the Principle of Least Privilege and how to apply it. You know the difference between IAM roles and users, network ACLs and Security Groups, and how data encryption (at-rest with KMS, in-transit with TLS) actually works.
• Level: Intermediate
• Skill: Infrastructure as Code (IaC) Principles
• Desc: You get the idea of declarative infrastructure ('this is the state I want'). You can manage state drift in a basic way and understand the potential 'blast radius' of your changes.
• Level: Intermediate
• Skill: High Availability & Disaster Recovery
• Desc: You understand multi-AZ architectures and why they're important. You can follow backup and restore procedures and know the difference between RTO (how fast you recover) and RPO (how much data you lose) in a practical sense.
• Level: Intermediate
• Skill: FinOps & Cost Optimization
• Desc: You're good at resource tagging and understand why it matters. You can use tools like AWS Cost Explorer to spot obvious cost sprawl and understand the basic trade-offs between different instance types.
• Level: Basic
• Skill: Cloud Networking Fundamentals
• Desc: You can troubleshoot a VPC/VNet, understanding subnets, route tables, internet gateways, NAT gateways, and load balancers. You can follow network diagrams and debug connectivity issues.
• Level: Intermediate
• Skill: Incident Management & Response
• Desc: You can follow a runbook accurately during a live incident. You contribute to post-mortems by providing clear timelines and actions. You understand and can monitor SLOs/SLAs.
• Level: Intermediate

Digital Tools

• Tool: AWS (EC2, S3, IAM, VPC, RDS, Lambda)
• Level: Intermediate
• Usage: Managing EC2 instances, S3 buckets, IAM users/roles, troubleshooting VPC networking, basic RDS operations, deploying existing Lambda functions.
• Tool: Azure (VM, Blob Storage, Azure AD, VNet, App Services)
• Level: Intermediate
• Usage: Managing Azure VMs, Blob Storage, Azure AD users, troubleshooting VNet connectivity, deploying/managing App Services.
• Tool: Terraform
• Level: Intermediate
• Usage: Reading HCL, running `terraform plan` and `apply` on existing modules, making minor modifications to variables, understanding state files.
• Tool: Ansible
• Level: Intermediate
• Usage: Executing pre-written playbooks for configuration management, understanding basic YAML syntax, making minor playbook adjustments.
• Tool: Docker
• Level: Intermediate
• Usage: Building Dockerfiles, running `docker-compose` for local development or testing, managing local containers.
• Tool: Kubernetes (kubectl)
• Level: Basic
• Usage: Using `kubectl` to check pod status (`get`, `describe`, `logs`), applying simple YAML manifests, troubleshooting basic pod issues.
• Tool: Datadog/New Relic
• Level: Intermediate
• Usage: Viewing dashboards, acknowledging alerts, performing basic and intermediate log queries to diagnose issues, creating simple custom dashboards.
• Tool: Git (GitHub/GitLab)
• Level: Intermediate
• Usage: Cloning repos, creating branches, committing code, opening pull requests, resolving common merge conflicts, understanding branching strategies.
• Tool: Bash Scripting
• Level: Intermediate
• Usage: Reading and executing existing shell scripts, writing simple scripts for automation (e.g., backups, log rotation, simple health checks).

Industry Knowledge

• Area: Cloud Computing Models
• Desc: You understand the differences between IaaS, PaaS, and SaaS, and how they apply to our services.
• Area: DevOps Principles
• Desc: You get the idea of continuous integration/continuous deployment (CI/CD) and why automation is important in cloud operations.
• Area: Operating Systems (Linux/Windows)
• Desc: You're comfortable with basic administration of both Linux (command line, package management) and Windows Server (PowerShell, services).

Regulatory Compliance Regulations

• Reg: GDPR (General Data Protection Regulation)
• Usage: You understand the basic principles of data protection and how they apply to storing and processing customer data in the cloud, particularly around data residency and access controls. You know when to escalate a potential GDPR issue.
• Reg: ISO 27001 (Information Security Management)
• Usage: You understand the importance of information security policies and procedures, especially around access control, incident management, and data encryption, as they relate to maintaining our ISO 27001 certification.

Essential Prerequisites

• At least 2 years of hands-on experience working with either AWS or Azure in an administrative or operational capacity.
• Demonstrable experience with Linux or Windows Server administration, including command-line operations.
• Practical experience with a version control system, preferably Git, including branching, merging, and pull requests.
• A solid grasp of networking fundamentals: TCP/IP, DNS, HTTP/S, firewalls, and VPNs.
• Experience with basic scripting (e.g., Bash, PowerShell, or Python) for automation tasks.
• Familiarity with monitoring and logging tools to troubleshoot system issues.

Career Pathway Context

These aren't just a checklist; they're the foundational skills you'll need to hit the ground running. We're not expecting you to be an expert in everything, but you should have a solid understanding of these areas from previous roles or self-study. If you're missing one or two, but excel elsewhere, we're still keen to chat. We're looking for potential, not perfection.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: Prompt Engineering for Cloud Operations
• Why: AI assistants are getting smarter. Being able to 'talk' to them effectively to generate code, summarise logs, or troubleshoot issues will be a huge productivity booster. Those who master this will simply get more done.
• Concepts: [{'concept_name': 'Effective Prompting for IaC', 'description': 'Learning how to write clear, concise prompts to generate Terraform or Ansible code that actually works for your specific use case.'}, {'concept_name': 'AI for Log Analysis', 'description': 'Using AI to quickly summarise vast amounts of log data, identify anomalies, and suggest potential root causes during an incident.'}, {'concept_name': 'Context Windows & Token Limits', 'description': 'Understanding how much information an AI can process at once and how to structure your prompts for optimal results.'}, {'concept_name': 'Output Validation', 'description': "Knowing that AI output isn't always perfect and developing a critical eye to validate generated code or summaries before using them."}]
• Prepare: This month: Start using GitHub Copilot or a similar AI assistant for all your scripting and IaC tasks. Treat it like a pair programmer.
• Next month: Experiment with an LLM (ChatGPT, Claude) to summarise log files from a past incident or to explain a complex cloud concept.
• Month 3: Try to generate a small, functional Terraform module from scratch using only natural language prompts, then refine it manually.
• Ongoing: Share your AI-powered productivity tips and tricks with the team. We're all learning here.
• QuickWin: Start using AI to draft your internal emails, summarise long technical articles, or generate basic shell scripts today. It's low-risk and immediately helpful.
• Skill: Sustainable Cloud Practices (GreenOps)
• Why: As cloud usage grows, so does its environmental impact. Businesses are increasingly focused on reducing their carbon footprint, and cloud administrators will be on the front lines of optimising for energy efficiency, not just cost.
• Concepts: [{'concept_name': 'Carbon Footprint Metrics', 'description': 'Understanding how to measure the energy consumption and carbon emissions of cloud resources.'}, {'concept_name': 'Optimising Resource Utilisation', 'description': 'Identifying and shutting down idle resources, right-sizing instances, and using serverless where appropriate to reduce energy waste.'}, {'concept_name': 'Renewable Energy Regions', 'description': 'Understanding which cloud regions run on renewable energy and how to factor this into deployment decisions.'}, {'concept_name': 'Lifecycle Management', 'description': "Implementing policies to automatically delete unused resources and prevent 'cloud waste' that consumes energy."}]
• Prepare: This quarter: Read up on the principles of GreenOps and FinOps. They're closely related.
• Next quarter: Identify one area in our current cloud setup where we could reduce energy consumption (e.g., by shutting down non-prod environments overnight).
• Month 6: Propose a 'GreenOps' initiative to the team, perhaps around optimising our development environments.
• Ongoing: Keep an eye on new features from AWS/Azure that help track or reduce environmental impact.
• QuickWin: Start by simply being more diligent about shutting down non-production resources when they're not in use. It saves money *and* energy.

Advancing Technical Skills

• Skill: Advanced Container Orchestration (Kubernetes)
• Why: More and more applications are moving to Kubernetes. You'll need to go beyond basic `kubectl` commands to truly manage and troubleshoot these complex environments.
• Concepts: [{'concept_name': 'Helm Charts', 'description': 'Deploying and managing applications using Helm for packaging and templating Kubernetes manifests.'}, {'concept_name': 'Debugging Pod Issues', 'description': 'Diagnosing complex issues like `CrashLoopBackOff`, `Pending` pods, or networking problems within a Kubernetes cluster.'}, {'concept_name': 'Ingress Controllers', 'description': 'Understanding how traffic enters the cluster and how to configure Ingress for routing and load balancing.'}, {'concept_name': 'Resource Management', 'description': 'Setting resource requests and limits, understanding Quality of Service (QoS) classes, and troubleshooting resource contention.'}]
• Prepare: This quarter: Take an online course on Kubernetes administration (e.g., from KodeKloud or A Cloud Guru).
• Next quarter: Set up a small Kubernetes cluster (Minikube or a free tier cloud cluster) and deploy a few applications using Helm.
• Month 6: Volunteer to help the development team troubleshoot a Kubernetes-related issue, even if it's just observing.
• Ongoing: Read the official Kubernetes documentation and follow community forums to stay updated.
• QuickWin: Familiarise yourself with the `helm` CLI tool and try installing a common application like Prometheus or Grafana into a test cluster.
• Skill: Advanced Cloud Networking & Security
• Why: As our cloud footprint grows, so does the complexity of our networks and the sophistication of threats. You'll need to be able to design more robust network architectures and implement tighter security controls.
• Concepts: [{'concept_name': 'VPC/VNet Peering & Transit Gateways', 'description': 'Connecting multiple virtual networks securely and efficiently across regions or accounts.'}, {'concept_name': 'Network Segmentation', 'description': 'Designing and implementing network segmentation strategies to isolate sensitive workloads.'}, {'concept_name': 'Web Application Firewalls (WAF)', 'description': 'Understanding how WAFs protect against common web exploits and how to configure rules.'}, {'concept_name': 'Identity Federation & SSO', 'description': 'Implementing single sign-on solutions for cloud access and integrating with corporate directories.'}]
• Prepare: This quarter: Deep dive into the advanced networking documentation for AWS and Azure.
• Next quarter: Design a multi-account, multi-VPC network architecture for a hypothetical application.
• Month 6: Take a cloud security specialisation course (e.g., AWS Certified Security – Specialty).
• Ongoing: Participate in security reviews and discussions within the team, offering your perspective.
• QuickWin: Review our current network diagrams and identify any areas where segmentation could be improved or simplified. Propose a small change.

Education Requirements

• Level: Minimum
• Req: A Levels (or equivalent vocational qualification in IT/Computing)
• Alts: We're pragmatic. If you've got 2-3 years of solid, hands-on experience in a similar role and can show us what you can do, that's just as good as formal qualifications. We value practical skills over certificates sometimes.
• Level: Preferred
• Req: Degree in Computer Science, Information Technology, or a related field
• Alts: While a degree is nice, it's not a deal-breaker. If you've self-taught, completed bootcamps, or have a strong portfolio of projects, we're interested.

Experience Requirements

You'll need at least 2-5 years of hands-on experience in a cloud administration or operations role, specifically working with either AWS or Azure. We're looking for someone who's comfortable with routine cloud tasks, has a good grasp of Linux or Windows server administration, and isn't afraid to get stuck into troubleshooting. Experience with Infrastructure as Code (like Terraform) and scripting (Bash, Python) is a big plus.

Preferred Certifications

• Cert: AWS Certified SysOps Administrator – Associate
• Prod: Amazon Web Services (AWS)
• Usage: This certification shows you've got a solid understanding of deploying, managing, and operating scalable, highly available, and fault-tolerant systems on AWS. It covers a lot of what you'll do day-to-day.
• Cert: Microsoft Certified: Azure Administrator Associate
• Prod: Microsoft Azure
• Usage: Demonstrates your ability to implement, manage, and monitor an organisation’s Microsoft Azure environment. It's a great way to prove your Azure chops.
• Cert: HashiCorp Certified: Terraform Associate
• Prod: HashiCorp
• Usage: Proves your fundamental understanding of Terraform concepts and skills. Given how much we use IaC, this is a really valuable one to have.

Recommended Activities

• Regularly engage with cloud provider documentation (AWS Docs, Azure Docs) to stay updated on new services and features.
• Participate in online communities, forums, or local meetups for cloud professionals to share knowledge and learn from peers.
• Maintain a personal cloud sandbox account to experiment with new technologies and practice skills without impacting production.
• Attend webinars or virtual conferences on cloud computing, DevOps, or security to keep your knowledge current.
• Contribute to open-source projects, even if it's just documentation updates or small bug fixes, to build practical experience.

Career Progression Pathways

Entry Paths to This Role

• Path: Junior IT Support / Helpdesk
• Time: 2-3 years
• Path: On-Premises Systems Administrator
• Time: 2-4 years
• Path: Recent Graduate (Computer Science/IT)
• Time: 0-2 years (with relevant internships/projects)

Career Progression From This Role

• Pathway: Senior Cloud Administrator
• Time: 3-5 years in this role
• Pathway: Cloud Engineer
• Time: 3-5 years in this role

Long Term Vision Potential Roles

• Title: Lead Cloud Administrator / Staff Cloud Engineer
• Time: 5-8 years
• Title: Cloud Operations Manager / Principal Cloud Architect
• Time: 8-12 years
• Title: Director of Cloud Infrastructure
• Time: 12-16 years

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.