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

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the description. First, we have a description paragraph: "Own AWS's competitive point of view on Google Cloud...". That's about the role. So we can put that under

About the role

with

. Then "Key job responsibilities" list: bullet points. We'll put under

Responsibilities

with

• . Then "A day in the life" paragraph: could be part of About the role or separate? It's more description of team. Could be part of About the role. But we can keep as part of About the role. Then "About The Team" paragraph: maybe also part of About the role. But we could include as part of About the role. Then "Basic Qualifications" list: we need to put under Requirements or Qualifications? The instruction: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map. Basic Qualifications likely go under Requirements (or Qualifications). Preferred Qualifications under Qualifications. Skills maybe from Preferred Qualifications? But we can treat Preferred Qualifications as Qualifications. Basic Qualifications as Requirements. Skills: maybe we can extract from Preferred Qualifications: infrastructure architecture, database architecture, networking experience, communicating complex concepts, migrating/transforming legacy solutions, architecting/operating solutions on any cloud, AWS certification, etc. Could put under Skills. Benefits: The posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, and parental leave." Also mentions sign-on payments and RSUs. So we have benefits content. Pay: The posting includes base salary ranges per location. So we have Pay content. Schedule: Not mentioned. So we should not include Schedule section. We must not include boilerplate like EEO, equal opportunity, scam warning, navigation, cookie, legal, etc. Also remove duplicated lines. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all specifics: bullet points, salary ranges per location, benefits details, etc. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  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.

  Then maybe include "A day in the life" and "About The Team" as part of About the role? Could add another paragraph. We could add another

  for "A day in the life" content. Let's extract that paragraph: "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." Then "About The Team" paragraph: "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." Then "Why Amazon" etc. That's more about company culture; could be included but not required. Might be considered boilerplate? It's about work/life balance, inclusive culture, mentorship. Might be considered substantive but not required headings. Could be included under About the role as extra paragraphs. But we need to avoid too many thin sections. We'll keep About the role with multiple paragraphs. Now Responsibilities: list from "Key job 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. We'll put each as

• . Now Requirements: Basic Qualifications list: - 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 We'll put each as
• under Requirements. Now Qualifications: Preferred Qualifications list: - 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. - experience AWS Certification (Cloud Technologist, Solutions Architect, SysOps Administrator, Developer), or equivalent - 4+ years working with AWS specializing in compute, storage, databases, ML/AI, and analytics We'll put each as
• under Qualifications. Now Skills: Could extract from Preferred Qualifications that are skill-like: infrastructure architecture, database architecture, networking, working with end user/developer communities, communicating complex concepts, migrating/transforming legacy solutions, architecting/operating solutions on any cloud, AWS certification, working with AWS compute/storage/databases/ML/AI/analytics. But we already have those in Qualifications. Might be redundant. Perhaps we can treat Skills as a separate section for soft skills: "think strategically about customers' complex business and technical needs", "move fluidly between C-level executives and technical decision makers", "partner naturally across product, go-to-market, and field leadership". But those are in About the role. Given instruction to prefer few substantive sections over many thin ones, maybe we can omit Skills section if not distinct. But we need to include only when posting has real specific content for it. The posting does not have a dedicated "Skills" heading; but we could infer skills from responsibilities and qualifications. However, we should not create a Skills section unless the posting actually states them. The posting does not have a "Skills" heading; but we could still include a Skills section if we have specific skill statements. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we can extract specific skill statements, we can include Skills. The posting includes: "think strategically about customers' complex business and technical needs", "move fluidly between C-level executives and technical decision makers", "partner naturally across product, go-to-market, and field leadership". Those are specific. Also "lives and breathes public cloud", "energized by continual learning". Those are more traits. We could create Skills section with those bullet points. But we must ensure not to duplicate content already elsewhere. It's okay to have some overlap? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but might be redundant. However, we could include Skills as a separate section with those specific skill statements. But we also have Benefits and Pay sections. Benefits: The posting includes: "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." We'll put that under Benefits. Pay: The posting includes base salary ranges per location: - USA, CA, Irvine - 153,600.00 - 207,800.00 USD annually - USA, CA, San Francisco - 176,600.00 - 239,000.00 USD annually - USA, GA, Atlanta - 153,600.00 - 207,800.00 USD annually - USA, IL, Chicago - 153,600.00 - 207,800.00 USD annually - USA, MA, Boston - 153,600.00 - 207,800.00 USD annually - USA, NY, New York - 169,000.00 - 228,600.00 USD annually - USA, TX, Austin - 153,600.00 - 207,800.00 USD annually - USA, TX, Dallas - 153,600.00 - 207,800.00 USD annually - USA, VA, Arlington - 153,600.00 - 207,800.00 USD annually - USA, WA, Seattle - 153,600.00 - 207,800.00 USD annually We'll put each as
• under Pay. Schedule: Not present, so omit. Now we need to remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove "Los Angeles County applicants:" etc. Also remove "Criminal history may have a direct..." etc. Also remove "Pursuant to the Los Angeles County Fair Chance Ordinance", etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." Also remove