Sign upLog in
See more jobs

Azure Technical Migration Consultant

Phoenix Business, Inc

  • Greater Seattle, WA
  • 3 days ago

    Highlights

    Strong signals Actually operated an ASH stamp mentions PEP/ERCS, scale units, update packages, marketplace syndication, capacity/N 1 planning, Test-AzureStack, Get-AzureStackLog. Red flags / disqualifiers Only public Azure cloud migration (Azure Migrate, lift-and-shift VMware Azure) with no Stack Hub/Edge exposure this is the most common false positive.

    Numbers & Facts

    LocationGreater Seattle, WA

    Description

    Non-negotiable technical spine (both roles)
    • Azure Stack Hub and Azure Stack Edge real operational exposure, not slideware
    • Azure Local / Azure Stack HCI
    • Azure Arc
    • Hybrid networking + Azure networking
    • Identity (Entra ID, AD FS in disconnected mode)
    • Compute / storage / backup / DR
    • PowerShell debugging someone else's migration workflows, not just writing scripts
    • Migration mechanics: readiness assessment, dependency checks, cutover, rollback/runback, post-migration validation
    How to screen profiles
    Strong signals
    • Actually operated an ASH stamp mentions PEP/ERCS, scale units, update packages, marketplace syndication, capacity/N 1 planning, Test-AzureStack, Get-AzureStackLog
    • ASE Pro/Pro GPU field deployments, not just "familiar with"
    • Named Azure Local / HCI cluster deployments with Arc onboarding
    • Migration/cutover war stories with rollback executed
    • Worked alongside Microsoft engineering/support (escalation, pilot/TAP programs)
    • Enterprise customer-facing delivery across time zones
    Red flags / disqualifiers
    • Only public Azure cloud migration (Azure Migrate, lift-and-shift VMware Azure) with no Stack Hub/Edge exposure this is the most common false positive
    • Pure VMware or on-prem Hyper-V admin with Azure certs but no hybrid/edge platform work
    • "Azure Stack" listed once in a skills blob with nothing in the experience bullets
    • Script authors only, with no evidence of debugging/validating others' automation
    • Backend-only engineers with no customer-facing track record 30% of this job is workshops and exec conversations
    Differentiators between the two
    • Lead: look for design authority, sequencing/dependency planning across a portfolio of customers, RCA ownership, exec presence, and reusable-artifact creation.
    • Engineer: look for execution volume how many migrations, how many environments, depth in log analysis and troubleshooting.

    Similar Jobs