Senior Solutions Architect, Fintech, Fintech

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the description. Let's extract sections: - About the role: The description starts with "Description AWS Global Sales drives adoption..." That's about the role? Actually it's about AWS Global Sales and Solutions Architect team. Could be "About the role". We'll treat that as About the role. - Responsibilities: "Key job responsibilities" list bullet points. - About The Team: maybe not required but could be part of About the role? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule if they have content. - Basic Qualifications: that's Requirements? Or Qualifications? Usually Basic Qualifications are Requirements. Preferred Qualifications are Qualifications or Skills? Might treat Basic Qualifications as Requirements, Preferred Qualifications as Qualifications (or Skills). We'll decide. - Skills: maybe not explicit; we could infer from responsibilities but better not to invent. If no explicit skills list, we skip Skills section. - Benefits: there is a paragraph about benefits: "Amazon also offers comprehensive benefits including health insurance..." plus link. So we can include Benefits. - Pay: there is base salary range listed for multiple locations. That's pay info. So include Pay. - Schedule: travel is mostly regional, expected 15-20%. That's schedule info (travel). So include Schedule. We must not include placeholder like "commensurate with experience". Not present. We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep the bullet points exactly as given? We can keep them but maybe rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can reformat. Probably we should keep the text as is, maybe copy bullet points. We need to output only HTML fragment, no html/body tags, no markdown fences. Let's craft:

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.

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%

But note travel is also schedule; we might keep it in responsibilities but also schedule section. However we should not duplicate content. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication might be okay but better to avoid duplication. Travel is a responsibility? It's more schedule. We could keep travel under Schedule section and not duplicate. But responsibilities list includes travel as a bullet. If we move it to Schedule, we would be omitting from responsibilities. That would lose detail. Better to keep it in responsibilities and also maybe not have separate Schedule? But we need Schedule section if posting actually states them. It does state travel expectation. So we need Schedule section. We could keep travel bullet under Responsibilities and also include Schedule section with same info? That would duplicate. Perhaps we can keep travel under Schedule and remove from responsibilities, but then we lose that responsibility detail. However the responsibility list includes travel as a bullet; maybe it's considered a responsibility (travel). The schedule section could be about work schedule (e.g., full-time, remote). Travel is more about schedule. The instruction: "include a section ONLY when the posting has real, specific content for it". Travel is specific content for schedule. So we should have Schedule section. We could keep travel bullet under Responsibilities as it's also a responsibility (travel). But to avoid duplication, we could keep travel bullet only under Schedule and not under Responsibilities. However the responsibilities list originally includes travel; if we remove it, we are omitting that piece of information from responsibilities. But we could keep responsibilities without travel and still have the other responsibilities. The travel is still captured under Schedule. That preserves all info (just moved). That seems acceptable. Thus responsibilities list without travel bullet. Now Requirements: Basic Qualifications. We need to list them as

• . The basic qualifications are: - 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 We should preserve exactly. Now Qualifications: Preferred Qualifications. List: - 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 Now Skills: Not explicitly listed; we could skip. Benefits: paragraph about benefits. We need to include the benefits 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." Also earlier mention: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's part of compensation but could be under Pay or Benefits. We'll include under Benefits maybe. Pay: base salary ranges for locations. We need to include all location ranges. List: - USA, CA, San Francisco - 176,600.00 - 239,000.00 USD annually - USA, MA, Boston - 153,600.00 - 207,800.00 USD annually - USA, NY, New York - 169,000.00 - 228,600.00 USD annually - USA, VA, Arlington - 153,600.00 - 207,800.00 USD annually - USA, WA, Bellevue - 153,600.00 - 207,800.00 USD annually We should preserve. Schedule: Travel is mostly regional, expected to be 15-20%. Now we need to ensure we don't include boilerplate like EEO, equal opportunity, etc. Remove those paragraphs. Also remove "Los Angeles County applicants:" etc. Also remove "Criminal history may have a direct..." etc. Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10558636". Also remove "Amazon is an equal opportunity employer..." etc. Now produce HTML. Let's craft:

  About the role

  ... (the paragraph)

  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.

  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

  Benefits

  Your Amazon package will include sign-on payments and restricted stock units (RSUs). 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.

  Pay

  • USA, CA, San Francisco - 176,600.00 - 239,000.00 USD annually
  • USA, MA, Boston - 153,600.00 - 207,800.00 USD annually
  • USA, NY, New York - 169,000.00 - 228,600.00 USD annually
  • USA, VA, Arlington - 153,600.00 - 207,800.00 USD annually
  • USA, WA, Bellevue - 153,600.00 - 207,800