Senior Solutions Architect, AWS Plus Team

for prose. Do not repeat job title. Do not include Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "About The Team" duplicated? There's "About The Team" appears twice; we need to keep content but not duplicate headings? Probably combine. We need to preserve all substantive information. Let's parse description. Sections: - Description (intro paragraph): "What if your customer was Amazon itself? ..." This is introductory prose. - Key job responsibilities: list of responsibilities. - A day in the life: prose. - About The Team: description of team. - Diverse Experiences: paragraph about encouraging applicants. - Why AWS?: paragraph about AWS. - Inclusive Team Culture: paragraph. - Mentorship & Career Growth: paragraph. - Work/Life Balance: paragraph. - BASIC QUALIFICATIONS: list. - PREFERRED QUALIFICATIONS: list. - Compensation and benefits: includes base salary range, sign-on payments, RSUs, benefits list. We need sections only when posting has real specific content. All these have content. We must not include sections like Pay/Schedule/Benefits unless posting actually states them. It does state base salary range and benefits, so we can include a Benefits section (maybe combine Pay and Benefits). The instruction: "Prefer a few substantive sections over many thin ones." Could combine some. But we need to follow rule: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use appropriate headings. Likely we should use headings like "Responsibilities", "Qualifications", "Benefits", etc. Use exactly those headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings; we should use them when appropriate. So we need sections: Responsibilities, Qualifications (maybe split Basic and Preferred), Benefits, About the Team? Not in list but could be "About the Team". The examples are not exhaustive; we can use other headings as needed but must be

. Probably safe to use headings: Responsibilities, A Day in the Life, About the Team, Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance, Basic Qualifications, Preferred Qualifications, Benefits. But to keep few sections, we could combine some. However instruction: "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. Could combine "About the Team", "Diverse Experiences", "Why AWS?", "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance" into a single "About AWS" section? But they are distinct topics; combining may lose specificity. However we must preserve all substantive information; we can still preserve by including paragraphs under a combined heading. That's okay. Let's think: The posting includes multiple sections about culture etc. Could combine into "About AWS" with sub-paragraphs. But the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create a section for each distinct heading if there is content. It's okay to have many sections as long as each has content. The "prefer a few substantive sections over many thin ones" is a suggestion, not a hard rule. We'll try to keep reasonable number. Maybe we can have sections: Responsibilities, A Day in the Life, About the Team, Qualifications, Benefits. Within About the Team we can include subpoints about diverse experiences, why AWS, inclusive culture, mentorship, work-life balance. Qualifications can include Basic and Preferred as sublists. Benefits can include salary range and benefits list. Let's craft. We need to output only HTML fragment, no /, no markdown. We'll produce:

Responsibilities

• ... each responsibility

A Day in the Life

... paragraph

About the Team

... description of AWS Plus team

... Diverse Experiences paragraph

... Why AWS? paragraph

... Inclusive Team Culture paragraph

... Mentorship & Career Growth paragraph

... Work/Life Balance paragraph

Qualifications

Basic Qualifications

...

Preferred Qualifications

...

for section headings, not

. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we should only use

. So we cannot use

. We could embed Basic and Preferred as or just as paragraphs with bold text. But we need to use

• for lists. So we can have a

  Qualifications

  then inside we can have two

  with bold headings? Or we could make two separate sections: Basic Qualifications and Preferred Qualifications each as

  . That would be okay: each heading is a section. So we will have separate sections: Basic Qualifications and Preferred Qualifications. Similarly Benefits could be its own

  . Thus sections: Responsibilities, A Day in the Life, About the Team, Basic Qualifications, Preferred Qualifications, Benefits. Now we need to extract content. Let's copy relevant text. Intro paragraph before responsibilities: "What if your customer was Amazon itself? 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." That's the description; we can put as introductory

  before any heading? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It didn't say we cannot have an intro paragraph before sections. Probably okay to have a leading

  summarizing the role. We'll include that as first

  . Then Responsibilities: list items: - 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. We'll put each as

  . A day in the life paragraph: "You'll work directly with the engineering teams behind one of Amazon's businesses, who run some of the largest workloads on AWS. That might mean an architecture review on a multi-region design one morning, a cost optimization deep dive in the afternoon, and a working session with an AWS service team on a customer feature request in between. You'll meet regularly with VP- and Director-level technology stakeholders, surface customer feedback to AWS product teams, and help shape how Amazon's internal businesses adopt new AWS capabilities. Your ability to go deep on your customer's domain is what earns you credibility." About The Team paragraph: "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." Then Diverse Experiences paragraph: "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? paragraph: "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." Inclusive Team Culture paragraph: "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 (diversity) conferences, inspire us to never stop embracing our uniqueness." Mentorship & Career Growth paragraph: "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." Work/Life Balance paragraph: "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" Note: The last sentence cut off: "in the clou". Probably typo; we keep as is. Now 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 We need to keep exactly as written. Preferred Qualifications list: - 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 Now Benefits section: includes base salary range, sign-on payments, RSUs, benefits list. Paragraph: "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