Senior Solutions Architect - Google Cloud Platform/Emerging Tech, Cloud Intelligence
Amazon Web Services (AWS) · New York, United States · 3 wk ago
ConsultingFull-time
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 description.
We have 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."
Then "Key job responsibilities" list bullet points.
Then "A day in the life" paragraph.
Then "About The Team" with subsections: Diverse Experiences, Why AWS, Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth. Those are more like company culture sections; but we only need to include sections if they have real specific content. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine culture info into maybe "About the team" but not required headings. However headings list includes "About the role". That could be used for the initial description. Responsibilities for the bullet list. Requirements/Qualifications for basic and preferred qualifications. Skills maybe from preferred qualifications? Benefits, Pay, Schedule: we have pay ranges listed per location; we have benefits description. No schedule info. So we should include Pay and Benefits sections if they have real specific content. Pay: we have salary ranges per location; we can include that. Benefits: we have description of benefits. Schedule: none, so omit.
We must not repeat job title as heading. No Job ID etc.
We must remove boilerplate: EEO, equal-opportunity, scam-warning, legal, cookie/navigation, duplicated lines, application instructions. Also remove "Amazon is an equal opportunity employer..." etc. Also remove Los Angeles County etc. Also remove "If you have a disability..." etc. Also remove "Learn more about our benefits at ..."? That's maybe okay but it's a link; but it's part of benefits description; we can keep the description but maybe drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is not necessarily boilerplate; but it's a reference; we could keep it as part of benefits description. However it's a URL; might be okay. But we can keep the description.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the salary ranges per location exactly as given. Also benefits description.
We need to use
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 description.
We have 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."
Then "Key job responsibilities" list bullet points.
Then "A day in the life" paragraph.
Then "About The Team" with subsections: Diverse Experiences, Why AWS, Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth. Those are more like company culture sections; but we only need to include sections if they have real specific content. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine culture info into maybe "About the team" but not required headings. However headings list includes "About the role". That could be used for the initial description. Responsibilities for the bullet list. Requirements/Qualifications for basic and preferred qualifications. Skills maybe from preferred qualifications? Benefits, Pay, Schedule: we have pay ranges listed per location; we have benefits description. No schedule info. So we should include Pay and Benefits sections if they have real specific content. Pay: we have salary ranges per location; we can include that. Benefits: we have description of benefits. Schedule: none, so omit.
We must not repeat job title as heading. No Job ID etc.
We must remove boilerplate: EEO, equal-opportunity, scam-warning, legal, cookie/navigation, duplicated lines, application instructions. Also remove "Amazon is an equal opportunity employer..." etc. Also remove Los Angeles County etc. Also remove "If you have a disability..." etc. Also remove "Learn more about our benefits at ..."? That's maybe okay but it's a link; but it's part of benefits description; we can keep the description but maybe drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is not necessarily boilerplate; but it's a reference; we could keep it as part of benefits description. However it's a URL; might be okay. But we can keep the description.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the salary ranges per location exactly as given. Also benefits description.
We need to use - for any list of duties/requirements/benefits. So responsibilities list should be ul li. Requirements/qualifications maybe also list.
We need to use
for prose.
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.
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.
Maybe also include "A day in the life" as part of About the role? Could be separate section but we don't have a heading for that; we could incorporate into About the role paragraph. But we have a paragraph about day in the life; we could add another after responsibilities? But we need to preserve all substantive information. The "A day in the life" paragraph is substantive. We could add a section heading like "About the team" but not required. However we have headings list includes "About the role" only; we could add another heading like "About the team" but not in the list; but instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we could use other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. But we could also use other headings if needed, but better to stick to those. We can incorporate the day in the life paragraph into About the role or maybe a separate
after responsibilities without a heading. That's acceptable as prose.
Then we need Requirements and Qualifications sections. The posting has Basic Qualifications and Preferred Qualifications. We could combine them into Requirements and Qualifications sections. Or we could have Requirements for basic, Qualifications for preferred. Let's do:
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
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 Administrator, Developer), or equivalent
- 4+ years working with AWS specializing in compute, storage, databases, ML/AI, and analytics
We could also include Skills section but we don't have explicit skills list; we could omit.
Now Benefits: we have description: "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."
We need to put that in a - for list of benefits? The instruction: Use
- for any list of duties/requirements/benefits. So we should list each benefit as li items. Let's extract:
- 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
- parental leave
Also maybe "option for Supplemental life plans" is part of health insurance; we can keep as part of that item.
We'll create
Benefits
with each.
Pay: we have salary ranges per location. We need to include Pay section. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated. So we need Pay section with the ranges. Should we list each location as li? Probably yes.
Thus:
Pay
- 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 should preserve the exact formatting: they have "USA, CA, Irvine - 153,600.00 -
for prose. 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.
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.
after responsibilities? But we need to preserve all substantive information. The "A day in the life" paragraph is substantive. We could add a section heading like "About the team" but not required. However we have headings list includes "About the role" only; we could add another heading like "About the team" but not in the list; but instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we could use other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. But we could also use other headings if needed, but better to stick to those. We can incorporate the day in the life paragraph into About the role or maybe a separate
after responsibilities without a heading. That's acceptable as prose. Then we need Requirements and Qualifications sections. The posting has Basic Qualifications and Preferred Qualifications. We could combine them into Requirements and Qualifications sections. Or we could have Requirements for basic, Qualifications for preferred. Let's do:
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
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 Administrator, Developer), or equivalent
- 4+ years working with AWS specializing in compute, storage, databases, ML/AI, and analytics
- for list of benefits? The instruction: Use
- for any list of duties/requirements/benefits. So we should list each benefit as li items. Let's extract:
- 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
- parental leave
Also maybe "option for Supplemental life plans" is part of health insurance; we can keep as part of that item.
We'll create
Benefits
- with each.
Pay: we have salary ranges per location. We need to include Pay section. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated. So we need Pay section with the ranges. Should we list each location as li? Probably yes.
Thus:
- 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
Pay
- for any list of duties/requirements/benefits. So we should list each benefit as li items. Let's extract:
- 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
- parental leave
Also maybe "option for Supplemental life plans" is part of health insurance; we can keep as part of that item.
We'll create