Senior Solutions Architect - Google Cloud Platform/Emerging Tech, Cloud Intelligence

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, description: "Own AWS's competitive point of view on Google Cloud. As a Senior GCP Cloud Intelligence SA, your analysis shapes how thousands of AWS field teams win — and feeds directly into our product roadmap and go-to-market strategy. This is a rare seat where deep Google Cloud expertise doesn't just close individual deals; it changes how AWS competes at scale. You'll be a technical and business leader who influences the AWS field on sales strategy and helps design cloud-native solutions for customers. You'll build and maintain cloud migration and modernization acumen across AWS and other public clouds, then scale that expertise by documenting your insights, sharpening our product offerings, and strengthening our go-to-market campaigns. The ideal candidate lives and breathes public cloud and is energized by continual learning as new offerings and industry shifts emerge. You partner naturally across product, go-to-market, and field leadership, think strategically about customers' complex business and technical needs, and move fluidly between C-level executives and technical decision makers. You bring a proven track record as a consultant, advisor, or key stakeholder delivering cloud-native solutions." That's about the role. So we can have

About the role

with paragraphs. Next: "Key job responsibilities" list bullet points: Serve as the subject matter expert on GCP technology and go-to-market strategy for the AWS field. Partner with field SAs and BDs to translate customers' business and technical requirements into the best-fit AWS approach, and present those recommendations directly to CxO and technical audiences (Architect/Director). Analyze competitive trends and offerings to generate technical and business insights, and grow a community of compete specialists who build on your work. Create technical content that scales your expertise — decks, whitepapers, and recordings — and deliver presentations and trainings to field SAs, BDMs, and product stakeholders. Manage a fast-moving pipeline of technical engagements with operational excellence, delivering rapidly and reprioritizing as opportunities shift. So we can have

Responsibilities

with

• each bullet. Next: "A day in the life" description: The AWS Cloud Intelligence team is a specialty services organization providing cloud compete expertise globally... etc. That's more description, maybe part of About the role or separate? Could be "About the team". But we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "Basic Qualifications" list: 8+ years of specific technology domain areas... etc. Also "Preferred Qualifications". Those can go under Requirements or Qualifications. The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put qualifications. Likely "Requirements" for basic qualifications, "Preferred Qualifications" maybe under Qualifications or Skills. But we need to avoid filler. We have "Basic Qualifications" with several bullet-like sentences (though not bullet list). We'll convert to
  • . We have "Preferred Qualifications" also list. We also have "About The Team" section with subpoints: Diverse Experiences, Why AWS, Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth. Those are more about company culture; could be placed under "About the role" or maybe omitted if not specific? The instruction: include a section ONLY when posting has real, specific content for it. Those are specific content about team culture. Could be placed under a section like "About the team" but we don't have that heading in allowed list. We could incorporate into "About the role" or maybe we can create a section "About the team" but not allowed headings list only those specific ones. The instruction says: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should stick to those? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. Thus we can put "About the role" covering description, day in the life, about the team maybe. "Responsibilities" as above. "Requirements" for basic qualifications. "Qualifications" for preferred qualifications. "Skills" maybe we can extract from preferred qualifications like infrastructure architecture, database architecture, networking, communicating complex concepts, migrating/transforming legacy solutions, etc. But we could also just put skills under Qualifications. However we need to decide if we need a Skills section. If we have content for skills, we can create it; else omit. We have "Benefits": The posting mentions benefits: "Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits." Thus we have benefits content. So we can have

    Benefits

    with a paragraph. Pay: The posting includes base salary ranges for various locations. That is pay info. So we can have

    Pay

    with maybe a paragraph listing ranges or a note that ranges vary by location. We should preserve all substantive information; we can list the ranges as given. Schedule: No mention of schedule (e.g., full-time, remote). Not present, so omit Schedule. We must not include boilerplate like EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. Also remove "Job ID", "Company - Amazon Web Services, Inc." maybe minor metadata; we can fold into a short

    or drop it. Probably drop. We must not repeat job title as heading. We must output only HTML fragment. Let's construct:

    About the role

    Own AWS's competitive point of view on Google Cloud. As a Senior GCP Cloud Intelligence SA, your analysis shapes how thousands of AWS field teams win — and feeds directly into our product roadmap and go-to-market strategy. This is a rare seat where deep Google Cloud expertise doesn't just close individual deals; it changes how AWS competes at scale. You'll be a technical and business leader who influences the AWS field on sales strategy and helps design cloud-native solutions for customers. You'll build and maintain cloud migration and modernization acumen across AWS and other public clouds, then scale that expertise by documenting your insights, sharpening our product offerings, and strengthening our go-to-market campaigns. The ideal candidate lives and breathes public cloud and is energized by continual learning as new offerings and industry shifts emerge. You partner naturally across product, go-to-market, and field leadership, think strategically about customers' complex business and technical needs, and move fluidly between C-level executives and technical decision makers. You bring a proven track record as a consultant, advisor, or key stakeholder delivering cloud-native solutions.

    The AWS Cloud Intelligence team is a specialty services organization providing cloud compete expertise globally. We're the subject matter experts on top and emerging competitors, key domains, and industry segments — enabling field teams to unblock customers quickly by removing business and technical barriers in the sales cycle. We advise account teams and their customers through at-scale content, gather and analyze insights on comparable cloud providers, and surface the product and positioning gaps customers experience so we can continuously improve AWS's overall value proposition. Alongside on-demand, self-service resources, we provide targeted one-to-one support on specific competitive opportunities. We hire SAs and BDMs who are SMEs in one or more public clouds to advise AWS field teams on the best strategies for building compelling business cases that support customers co-existing and partnering with competing public cloud services.

    Diverse Experiences Amazon values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying.

    Why AWS Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses.

    Work/Life Balance We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve in the cloud.

    Inclusive Team Culture Here at AWS, it’s in our nature to learn and be curious. Our employee-led affinity groups foster a culture of inclusion that empower us to be proud of our differences. Ongoing events and learning experiences, including our Conversations on Race and Ethnicity (CORE) and AmazeCon (gender diversity) conferences, inspire us to never stop embracing our uniqueness.

    Mentorship and Career Growth We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional.

    That seems a lot but okay. Next Responsibilities:

    Responsibilities

    • Serve as the subject matter expert on GCP technology and go-to-market strategy for the AWS field.
    • Partner with field SAs and BDs to translate customers' business and technical requirements into the best-fit AWS approach, and present those recommendations directly to CxO and technical audiences (Architect/Director).
    • Analyze competitive trends and offerings to generate technical and business insights, and grow a community of compete specialists who build on your work.
    • Create technical content that scales your expertise — decks, whitepapers, and recordings — and deliver presentations and trainings to field SAs, BDMs, and product stakeholders.
    • Manage a fast-moving pipeline of technical engagements with operational excellence, delivering rapidly and reprioritizing as opportunities shift.
    Next Requirements (basic qualifications):

    Requirements

    • 8+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
    • 3+ years of design, implementation, or consulting in applications and infrastructures experience
    • 10+ years of IT development or implementation/consulting in the software or Internet industries experience
    • Bachelor's degree in Computer Science or other technical degree or related experience
    • 4+ years of technology role experience
    • 4+ years experience architecting cloud solutions in GCP
    Next Qualifications (preferred):

    Qualifications

    • 6+ years of infrastructure architecture, database architecture and networking experience
    • Experience working with end user or developer communities
    • Experience effectively communicating complex concepts through written and verbal communication
    • Experience migrating or transforming legacy customer solutions to the cloud
    • 4+ years of architecting/operating solutions built on any cloud service provider like Azure, AWS, GCP, OCI, etc.
    • AWS Certification (Cloud Technologist, Solutions Architect, SysOps