Banking Sr Solutions Architect, Worldwide Financial Services
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide what goes where.
"About the role": could be the initial description paragraph(s) before "Key job responsibilities". That includes: "The Amazon Web Services (AWS) Worldwide Financial Services team is looking for a Banking industry senior solution architect to join our fast-paced team and help drive worldwide AWS adoption in banking globally. As a Worldwide Banking Solution Architect, you will be part of a team focused on accelerating technology adoption of cloud computing, working with C-level and line of business executives across our customers, and internally with sales and marketing, partner, product teams and AWS senior leadership to meet our customers’ needs. You will drive new business in Banking, leading the organization as a whole to effectively sell into that industry, developing programs to accelerate our customers’ moves from legacy on-premises environments to AWS-based services. Your specialized industry knowledge and expertise bridges businesses and technology, and you understand the regulatory and compliance environment that our customer base operates in. You speak the language of our customers, mapping their business and regulatory needs to AWS services and partner-led solutions, defining reference architectures, and building industry facing accelerators, APIs, and demonstrable solutions."
That's prose; we can put in
.
"Responsibilities": list under "Key job responsibilities". Those are bullet-like sentences each starting with a verb. We'll put each as
- .
"Requirements": maybe Basic Qualifications. Those are bullet points: "Experience in IT development or implementation/consulting in the software or Internet industries", "Experience within specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics).", "Experience migrating or transforming legacy customer solutions to the cloud", "Experience in design, implementation, or consulting in applications and infrastructures", "Experience communicating across technical and non-technical audiences, including executive level stakeholders or clients". We'll put as
- .
"Qualifications": maybe Preferred Qualifications: "Knowledge of cloud architecture", "Experience in infrastructure architecture, database architecture and networking", "Experience working with end user or developer communities". We'll put as
- .
"Skills": Not explicitly listed; maybe we could infer but we should not create unless posting has real specific content. There's no explicit skills list. So omit Skills section.
"Benefits": The posting mentions: "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." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation but could be part of Pay. Benefits section: we can include the comprehensive benefits list. We'll put as
- .
"Pay": base salary range and sign-on payments and RSUs. So we can put in
maybe with details.
"Schedule": not present, omit.
We also have "About The Team" section with subpoints: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This is more about team/culture. Could be considered part of "About the role" or maybe a separate section like "About the team". But headings list only includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the team". We could incorporate that content into About the role or maybe into a separate section not in list? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should only emit those headings if posting has real specific content for them. It didn't forbid other headings, but likely they expect only those. Safer to stick to those headings and fold team info into About the role or maybe Benefits? Probably About the role can include team description.
Thus we can expand About the role paragraph to include team description details.
We must not repeat job title as heading. No Job ID.
We must 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 keep benefits description but not the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is maybe navigation; we can drop the link but keep the benefits description.
Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." etc.
Also remove "Company - Amazon Web Services, Inc." maybe not needed.
We need to preserve all substantive information: so keep the description, responsibilities, qualifications, benefits, pay.
Now produce HTML fragment.
Structure:
About the role
... (combined description and team info)
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
...
No Schedule.
Make sure to not include empty sections.
Now craft the content.
About the role paragraph: combine initial description and team info.
Initial description: "The Amazon Web Services (AWS) Worldwide Financial Services team is looking for a Banking industry senior solution architect to join our fast-paced team and help drive worldwide AWS adoption in banking globally. As a Worldwide Banking Solution Architect, you will be part of a team focused on accelerating technology adoption of cloud computing, working with C-level and line of business executives across our customers, and internally with sales and marketing, partner, product teams and AWS senior leadership to meet our customers’ needs. You will drive new business in Banking, leading the organization as a whole to effectively sell into that industry, developing programs to accelerate our customers’ moves from legacy on-premises environments to AWS-based services. Your specialized industry knowledge and expertise bridges businesses and technology, and you understand the regulatory and compliance environment that our customer base operates in. You speak the language of our customers, mapping their business and regulatory needs to AWS services and partner-led solutions, defining reference architectures, and building industry facing accelerators, APIs, and demonstrable solutions."
Team info: "About the team Diverse Experiences 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? 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 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 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 in the cloud."
We can combine into a paragraph or multiple paragraphs. Use for prose; could be multiple
under same heading? Probably one
with multiple sentences is fine.
Now Responsibilities list: extract each bullet.
From "Key job responsibilities":
- Serve as a key member of the Worldwide Banking team in helping to drive AWS marketing, sales, and technical strategies for the Banking industry
- Coach sales teams on AWS services relevant to banking customers
- Understand the unique technical requirements of banking customers, and work closely with the internal teams to guide the direction of the adoption of AWS services for our largest and most complex customers
- Work directly with customers to accelerate their business outcomes and recommend best-practice cloud architectures in line with their long-term business needs.
- Drive technical solutions discussions with your customers, diving deep into the details to solve complex technical challenges and use your knowledge to craft scalable, flexible, and resilient cloud architectures.
- Define and execute on the strategy by engaging highly technical teams (Solutions Architects, Technical Account Managers, AWS professional services consultants and consulting/managed services partners).
- Act as a thought leader in the wider community, playing a key role in educating, sharing best practices, presenting at events, writing white papers, blogs, and running workshops.
- Share the voice of the customer to influence the roadmap of new features and services for the AWS platform.
- Proactively work within the organization to influence the evolution of the platform.
- Scope and own customer engagements, with attention towards clear and well-defined objectives and success criteria.
- Work backwards from your customer's business needs to accelerate adoption of the most appropriate AWS technology
- Serve as a key technical member of the Solutions Architecture team through influencing decision makers across multiple domains to ensure customer success in building applications and services on the AWS platform which align to long-term business goals
Make sure each ends with period maybe.
Now Requirements (Basic Qualifications):
- Experience in IT development or implementation/consulting in the software or Internet industries
- Experience within specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics).
- Experience migrating or transforming legacy customer solutions to the cloud
- Experience in design, implementation, or consulting in applications and infrastructures
- Experience communicating across technical and non-technical audiences, including executive level stakeholders or clients
Now Qualifications (Preferred Qualifications):
- Knowledge of cloud architecture
- Experience in infrastructure architecture, database architecture and networking
- Experience working with end user or developer communities
Now Benefits: list items from description:
- health insurance (medical, dental, vision, prescription, Basic
for prose. We need to decide what goes where. "About the role": could be the initial description paragraph(s) before "Key job responsibilities". That includes: "The Amazon Web Services (AWS) Worldwide Financial Services team is looking for a Banking industry senior solution architect to join our fast-paced team and help drive worldwide AWS adoption in banking globally. As a Worldwide Banking Solution Architect, you will be part of a team focused on accelerating technology adoption of cloud computing, working with C-level and line of business executives across our customers, and internally with sales and marketing, partner, product teams and AWS senior leadership to meet our customers’ needs. You will drive new business in Banking, leading the organization as a whole to effectively sell into that industry, developing programs to accelerate our customers’ moves from legacy on-premises environments to AWS-based services. Your specialized industry knowledge and expertise bridges businesses and technology, and you understand the regulatory and compliance environment that our customer base operates in. You speak the language of our customers, mapping their business and regulatory needs to AWS services and partner-led solutions, defining reference architectures, and building industry facing accelerators, APIs, and demonstrable solutions." That's prose; we can put in
. "Responsibilities": list under "Key job responsibilities". Those are bullet-like sentences each starting with a verb. We'll put each as
- .
"Qualifications": maybe Preferred Qualifications: "Knowledge of cloud architecture", "Experience in infrastructure architecture, database architecture and networking", "Experience working with end user or developer communities". We'll put as
- .
"Skills": Not explicitly listed; maybe we could infer but we should not create unless posting has real specific content. There's no explicit skills list. So omit Skills section.
"Benefits": The posting mentions: "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." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation but could be part of Pay. Benefits section: we can include the comprehensive benefits list. We'll put as
- .
"Pay": base salary range and sign-on payments and RSUs. So we can put in
maybe with details. "Schedule": not present, omit. We also have "About The Team" section with subpoints: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This is more about team/culture. Could be considered part of "About the role" or maybe a separate section like "About the team". But headings list only includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the team". We could incorporate that content into About the role or maybe into a separate section not in list? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should only emit those headings if posting has real specific content for them. It didn't forbid other headings, but likely they expect only those. Safer to stick to those headings and fold team info into About the role or maybe Benefits? Probably About the role can include team description. Thus we can expand About the role paragraph to include team description details. We must not repeat job title as heading. No Job ID. We must 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 keep benefits description but not the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is maybe navigation; we can drop the link but keep the benefits description. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." etc. Also remove "Company - Amazon Web Services, Inc." maybe not needed. We need to preserve all substantive information: so keep the description, responsibilities, qualifications, benefits, pay. Now produce HTML fragment. Structure:
About the role
... (combined description and team info)
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
...
No Schedule. Make sure to not include empty sections. Now craft the content. About the role paragraph: combine initial description and team info. Initial description: "The Amazon Web Services (AWS) Worldwide Financial Services team is looking for a Banking industry senior solution architect to join our fast-paced team and help drive worldwide AWS adoption in banking globally. As a Worldwide Banking Solution Architect, you will be part of a team focused on accelerating technology adoption of cloud computing, working with C-level and line of business executives across our customers, and internally with sales and marketing, partner, product teams and AWS senior leadership to meet our customers’ needs. You will drive new business in Banking, leading the organization as a whole to effectively sell into that industry, developing programs to accelerate our customers’ moves from legacy on-premises environments to AWS-based services. Your specialized industry knowledge and expertise bridges businesses and technology, and you understand the regulatory and compliance environment that our customer base operates in. You speak the language of our customers, mapping their business and regulatory needs to AWS services and partner-led solutions, defining reference architectures, and building industry facing accelerators, APIs, and demonstrable solutions." Team info: "About the team Diverse Experiences 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? 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 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 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 in the cloud." We can combine into a paragraph or multiple paragraphs. Usefor prose; could be multiple
under same heading? Probably one
with multiple sentences is fine. Now Responsibilities list: extract each bullet. From "Key job responsibilities": - Serve as a key member of the Worldwide Banking team in helping to drive AWS marketing, sales, and technical strategies for the Banking industry - Coach sales teams on AWS services relevant to banking customers - Understand the unique technical requirements of banking customers, and work closely with the internal teams to guide the direction of the adoption of AWS services for our largest and most complex customers - Work directly with customers to accelerate their business outcomes and recommend best-practice cloud architectures in line with their long-term business needs. - Drive technical solutions discussions with your customers, diving deep into the details to solve complex technical challenges and use your knowledge to craft scalable, flexible, and resilient cloud architectures. - Define and execute on the strategy by engaging highly technical teams (Solutions Architects, Technical Account Managers, AWS professional services consultants and consulting/managed services partners). - Act as a thought leader in the wider community, playing a key role in educating, sharing best practices, presenting at events, writing white papers, blogs, and running workshops. - Share the voice of the customer to influence the roadmap of new features and services for the AWS platform. - Proactively work within the organization to influence the evolution of the platform. - Scope and own customer engagements, with attention towards clear and well-defined objectives and success criteria. - Work backwards from your customer's business needs to accelerate adoption of the most appropriate AWS technology - Serve as a key technical member of the Solutions Architecture team through influencing decision makers across multiple domains to ensure customer success in building applications and services on the AWS platform which align to long-term business goals Make sure each ends with period maybe. Now Requirements (Basic Qualifications): - Experience in IT development or implementation/consulting in the software or Internet industries - Experience within specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics). - Experience migrating or transforming legacy customer solutions to the cloud - Experience in design, implementation, or consulting in applications and infrastructures - Experience communicating across technical and non-technical audiences, including executive level stakeholders or clients Now Qualifications (Preferred Qualifications): - Knowledge of cloud architecture - Experience in infrastructure architecture, database architecture and networking - Experience working with end user or developer communities Now Benefits: list items from description: - health insurance (medical, dental, vision, prescription, Basic
- .
"Pay": base salary range and sign-on payments and RSUs. So we can put in
- .
"Skills": Not explicitly listed; maybe we could infer but we should not create unless posting has real specific content. There's no explicit skills list. So omit Skills section.
"Benefits": The posting mentions: "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." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation but could be part of Pay. Benefits section: we can include the comprehensive benefits list. We'll put as