Senior Cloud Solution Architect｜Shenzhen
Role definition, delivery scope, candidate criteria, interview evidence, and responsible hiring guardrails
Version 1.2 · EnglishScroll to review the complete document · Pending final approval
ROLE & SCOPE DELIVERY DEFINITION
Role Mission
Act as a trusted technical advisor who translates business goals, existing environments, organizational capabilities, and budget constraints into secure, reliable, and operable cloud, multi-cloud, and AI platform architectures.
Key Responsibilities
- Lead discovery and architecture for cloud migration, application modernization, data, and AI platform initiatives.
- Turn business requirements into target architectures, roadmaps, decision records, risk registers, and cost models.
- Design practical solutions across Kubernetes, Terraform, identity, networking, security, data, and observability.
- Facilitate customer architecture workshops and explain trade-offs to technical and business stakeholders.
- Define and lead PoCs with explicit success criteria, scope, risks, and exit conditions.
- Partner with product, delivery, and ecosystem teams through review, handoff, operational readiness, and risk closure.
Priority Scenarios
Cloud migrationPortfolio, dependency, data-gravity, and wave planning
ModernizationContainers, platform engineering, and developer experience
Data and AIPlatforms, governance, performance, and cost architecture
Hybrid / multi-cloudBoundaries, governance, and operational complexity
Security / resilienceIdentity, Zero Trust, backup, and DR
FinOpsCapacity, unit economics, guardrails, and optimization
Core Deliverables
- Current-state assessment and workload segmentation
- Target architecture, decision records, and non-functional requirements
- Phased migration or modernization roadmap
- Risk, dependency, cost, governance, and operational-readiness register
- PoC design, success criteria, and outcome review
- Executive-ready recommendation and next-step plan
Role PositioningThis is not a product-presentation role. The architect connects business outcomes, technical judgment, and an executable delivery path across customer and Microsoft stakeholders.
PROFILE & ASSESSMENT EVIDENCE-BASED HIRING
Must-have Qualifications
- 5+ years in cloud, infrastructure, platform engineering, or a related discipline, including 3+ years with architecture ownership.
- Production experience with Kubernetes and infrastructure as code, including Terraform or an equivalent tool.
- Deep expertise in at least one public cloud and sound judgment across hybrid and multi-cloud trade-offs.
- Working knowledge of networking, identity, security, reliability, and observability as architecture concerns.
- Strong customer-facing communication and the ability to translate complex technology into business language and action.
- Professional fluency in Chinese and English, with willingness to travel for customer engagements.
Preferred Qualifications
- Experience with AI / ML platforms, Zero Trust, FinOps, data platforms, or platform engineering.
- Delivery experience with internet, consumer-electronics, cross-regional, or ecosystem-heavy customers.
- Ability to build order-of-magnitude cost models and explain performance, cost, resilience, and operational trade-offs.
- Experience with architecture reviews, workshops, PoC design, or cross-team delivery.
- Verifiable technical writing, public speaking, or community contribution.
Interview Evidence
Architecture judgmentClarifies constraints before recommending
Technical depthReasons about capacity and resilience
Customer communicationHandles objections while preserving trust
Commercial awarenessBalances cost, time, risk, and competition
ExecutionConverts architecture into ownership and steps
Learning agilityDefines validation paths for unknowns
Not Automatic Hard GatesSpecific certifications, single-cloud background, exact years, current title, and prior industry cannot replace evidence of capability.
Responsible Hiring GuardrailSensitive attributes must not enter scoring. Missing information means “needs clarification.” Interviewers record evidence independently before discussion. Scout does not auto-reject candidates.
Success in the First 90 Days
Day 30Map the customer, technology, and stakeholders
Day 60Lead an assessment and workshop independently
Day 90Deliver a roadmap, cost model, and risk plan
