UX Designer, AWS Field Experience

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. The posting includes description, responsibilities, qualifications, preferred qualifications, benefits, pay (salary range), schedule? Not explicit schedule. There's mention of work/life balance, flexibility, but not explicit schedule. Probably we should not include Schedule unless explicit. Benefits: they mention comprehensive benefits list. So include Benefits section. Pay: they list salary ranges for locations. So include Pay section. About the role: we have description at top. Responsibilities: "Key job responsibilities" bullet list. Requirements: "Basic Qualifications". Qualifications: maybe "Preferred Qualifications". Skills: maybe we can combine? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to include those with content. For Skills, we could extract from qualifications: "Highly proficient using design software and AI tools. Hands-on experience creating user flows, lo/high fidelity designs, and prototypes. Familiarity with interaction design, agentic experience design and information architecture. Working knowledge of responsive design, design systems and grid principles." Also "Knowledge of basic front end languages (HTML/CSS, Javascript)." So we can put Skills section. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, accommodations, etc. Also remove "Inclusive Team Culture", "Work/Life Balance", "Mentorship & Career Growth", "About The Team" maybe those are not required headings but could be part of About the role? The instruction: use headings for those specific section names. We should include only those headings if we have content. We could put some of that descriptive text under About the role. But we must preserve all substantive information; we cannot discard details like inclusive culture etc. However we can embed them under About the role as prose. That's okay. We need to output only HTML fragment, no markdown fences. Let's structure:

About the role

... description ...

Responsibilities

• ... each responsibility ...

Requirements

• ... basic qualifications ...

Qualifications

• ... preferred qualifications ...

Skills

• ... skills ...

Benefits

• ... benefits list ...

Pay

... salary ranges ...

We should not include Schedule. Now extract content. About the role: The initial paragraph: "AWS Field Experience (AFX) is looking for an innovative UX Designer who wants to help set direction for a strategic AWS initiative supporting a rapidly growing world-wide AWS Sales organization. We are looking for someone who will obsess over delivering the best experience for customers and thrives on the challenge of designing something new that will operate at worldwide scale. As a successful candidate, you will have a deep understanding of design thinking methodology, and interaction design, designing for and with AI, along with top-notch communications skills. You will take a nimble, creative and pragmatic approach and will possess endless curiosity and passion for delivering customer-focused experiences. As a storyteller, you will influence the business strategy by depicting experiences that demonstrate empathy for users and an innate understanding of their ‘day-to-day’. You will design at pace, balance multiple priorities, and show good judgment when weighing trade-offs. You will be able to distill customer needs from many diverse inputs and provide the clarity needed to solve complex business problems. You will work autonomously, build relationships outside of your immediate team, and demonstrate excellent stakeholder management skills. You will be seen as an expert in your discipline and play a significant role in leading the creative process and advocating for design excellence." We can keep that as prose. Responsibilities: The bullet list under "Key job responsibilities". Let's extract each sentence: - Provide designs for new and existing solutions in consideration of the end-to-end experience from big picture conception to execution. - You will be responsible, alongside design leadership, negotiating priorities, achieving alignment on customer problems and product vision. - You should be comfortable with designing complex workflows and balancing divergent user perspectives, across a variety of technologies. - Be a self starter and be able to work independently, while actively collaborating and communicating with cross-functional teams, peer designers, management and stakeholders. - You will be responsible for building and maintaining healthy and positive relationships with all stakeholders and end users. - Understand the holistic experience and produce designs that integrate seamlessly into our agentic experiences. - You will also identify measures that capture the health of the user experience (quantitatively and qualitatively) and actively pursue new opportunities to work backwards from user needs. - Help scale design processes and mechanisms raising the bar on design quality. Also there is "A day in the life" but that's more culture; we could incorporate into About the role or maybe ignore as not under a heading. But we must preserve all substantive information; we could include that under About the role as additional prose. However the instruction: "Prefer a few substantive sections over many thin ones." So we could merge "A day in the life", "Inclusive Team Culture", "Work/Life Balance", "Mentorship & Career Growth", "About The Team" into About the role as prose. That preserves info. Thus About the role will be longer. Now Requirements: Basic Qualifications list: - 5+ years of design experience - Bachelor's degree or above in design, human-computer interaction (HCI) - Have a portfolio demonstrating past work experience and deliverables (e.g., study plans, reports, personas) - A strong foundation and understanding of design thinking practices, and usability principles and techniques. - Highly proficient using design software and AI tools. - Hands-on experience creating user flows, lo/high fidelity designs, and prototypes. - Familiarity with interaction design, agentic experience design and information architecture. - Working knowledge of responsive design, design systems and grid principles. We'll put each as

. Qualifications: Preferred Qualifications list: - Strong problem solving aptitude, business acumen and a natural curiosity for how experiences come together. - Extremely proactive; takes personal ownership for producing positive results. - Strong interpersonal skills, ability to quickly build rapport and establish credibility. - Strong communication and presentation skills; experience presenting complex ideas to customers and colleagues in compelling and actionable ways. - The ability to thrive in a fast-paced work environment that requires independent self-direction, excellent time management, strong attention to detail and an aptitude for team collaboration. - Demonstrated experience performing user research, and crafting persona or jobs to be done. - A team player with experience working in an Agile software development process. - Knowledge of basic front end languages (HTML/CSS, Javascript). We'll put as

. Skills: Could be derived from both but we already used many. However we need a Skills section; we could list specific skills like: design thinking, interaction design, AI-integrated design, user flows, prototyping, responsive design, design systems, grid principles, front-end languages (HTML/CSS, Javascript), stakeholder management, storytelling, etc. But we must not invent; we need to extract from posting. The posting already mentions many skills in qualifications. To avoid duplication, we could still create Skills section with those items that are explicitly skill-based: "Highly proficient using design software and AI tools.", "Hands-on experience creating user flows, lo/high fidelity designs, and prototypes.", "Familiarity with interaction design, agentic experience design and information architecture.", "Working knowledge of responsive design, design systems and grid principles.", "Knowledge of basic front end languages (HTML/CSS, Javascript).", "Strong communication and presentation skills.", "Strong interpersonal skills.", "Strong problem solving aptitude.", etc. However that duplicates content from Requirements/Qualifications. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication across sections, but we should avoid unnecessary duplication? It didn't forbid. However better to keep each piece only once. But we need a Skills section; we could move some skill items there and remove from Requirements/Qualifications? But then we would lose those details from those sections. The instruction says preserve ALL substantive information; we can move them but still preserve. So we could reassign: Requirements = basic qualifications (education, experience, portfolio). Qualifications = preferred qualifications (behavioral, experience). Skills = technical skills (design software, prototyping, interaction design, responsive design, front-end languages). That seems reasonable and avoids duplication. Thus: Requirements (Basic Qualifications): - 5+ years of design experience - Bachelor's degree or above in design, human-computer interaction (HCI) - Have a portfolio demonstrating past work experience and deliverables (e.g., study plans, reports, personas) Qualifications (Preferred Qualifications): - Strong problem solving aptitude, business acumen and a natural curiosity for how experiences come together. - Extremely proactive; takes personal ownership for producing positive results. - Strong interpersonal skills, ability to quickly build rapport and establish credibility. - Strong communication and presentation skills; experience presenting complex ideas to customers and colleagues in compelling and actionable ways. - The ability to thrive in a fast-paced work environment that requires independent self-direction, excellent time management, strong attention to detail and an aptitude for team collaboration. - Demonstrated experience performing user research, and crafting persona or jobs to be done. - A team player with experience working in an Agile software development process. - Knowledge of basic front end languages (HTML/CSS, Javascript). Skills: - A strong foundation and understanding of design thinking practices, and usability principles and techniques. - Highly proficient using design software and AI tools. - Hands-on experience creating user flows, lo/high fidelity designs, and prototypes. - Familiarity with interaction design, agentic experience design and information architecture. - Working knowledge of responsive design, design systems and grid principles. Now Benefits: The paragraph: "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'll put as

• ... each benefit? Could be one li with the whole sentence. But better to split: health insurance (list), 401(k) matching, paid time off, parental leave. However we must not invent. The sentence includes health insurance details; we can keep as one li. That's fine. Pay: The salary ranges: "USA, MA, Boston - 117,800.00 - 160,000.00 USD annually USA, TX, Dallas - 117,800.00 - 160,000.00 USD annually USA, WA, Seattle - 117,800.00 - 160,000.00 USD annually". We'll put as

  ... maybe list each location. We should also include the note about sign-on payments and RSUs: "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." That's substantive; include in Pay section. Now About the role: We'll combine the initial description plus the "A day in the life", "Inclusive Team Culture", "Work/Life Balance", "Mentorship & Career Growth", "About The Team". Let's extract those paragraphs. "A day in the life" heading but no content under it? Actually after "Key job responsibilities" there is "A day in the life" then "Inclusive Team Culture". The text after "A day in the life"