Senior Solutions Architect, Fintech, Fintech

We need to output HTML fragment with sections: About the role (description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse. Description: first paragraph about AWS Global Sales, then about Solutions Architect team. That's description. Responsibilities: list under "Key job responsibilities". Items: Communicate effectively..., Participate..., Author..., In partnership..., Build deep..., Capture..., Travel is mostly regional, and is expected to be 15-20% (maybe part of responsibilities). So we can include responsibilities list. Requirements: Basic Qualifications list (three bullet points). Also Preferred Qualifications list (three bullet points). Could combine as Requirements? The instruction: Use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections to include. We have description (About the role). Responsibilities we have. Requirements: Basic Qualifications (maybe as Requirements). Qualifications: Preferred Qualifications? Or we could treat Basic Qualifications as Requirements and Preferred Qualifications as Qualifications. Skills: maybe not explicit; we could infer from qualifications but not explicit list. Benefits: there is a paragraph about benefits: "Amazon also offers comprehensive benefits including health insurance ... 401(k) matching, paid time off, and parental leave." Also mention sign-on payments and RSUs. So we have benefits content. Pay: Salary ranges listed for various locations. So we have pay info. Schedule: Travel is mostly regional, expected 15-20% - that could be schedule? But schedule maybe not explicit; travel percentage could be considered schedule? However schedule section is for work schedule like full-time, part-time, remote, etc. Not present. Travel is more about responsibilities. So we likely omit Schedule. We must not include sections with filler like "commensurate with experience". We have actual salary ranges, so Pay section is valid. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate like EEO, legal, etc. We need to preserve all substantive information. So we need to include all bullet points from Basic Qualifications, Preferred Qualifications, responsibilities, benefits, pay ranges, description. We need to format as HTML: use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide which content goes into which section. Let's outline:

  About the role

  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 unwavering 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. The Amazon Web Services (AWS) Solutions Architect team partners with customers to design and build some of the most scalable, flexible and resilient cloud architectures and solutions. AWS Solutions Architects collaborate with AWS Sales and other AWS teams to help address customer business challenges and accelerate the adoption of AWS services. As a trusted customer advocate, Solutions Architects help organizations understand best practices around advanced cloud-based solutions, and provide advice on strategies for migrating existing workloads to the cloud. You’ll help drive successful business outcomes across a broad set of enterprise customers through your passion for educating, training, designing and building cloud solutions. You will have the opportunity to help shape and execute a strategy to build deep adoption and broad use of AWS within your enterprise customers, and you will do this by mobilizing resources within AWS and working with our extensive partner network.

  That seems good.

  Responsibilities

  • Communicate effectively with both business and technical stakeholders as a trusted technical advisor.
  • Participate in deep architectural and design discussions to create world-class solutions built on AWS while ensuring solutions are designed for successful deployment in the cloud.
  • Author and contribute to AWS customer-facing publications such as whitepapers and proof of concepts.
  • In partnership with the sales team, formulate and execute a sales strategy to exceed revenue objectives through the adoption of AWS.
  • Build deep relationships with business and senior technical individuals within customers to enable them to be cloud advocates.
  • Capture and share best-practice knowledge amongst the AWS solutions architect community.
  • Travel is mostly regional, and is expected to be 15-20%.

  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

  Qualifications

  • 5+ years of infrastructure architecture, database architecture and networking experience
  • Experience working with end user or developer communities
  • Proven experience as a technical builder or leader in the Financial Services Industry
  We might also include Skills? Not explicit; we could skip.

  Benefits

  • Sign-on payments and restricted stock units (RSUs)
  • 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
  • Parental leave
  We could also mention "Learn more about our benefits at https://amazon.jobs/en/benefits." but that's a link; maybe include as prose? It's not essential but could be included. However instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is substantive? It's a reference. Could include as

  Learn more about our benefits at amazon.jobs/en/benefits.

  But we are not supposed to add markdown; HTML is fine. However we might avoid links to keep simple. The instruction didn't forbid links. But we can include as

  Learn more about our benefits at https://amazon.jobs/en/benefits.

  . That's prose.

  Pay

  USA, CA, San Francisco - $176,600.00 - $239,000.00 annually

  USA, MA, Boston - $153,600.00 - $207,800.00 annually

  USA, NY, New York - $169,000.00 - $228,600.00 annually

  USA, VA, Arlington - $153,600.00 - $207,800.00 annually

  USA, WA, Bellevue - $153,600.00 - $207,800.00 annually

  We could also mention base salary range and that final compensation based on experience etc. That's substantive. Could add a 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." That's from the text. Should we include? Yes, it's substantive. So include as

  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.

  then the list. We need to ensure we don't repeat info. Already have sign-on payments in Benefits; but it's okay to mention again in Pay section? Might be duplication but it's from original text. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in original. However we should avoid unnecessary duplication? Not prohibited. But we could keep it once. However the base salary description includes sign-on payments and RSUs; we already have them in Benefits. Might be okay to keep in Pay section as part of description. We'll include it. Now check for any other substantive content: "Diverse Experiences" section about encouraging candidates to apply even if not meet all qualifications. That's substantive? It's encouraging to apply. Could be part of About the role or a separate section like "About the Team". There's a heading "About The Team". The content includes "Diverse Experiences", "Why AWS?", "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance". Those are substantive. Should we include them? According to instruction, we should include sections only when posting has real, specific content for it. We have content for "About the Team". Could create a section "About the Team" but not in the prescribed headings list. The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not include About the Team. However we could incorporate that content into About the role or maybe treat as part of About the role. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning examples, not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create other headings like About the Team. We should fold that content into existing sections, perhaps About the role or maybe Benefits? But it's about team culture, mentorship, work-life balance. Could be part of Benefits? Not exactly. Could be part of About the role? Might be okay to include as a paragraph under About the role after the description. That would preserve the info. Thus we need to incorporate "Diverse Experiences", "Why AWS?", "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance" into About the role section. Let's extract that content: "About The Team 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