Solutions Architect, Commercial Midmarket

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 must not repeat job title as heading. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Keep substantive info. We need to parse the description. Key sections: Description (intro) maybe "About the role" or similar. The posting includes description paragraphs about AWS Global Sales, Solutions Architect role, etc. Then "Key job responsibilities" list. Then "A day in the life" narrative. Then "About The Team" with subpoints: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Then "Basic Qualifications" list. Then "Preferred Qualifications" list. Then salary/pay info: "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 ...". Also location salary ranges: USA, IL, Chicago - 131,300.00 - 177,600.00 USD annually etc. Thus we have Pay section (salary range). Benefits section (list of benefits). Schedule? Not mentioned. So we omit Schedule. We need to decide headings: "About the role" (intro), "Responsibilities", "Qualifications" (maybe combine Basic and Preferred?), "Skills"? Not explicit. Could have "Basic Qualifications" and "Preferred Qualifications" as subheadings under Qualifications? But rule: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also "Skills" if we have skills list; but not explicit. Could embed skills in responsibilities. We must not create sections with filler. So we include only those with content. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need
  . For qualifications list (basic and preferred) we need
  . For benefits list we need
  . For pay we can just have

  with salary ranges. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them. We need to remove boilerplate: EEO, accommodation link, etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "Learn more about our benefits at https://..." maybe we can keep mention but not the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link might be considered navigation? It's a link to learn more; maybe we can keep the sentence but drop the URL? Safer to remove the link entirely, but we need to preserve substantive info: "Amazon also offers comprehensive benefits including ..." that's substantive. The link is not substantive; we can drop it. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Company - Amazon Web Services, Inc. Job ID: A10558638" (metadata). Also remove "USA, IL, Chicago - 131,300.00 - 177,600.00 USD annually" etc? That's pay info, we need to keep. We need to keep location salary ranges: three locations with same range. Could list them. Now craft HTML. Structure:

  About the role

  ... intro paragraphs ...

  Then

  Responsibilities

  • ... each responsibility ...
  We have responsibilities list: "Key job responsibilities" bullet points: - Serve as a key member of the Solutions Architecture team in helping to ensure customer success in building applications and services on the AWS platform. - Scope each customer engagement, with attention towards clear and well-defined objectives and success criteria. - Own each engagement, and help ensure a timely and successful delivery of value. - Capture and share best-practice knowledge amongst the solution architect community. - Understand the AWS market segments, customer base, and industry verticals. - Understand and use of salesforce.com and other internal Amazon systems. Also "A day in the life" narrative could be part of responsibilities or separate section? Could be under "About the role" or separate "Typical day". But we only have allowed headings; we could include it under About the role as prose. Thus About the role includes the initial description paragraphs plus "A day in the life" paragraph. Now Qualifications: we have Basic Qualifications and Preferred Qualifications. Could combine under Qualifications heading with two sublists? But we only have

  headings; we could have

  Qualifications

  then maybe

  Basic Qualifications

  but not allowed? The instruction only mentions using

  for section headings; doesn't forbid other headings, but we should stick to

  for sections. Could embed Basic and Preferred as

  with bold? But better to keep as

  with items prefixed? Might be okay to have two separate

  sections: Basic Qualifications and Preferred Qualifications? But the allowed list includes Qualifications (singular). Could treat Basic and Preferred as sub-sections under Qualifications using

  or . However we need to preserve all detail; we can list them as separate

  with headings

  Basic Qualifications:

  then list. But the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but to be safe we can use

  for each major section: About the role, Responsibilities, Qualifications, Benefits, Pay. Within Qualifications we can have two

  headings (like Basic Qualifications:) then

  . Similarly Benefits: we have list of benefits. Pay: we have salary ranges and mention of sign-on payments and RSUs. Now craft. We need to ensure we don't include any boilerplate like "Amazon is an equal opportunity employer..." etc. Let's extract substantive paragraphs. Intro: "AWS Global Sales drives adoption of the AWS cloud worldwide, enabling customers of all sizes to innovate and expand in the cloud. Our team empowers every customer to grow by providing tailored service, unmatched technology, and committed support. We dive deep to understand each customer's unique challenges, then craft innovative solutions that accelerate their success. This customer-first approach is how we built the world's most adopted cloud. Join us and help us grow. Amazon Web Services is looking for a highly motivated Solutions Architect to help accelerate customer adoption. This is an excellent opportunity to join Amazon’s world class technical teams, working with some of the best and brightest engineers, architects and technical managers while also developing your skills and furthering your career within one of the most innovative and progressive technology companies anywhere. As a Solutions Architect in the AWS Commercial Midmarket group you will work directly with Small and Medium Business customers. We are looking for individuals who are motivated by the opportunity to work backwards from these customers' needs and help them gain competitive edge using AWS. As an experienced technologist and key member of the Account team you will help influence customers' architectural choices across broad use cases involving security, compute, storage networking as well as advanced scenarios involving serverless, analytics, and AI/ML. As a part of the role, you will provide exceptional technical design guidance and thought leadership. You will lead efforts to capture and share best-practice knowledge with the AWS solution architect community. You will also gain the opportunity to learn from, collaborate with, and educate some of the brightest technical minds in the industry today across the breadth of enterprise architecture." That's the intro. Then "A day in the life" paragraph: "A typical day as an AWS Solutions Architect blends strategic customer engagements with technical deep-dives. You might start with a workshop helping a customer architect their generative AI solution, followed by collaborating with account teams to develop approaches for an upcoming migration project. After lunch, you'll lead a technical discovery session with a customer exploring analytics solutions, then spend time reviewing architectural designs and providing best practice guidance. The day might end with contributing to internal knowledge-sharing sessions or preparing for upcoming customer presentations. Each day brings unique challenges and opportunities to help customers innovate on AWS." Now responsibilities list as above. Now About The Team section: includes subpoints: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Each has prose. We could incorporate this into About the role or maybe a separate section "About the team". But allowed headings don't include About the team; we could put under About the role as well. However we have a lot of content; maybe we create a section "About the team" using

  About the team

  though not in list but maybe acceptable? The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive list. So we can add other headings like About the team. Safer to include it as a section. Thus we can have sections: About the role, Responsibilities, About the team, Qualifications, Benefits, Pay. Now About the team content: "Diverse Experiences AWS 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." "Why AWS? 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 AWS values curiosity and connection. Our employee-led and company-sponsored affinity groups promote inclusion and empower our people to take pride in what makes us unique. Our inclusion events foster stronger, more collaborative teams. Our continual innovation is fueled by the bold ideas, fresh perspectives, and passionate voices our teams bring to everything we do." "Mentorship & Career Growth 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 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." Now Qualifications: Basic Qualifications list: - 2+ years of design, implementation, or consulting in applications and infrastructures experience - 4+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience - 10+ years of IT development or implementation/consulting in the software or Internet industries experience Preferred Qualifications