{"id":75020,"date":"2026-04-16T10:01:35","date_gmt":"2026-04-16T10:01:35","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/senior-cloud-migration-specialist-role-blueprint-responsibilities-skills-kpis-and-career-path\/"},"modified":"2026-04-16T10:01:35","modified_gmt":"2026-04-16T10:01:35","slug":"senior-cloud-migration-specialist-role-blueprint-responsibilities-skills-kpis-and-career-path","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/senior-cloud-migration-specialist-role-blueprint-responsibilities-skills-kpis-and-career-path\/","title":{"rendered":"Senior Cloud Migration Specialist: Role Blueprint, Responsibilities, Skills, KPIs, and Career Path"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">1) Role Summary<\/h2>\n\n\n\n<p>The <strong>Senior Cloud Migration Specialist<\/strong> plans and executes the end-to-end migration of applications, data, and infrastructure from on\u2011premises or legacy hosting environments to public cloud and cloud-native platforms. This role combines hands-on engineering with migration strategy, risk management, and stakeholder leadership to deliver reliable cutovers while improving security posture, scalability, and cost efficiency.<\/p>\n\n\n\n<p>This role exists in software and IT organizations because cloud migration is not a one-time lift-and-shift task\u2014it requires portfolio assessment, dependency mapping, landing zone design, automation, wave planning, testing, cutover orchestration, and post-migration stabilization. The Senior Cloud Migration Specialist creates business value by accelerating cloud adoption, reducing operational risk, modernizing platforms, improving time-to-market, and enabling future platform capabilities (containers, managed services, DevSecOps, SRE practices).<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Role horizon:<\/strong> Current (widely established expectations and proven methods exist today)<\/li>\n<li><strong>Primary value created:<\/strong> Reduced migration risk and downtime, faster migration throughput, higher-quality outcomes (security, cost, performance), and repeatable migration patterns (\u201cmigration factory\u201d approach)<\/li>\n<li><strong>Typical interaction footprint:<\/strong> Cloud Platform\/Infrastructure, Application Engineering, Security, SRE\/Operations, Network, Database teams, Architecture, PMO\/Delivery, Finance\/FinOps, Vendor partners, and business application owners<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">2) Role Mission<\/h2>\n\n\n\n<p><strong>Core mission:<\/strong> Deliver safe, repeatable, and measurable migrations to cloud platforms by combining deep technical execution with rigorous planning, governance, and cross-functional coordination\u2014resulting in stable production workloads and modernized operational practices.<\/p>\n\n\n\n<p><strong>Strategic importance to the company:<\/strong>\n&#8211; Cloud migration is often foundational to broader objectives: product scalability, global availability, cost optimization, M&amp;A integration, data platform modernization, disaster recovery uplift, and compliance improvements.\n&#8211; Migration outcomes directly influence customer experience (availability and performance), engineering throughput, and infrastructure cost base.\n&#8211; Migration decisions (rehost vs replatform vs refactor) shape the long-term architecture, operational model, and cloud spend.<\/p>\n\n\n\n<p><strong>Primary business outcomes expected:<\/strong>\n&#8211; Successful migration of targeted workloads within agreed timelines and risk thresholds\n&#8211; Reduction of technical debt and operational toil through standard patterns and automation\n&#8211; Improved security\/compliance posture through standardized controls (IAM, logging, encryption, network segmentation)\n&#8211; Increased platform reliability via well-tested cutovers, rollback plans, and stabilization processes\n&#8211; Transparent reporting of progress, risks, dependencies, and cost implications<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3) Core Responsibilities<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Strategic responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Define workload migration approach per application<\/strong> (rehost, replatform, refactor, retire, retain) aligned to business criticality, constraints, and ROI.<\/li>\n<li><strong>Establish and evolve migration factory patterns<\/strong> (templates, runbooks, golden paths, automation modules) to increase throughput and consistency.<\/li>\n<li><strong>Contribute to cloud adoption roadmap<\/strong> by identifying sequencing opportunities (quick wins, foundational capabilities, dependency-driven waves).<\/li>\n<li><strong>Drive technical risk management<\/strong> for migration scope (downtime windows, data integrity, security controls, identity integration, DR readiness).<\/li>\n<li><strong>Advise on target-state architecture tradeoffs<\/strong> (managed services vs self-managed, containerization, network topology, identity model).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Operational responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"6\">\n<li><strong>Run migration waves end-to-end<\/strong>: discovery \u2192 planning \u2192 build \u2192 test \u2192 cutover \u2192 stabilize \u2192 decommission.<\/li>\n<li><strong>Coordinate cutover planning<\/strong> including change windows, stakeholder communications, go\/no-go criteria, rollback procedures, and on-call coverage.<\/li>\n<li><strong>Manage migration work intake and prioritization<\/strong> with delivery partners (PMO, product owners, platform teams) based on readiness and dependencies.<\/li>\n<li><strong>Ensure post-migration stabilization<\/strong> with defined success criteria, monitoring baselines, SLO alignment, and operational handover.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Technical responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"10\">\n<li><strong>Perform environment discovery and dependency mapping<\/strong> (network flows, identity dependencies, storage, database links, external integrations).<\/li>\n<li><strong>Design and implement migration landing zone components<\/strong> in collaboration with cloud platform teams (accounts\/subscriptions, IAM, network, logging, policies).<\/li>\n<li><strong>Build migration automation and IaC<\/strong> (Terraform\/CloudFormation\/Bicep, CI\/CD pipelines, configuration management).<\/li>\n<li><strong>Execute compute and data migration<\/strong> using appropriate tools (image-based migration, containerization, DB replication, file transfer, messaging rehydration).<\/li>\n<li><strong>Plan and validate performance<\/strong> (load testing, capacity sizing, autoscaling, caching, database tuning) to meet production requirements.<\/li>\n<li><strong>Implement reliability patterns<\/strong> (backup\/restore, DR replication, multi-AZ\/region design as required, health checks, automated rollback mechanisms).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Cross-functional or stakeholder responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"16\">\n<li><strong>Partner with application owners and engineering teams<\/strong> to remediate blockers (OS compatibility, library versions, certificates, secrets, hard-coded endpoints).<\/li>\n<li><strong>Align with Security\/Compliance<\/strong> on threat modeling, IAM, encryption, key management, vulnerability remediation, audit evidence.<\/li>\n<li><strong>Collaborate with FinOps\/Finance<\/strong> to forecast cloud spend, track cost variance, and optimize post-migration cost controls.<\/li>\n<li><strong>Manage vendors or migration partners<\/strong> when used: scope clarity, acceptance criteria, quality checks, and knowledge transfer.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Governance, compliance, or quality responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"20\">\n<li><strong>Maintain migration governance artifacts<\/strong>: risk logs, decision records (ADRs), architecture reviews, test evidence, and change approvals.<\/li>\n<li><strong>Enforce quality gates<\/strong> (readiness checklists, test coverage thresholds, security baselines, observability requirements).<\/li>\n<li><strong>Ensure decommissioning and data hygiene<\/strong>: shut down legacy resources, update CMDB, revoke unused access, finalize retention policies.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Leadership responsibilities (Senior IC scope)<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"23\">\n<li><strong>Mentor engineers and peers<\/strong> on migration tooling, patterns, and operational readiness (without direct people management by default).<\/li>\n<li><strong>Lead technical workshops<\/strong> (app readiness, cutover rehearsals, incident game-days) and act as escalation point for complex migrations.<\/li>\n<li><strong>Influence standards<\/strong> across Cloud &amp; Infrastructure by proposing improvements to landing zones, golden paths, and migration playbooks.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">4) Day-to-Day Activities<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Daily activities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Review migration pipeline status (work items, blockers, readiness gates) and adjust sequencing as dependencies shift.<\/li>\n<li>Troubleshoot migration issues: connectivity, DNS, IAM policies, replication lag, performance regressions, configuration drift.<\/li>\n<li>Pair with app teams on remediation tasks: secret management, config externalization, certificate rotation, endpoint updates.<\/li>\n<li>Update artifacts: runbooks, checklists, dependency maps, risk registers, cutover steps, rollback plans.<\/li>\n<li>Validate IaC changes via CI pipelines; review merge requests and ensure policy compliance (tagging, guardrails, network controls).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Weekly activities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Run migration wave planning sessions (scope confirmation, readiness review, dependency alignment).<\/li>\n<li>Attend architecture\/security review boards for upcoming migrations; capture actions and decisions in ADRs.<\/li>\n<li>Execute rehearsal activities: cutover dry-runs, data reconciliation tests, failover drills.<\/li>\n<li>Share progress dashboards with stakeholders: migrated workloads, burn-down, risks, change calendar impacts.<\/li>\n<li>Conduct post-migration retrospectives focused on repeatability and automation opportunities.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monthly or quarterly activities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Refresh application portfolio segmentation and migration factory throughput metrics (cycle time, success rate, defect rates).<\/li>\n<li>Contribute to quarterly cloud roadmap: foundational improvements, migration acceleration initiatives, platform enhancements.<\/li>\n<li>Perform cost and performance reviews for newly migrated workloads; drive optimization backlog (reserved instances\/savings plans, storage tiering, managed service tuning).<\/li>\n<li>Lead resilience and compliance checkpoints: DR plan validation, audit evidence reviews, security posture reporting.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Recurring meetings or rituals<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migration standup (daily or 3x\/week depending on volume)<\/li>\n<li>Wave readiness review \/ go-no-go meeting (per migration)<\/li>\n<li>Change Advisory Board (CAB) \/ change management sync (weekly in regulated environments)<\/li>\n<li>Architecture review (weekly\/biweekly)<\/li>\n<li>Ops\/SRE handover or service transition meeting (per workload)<\/li>\n<li>FinOps review (monthly)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Incident, escalation, or emergency work (as relevant)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Participate in cutover weekend\/on-call rotations during critical migrations.<\/li>\n<li>Lead rapid rollback decisions when success criteria are not met (based on pre-defined go\/no-go gates).<\/li>\n<li>Support P1\/P2 incidents related to migrated workloads: misconfigured routing, IAM regression, scaling issues, data inconsistency.<\/li>\n<li>Run post-incident reviews (PIRs) and implement corrective actions in templates\/runbooks to prevent recurrence.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5) Key Deliverables<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Migration strategy per workload<\/strong> (approach selection, rationale, constraints, required platform capabilities)<\/li>\n<li><strong>Application\/workload assessment reports<\/strong> (readiness score, dependency map, risk and remediation backlog)<\/li>\n<li><strong>Migration wave plan<\/strong> (sequence, prerequisites, timelines, resource plan, change windows)<\/li>\n<li><strong>Cutover plan and rollback plan<\/strong> (step-by-step actions, owners, timing, verification tests, go\/no-go criteria)<\/li>\n<li><strong>Landing zone integration requirements<\/strong> (accounts\/subscriptions, network, IAM, logging, policy, tagging, key management)<\/li>\n<li><strong>Infrastructure as Code modules<\/strong> for repeatable migrations (network patterns, compute baselines, security controls)<\/li>\n<li><strong>Automation scripts and pipelines<\/strong> for provisioning, configuration, and migration execution<\/li>\n<li><strong>Data migration design and validation artifacts<\/strong> (replication approach, reconciliation checks, integrity validation)<\/li>\n<li><strong>Observability baseline<\/strong> (dashboards, alerts, log routing, SLO\/SLA alignment)<\/li>\n<li><strong>Operational runbooks<\/strong> (steady-state ops, incident response, backup\/restore, patching, scaling)<\/li>\n<li><strong>Service transition \/ handover package<\/strong> to operations\/SRE (ownership, support model, escalation paths, known risks)<\/li>\n<li><strong>Decommission plan<\/strong> for legacy environments (shutdown checklist, CMDB updates, access revocation, cost confirmation)<\/li>\n<li><strong>Migration progress dashboard and executive status report<\/strong> (throughput, risks, cost, quality, forecast)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6) Goals, Objectives, and Milestones<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">30-day goals (onboarding and baseline establishment)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Understand current cloud strategy, landing zone standards, and migration governance model.<\/li>\n<li>Review active migration pipeline and identify top blockers (network, identity, tooling, environment gaps).<\/li>\n<li>Deliver at least one end-to-end workload assessment and propose a migration approach with risks and remediation plan.<\/li>\n<li>Gain access, credentials, and working proficiency in the organization\u2019s IaC, CI\/CD, and observability stack.<\/li>\n<li>Build trust with key stakeholders (platform, security, app owners, PMO).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">60-day goals (execution and repeatability)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Lead at least one medium-complexity migration wave (or multiple smaller workloads) through cutover and stabilization.<\/li>\n<li>Produce standardized templates\/checklists for readiness, cutover, rollback, and handover.<\/li>\n<li>Improve at least one migration factory metric (e.g., reduce cycle time by standardizing a common step).<\/li>\n<li>Validate operational readiness for migrated workloads (monitoring, alerts, runbooks, on-call).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">90-day goals (scaling impact)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Consistently deliver migrations with predictable timelines and quality gates.<\/li>\n<li>Implement automation or IaC improvements that reduce manual effort across migrations (e.g., standardized IAM roles, network patterns, pipeline stages).<\/li>\n<li>Establish migration reporting cadence and dashboards used by leadership (progress, risk, throughput, quality).<\/li>\n<li>Reduce incident rates or cutover failures by improving rehearsals and verification tests.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6-month milestones<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Demonstrate measurable throughput increase (e.g., more workloads migrated per quarter with equal or lower incident rates).<\/li>\n<li>Mature governance artifacts: ADR library, standard risk controls, documented patterns for common workload types.<\/li>\n<li>Partner with Security and FinOps to embed controls into templates (policy-as-code, tagging, encryption defaults, budget alerts).<\/li>\n<li>Institutionalize post-migration stabilization and decommissioning steps to capture savings and reduce operational complexity.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12-month objectives<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Become a recognized migration authority: lead the complex migrations (high availability, regulated, high transaction volumes).<\/li>\n<li>Establish or significantly enhance the organization\u2019s migration factory capability (playbooks, automation, standard architectures).<\/li>\n<li>Improve cloud cost posture for migrated workloads (reduce waste, improve rightsizing, align service tiers).<\/li>\n<li>Strengthen reliability and resilience: measurable improvement in availability\/SLO compliance for migrated services.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Long-term impact goals (beyond 12 months)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Drive modernization beyond migration: enable refactoring and platform engineering adoption through paved-road solutions.<\/li>\n<li>Reduce technical debt in legacy environments and simplify operations via standardized cloud operating model.<\/li>\n<li>Raise organizational capability: coaching, documentation, patterns, and training that enable other teams to migrate safely.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Role success definition<\/h3>\n\n\n\n<p>A successful Senior Cloud Migration Specialist consistently delivers migrations that are <strong>on-time, low-downtime, secure, cost-aware, operationally ready<\/strong>, and <strong>repeatable<\/strong> through patterns and automation\u2014without creating new long-term fragility.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What high performance looks like<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Predictable migration execution with minimal escalations and strong stakeholder confidence<\/li>\n<li>Fewer defects and post-cutover incidents due to strong testing and rehearsal discipline<\/li>\n<li>High reuse of templates and automation; measurable reduction in manual steps<\/li>\n<li>Strong risk management: no surprises, clear decision records, timely escalation<\/li>\n<li>Positive operations handover: clear runbooks, monitoring, and ownership boundaries<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">7) KPIs and Productivity Metrics<\/h2>\n\n\n\n<p>The metrics below are designed for enterprise migration programs and can be tailored to workload criticality and regulatory requirements.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Metric name<\/th>\n<th>What it measures<\/th>\n<th>Why it matters<\/th>\n<th>Example target\/benchmark<\/th>\n<th>Frequency<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Workloads migrated (count)<\/td>\n<td>Number of workloads moved to cloud and accepted into steady-state<\/td>\n<td>Core throughput indicator<\/td>\n<td>3\u201310 workloads\/month depending on complexity<\/td>\n<td>Weekly\/Monthly<\/td>\n<\/tr>\n<tr>\n<td>Migration cycle time<\/td>\n<td>Time from readiness start to production cutover and acceptance<\/td>\n<td>Predictability and program efficiency<\/td>\n<td>Reduce by 15\u201330% over 2\u20133 quarters<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Wave plan adherence (%)<\/td>\n<td>Planned vs actual dates and scope<\/td>\n<td>Planning accuracy and dependency management<\/td>\n<td>\u2265 85% adherence<\/td>\n<td>Per wave\/Monthly<\/td>\n<\/tr>\n<tr>\n<td>Cutover success rate<\/td>\n<td>% cutovers completed without rollback<\/td>\n<td>Quality of rehearsals and execution<\/td>\n<td>\u2265 95% success for medium complexity<\/td>\n<td>Per wave<\/td>\n<\/tr>\n<tr>\n<td>Rollback rate<\/td>\n<td>% migrations requiring rollback<\/td>\n<td>Stability and risk control<\/td>\n<td>\u2264 5% (context-dependent)<\/td>\n<td>Per wave\/Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Downtime minutes per cutover<\/td>\n<td>Total planned + unplanned downtime<\/td>\n<td>Customer and business impact<\/td>\n<td>Within approved window; unplanned near zero<\/td>\n<td>Per cutover<\/td>\n<\/tr>\n<tr>\n<td>Sev1\/Sev2 incidents post-migration<\/td>\n<td>Production incidents attributable to migration changes<\/td>\n<td>Stabilization effectiveness<\/td>\n<td>0\u20131 Sev2 per workload in first 30 days<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Defect leakage<\/td>\n<td>Issues found in production vs pre-prod testing<\/td>\n<td>Test quality and readiness gates<\/td>\n<td>\u2265 80% of issues caught pre-prod<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Automation coverage (%)<\/td>\n<td>% migration steps automated (provisioning, config, validation)<\/td>\n<td>Scalability and reduced human error<\/td>\n<td>+10\u201320% improvement per quarter until plateau<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>IaC compliance rate<\/td>\n<td>% infrastructure created via approved IaC modules<\/td>\n<td>Governance and auditability<\/td>\n<td>\u2265 90\u201395%<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Security baseline compliance<\/td>\n<td>% workloads meeting required controls (encryption, logging, IAM)<\/td>\n<td>Risk reduction and audit readiness<\/td>\n<td>\u2265 95\u2013100% for critical workloads<\/td>\n<td>Per wave\/Monthly<\/td>\n<\/tr>\n<tr>\n<td>Policy violations<\/td>\n<td>Guardrail breaches (tagging, public exposure, IAM over-permission)<\/td>\n<td>Prevents misconfigurations and cost risk<\/td>\n<td>Downward trend; critical violations = 0<\/td>\n<td>Weekly\/Monthly<\/td>\n<\/tr>\n<tr>\n<td>Data reconciliation pass rate<\/td>\n<td>% migrations passing integrity checks<\/td>\n<td>Prevents data loss\/corruption<\/td>\n<td>100% for critical datasets<\/td>\n<td>Per migration<\/td>\n<\/tr>\n<tr>\n<td>Cost variance vs forecast<\/td>\n<td>Actual cloud spend vs migration forecast<\/td>\n<td>Financial control and trust<\/td>\n<td>Within \u00b110\u201315% after stabilization<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Unit cost improvement<\/td>\n<td>Cost per transaction\/user\/workload vs baseline<\/td>\n<td>Business case realization<\/td>\n<td>5\u201320% improvement (varies)<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Decommission completion rate<\/td>\n<td>% legacy resources shut down post-migration<\/td>\n<td>Captures savings and reduces attack surface<\/td>\n<td>\u2265 90% within 60\u201390 days<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Stakeholder satisfaction<\/td>\n<td>Feedback score from app owners, ops, security<\/td>\n<td>Collaboration effectiveness<\/td>\n<td>\u2265 4.2\/5 average<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Knowledge transfer completion<\/td>\n<td>Handover checklist completion and ops readiness<\/td>\n<td>Operational continuity<\/td>\n<td>100% before service transition<\/td>\n<td>Per workload<\/td>\n<\/tr>\n<tr>\n<td>Mentoring impact (Senior IC)<\/td>\n<td>Sessions delivered, adoption of patterns<\/td>\n<td>Capability building<\/td>\n<td>1\u20132 enablement sessions\/month<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">8) Technical Skills Required<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Must-have technical skills<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Public cloud fundamentals (AWS\/Azure\/GCP)<\/strong> <\/li>\n<li><em>Use:<\/em> Design target environments, services selection, troubleshoot cloud-native issues  <\/li>\n<li><em>Importance:<\/em> <strong>Critical<\/strong><\/li>\n<li><strong>Cloud migration strategies (6Rs \/ 7Rs)<\/strong> <\/li>\n<li><em>Use:<\/em> Choose correct approach and sequence; justify decisions to stakeholders  <\/li>\n<li><em>Importance:<\/em> <strong>Critical<\/strong><\/li>\n<li><strong>Networking for migrations (VPC\/VNet, routing, DNS, VPN\/Direct Connect\/ExpressRoute)<\/strong> <\/li>\n<li><em>Use:<\/em> Ensure connectivity, hybrid integration, and cutover routing  <\/li>\n<li><em>Importance:<\/em> <strong>Critical<\/strong><\/li>\n<li><strong>Identity and access management (IAM\/RBAC, federation, least privilege)<\/strong> <\/li>\n<li><em>Use:<\/em> Secure workload access, service accounts, cross-account access patterns  <\/li>\n<li><em>Importance:<\/em> <strong>Critical<\/strong><\/li>\n<li><strong>Infrastructure as Code (Terraform common; CloudFormation\/Bicep context-specific)<\/strong> <\/li>\n<li><em>Use:<\/em> Repeatable landing zone integration, workload provisioning, compliance  <\/li>\n<li><em>Importance:<\/em> <strong>Critical<\/strong><\/li>\n<li><strong>Linux\/Windows server administration<\/strong> <\/li>\n<li><em>Use:<\/em> Source environment validation, agent installs, OS tuning, patching approach  <\/li>\n<li><em>Importance:<\/em> <strong>Important<\/strong><\/li>\n<li><strong>Observability basics (logs, metrics, traces; dashboards and alerting)<\/strong> <\/li>\n<li><em>Use:<\/em> Define post-migration readiness and detect regressions  <\/li>\n<li><em>Importance:<\/em> <strong>Important<\/strong><\/li>\n<li><strong>Data migration fundamentals (backup\/restore, replication, consistency models)<\/strong> <\/li>\n<li><em>Use:<\/em> Migrate databases and stateful systems safely  <\/li>\n<li><em>Importance:<\/em> <strong>Important<\/strong><\/li>\n<li><strong>Security baseline controls (encryption, key management, vulnerability mgmt)<\/strong> <\/li>\n<li><em>Use:<\/em> Meet security\/compliance requirements and audit expectations  <\/li>\n<li><em>Importance:<\/em> <strong>Important<\/strong><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Good-to-have technical skills<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Containers and orchestration (Docker, Kubernetes, EKS\/AKS\/GKE)<\/strong> <\/li>\n<li><em>Use:<\/em> Replatforming to containers; standardization of runtime environments  <\/li>\n<li><em>Importance:<\/em> <strong>Optional<\/strong> (depends on strategy)<\/li>\n<li><strong>CI\/CD pipeline engineering (GitHub Actions\/GitLab\/Jenkins\/Azure DevOps)<\/strong> <\/li>\n<li><em>Use:<\/em> Automate infrastructure provisioning and validation gates  <\/li>\n<li><em>Importance:<\/em> <strong>Important<\/strong><\/li>\n<li><strong>Configuration management (Ansible\/Chef\/Puppet)<\/strong> <\/li>\n<li><em>Use:<\/em> Standardize host configuration and drift prevention  <\/li>\n<li><em>Importance:<\/em> <strong>Optional<\/strong><\/li>\n<li><strong>Database platform skills (PostgreSQL, MySQL, SQL Server, Oracle)<\/strong> <\/li>\n<li><em>Use:<\/em> Migration planning, performance tuning, replication strategy  <\/li>\n<li><em>Importance:<\/em> <strong>Important<\/strong><\/li>\n<li><strong>Load testing\/performance engineering basics<\/strong> <\/li>\n<li><em>Use:<\/em> Validate capacity and identify performance regressions  <\/li>\n<li><em>Importance:<\/em> <strong>Optional<\/strong><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Advanced or expert-level technical skills<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Complex hybrid connectivity and segmentation<\/strong> (transit gateways, hub-spoke, shared services)  <\/li>\n<li><em>Use:<\/em> Large-scale enterprise migrations; multi-account\/subscription designs  <\/li>\n<li><em>Importance:<\/em> <strong>Critical<\/strong> in enterprise contexts<\/li>\n<li><strong>Resilience engineering and DR design<\/strong> (RTO\/RPO, multi-region, failover testing)  <\/li>\n<li><em>Use:<\/em> Business-critical workloads requiring strong continuity controls  <\/li>\n<li><em>Importance:<\/em> <strong>Important\/Critical<\/strong> (workload-dependent)<\/li>\n<li><strong>Cloud cost engineering (FinOps practices, rightsizing, commitment strategies)<\/strong> <\/li>\n<li><em>Use:<\/em> Prevent cost overruns and improve unit economics post-migration  <\/li>\n<li><em>Importance:<\/em> <strong>Important<\/strong><\/li>\n<li><strong>Policy-as-code and compliance automation<\/strong> (e.g., AWS Config, Azure Policy, OPA)  <\/li>\n<li><em>Use:<\/em> Enforce guardrails and reduce audit burden  <\/li>\n<li><em>Importance:<\/em> <strong>Important<\/strong><\/li>\n<li><strong>Large-scale automation patterns<\/strong> (pipelines, golden images, platform modules)  <\/li>\n<li><em>Use:<\/em> Increase throughput; reduce manual error at scale  <\/li>\n<li><em>Importance:<\/em> <strong>Critical<\/strong> for senior performance<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Emerging future skills for this role (next 2\u20135 years)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Platform engineering \u201cpaved road\u201d design<\/strong> <\/li>\n<li><em>Use:<\/em> Turn migration outcomes into durable internal platforms  <\/li>\n<li><em>Importance:<\/em> <strong>Important<\/strong><\/li>\n<li><strong>Software supply chain security<\/strong> (SBOMs, artifact signing, provenance)  <\/li>\n<li><em>Use:<\/em> Strengthen security posture as workloads modernize  <\/li>\n<li><em>Importance:<\/em> <strong>Optional\/Important<\/strong> (industry-dependent)<\/li>\n<li><strong>AI-assisted operations and migration automation<\/strong> <\/li>\n<li><em>Use:<\/em> Faster assessments, better troubleshooting, automated documentation  <\/li>\n<li><em>Importance:<\/em> <strong>Important<\/strong><\/li>\n<li><strong>Multi-cloud governance and portability patterns<\/strong> <\/li>\n<li><em>Use:<\/em> M&amp;A, regional constraints, vendor risk strategies  <\/li>\n<li><em>Importance:<\/em> <strong>Optional<\/strong> (strategy-dependent)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">9) Soft Skills and Behavioral Capabilities<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Structured problem solving<\/strong> <\/li>\n<li><em>Why it matters:<\/em> Migrations fail due to hidden dependencies and emergent issues under time pressure.  <\/li>\n<li><em>How it shows up:<\/em> Rapid isolation of root causes (network\/DNS\/IAM\/latency), clear hypotheses, controlled experiments.  <\/li>\n<li>\n<p><em>Strong performance looks like:<\/em> Solves ambiguous incidents with minimal disruption; documents learnings into runbooks.<\/p>\n<\/li>\n<li>\n<p><strong>Stakeholder management and influence without authority<\/strong> <\/p>\n<\/li>\n<li><em>Why it matters:<\/em> App owners, security, network, and ops teams have competing priorities.  <\/li>\n<li><em>How it shows up:<\/em> Aligns on readiness gates, negotiates cutover windows, secures commitment for remediation work.  <\/li>\n<li>\n<p><em>Strong performance looks like:<\/em> Stakeholders proactively seek guidance; fewer last-minute escalations.<\/p>\n<\/li>\n<li>\n<p><strong>Risk management discipline<\/strong> <\/p>\n<\/li>\n<li><em>Why it matters:<\/em> Migration risk is business risk (downtime, data loss, audit gaps).  <\/li>\n<li><em>How it shows up:<\/em> Maintains risk logs, defines go\/no-go criteria, ensures rollback realism, escalates early.  <\/li>\n<li>\n<p><em>Strong performance looks like:<\/em> No \u201csurprise\u201d failures; leadership trusts status reports.<\/p>\n<\/li>\n<li>\n<p><strong>Clear technical communication<\/strong> <\/p>\n<\/li>\n<li><em>Why it matters:<\/em> Migration status must be consumable by both engineers and executives.  <\/li>\n<li><em>How it shows up:<\/em> Crisp cutover plans, readable diagrams, concise status reporting, actionable incident updates.  <\/li>\n<li>\n<p><em>Strong performance looks like:<\/em> Decisions are made faster because information is clear and complete.<\/p>\n<\/li>\n<li>\n<p><strong>Planning and operational rigor<\/strong> <\/p>\n<\/li>\n<li><em>Why it matters:<\/em> Cutovers succeed through preparation and repetition, not heroics.  <\/li>\n<li><em>How it shows up:<\/em> Checklists, rehearsals, change coordination, evidence capture, handover packages.  <\/li>\n<li>\n<p><em>Strong performance looks like:<\/em> Predictable outcomes and reduced toil across waves.<\/p>\n<\/li>\n<li>\n<p><strong>Coaching and enablement (Senior IC expectation)<\/strong> <\/p>\n<\/li>\n<li><em>Why it matters:<\/em> Migration programs scale when others can repeat the patterns.  <\/li>\n<li><em>How it shows up:<\/em> Workshops, templates, pairing, code reviews for IaC, runbook reviews.  <\/li>\n<li>\n<p><em>Strong performance looks like:<\/em> Teams adopt standards voluntarily; migration throughput increases.<\/p>\n<\/li>\n<li>\n<p><strong>Resilience under pressure<\/strong> <\/p>\n<\/li>\n<li><em>Why it matters:<\/em> Cutover weekends and incidents are high-stakes and time-bound.  <\/li>\n<li><em>How it shows up:<\/em> Maintains calm during outages, communicates clearly, avoids untested changes.  <\/li>\n<li>\n<p><em>Strong performance looks like:<\/em> Faster recovery, fewer compounding errors.<\/p>\n<\/li>\n<li>\n<p><strong>Customer\/service mindset<\/strong> <\/p>\n<\/li>\n<li><em>Why it matters:<\/em> Internal users (app teams, ops) rely on migration quality and supportability.  <\/li>\n<li><em>How it shows up:<\/em> Designs for operability; validates monitoring and runbooks; ensures clean handoffs.  <\/li>\n<li><em>Strong performance looks like:<\/em> Operations teams accept ownership confidently; fewer repeat tickets.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">10) Tools, Platforms, and Software<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Category<\/th>\n<th>Tool \/ platform<\/th>\n<th>Primary use<\/th>\n<th>Commonality<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Cloud platforms<\/td>\n<td>AWS \/ Microsoft Azure \/ Google Cloud<\/td>\n<td>Target hosting platform and managed services<\/td>\n<td>Common (at least one)<\/td>\n<\/tr>\n<tr>\n<td>Cloud migration (compute)<\/td>\n<td>AWS Application Migration Service (MGN)<\/td>\n<td>Lift-and-shift server migration<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Cloud migration (compute)<\/td>\n<td>Azure Migrate<\/td>\n<td>Discovery and migration to Azure<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Cloud migration (compute)<\/td>\n<td>Google Migrate to VMs<\/td>\n<td>VM migration to GCP<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Cloud migration (DB)<\/td>\n<td>AWS Database Migration Service (DMS)<\/td>\n<td>Replication and database migration<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Cloud migration (DB)<\/td>\n<td>Azure Database Migration Service<\/td>\n<td>Database migration to Azure<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Data transfer<\/td>\n<td>AWS DataSync \/ Azure Data Box \/ rsync<\/td>\n<td>File\/object transfer at scale<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>IaC<\/td>\n<td>Terraform<\/td>\n<td>Provision cloud resources, reusable modules<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>IaC<\/td>\n<td>CloudFormation \/ Bicep (ARM)<\/td>\n<td>Provider-native IaC<\/td>\n<td>Optional \/ Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Config management<\/td>\n<td>Ansible<\/td>\n<td>Host config standardization and orchestration<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>CI\/CD<\/td>\n<td>GitHub Actions \/ GitLab CI \/ Jenkins \/ Azure DevOps<\/td>\n<td>Automated pipelines for infra + app changes<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Source control<\/td>\n<td>Git (GitHub\/GitLab\/Bitbucket)<\/td>\n<td>Version control for IaC, scripts, docs<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Containers<\/td>\n<td>Docker<\/td>\n<td>Packaging workloads, consistent runtime<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Orchestration<\/td>\n<td>Kubernetes (EKS\/AKS\/GKE)<\/td>\n<td>Container platform for replatforming<\/td>\n<td>Optional \/ Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Observability<\/td>\n<td>CloudWatch \/ Azure Monitor \/ GCP Operations<\/td>\n<td>Native logging\/metrics\/tracing<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Observability<\/td>\n<td>Prometheus + Grafana<\/td>\n<td>Metrics and dashboards (often Kubernetes)<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Observability<\/td>\n<td>Datadog \/ New Relic<\/td>\n<td>APM and infra monitoring<\/td>\n<td>Optional \/ Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Security posture<\/td>\n<td>AWS Security Hub \/ Azure Defender \/ CSPM tools<\/td>\n<td>Baseline security visibility<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Secrets management<\/td>\n<td>AWS Secrets Manager \/ Azure Key Vault \/ HashiCorp Vault<\/td>\n<td>Store and rotate secrets<\/td>\n<td>Common (one)<\/td>\n<\/tr>\n<tr>\n<td>Vulnerability mgmt<\/td>\n<td>Trivy \/ Snyk \/ Qualys \/ Defender scanners<\/td>\n<td>Scan images\/hosts and track vulnerabilities<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>ITSM<\/td>\n<td>ServiceNow \/ Jira Service Management<\/td>\n<td>Change management, incident\/problem tickets<\/td>\n<td>Common in enterprise<\/td>\n<\/tr>\n<tr>\n<td>Collaboration<\/td>\n<td>Microsoft Teams \/ Slack<\/td>\n<td>Coordination during waves and cutovers<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Documentation<\/td>\n<td>Confluence \/ SharePoint<\/td>\n<td>Runbooks, plans, governance artifacts<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Project delivery<\/td>\n<td>Jira \/ Azure Boards<\/td>\n<td>Migration backlog, tracking, reporting<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Diagramming<\/td>\n<td>Lucidchart \/ draw.io<\/td>\n<td>Architecture and dependency diagrams<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Scripting<\/td>\n<td>Bash \/ PowerShell \/ Python<\/td>\n<td>Automation and glue scripting<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Testing<\/td>\n<td>JMeter \/ k6<\/td>\n<td>Load\/performance testing<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Identity<\/td>\n<td>Azure AD \/ Entra ID \/ Okta<\/td>\n<td>Federation\/SSO patterns for migrated apps<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">11) Typical Tech Stack \/ Environment<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Infrastructure environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hybrid source environments: on-prem VMware, bare metal, colocation, or legacy IaaS<\/li>\n<li>Target environments: one primary cloud (AWS or Azure most common), with multi-account\/subscription design<\/li>\n<li>Network patterns: hub-and-spoke, shared services VPC\/VNet, private connectivity (VPN\/Direct Connect\/ExpressRoute)<\/li>\n<li>Standard governance: tagging policies, centralized logging, guardrails, image baselines, patching standards<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Application environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Mix of monolith and microservices; common runtimes include Java\/.NET\/Node.js\/Python<\/li>\n<li>Legacy constraints: hard-coded IPs, older OS versions, local storage assumptions, manual deployments<\/li>\n<li>Target patterns: VM-based rehost, managed PaaS (App Service, ECS), container replatforming, or selective refactor<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Data environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Relational databases (PostgreSQL, MySQL, SQL Server, Oracle); caching layers (Redis)<\/li>\n<li>File systems and object storage; data replication tools for minimal downtime<\/li>\n<li>Data integrity and reconciliation requirements for critical systems<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Centralized IAM and federation; mandatory encryption at rest\/in transit<\/li>\n<li>Centralized log collection and retention; vulnerability scanning and security incident processes<\/li>\n<li>Policy-based controls for public exposure, allowed regions, and resource types (enterprise-dependent)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Delivery model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migration waves delivered via an enablement model (platform team + migration specialists + app teams)<\/li>\n<li>A migration program office (PMO) or portfolio lead may coordinate scope and stakeholder reporting<\/li>\n<li>Service transition to operations\/SRE teams after stabilization<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Agile or SDLC context<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Typically agile delivery (sprints) for remediation work, combined with milestone-based cutover scheduling<\/li>\n<li>Change management gates may exist (CAB) for production cutovers, especially in regulated environments<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scale or complexity context<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Portfolio ranges from dozens to thousands of workloads; this role typically handles complex or high-risk workloads and sets repeatable standards<\/li>\n<li>Complexity drivers: dependency coupling, data volume, performance sensitivity, compliance constraints, and DR requirements<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team topology<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reports into Cloud &amp; Infrastructure (often Cloud Platform Engineering or Cloud Transformation)<\/li>\n<li>Works in a matrix with application product teams, security, network, and operations<\/li>\n<li>Often acts as \u201ctechnical lead\u201d per migration wave without being a line manager<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">12) Stakeholders and Collaboration Map<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Internal stakeholders<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Head of Cloud &amp; Infrastructure \/ Cloud Platform Engineering Manager (typical manager):<\/strong> prioritization, standards, escalation path<\/li>\n<li><strong>Cloud Platform Engineers:<\/strong> landing zone capabilities, networking\/IAM patterns, shared services<\/li>\n<li><strong>Application Engineering Teams:<\/strong> remediation, deployment, configuration updates, validation testing<\/li>\n<li><strong>SRE \/ Operations \/ NOC:<\/strong> monitoring, on-call, incident response, service transition acceptance<\/li>\n<li><strong>Network Engineering:<\/strong> routing, firewall, proxy, DNS, private connectivity<\/li>\n<li><strong>Security \/ GRC:<\/strong> baseline controls, risk acceptance, audit evidence, threat modeling<\/li>\n<li><strong>Enterprise Architecture \/ Solution Architects:<\/strong> target-state alignment and design reviews<\/li>\n<li><strong>PMO \/ Delivery Leads:<\/strong> schedule governance, RAID logs, stakeholder reporting<\/li>\n<li><strong>FinOps \/ Finance:<\/strong> cost forecasting, showback\/chargeback, optimization governance<\/li>\n<li><strong>Data\/DBA Teams:<\/strong> replication approaches, schema changes, performance tuning<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">External stakeholders (as applicable)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud vendors (AWS\/Azure\/GCP) solution architects for reference patterns and escalation<\/li>\n<li>Migration tooling vendors and systems integrators for surge capacity or specialized migrations<\/li>\n<li>External auditors (regulated environments) for evidence reviews<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Peer roles<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Senior Cloud Engineer, Platform Engineer, DevOps Engineer, Site Reliability Engineer<\/li>\n<li>Security Engineer \/ Cloud Security Specialist<\/li>\n<li>Technical Program Manager (Cloud Transformation)<\/li>\n<li>Solutions Architect (application modernization)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Upstream dependencies<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Landing zone readiness (accounts, network, IAM, logging, policies)<\/li>\n<li>Connectivity setup (VPN\/Direct Connect\/ExpressRoute)<\/li>\n<li>App remediation backlog completion<\/li>\n<li>Security approvals and exception processes<\/li>\n<li>Change calendar availability<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Downstream consumers<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Operations\/SRE teams taking steady-state ownership<\/li>\n<li>Product teams relying on stable environments for feature delivery<\/li>\n<li>Finance\/FinOps relying on accurate tagging and cost allocation<\/li>\n<li>Security relying on consistent telemetry and controls<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Nature of collaboration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The role frequently leads \u201cvirtual teams\u201d for each migration wave: aligning work across multiple teams with clear RACI and cutover ownership.<\/li>\n<li>Collaboration is evidence-driven: readiness checklists, test outcomes, and risk logs drive go\/no-go decisions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Typical decision-making authority<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Owns technical migration plan and execution details within established standards.<\/li>\n<li>Can recommend migration approach and sequencing; final approvals may sit with architecture boards or program leadership depending on governance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Escalation points<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cutover risk disputes (e.g., incomplete testing) \u2192 Cloud Platform Engineering Manager \/ Change authority<\/li>\n<li>Security exceptions \u2192 Security leadership \/ GRC<\/li>\n<li>Major dependency conflicts \u2192 Program\/Portfolio leadership<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">13) Decision Rights and Scope of Authority<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Decisions this role can typically make independently<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migration execution plan details for assigned workloads (step sequencing, tooling choice within approved list)<\/li>\n<li>Readiness assessment outcomes and remediation task definitions<\/li>\n<li>Operational monitoring and alerting baseline requirements per workload<\/li>\n<li>Technical troubleshooting approach during migration (within guardrails)<\/li>\n<li>Recommendations for rehost vs replatform where scope permits (often jointly with app owners)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Decisions requiring team approval (peer\/platform alignment)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Changes to shared landing zone modules, network patterns, or IAM role structures<\/li>\n<li>Updates to standard runbooks\/checklists that affect multiple teams<\/li>\n<li>New automation pipelines that integrate with enterprise CI\/CD standards<\/li>\n<li>Selection of observability patterns that impact platform-wide telemetry<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Decisions requiring manager\/director\/executive approval<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Exceptions to security baselines (public exposure, encryption exceptions, logging exemptions)<\/li>\n<li>Major schedule changes affecting business commitments or customer-facing downtime windows<\/li>\n<li>Vendor\/tool procurement, licensing expansions, or professional services engagements<\/li>\n<li>Budget-impacting architecture changes (multi-region expansion, premium managed services)<\/li>\n<li>Risk acceptance for high-criticality workloads<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Budget, vendor, delivery, hiring, compliance authority (typical)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Budget:<\/strong> Usually influences via recommendations and cost forecasts; does not own budgets directly.<\/li>\n<li><strong>Vendors:<\/strong> Can evaluate tools and manage vendor deliverables if assigned, but procurement approval typically sits with management\/procurement.<\/li>\n<li><strong>Delivery:<\/strong> Owns technical delivery of migration tasks; program schedule ownership may sit with PMO\/TPM.<\/li>\n<li><strong>Hiring:<\/strong> May participate in interviews and technical evaluations; not typically the hiring manager.<\/li>\n<li><strong>Compliance:<\/strong> Ensures evidence capture and control implementation; formal sign-off belongs to GRC\/security and change authorities.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">14) Required Experience and Qualifications<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Typical years of experience<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>7\u201312 years<\/strong> total in infrastructure\/cloud\/DevOps\/operations engineering roles<\/li>\n<li><strong>3\u20136 years<\/strong> directly involved in cloud migrations (portfolio or wave-based)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Education expectations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Bachelor\u2019s degree in Computer Science, Information Systems, Engineering, or equivalent experience<\/li>\n<li>Advanced degrees are optional; practical migration experience is typically more predictive<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certifications (Common \/ Optional \/ Context-specific)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Common (helpful, not always required):<\/strong><\/li>\n<li>AWS Certified Solutions Architect \u2013 Associate\/Professional<\/li>\n<li>Microsoft Certified: Azure Solutions Architect Expert<\/li>\n<li>Google Professional Cloud Architect<\/li>\n<li><strong>Optional (role-enhancing):<\/strong><\/li>\n<li>HashiCorp Terraform certification<\/li>\n<li>Kubernetes certifications (CKA\/CKAD) for container-heavy environments<\/li>\n<li>ITIL Foundation (enterprise ITSM-heavy orgs)<\/li>\n<li><strong>Context-specific (regulated\/high-security):<\/strong><\/li>\n<li>Security certifications (e.g., Security+, CCSP) depending on governance expectations<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prior role backgrounds commonly seen<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Senior Cloud Engineer \/ Cloud Infrastructure Engineer<\/li>\n<li>DevOps Engineer \/ Platform Engineer<\/li>\n<li>Systems Engineer (Windows\/Linux) with migration program exposure<\/li>\n<li>SRE\/Operations Engineer with strong automation and reliability background<\/li>\n<li>Network engineer who transitioned to cloud network and migration delivery<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Domain knowledge expectations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Broadly cross-industry; must understand enterprise IT constraints and production risk<\/li>\n<li>Regulated experience (financial services, healthcare, government) is valuable when relevant, but not mandatory for all employers<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Leadership experience expectations (Senior IC)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Proven ability to lead cross-functional technical initiatives (migration waves, cutovers)<\/li>\n<li>Mentoring and standard-setting experience (templates, automation patterns)<\/li>\n<li>Not necessarily people management; influence-based leadership is the norm<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">15) Career Path and Progression<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Common feeder roles into this role<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Engineer (IaaS\/PaaS)<\/li>\n<li>DevOps\/Platform Engineer<\/li>\n<li>Systems Engineer \/ Infrastructure Engineer (with IaC and automation)<\/li>\n<li>SRE \/ Production Engineer<\/li>\n<li>Technical Consultant in cloud migration practices<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Next likely roles after this role<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Principal Cloud Migration Specialist \/ Principal Cloud Architect<\/strong> (larger scope, complex programs, multi-domain design authority)<\/li>\n<li><strong>Cloud Transformation Lead \/ Migration Factory Lead<\/strong> (owns migration methodology, governance, and throughput)<\/li>\n<li><strong>Staff Platform Engineer \/ Platform Architect<\/strong> (paved road, internal platform productization)<\/li>\n<li><strong>SRE Lead (IC) \/ Reliability Architect<\/strong> (standardizes reliability and operational model for cloud workloads)<\/li>\n<li><strong>Technical Program Manager (Cloud)<\/strong> (if moving toward delivery leadership over hands-on engineering)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Adjacent career paths<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Security Specialist (focus on IAM, policy-as-code, threat modeling, compliance automation)<\/li>\n<li>FinOps \/ Cloud Cost Engineer (cost modeling, optimization governance)<\/li>\n<li>Data Platform Migration Specialist (data lake\/warehouse modernization)<\/li>\n<li>Network\/Connectivity Architect (large-scale hybrid and segmentation design)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Skills needed for promotion<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ability to lead migrations that are multi-region, high-volume, high-availability, or heavily regulated<\/li>\n<li>Demonstrated improvement to organization-wide migration throughput via automation and patterns<\/li>\n<li>Strong architecture judgment (service selection, tradeoffs, operational model)<\/li>\n<li>Program-level risk management and governance credibility<\/li>\n<li>Influence across teams: adoption of standards and paved-road solutions<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How this role evolves over time<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Early: workload execution and stabilization leadership  <\/li>\n<li>Mid: migration factory optimization, reusable modules, governance maturity  <\/li>\n<li>Late (principal\/staff): platform productization, modernization acceleration, enterprise-wide architecture and operating model shaping<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">16) Risks, Challenges, and Failure Modes<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Common role challenges<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Hidden dependencies:<\/strong> undocumented integrations, brittle legacy assumptions, hard-coded network endpoints.<\/li>\n<li><strong>Environment readiness gaps:<\/strong> landing zone missing capabilities (central logging, DNS patterns, identity federation).<\/li>\n<li><strong>Competing priorities:<\/strong> app teams often prioritize feature work over migration remediation.<\/li>\n<li><strong>Change windows constraints:<\/strong> limited downtime windows create pressure and increase risk.<\/li>\n<li><strong>Data gravity and volume:<\/strong> large datasets increase migration time and complicate consistency guarantees.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Bottlenecks<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Network\/security approvals and firewall rule changes<\/li>\n<li>Identity integration and permission model design<\/li>\n<li>DBA capacity for replication setup and cutover validation<\/li>\n<li>Environment provisioning delays when not fully automated<\/li>\n<li>Testing capacity and realistic performance baselines<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Anti-patterns to avoid<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cLift-and-shift everything\u201d without operational readiness, cost controls, or decommissioning<\/li>\n<li>Skipping rehearsals and relying on heroics during cutover<\/li>\n<li>Inadequate rollback planning (no tested rollback path, unclear triggers)<\/li>\n<li>Treating migration as purely infrastructure work (ignoring app config, secrets, observability)<\/li>\n<li>Failing to decommission legacy assets and thus not realizing savings<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common reasons for underperformance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Over-indexing on tooling without understanding workload needs and constraints<\/li>\n<li>Weak stakeholder communication leading to surprises and loss of trust<\/li>\n<li>Insufficient rigor in readiness gates and test validation<\/li>\n<li>Lack of documentation and handover discipline (creating downstream ops burden)<\/li>\n<li>Poor prioritization: spending time on low-value tasks instead of unblocking critical path<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Business risks if this role is ineffective<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Unplanned downtime and customer impact during migrations<\/li>\n<li>Data loss, corruption, or compliance breaches due to inadequate controls<\/li>\n<li>Cloud spend overruns from poor sizing and lack of FinOps integration<\/li>\n<li>Program delays that block product delivery or M&amp;A integration objectives<\/li>\n<li>Increased operational toil and incident rates post-migration, eroding confidence in cloud strategy<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">17) Role Variants<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">By company size<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Startup\/small company:<\/strong> <\/li>\n<li>Role may combine platform build + migration execution; fewer governance layers; faster decisions; broader hands-on scope.<\/li>\n<li><strong>Mid-size software company:<\/strong> <\/li>\n<li>Balanced: migration waves plus building repeatable patterns; strong collaboration with product engineering; moderate governance.<\/li>\n<li><strong>Large enterprise:<\/strong> <\/li>\n<li>Heavier governance (CAB, security reviews), complex networks, multiple stakeholders; emphasis on evidence, risk management, and repeatable factory throughput.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">By industry<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Regulated (finance, healthcare, public sector):<\/strong> <\/li>\n<li>More stringent controls, audit evidence, data residency constraints, formal change management; longer lead times.<\/li>\n<li><strong>Non-regulated (SaaS, tech):<\/strong> <\/li>\n<li>Faster iteration; greater willingness to refactor and adopt containers\/managed services; more automation-first expectations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">By geography<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Differences are usually driven by <strong>data residency<\/strong> and <strong>regional service availability<\/strong>, not by core job design.<\/li>\n<li>Global companies may require coordination across time zones and multi-region architecture patterns.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Product-led vs service-led company<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Product-led (SaaS):<\/strong> <\/li>\n<li>More focus on reliability, performance, SLOs, blue\/green releases, and platform engineering integration.<\/li>\n<li><strong>Service-led (IT services \/ internal IT):<\/strong> <\/li>\n<li>More focus on portfolio governance, standardized migration runbooks, and service transition to operations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup vs enterprise operating model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Startup:<\/strong> lighter documentation; more direct execution; fewer dependency teams.  <\/li>\n<li><strong>Enterprise:<\/strong> formal governance, clear separation of duties, strong emphasis on compliance and operational handover.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Regulated vs non-regulated environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Regulated environments demand: evidence capture, risk acceptance workflows, encryption\/key management rigor, access reviews, retention policies, and audited change controls.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">18) AI \/ Automation Impact on the Role<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Tasks that can be automated effectively<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Discovery augmentation:<\/strong> AI-assisted parsing of inventories, logs, and configuration exports to suggest dependency candidates (still needs validation).<\/li>\n<li><strong>Documentation drafting:<\/strong> first-pass cutover plans, runbooks, and status reports from templates and prior migrations.<\/li>\n<li><strong>IaC generation:<\/strong> scaffolding Terraform modules or cloud templates (with mandatory review and policy checks).<\/li>\n<li><strong>Log analysis and troubleshooting:<\/strong> AI-assisted correlation of logs\/metrics during cutover and stabilization.<\/li>\n<li><strong>Policy checks:<\/strong> automated detection of misconfigurations (public exposure, missing tags, weak IAM) via policy-as-code and CSPM tools.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tasks that remain human-critical<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migration approach selection and architecture tradeoffs based on business context<\/li>\n<li>Risk acceptance and go\/no-go decisions under uncertainty<\/li>\n<li>Stakeholder negotiation (downtime windows, remediation commitments, sequencing)<\/li>\n<li>Designing rollback strategies that are realistic for stateful systems<\/li>\n<li>Deep accountability during incidents and cutovers where judgment matters<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How AI changes the role over the next 2\u20135 years<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The role becomes more <strong>pattern- and platform-driven<\/strong>: specialists will be expected to codify migration logic into reusable modules and pipelines with AI-assisted generation.<\/li>\n<li>Increased expectation to use AI for faster root cause analysis, improved reporting, and reduced manual documentation toil.<\/li>\n<li>Greater emphasis on <strong>guardrails<\/strong>: as AI accelerates changes, the Senior Cloud Migration Specialist will need stronger review discipline, testing gates, and compliance automation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">New expectations caused by AI, automation, and platform shifts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ability to validate AI-generated IaC and scripts for security, correctness, and operational fit<\/li>\n<li>Stronger governance integration: policy-as-code, automated evidence capture, automated drift detection<\/li>\n<li>Higher migration throughput expectations without sacrificing reliability (measured via cycle time and cutover success KPIs)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">19) Hiring Evaluation Criteria<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to assess in interviews (high-signal areas)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Migration strategy judgment:<\/strong> Can they choose and justify rehost vs replatform vs refactor with clear constraints and outcomes?<\/li>\n<li><strong>Hybrid connectivity expertise:<\/strong> Can they reason about DNS, routing, firewall rules, latency, and private connectivity?<\/li>\n<li><strong>Execution discipline:<\/strong> Do they use rehearsals, checklists, go\/no-go gates, rollback plans?<\/li>\n<li><strong>Automation maturity:<\/strong> Can they build repeatable IaC modules and CI\/CD pipelines with guardrails?<\/li>\n<li><strong>Operational readiness mindset:<\/strong> Do they design for observability, incident response, and service transition?<\/li>\n<li><strong>Security-by-design:<\/strong> Can they implement IAM least privilege, encryption, logging, and policy compliance?<\/li>\n<li><strong>Stakeholder leadership:<\/strong> Can they lead cross-team cutovers and manage conflict?<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Practical exercises or case studies (recommended)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Case study (90 minutes): Migration wave plan<\/strong> <\/li>\n<li>Input: 12 applications with mixed criticality, dependencies, and data volumes; limited change windows; partial landing zone readiness.  <\/li>\n<li>Output: Wave plan, readiness gates, risks, tool choices, cutover and rollback approach, stakeholder plan.<\/li>\n<li><strong>Hands-on (60\u2013120 minutes): IaC + guardrails<\/strong> <\/li>\n<li>Task: Produce a Terraform module (or review an existing one) for a standard workload baseline (network\/security\/logging\/tagging). Explain how it integrates into CI\/CD and policy checks.<\/li>\n<li><strong>Scenario interview: Cutover incident<\/strong> <\/li>\n<li>Prompt: During cutover, latency spikes and database replication lag increases beyond threshold.  <\/li>\n<li>Evaluate: Decision-making, communication, rollback triggers, troubleshooting approach.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Strong candidate signals<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Has led multiple production cutovers with measured success criteria and tested rollback plans<\/li>\n<li>Demonstrates clear patterns and reusability (templates, modules, automation)<\/li>\n<li>Can articulate real migration failures they experienced and what they changed to prevent recurrence<\/li>\n<li>Understands operational ownership: monitoring, alerting, on-call, and handover requirements<\/li>\n<li>Communicates risks early, with concrete mitigation plans and decision points<\/li>\n<li>Comfort navigating security and compliance requirements without treating them as \u201csomeone else\u2019s job\u201d<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Weak candidate signals<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Speaks only in generic cloud terms; lacks migration-specific rigor (rehearsals, rollback)<\/li>\n<li>Over-reliance on a single tool without understanding underlying mechanics<\/li>\n<li>Treats migration as \u201ccopy servers to cloud\u201d with minimal app\/data\/ops consideration<\/li>\n<li>Limited evidence of cross-functional leadership or stakeholder communication<\/li>\n<li>No clear examples of troubleshooting in complex hybrid environments<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Red flags<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Claims \u201czero downtime\u201d as a default without understanding data consistency and cutover mechanics<\/li>\n<li>Dismisses security\/compliance controls or suggests bypassing guardrails for speed<\/li>\n<li>Cannot explain how to validate data integrity and reconciliation after migration<\/li>\n<li>Has not owned outcomes (blames other teams without showing influence and mitigation)<\/li>\n<li>Cannot articulate go\/no-go criteria or rollback triggers<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scorecard dimensions (recommended)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migration strategy and architecture judgment<\/li>\n<li>Hybrid networking and identity competence<\/li>\n<li>Automation\/IaC competence and quality discipline<\/li>\n<li>Operational readiness and reliability mindset<\/li>\n<li>Security and compliance implementation<\/li>\n<li>Troubleshooting depth and incident leadership<\/li>\n<li>Stakeholder leadership and communication<\/li>\n<li>Delivery rigor (planning, risk logs, metrics)<\/li>\n<li>Learning agility and ability to codify patterns<\/li>\n<li>Culture add (ownership, calm under pressure)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">20) Final Role Scorecard Summary<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Category<\/th>\n<th>Summary<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Role title<\/td>\n<td>Senior Cloud Migration Specialist<\/td>\n<\/tr>\n<tr>\n<td>Role purpose<\/td>\n<td>Lead the planning and execution of workload migrations to cloud with strong automation, governance, and operational readiness to deliver stable production outcomes.<\/td>\n<\/tr>\n<tr>\n<td>Top 10 responsibilities<\/td>\n<td>1) Workload assessment &amp; dependency mapping 2) Migration approach selection (6Rs\/7Rs) 3) Wave planning &amp; sequencing 4) Landing zone integration coordination 5) IaC and automation delivery 6) Cutover orchestration (go\/no-go, rollback) 7) Data migration planning &amp; reconciliation 8) Security baseline implementation &amp; evidence 9) Observability and ops readiness\/handover 10) Decommissioning legacy resources and capturing savings<\/td>\n<\/tr>\n<tr>\n<td>Top 10 technical skills<\/td>\n<td>1) Cloud platform expertise (AWS\/Azure\/GCP) 2) Migration methodologies 3) Hybrid networking (DNS\/routing\/connectivity) 4) IAM and federation 5) Terraform\/IaC 6) CI\/CD pipelines 7) Linux\/Windows administration 8) Observability (logs\/metrics\/traces) 9) Data migration strategies 10) DR\/resilience patterns<\/td>\n<\/tr>\n<tr>\n<td>Top 10 soft skills<\/td>\n<td>1) Structured problem solving 2) Risk management discipline 3) Stakeholder influence 4) Clear technical communication 5) Planning\/operational rigor 6) Calm under pressure 7) Coaching\/enablement 8) Ownership\/accountability 9) Negotiation and conflict resolution 10) Service mindset (operability-first)<\/td>\n<\/tr>\n<tr>\n<td>Top tools or platforms<\/td>\n<td>Cloud platform (AWS\/Azure\/GCP), Terraform, Git + CI\/CD (GitHub\/GitLab\/Jenkins\/Azure DevOps), Cloud-native monitoring (CloudWatch\/Azure Monitor), Secrets management (Key Vault\/Secrets Manager\/Vault), ITSM (ServiceNow\/JSM), Diagramming + docs (Lucidchart\/Confluence), Migration tooling (Azure Migrate\/AWS MGN\/DMS as applicable)<\/td>\n<\/tr>\n<tr>\n<td>Top KPIs<\/td>\n<td>Migration throughput, cycle time, cutover success rate, downtime minutes, post-migration incident rate, automation coverage, security baseline compliance, IaC compliance, cost variance vs forecast, decommission completion rate<\/td>\n<\/tr>\n<tr>\n<td>Main deliverables<\/td>\n<td>Workload assessments, migration wave plans, cutover\/rollback plans, IaC modules, automation scripts\/pipelines, observability baselines, runbooks\/handover packages, risk logs\/ADRs, decommission plans, stakeholder dashboards\/status reports<\/td>\n<\/tr>\n<tr>\n<td>Main goals<\/td>\n<td>Deliver predictable, low-risk migrations with strong operational readiness; scale migration throughput via patterns and automation; maintain security and cost controls; achieve clean decommissioning and measurable business value realization.<\/td>\n<\/tr>\n<tr>\n<td>Career progression options<\/td>\n<td>Principal Cloud Migration Specialist, Principal\/Staff Cloud Architect, Cloud Transformation Lead\/Migration Factory Lead, Staff Platform Engineer\/Platform Architect, SRE\/Reliability Architect, Cloud Security Specialist, FinOps\/Cost Engineer (adjacent)<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>The **Senior Cloud Migration Specialist** plans and executes the end-to-end migration of applications, data, and infrastructure from on\u2011premises or legacy hosting environments to public cloud and cloud-native platforms. This role combines hands-on engineering with migration strategy, risk management, and stakeholder leadership to deliver reliable cutovers while improving security posture, scalability, and cost efficiency.<\/p>\n","protected":false},"author":61,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_joinchat":[],"footnotes":""},"categories":[24455,24508],"tags":[],"class_list":["post-75020","post","type-post","status-publish","format-standard","hentry","category-cloud-infrastructure","category-specialist"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75020","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/61"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=75020"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75020\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=75020"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=75020"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=75020"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}