Senior Solutions Architect, AWS Plus Team
Amazon Web Services (AWS) · Houston, TX · 1 mo ago
ConsultingFull-time
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 must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, accommodations, etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Pay and Schedule only if posting actually states them. The posting includes salary range: "USA, WA, Seattle - 153,600.00 - 207,800.00 USD annually". Also mentions sign-on payments and RSUs, benefits. So Pay section can include salary range and mention sign-on and RSUs. Schedule: not mentioned explicitly; there is mention of work-life balance, flexibility in working hours, but not a specific schedule. Probably we should not create Schedule section because no explicit schedule. Benefits: we have description of benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention "Amazon offers a competitive package including shares, sign-on bonus, and benefits." and later details. So Benefits section.
About the role: we have description of role: "What if your customer was Amazon itself? AWS Plus...". So we can put that in About the role.
Responsibilities: list of key job responsibilities bullet points.
Requirements: Basic Qualifications.
Qualifications: Preferred Qualifications.
Skills: maybe combine? The posting includes "Knowledge of cloud architecture" etc. Could be under Skills. But we have separate sections for Requirements and Qualifications. Might also have Skills section for specific skills like "Knowledge of software development tools and methodologies". We'll decide.
We must not repeat job title. Must not include Job ID. Must not include boilerplate like EEO, accommodations, etc. Must not include duplicated lines (like "About The Team" appears twice). We'll need to deduplicate.
We need to preserve all substantive information. Let's extract substantive content:
- Role description: AWS Plus is a specialized account team within AWS that supports Amazon's own business units as strategic cloud customers. As a Senior Solutions Architect on this team, you'll be the primary technical advisor to one or more of Amazon's businesses, working directly with their engineering teams and technology leaders to design, operate, and optimize AWS workloads at a scale few external customers ever reach. Amazon's businesses run some of the largest and most demanding workloads on AWS, and they expect their Solutions Architect to operate as a true peer to their engineers. You'll go deep on your customer's domain, make prescriptive architecture recommendations, and help them adopt new AWS capabilities, including generative and agentic AI, ahead of the broader market.
- Key job responsibilities (list):
* Own the technical relationship with your assigned Amazon business units, serving as trusted advisor to engineering teams and VP- and Director-level technology leaders, and translating their business goals into AWS architecture and adoption strategy.
* Make prescriptive recommendations on security, cost, performance, reliability, and operational efficiency for large-scale, business-critical workloads.
* Architect and advise on solutions across a broad range of AWS services, including compute, storage, data and analytics, integration, and AI/ML, matched to the customer's domain.
* Guide adoption of generative and agentic AI capabilities, using services such as Amazon Bedrock.
* Work backwards from customer business needs to translate requirements into well-architected designs and into the feature requests that influence AWS service roadmaps.
* Collaborate with AWS account management, Customer Solutions Managers, AWS Support, service teams, and the broader Solutions Architecture community to deliver complete technical coverage and speed up resolution of complex challenges.
- A day in the life (could be part of responsibilities or separate? Might be considered responsibilities but we can include as part of About the role? It's descriptive. Could be part of About the role or separate section "A day in the life" but not in required headings. We could incorporate into About the role or Responsibilities. Probably we can keep as part of About the role.
- About The Team: AWS Plus is a dedicated account team that supports Amazon's own business units as strategic AWS customers. Our customers span Amazon's consumer, media, devices, operations, and corporate businesses, and together they represent some of the largest AWS deployments in the world. We work alongside aligned Customer Solutions Managers, AWS Support, and AWS service teams to make Amazon a strong reference for running on AWS at scale. We value work-life balance, offer flexibility in working hours, and believe the right balance between your personal and professional life is key to long-term fulfilment. Amazon offers a competitive package including shares, sign-on bonus, and benefits.
- About The Team Diverse Experiences: AWS values diverse experiences. Even if you do not meet all of the 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? (maybe not needed as heading; but could be part of About the role? It's generic marketing. Might be considered boilerplate? It's not specific to role but still substantive. However instructions: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This "Why AWS?" is not boilerplate but could be considered generic marketing. Might be okay to keep but we have no heading for it. Could be placed under About the role? Might be considered filler. Safer to omit? The instruction: "Prefer a few substantive sections over many thin ones." Could include as part of About the role? But it's not directly about role. Might be considered not essential. I'd omit to keep concise.
- Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance: these are generic benefits/culture. Could be considered part of Benefits or About the Team? They are not specific to role but still substantive. However they are generic AWS benefits. Might be considered boilerplate? Not exactly legal/EEO. Might be okay to include under Benefits or About the Team. But we already have Benefits section for concrete benefits. The culture statements could be considered part of Benefits? Not exactly. Might be omitted to keep focused.
- 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
* Knowledge of cloud architecture
- PREFERRED QUALIFICATIONS:
* 5+ years of infrastructure architecture, database architecture and networking experience
* Experience working with end user or developer communities
* Knowledge of software development tools and methodologies
- Pay: "The base salary range for this position is listed below. 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. USA, WA, Seattle - 153,600.00 - 207,800.00 USD annually"
Thus Pay section: include salary range and mention sign-on payments and RSUs.
Benefits section: include health insurance details, 401(k) matching, paid time off, parental leave, etc. Also mention "Amazon offers a comprehensive benefits including ..." plus maybe "Learn more about our benefits at ..." but that's a link; we could keep as text.
Schedule: not present; we should not create Schedule section.
Now we need to output HTML fragment with headings for each section we include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly Skills we could combine some skill statements from qualifications? But we have Requirements (basic qualifications) and Qualifications (preferred). Skills maybe we can include "Knowledge of cloud architecture", "Knowledge of software development tools and methodologies". However those are already in qualifications. Might be redundant. Better to not create Skills section if no distinct skill list beyond those. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills.
Thus sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay.
Check for duplicated content: "About The Team" appears twice; we need to merge and avoid duplication. We'll combine the team description: AWS Plus is a dedicated account team that supports Amazon's own business units as strategic AWS customers. Our customers span Amazon's consumer, media, devices, operations, and corporate businesses, and together they represent some of the largest AWS deployments in the world. We work alongside aligned Customer Solutions Managers, AWS Support, and AWS service teams to make Amazon a strong reference for running on AWS at scale. We value work-life balance, offer flexibility in working hours, and believe the right balance between your personal and professional life is key to long-term fulfilment. Amazon offers a competitive package including shares, sign-on bonus, and benefits. Also include Diverse Experiences statement: AWS values diverse experiences. Even if you do not meet all of the 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 apply.
We could put that under About the role or a separate section "About the Team". But headings list does not include About the Team; only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should incorporate team info into About the role or maybe Responsibilities? Probably About the role is appropriate to include overview of team and role.
Thus About the role will contain: description of AWS Plus, role, team, diverse experiences, work-life balance, etc.
Now we need to ensure we don't include boilerplate like "If you have a disability and need a workplace accommodation..." etc. Remove that.
Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe we can keep as part of Benefits but it's a link; could be considered application instruction? It's not exactly instruction to apply but a link for more info. Might be okay to keep but maybe safer to omit as it's not substantive detail? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The link is substantive? It's a reference. Might be okay to keep but it's not essential. I'd keep the benefits description but maybe drop the link.
Now produce HTML.
Structure:
for each section we include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly Skills we could combine some skill statements from qualifications? But we have Requirements (basic qualifications) and Qualifications (preferred). Skills maybe we can include "Knowledge of cloud architecture", "Knowledge of software development tools and methodologies". However those are already in qualifications. Might be redundant. Better to not create Skills section if no distinct skill list beyond those. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills.
Thus sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay.
Check for duplicated content: "About The Team" appears twice; we need to merge and avoid duplication. We'll combine the team description: AWS Plus is a dedicated account team that supports Amazon's own business units as strategic AWS customers. Our customers span Amazon's consumer, media, devices, operations, and corporate businesses, and together they represent some of the largest AWS deployments in the world. We work alongside aligned Customer Solutions Managers, AWS Support, and AWS service teams to make Amazon a strong reference for running on AWS at scale. We value work-life balance, offer flexibility in working hours, and believe the right balance between your personal and professional life is key to long-term fulfilment. Amazon offers a competitive package including shares, sign-on bonus, and benefits. Also include Diverse Experiences statement: AWS values diverse experiences. Even if you do not meet all of the 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 apply.
We could put that under About the role or a separate section "About the Team". But headings list does not include About the Team; only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should incorporate team info into About the role or maybe Responsibilities? Probably About the role is appropriate to include overview of team and role.
Thus About the role will contain: description of AWS Plus, role, team, diverse experiences, work-life balance, etc.
Now we need to ensure we don't include boilerplate like "If you have a disability and need a workplace accommodation..." etc. Remove that.
Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe we can keep as part of Benefits but it's a link; could be considered application instruction? It's not exactly instruction to apply but a link for more info. Might be okay to keep but maybe safer to omit as it's not substantive detail? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The link is substantive? It's a reference. Might be okay to keep but it's not essential. I'd keep the benefits description but maybe drop the link.
Now produce HTML.
Structure:
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
... salary range and sign-on payments/RSUs ...
Make sure not to include any extra text outside HTML. Now craft content. About the role paragraph(s): We can combine: "AWS Plus is a specialized account team within AWS that supports Amazon's own business units as strategic cloud customers. As a Senior Solutions Architect on this team, you'll be the primary technical advisor to one or more of Amazon's businesses, working directly with their engineering teams and technology leaders to design, operate, and optimize AWS workloads at a scale few external customers ever reach.