Cloud Migration Coordinator

Role Purpose & Context

Role Summary

The Cloud Migration Coordinator is here to make sure our cloud migration waves actually happen, on time and without too many fireworks. You'll be taking the overall migration plan and breaking it down into daily tasks, then making sure everyone involved—from network engineers to application owners—knows what they need to do and when. This role sits right in the thick of it, connecting our legacy infrastructure teams with our shiny new cloud platform team. You'll be translating complex technical requirements into project plans, tracking progress, and flagging issues before they become full-blown crises. When this role is done well, migrations run smoothly, applications move without downtime, and our business keeps ticking along. If it's not, well, critical systems can go offline, projects get delayed by weeks, and we're looking at some serious costs and unhappy customers. The challenge? It's like herding cats, sometimes. You're relying on a lot of different people, and things rarely go exactly to plan. But the reward is seeing a complex, high-stakes project successfully land in the cloud, knowing you were a huge part of making it happen.

Reporting Structure

• Reports to: Senior Cloud Migration Coordinator
• Direct reports: None, but you'll often help new joiners find their feet.
• Matrix relationships: Migration Project Coordinator, Cloud Transition Specialist, Technical Migration Analyst,

Key Stakeholders

Internal:

• Infrastructure and Operations Teams (the folks who manage our current data centres)
• Cloud Platform Engineering (the team building our new cloud environments)
• Application Owners (the people who actually use the systems we're moving)
• Security and Networking Teams (critical for making sure everything is safe and connected)
• Project Managers (who need your updates to keep the overall programme on track)

External:

• Cloud Provider Support (AWS, Azure, GCP – for technical issues)
• Third-party Vendors (sometimes we use external consultants for specific migration tasks)

Organisational Impact

Scope: You're directly responsible for the smooth execution of migration waves, which means you're helping us shut down expensive data centres and move to a more agile, cost-effective cloud infrastructure. Get it right, and we save money and innovate faster. Get it wrong, and we face downtime, budget overruns, and a lot of frustrated colleagues.

Performance Metrics

Quantitative Metrics

1. Metric: Task Completion Rate for Assigned Move Groups
2. Desc: The percentage of migration tasks you're responsible for that get finished by their due date.
3. Target: >95% on-time completion
4. Freq: Weekly, reviewed in 1:1s and project stand-ups
5. Example: If your assigned move group has 50 tasks for the week, you'll aim to get 48-49 of them done or formally re-planned with agreement.
6. Metric: Runbook Accuracy for Cutover Events
7. Desc: How many errors or missing steps are found in the migration runbooks you've helped prepare.
8. Target: Zero critical errors or omissions
9. Freq: Per migration cutover, reviewed during pre-migration 'go/no-go' calls
10. Example: Your runbook for the 'Finance Reporting' move group correctly listed all DNS updates, firewall changes, and application startup sequences, preventing any delays.
11. Metric: Reduction in Migration-Related Incidents
12. Desc: The number of unplanned outages or major issues that happen during or immediately after a migration wave you've coordinated.
13. Target: <1 major incident per 10 migrations
14. Freq: Monthly, tracked against overall migration programme
15. Example: You coordinated 12 server migrations this quarter, and only one had a minor, non-critical issue that was resolved within 30 minutes, keeping us well under target.
16. Metric: Stakeholder Update Timeliness
17. Desc: How consistently you provide status updates to relevant teams and project managers.
18. Target: All scheduled updates delivered on time
19. Freq: Weekly, via project dashboards and team meetings
20. Example: Your weekly status report for the 'CRM Migration' wave was sent out every Monday morning, giving everyone a clear picture of progress and blockers.

Qualitative Metrics

1. Metric: Problem Identification & Escalation
2. Desc: Your ability to spot potential problems early and get the right people involved before they become big issues.
3. Evidence: You're often the first to flag a looming dependency issue or a resource conflict. You bring solutions or clear options to your manager, not just problems. You don't sit on bad news.
4. Metric: Cross-Team Collaboration
5. Desc: How effectively you work with different technical and business teams to get things done.
6. Evidence: Other teams readily respond to your requests. You're seen as a helpful point of contact, not just someone chasing them. You can smooth over minor disagreements between teams.
7. Metric: Documentation Quality
8. Desc: The clarity and completeness of the documentation you produce, like task lists, dependency trackers, and meeting notes.
9. Evidence: Your documentation is easy for anyone to understand, even if they weren't in the meeting. Key decisions and action items are clearly recorded and followed up on. People rarely ask for clarification on your notes.
10. Metric: Adaptability to Change
11. Desc: How well you handle it when plans change (and they will!) or new priorities pop up.
12. Evidence: When a migration date shifts, you quickly re-plan tasks and communicate the new timeline without getting flustered. You can adjust your approach when a technical challenge requires a different solution.

Primary Traits

• Trait: Process-Minded
• Manifestation: You're the person who instinctively creates a checklist for everything, even your grocery shopping. You believe in the power of a well-defined runbook and make sure every single sign-off box is ticked before a 'go/no-go' decision. You'll spot when someone's trying to skip a step because 'it's quicker' and gently but firmly guide them back to the agreed process.
• Benefit: Honestly, a single missed step in a migration cutover—like forgetting to update a DNS entry or a firewall rule—can cause a multi-million-pound outage. It’s not just about inconvenience; it's about serious business impact. This trait is our organisational immune system against human error, especially when things are moving fast.
• Trait: Calm Under Pressure
• Manifestation: It's 2 AM on a Saturday, a critical service has failed to start after a migration, and tensions are high. Your voice remains steady. You methodically go through the rollback plan, checking each step without panic. You're the anchor in the storm, keeping everyone focused on the plan, not the drama. You don't get easily flustered when things inevitably go wrong.
• Benefit: Panic is incredibly contagious, especially during high-stakes migration cutovers. The coordinator has to be a source of stability, making sure the team follows the plan and makes rational decisions, even when everything feels like it’s falling apart. Your ability to stay level-headed can literally prevent a minor issue from escalating into a major incident.
• Trait: Relentless Follow-up
• Manifestation: You're perfectly comfortable sending that 'gentle reminder' email for the fifth time. You know exactly which stakeholders respond best to a quick Slack message, who needs a direct phone call, and who only moves when a calendar invite for a 'decision required' meeting lands in their inbox. You probably have a mental (or actual) list of 'who owes me what' at all times.
• Benefit: Migrations are a massive team sport involving dozens of different groups: networking, security, application owners, database administrators, and more. You're the human message bus, making sure no dependency is dropped, no approval is forgotten, and no task falls through the cracks. Without this, delays can cascade for weeks, costing us a fortune and frustrating everyone involved.

Supporting Traits

• Trait: Diplomatic
• Desc: You'll often need to translate complex engineer-speak for business stakeholders and explain business priorities to technical teams, all without losing the core message or offending anyone. It's a bit like being a multilingual translator.
• Trait: Inquisitive
• Desc: You're not afraid to ask 'why?' or 'what if?' to uncover hidden assumptions, undocumented dependencies, or potential risks that others might miss. You want to understand the full picture, not just the surface-level request.
• Trait: Pragmatic
• Desc: You understand that sometimes the 'perfect' technical solution isn't the 'right' solution if it means delaying the entire project by months. You can help find practical, achievable paths forward, balancing ideal outcomes with real-world constraints.
• Trait: Organised
• Desc: You keep track of multiple moving parts, deadlines, and dependencies without dropping the ball. Your notes are clear, your files are tidy, and you know where everything is when someone asks for it.

Primary Motivators

1. Motivator: Bringing Order to Chaos
2. Daily: You get a genuine kick out of taking a messy, complex problem (like moving 100 applications) and breaking it down into manageable, trackable steps. You love seeing the 'to-do' list shrink.
3. Motivator: Being the Central Hub
4. Daily: You enjoy being the go-to person for information, the one who knows what's happening across different teams and can connect the dots. You like being the conduit for critical updates.
5. Motivator: Achieving Tangible Outcomes
6. Daily: You're driven by seeing a project actually complete. There’s a real sense of accomplishment when a server successfully moves to the cloud, and you know you played a key part.

Potential Demotivators

Honestly, this role isn't for everyone. You'll spend a fair bit of time chasing people for updates, and sometimes you'll feel like you're nagging. The 'urgent' request that disrupted your Thursday might get deprioritised on Friday, and you'll have to pivot quickly. You'll often be the messenger of bad news (delays, issues) even if they aren't your fault. If you need every piece of work you touch to be a deep technical dive or to see every single idea make it to production, you might struggle here.

Common Frustrations

1. Archaeological Digs: Trying to migrate a 15-year-old application with zero documentation and the original developers long gone. It’s like being an IT detective with no clues.
2. Ghost Stakeholders: Chasing application owners for critical information, only to find they are unresponsive, uncooperative, or view the migration as a low-priority distraction.
3. The 2 AM Surprise: Discovering a critical, undocumented hard-coded IP address during the final cutover, forcing a high-stress rollback. It's never a fun call.
4. Scope Creep by a Thousand Cuts: The endless stream of 'while you're in there, can you just...' requests that threaten to derail the entire migration timeline.
5. Approval Limbo: Having a migration wave ready to go but being blocked for weeks waiting for sign-offs from separate Security, Networking, and Finance committees. The bureaucracy can be maddening.

What Role Doesn't Offer

1. Deep, hands-on coding or infrastructure build-out: While you'll understand the tech, you won't be writing the Terraform or configuring the network yourself.
2. Predictable, routine work: Expect curveballs. Plans change, issues arise, and you'll need to adapt constantly.
3. Sole ownership of technical solutions: You're coordinating the solution, not designing the architecture from scratch.

ADHD Positives

1. The fast-paced, varied nature of managing multiple tasks and chasing different teams can be engaging and prevent boredom.
2. The need for rapid problem-solving during cutovers can be stimulating and play to strengths in quick thinking.
3. The role often requires switching contexts, which can suit those who thrive on novelty and diverse challenges.

ADHD Challenges and Accommodations

1. Maintaining focus on detailed documentation or repetitive tasks can be challenging; using templates and breaking tasks into smaller chunks can help.
2. Organisational systems (Jira, Confluence) are key; personalised training on how to best use these tools for tracking and reminders could be beneficial.
3. Potential for overwhelm with many simultaneous requests; clear prioritisation frameworks and regular check-ins with your manager are crucial.

Dyslexia Positives

1. Strong verbal communication and problem-solving skills are highly valued, often compensating for written challenges.
2. The ability to see the 'big picture' of a migration and connect disparate tasks can be a significant strength.
3. Often excels in visualising complex workflows and dependencies, which is vital for migration planning.

Dyslexia Challenges and Accommodations

1. Extensive reading and writing of documentation (runbooks, reports) might be challenging; tools with text-to-speech, grammar checkers, and clear, templated formats can help.
2. Proofreading is critical; pairing with a colleague for important documents or using advanced AI writing assistants for initial drafts can be useful.
3. Clear, concise written communication is important; training on structured writing for technical documents can be provided.

Autism Positives

1. A strong adherence to processes and meticulous attention to detail (e.g., in runbooks) is highly valued and critical for success.
2. The ability to identify patterns and logical inconsistencies in migration plans can be a significant asset.
3. Clear, structured communication (e.g., in project tools like Jira) is often preferred and can be a strength.

Autism Challenges and Accommodations

1. Navigating complex social dynamics and unspoken expectations across many teams can be challenging; explicit communication norms and clear expectations for interactions are helpful.
2. Unexpected changes or last-minute shifts in plans can be difficult; advance notice and clear explanations for changes are important.
3. Sensory overload during intense cutover calls (multiple voices, screens, high pressure) might be an issue; options for quieter workspaces or specific communication protocols could be explored.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Cloud Migration Coordinator (Mid-Level)
2. Responsibilities: Take ownership of the coordination for a specific 'move group' (a collection of applications/servers moving together). This means knowing every task, every dependency, and who's responsible for what.
3. Independently track and update migration tasks in Jira and Confluence, making sure all statuses are accurate and blockers are clearly logged. You'll be the source of truth for your assigned wave.
4. Help prepare detailed migration runbooks for cutover events, working closely with technical teams to capture every step. You'll double-check these for accuracy.
5. Coordinate pre-migration activities like dependency mapping sessions and readiness checks for your move group. This involves scheduling meetings, sending reminders, and making sure people actually turn up.
6. Communicate progress, risks, and issues for your assigned migration wave to your Senior Coordinator and the broader project team. You'll be expected to provide clear, concise updates.
7. Assist in post-migration verification activities, making sure everything has landed correctly and is working as expected. This might involve checking dashboards or running simple tests.
8. Provide informal guidance and support to new or junior team members, helping them understand our processes and tools. Think of it as showing them the ropes.
9. Supervision: You'll have weekly check-ins with your Senior Cloud Migration Coordinator. For routine tasks, you'll work independently, but you're expected to flag any novel or complex issues for discussion and guidance.
10. Decision: You can make routine decisions within established guidelines for your assigned move group, like re-prioritising tasks within a week or adjusting meeting schedules. You'll escalate any technical architecture decisions, major timeline changes, or significant resource conflicts to your Senior Coordinator.
11. Success: You'll know you're doing well when your assigned migration waves consistently hit their deadlines, have minimal post-migration issues, and other teams see you as a reliable, organised point of contact. Your documentation will be clear, and you'll be proactive in identifying and flagging potential problems.

Decision-Making Authority

• Type: Task Prioritisation within a Move Group
• Entry: Escalate to Senior Coordinator for approval.
• Mid: Can independently re-prioritise tasks within your assigned move group, informing your Senior Coordinator. Major shifts require consultation.
• Senior: Full autonomy to prioritise tasks across multiple move groups; consult Lead Coordinator on resource allocation conflicts.
• Type: Migration Runbook Content
• Entry: Contribute specific steps under direct supervision; all content reviewed by Senior Coordinator.
• Mid: Draft sections of runbooks independently, working with technical teams; final review by Senior Coordinator.
• Senior: Own the creation and finalisation of runbooks for complex waves, including critical path analysis and rollback plans.
• Type: Escalation of Blockers/Issues
• Entry: Escalate all blockers immediately to Senior Coordinator.
• Mid: Identify and document blockers, propose initial solutions, then escalate to Senior Coordinator for approval/action.
• Senior: Independently assess severity of blockers, engage relevant stakeholders, and drive resolution. Escalate only high-impact, cross-programme issues to Lead/Manager.
• Type: Tooling & Process Improvements
• Entry: Suggest minor improvements to Senior Coordinator.
• Mid: Propose and, with approval, implement minor improvements to Jira workflows or Confluence templates for your move group.
• Senior: Design and implement significant process improvements or tooling enhancements for entire migration waves, getting buy-in from relevant teams.

Competency Requirements

Foundation Skills (Transferable)

These are the fundamental skills that underpin everything you'll do. They're not just 'nice-to-haves'; they're essential for keeping complex migration projects on track and communicating effectively with a diverse group of people.

• Category: Communication & Collaboration
• Skills: Clear Written Communication: You'll be writing a lot of emails, status updates, and documentation. They need to be concise and easy to understand.
• Active Listening: You need to really hear what technical teams are saying about risks or dependencies, and what business teams need.
• Meeting Facilitation: Running stand-ups, dependency mapping sessions, and status meetings effectively, keeping them on track and productive.
• Conflict Resolution (Basic): Being able to gently mediate minor disagreements between teams about priorities or resources.
• Category: Problem-Solving & Critical Thinking
• Skills: Issue Identification: Spotting potential problems in a migration plan before they blow up.
• Root Cause Analysis (Basic): Asking 'why' enough times to understand *why* something went wrong, not just *what* went wrong.
• Prioritisation: Knowing what needs to be done first, especially when you have multiple urgent requests.
• Structured Thinking: Breaking down complex problems into smaller, manageable pieces.
• Category: Organisational & Planning
• Skills: Task Management: Keeping track of your own tasks and those of your assigned move group.
• Time Management: Juggling multiple deadlines and ensuring you're using your time effectively.
• Attention to Detail: Catching those small errors in a runbook or a dependency list that could cause big problems.
• Process Adherence: Following established procedures and encouraging others to do the same.
• Category: Adaptability & Resilience
• Skills: Flexibility: Being able to pivot quickly when plans change or new information comes to light.
• Stress Management: Staying calm and focused during high-pressure situations, like cutover weekends.
• Learning Agility: Picking up new tools, processes, or cloud concepts quickly.

Functional Skills (Role-Specific Technical)

These are the specific methodologies, technical concepts, and tools you'll be using day-in, day-out. You don't need to be an expert in everything, but you'll need to know enough to be dangerous and coordinate effectively.

Technical Competencies

• Skill: Cloud Adoption Frameworks (CAF)
• Desc: You'll need a solid grasp of the core principles behind major cloud providers' frameworks (like AWS CAF or Azure CAF). This means understanding the different 'pillars' or 'perspectives' – things like Business, People, Governance, and Platform – and how they guide a migration. You won't be writing the strategy, but you'll need to understand the 'why' behind the steps.
• Level: Intermediate
• Skill: The 6 R's of Migration Strategy
• Desc: This is about knowing the different ways we can move an application to the cloud: Rehost (lift and shift), Replatform, Repurchase, Refactor/Rearchitect, Retire, or Retain. You should be able to understand which 'R' is being applied to an application and what that means for the migration plan.
• Level: Intermediate
• Skill: Wave/Move Group Planning
• Desc: You'll be working with these. This is the practice of bundling applications and infrastructure into logical migration groups based on dependencies, business impact, and technical complexity. You'll need to understand why certain applications are grouped together and track the progress of your assigned group.
• Level: Intermediate
• Skill: Application Dependency Mapping (ADM)
• Desc: While you might not be doing the deep technical mapping yourself, you'll need to understand the *process* of uncovering and documenting all upstream and downstream dependencies for an application (data, network, service calls). You'll be chasing people for this information and making sure it's recorded.
• Level: Intermediate
• Skill: ITIL/ITSM Principles (Change Management)
• Desc: You'll be involved in formal Change Management processes. This means understanding how to submit change requests, what information is needed, and why we follow these steps to ensure smooth transitions and operational readiness during and after migration.
• Level: Intermediate
• Skill: Cloud Economics (Basic)
• Desc: You don't need to build a full TCO model, but you should understand the basic concepts of cloud costs, like instance types, storage costs, and how moving to the cloud changes capital expenditure to operational expenditure. You'll often be tracking costs against a budget for your move group.
• Level: Basic

Digital Tools

• Tool: Jira & Confluence
• Level: Intermediate
• Usage: You'll be living in Jira, creating and updating tickets, managing Kanban boards for your move group, and running basic JQL queries to track progress. In Confluence, you'll be editing pages, updating runbooks from templates, and ensuring documentation is current.
• Tool: AWS/Azure/GCP Console (one primary, basic familiarity with others)
• Level: Intermediate
• Usage: You'll need to navigate the console of our primary cloud provider (e.g., AWS) to check the status of migrated services (EC2, S3, VMs, Blob storage), confirm basic configurations, and interpret simple monitoring dashboards. Basic understanding of the others is helpful.
• Tool: Cloudamize / Flexera One (or similar discovery tool)
• Level: Intermediate
• Usage: You'll be running pre-configured reports from these tools to get server inventories and basic dependency data. You might even help troubleshoot minor agent issues or export data for analysis by other teams.
• Tool: CloudHealth / Cloudability (or similar cost management tool)
• Level: Basic
• Usage: You'll view and navigate pre-built dashboards to track spend against budget for your specific migration wave. You'll flag any unexpected cost spikes to your Senior Coordinator.
• Tool: Slack / MS Teams
• Level: Advanced
• Usage: This is your primary communication hub. You'll be an active participant in project channels, providing clear status updates, setting up ad-hoc calls, and using integrations for automated notifications.
• Tool: Microsoft Office Suite (Excel, PowerPoint, Word)
• Level: Advanced
• Usage: You'll be using Excel for tracking, PowerPoint for status updates (often from templates), and Word for drafting communications or detailed documentation. Strong formatting and data presentation skills are key.

Industry Knowledge

• Area: Cloud Computing Fundamentals
• Desc: You should understand the basic concepts of cloud computing: IaaS, PaaS, SaaS, elasticity, scalability, and the shared responsibility model. You don't need to be an architect, but you need to speak the language.
• Area: Data Centre Infrastructure (Basic)
• Desc: A basic understanding of how on-premise data centres work – servers, storage, networking, virtualisation – is really helpful. It helps you understand what we're moving *from*.
• Area: Agile Project Methodologies
• Desc: We run our migrations using Agile principles. You should understand concepts like sprints, stand-ups, backlogs, and how to work in an iterative fashion.

Regulatory Compliance Regulations

• Reg: GDPR (General Data Protection Regulation)
• Usage: Understand that data location and security are critical during migration. You'll need to know to flag any potential GDPR concerns to the Security and Legal teams if you spot them in a migration plan.
• Reg: ISO 27001 (Information Security Management)
• Usage: Recognise the importance of information security during all phases of migration. You'll ensure that security requirements (e.g., encryption, access controls) are tracked as part of your move group's tasks.

Essential Prerequisites

• At least 2 years of experience in an IT project coordination, technical support, or junior project management role, ideally within an infrastructure or operations team.
• Demonstrable experience working with project management tools like Jira or similar, including creating tasks, updating statuses, and running basic reports.
• A foundational understanding of cloud computing concepts (e.g., AWS Cloud Practitioner or Azure Fundamentals certification, or equivalent practical knowledge).
• Proven ability to communicate clearly and concisely, both in writing and verbally, with technical and non-technical audiences.
• Experience in tracking multiple tasks and dependencies, ideally in a fast-moving technical environment.

Career Pathway Context

These prerequisites mean you're not starting from zero. You've got a solid foundation in how IT projects work and a basic grasp of cloud. We're looking for someone who can hit the ground running on coordination, even if the specific migration tech is new to them.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: AI-Assisted Workflow Optimisation
• Why: AI is already here, and it's getting better at automating repetitive tasks. Coordinators who can effectively use AI tools to manage their workflows will be significantly more productive, freeing them up for more complex problem-solving and human interaction.
• Concepts: [{'concept_name': 'Prompt Engineering (Basic)', 'description': "Learning how to ask AI the right questions to get useful outputs, whether it's drafting an email or summarising a document."}, {'concept_name': 'AI for Data Analysis', 'description': 'Using AI to quickly analyse migration readiness data, spot trends, or identify potential issues in large datasets.'}, {'concept_name': 'AI for Communication', 'description': 'Leveraging AI to draft initial versions of status reports, meeting summaries, or stakeholder communications, saving significant time.'}, {'concept_name': 'Output Validation', 'description': "Understanding that AI can 'hallucinate' and developing a critical eye for reviewing AI-generated content to ensure accuracy and context."}]
• Prepare: This week: Experiment with ChatGPT or Claude to summarise technical documents or draft simple emails.
• This month: Identify one repetitive task in your current workflow and try to automate a part of it using an AI tool (e.g., summarising Jira comments).
• Month 2: Explore how AI can help you analyse migration readiness data more quickly, perhaps by identifying missing information.
• Month 3: Share your AI productivity wins and challenges with your team, helping others learn.
• QuickWin: Start using AI to draft your daily stand-up updates or to summarise long email threads. It’s an immediate time saver with minimal risk.
• Skill: Basic Cloud FinOps Understanding
• Why: As more workloads move to the cloud, managing costs becomes absolutely critical. Coordinators who understand the financial implications of migration decisions and can help track cloud spend will be invaluable. It's not just about moving; it's about moving smartly.
• Concepts: [{'concept_name': 'Cloud Cost Components', 'description': 'Understanding the different elements that contribute to cloud bills: compute, storage, networking, databases, etc.'}, {'concept_name': 'Reserved Instances / Savings Plans', 'description': "Knowing what these are and how they help reduce costs, even if you're not directly purchasing them."}, {'concept_name': 'Cost Optimisation Strategies (Basic)', 'description': "Awareness of concepts like right-sizing (making sure resources aren't too big) and identifying idle resources."}, {'concept_name': 'Budget Tracking', 'description': 'How to monitor cloud spend against an allocated budget and flag deviations.'}]
• Prepare: This week: Read an introductory article on Cloud FinOps principles.
• This month: Spend time exploring CloudHealth/Cloudability dashboards, understanding where costs are coming from for a migrated workload.
• Month 2: Ask your Senior Coordinator or a FinOps specialist how migration decisions impact our cloud bill.
• Month 3: Identify one potential cost-saving opportunity for a migrated application and discuss it with your team.
• QuickWin: Regularly check the cloud cost dashboard for your assigned move group and flag any unexpected spikes. It shows you're thinking beyond just 'getting it moved'.

Advancing Technical Skills

• Skill: Advanced Infrastructure as Code (IaC) Comprehension
• Why: More and more infrastructure is built using code (Terraform, Ansible). While you won't be writing it at this level, understanding how it works, how to read it, and how it impacts deployments will be crucial for troubleshooting and coordinating effectively.
• Concepts: [{'concept_name': 'IaC Principles', 'description': 'Understanding why we use code to define infrastructure and its benefits (consistency, speed).'}, {'concept_name': 'Reading Terraform/Ansible', 'description': "Being able to look at a basic configuration file and understand what resources it's creating or configuring."}, {'concept_name': 'Deployment Pipelines', 'description': 'Understanding the stages of an automated deployment pipeline and how IaC fits into it.'}, {'concept_name': 'State Management (Basic)', 'description': "Awareness of what a 'state file' is in IaC and why it's important."}]
• Prepare: This week: Ask an engineer to walk you through a simple Terraform file for creating a cloud server.
• This month: Find online tutorials or documentation on basic Terraform syntax and concepts.
• Month 2: Attend code review sessions (even if just to observe) for IaC deployments to see how it works in practice.
• Month 3: Volunteer to help document some of our standard IaC modules in Confluence, which will force you to understand them better.
• QuickWin: When a new environment is being built, ask to see the IaC code that defines it. Just looking at it will start to build your familiarity.
• Skill: Deep Dive into Cloud-Native Services
• Why: We're not just 'lifting and shifting' anymore; we're re-platforming and re-architecting applications to use cloud-native services. Understanding what these services do (e.g., serverless functions, managed databases) will help you coordinate more effectively and anticipate challenges.
• Concepts: [{'concept_name': 'Serverless Computing (e.g., AWS Lambda, Azure Functions)', 'description': "Understanding what serverless means and when it's used."}, {'concept_name': 'Containerisation (e.g., Docker, Kubernetes basics)', 'description': "Knowing what containers are and why they're important for cloud-native applications."}, {'concept_name': 'Managed Database Services (e.g., RDS, Azure SQL DB)', 'description': 'Understanding the benefits and considerations of using managed database services over self-hosted ones.'}, {'concept_name': 'Event-Driven Architectures', 'description': 'Basic awareness of how applications can communicate using events in the cloud.'}]
• Prepare: This week: Pick one cloud-native service (e.g., AWS Lambda) and read its basic documentation.
• This month: Find a simple online course or tutorial on a cloud-native concept like serverless or containers.
• Month 2: Ask an application team how they're planning to use cloud-native services for an upcoming migration.
• Month 3: Join a technical discussion about re-platforming an application, even if you just listen and ask clarifying questions.
• QuickWin: Whenever an application is being re-platformed, ask the technical lead to explain *which* cloud-native services they're using and *why*. You'll learn a lot just by asking.

Education Requirements

• Level: Minimum
• Req: A-levels (or equivalent vocational qualification like an NVQ Level 3/4 in IT) or a relevant apprenticeship.
• Alts: We're open to candidates with equivalent practical experience. If you've been working in IT coordination or support for 3-5 years and can show you've got the chops, we're interested. A degree isn't strictly necessary if you have the right experience.
• Level: Preferred
• Req: A degree in Computer Science, Information Technology, Project Management, or a related technical field.
• Alts: While a degree is great, we value real-world experience and demonstrable skills more. If you've got a strong portfolio of coordinating technical projects, that's just as good, if not better.

Experience Requirements

You'll need roughly 2-5 years of hands-on experience in a technical coordination, project support, or junior project management role. This should ideally include some exposure to infrastructure projects or, even better, cloud environments. We're looking for someone who's seen a few technical projects through from start to finish and understands the rhythm of delivery. Experience working with multiple technical teams and chasing dependencies is key.

Preferred Certifications

• Cert: AWS Certified Cloud Practitioner or Azure Fundamentals
• Prod: Amazon Web Services / Microsoft Azure
• Usage: These show you have a foundational understanding of cloud concepts, which is really helpful for hitting the ground running. It tells us you've got the basics down.
• Cert: CompTIA Project+
• Prod: CompTIA
• Usage: Demonstrates a solid understanding of project management principles, which is directly applicable to coordinating migration waves, even if it's not cloud-specific.
• Cert: ITIL Foundation
• Prod: AXELOS
• Usage: Shows you understand IT Service Management best practices, especially around change management and incident management, which are critical during migrations.

Recommended Activities

• Regularly engage with cloud provider documentation and blogs (AWS, Azure, GCP) to stay up-to-date on new services and best practices.
• Participate in online courses or webinars focused on cloud migration strategies or project coordination techniques.
• Join relevant industry forums or communities to learn from peers and share experiences.
• Seek out opportunities to shadow more senior coordinators or engineers during complex migration activities.

Career Progression Pathways

Entry Paths to This Role

• Path: IT Support / Helpdesk Specialist
• Time: 2-3 years
• Path: Junior Project Coordinator / PMO Analyst
• Time: 1-2 years
• Path: Technical Administrator / Operations Analyst
• Time: 2-4 years

Career Progression From This Role

• Pathway: Senior Cloud Migration Coordinator (L3)
• Time: 3-5 years in current role

Long Term Vision Potential Roles

• Title: Lead Cloud Migration Coordinator (L4)
• Time: 5-8 years from current role
• Title: Cloud Migration Program Manager (L5)
• Time: 8-12 years from current role
• Title: Cloud Architect / Solutions Architect
• Time: 7-10 years from current 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.