Solutions Architect - Global Financial Services (GFS), Global Financial Services (GFS)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate like EEO, accommodations, etc. Also remove application instructions. We need to preserve all substantive info.
Let's parse content:
- Intro: "Amazon Web Services (AWS) is looking for experienced and motivated technologists who possess a unique balance of technical breadth/depth and strong interpersonal skills. As a Solutions Architect, you will partner some of the world’s largest financial services companies, AWS Sales, and several other AWS teams to craft highly scalable, flexible and resilient cloud architectures that address customer business problems and accelerate the adoption of AWS services. In collaboration with sales, you will drive revenue growth across a small set of global financial services customers. As a trusted customer advocate, the solutions architect will help organizations understand best practices around advanced cloud-based solutions, and how to migrate existing workloads to the cloud. You will have the opportunity to help shape and execute a strategy to build mindshare and broad use of AWS within enterprise customers. The ideal candidate must be self-motivated with a proven track record to connect technology to measurable business value. You should also have a demonstrated ability to think strategically about business, products, and technical challenges. Here Are Some Other Qualities We Are Looking For Enjoy working with large, global customers. You will have a passion for educating, training, designing, and building cloud solutions for a diverse and challenging set of enterprise customers. Have a strong understanding of large-scale computing solutions."
That's about the role.
- Then "Key job responsibilities" list bullet points (starting with "As a key member of the account team...").
- Then "About The Team" paragraph about diverse experiences, encouraging to apply.
- Then "Why AWS?" paragraphs about AWS, mentorship, work/life balance.
- Then "Basic Qualifications" list: 4+ years..., 6+ years..., Knowledge of cloud architecture.
- Then "Preferred Qualifications": Experience with AWS or cloud technologies, Experience in the financial services industry.
- Then EEO etc (remove).
- Then "If you have a disability..." (accommodations) remove.
- Then "If the country/region you’re applying in isn’t listed..." remove.
- Then "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 https://amazon.jobs/en/benefits."
- Then location: "USA, NY, New York - 169,000.00 - 228,600.00 USD annually"
- Then "Company - Amazon Web Services, Inc. Job ID: A10549201" (remove Job ID, maybe keep company? Probably not needed as heading; we can drop minor metadata.)
We need sections: About the role (maybe from intro). Responsibilities (Key job responsibilities). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills? Not explicitly listed; maybe we can infer from responsibilities? But we should only include sections if posting has real specific content. There's no explicit "Skills" section; we could omit.
Benefits: we have benefits described (health insurance etc). Pay: we have salary range. Schedule: not mentioned (travel up to 20% could be included and will be discussed at interview stage). That's about travel, not schedule. No explicit schedule. So we may omit Schedule.
We need to preserve all substantive info; we should not invent or summarize away detail. So we need to include the benefits description exactly as given (maybe trimmed but preserve). Also include salary range.
We need to format lists with - . For prose use
.
We need headings
for each section.
Let's craft sections:
About the role
... (intro paragraph plus maybe the "Here Are Some Other Qualities We Are Looking For" part). We'll combine into one paragraph? Could be multiple paragraphs but we can keep as one
with line breaks? Better to keep as
containing the text; line breaks okay.
We need to ensure we don't repeat job title. Good.
Responsibilities: list each bullet.
We have bullet points:
- As a key member of the account team, partner with customers to ensure their long-term success by helping them harness the power of AWS services to accelerate their business.
- Formulate and execute a cloud adoption strategy that delights our customers and builds strong relationships that lead to strategic revenue streams that exceed AWS objectives.
- Become a trusted advisor by gaining deep knowledge of AWS services, design patterns and best practices, and sharing that knowledge with clients, other SAs and the wider AWS builder community.
- Act as the voice of the customer for AWS service teams to enhance the AWS platform.
- Work with other SAs to develop reusable solutions to common business and architectural problems.
- Educate customers by leading workshops and hands-on classes to demonstrate how to use AWS services.
- Network and build deep relationships with senior technical individuals within customer organizations to enable them to be cloud advocates.
- Author and contribute to AWS customer-facing publications such as whitepapers, blog posts and open source projects, and speak at public events.
- Help hire, on-board and train new SAs via mentorship and builder programs.
- Travel up to 20% could be included and will be discussed at the interview stage.
We should keep travel bullet as is.
Requirements (Basic Qualifications):
- 4+ years of design, implementation, or consulting in applications and infrastructures experience
- 6+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
- Knowledge of cloud architecture
Qualifications (Preferred Qualifications):
- Experience with AWS or cloud technologies
- Experience in the financial services industry
Benefits: The paragraph about benefits. We'll include as
.
Pay: Salary range: "USA, NY, New York - 169,000.00 - 228,600.00 USD annually". Also mention sign-on payments and RSUs etc. The text: "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 substantive. We'll include that as
under Pay heading.
Schedule: Not present; we omit.
We also have "About The Team" and "Why AWS?" sections. Those could be considered part of About the role or maybe separate sections like "About the team" and "Why AWS?" but headings list only includes specific ones; we could incorporate them into About the role or maybe create additional sections not in list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we could also add other headings if needed? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but we should likely stick to those. However we have extra content like About The Team and Why AWS? which is substantive. We could incorporate them into About the role section as additional paragraphs. That would preserve info.
Thus About the role will include intro, the "Here Are Some Other Qualities..." paragraph, About The Team paragraph, Why AWS? paragraphs.
Let's extract those:
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. 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'll combine.
Now produce HTML.
We must not include or . Just fragment.
Let's craft:
About the role
Amazon Web Services (AWS) is looking for experienced and motivated technologists who possess a unique balance of technical breadth/depth and strong interpersonal skills. As a Solutions Architect, you will partner some of the world’s largest financial services companies, AWS Sales, and several other AWS teams to craft highly scalable, flexible and resilient cloud architectures that address customer business problems and accelerate the adoption of AWS services. In collaboration with sales, you will drive revenue growth across a small set of global financial services customers. As a trusted customer advocate, the solutions architect will help organizations understand best practices around advanced cloud-based solutions, and how to migrate existing workloads to the cloud. You will have the opportunity to help shape and execute a strategy to build mindshare and broad use of AWS within enterprise customers. The ideal candidate must be self-motivated with a proven track record to connect technology to measurable business value. You should also have a demonstrated ability to think strategically about business, products, and technical challenges. Here Are Some Other Qualities We Are Looking For Enjoy working with large, global customers. You will have a passion for educating, training, designing, and building cloud solutions for a diverse and challenging set of enterprise customers. Have a strong understanding of large-scale computing solutions. 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. 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. 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.
But that's a huge paragraph; maybe better to split into multiple for readability. The instruction says use
for prose. It doesn't forbid multiple
. So we can break into logical paragraphs: intro, other qualities, about team, why AWS. That's fine.
Let
. We need headings
for each section.
Let's craft sections:
About the role
... (intro paragraph plus maybe the "Here Are Some Other Qualities We Are Looking For" part). We'll combine into one paragraph? Could be multiple paragraphs but we can keep as one
with line breaks? Better to keep as
containing the text; line breaks okay. We need to ensure we don't repeat job title. Good. Responsibilities: list each bullet. We have bullet points: - As a key member of the account team, partner with customers to ensure their long-term success by helping them harness the power of AWS services to accelerate their business. - Formulate and execute a cloud adoption strategy that delights our customers and builds strong relationships that lead to strategic revenue streams that exceed AWS objectives. - Become a trusted advisor by gaining deep knowledge of AWS services, design patterns and best practices, and sharing that knowledge with clients, other SAs and the wider AWS builder community. - Act as the voice of the customer for AWS service teams to enhance the AWS platform. - Work with other SAs to develop reusable solutions to common business and architectural problems. - Educate customers by leading workshops and hands-on classes to demonstrate how to use AWS services. - Network and build deep relationships with senior technical individuals within customer organizations to enable them to be cloud advocates. - Author and contribute to AWS customer-facing publications such as whitepapers, blog posts and open source projects, and speak at public events. - Help hire, on-board and train new SAs via mentorship and builder programs. - Travel up to 20% could be included and will be discussed at the interview stage. We should keep travel bullet as is. Requirements (Basic Qualifications): - 4+ years of design, implementation, or consulting in applications and infrastructures experience - 6+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience - Knowledge of cloud architecture Qualifications (Preferred Qualifications): - Experience with AWS or cloud technologies - Experience in the financial services industry Benefits: The paragraph about benefits. We'll include as
. Pay: Salary range: "USA, NY, New York - 169,000.00 - 228,600.00 USD annually". Also mention sign-on payments and RSUs etc. The text: "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 substantive. We'll include that as
under Pay heading. Schedule: Not present; we omit. We also have "About The Team" and "Why AWS?" sections. Those could be considered part of About the role or maybe separate sections like "About the team" and "Why AWS?" but headings list only includes specific ones; we could incorporate them into About the role or maybe create additional sections not in list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we could also add other headings if needed? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but we should likely stick to those. However we have extra content like About The Team and Why AWS? which is substantive. We could incorporate them into About the role section as additional paragraphs. That would preserve info.
Thus About the role will include intro, the "Here Are Some Other Qualities..." paragraph, About The Team paragraph, Why AWS? paragraphs.
Let's extract those:
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. 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'll combine.
Now produce HTML.
We must not include or . Just fragment.
Let's craft:
About the role
About the role
Amazon Web Services (AWS) is looking for experienced and motivated technologists who possess a unique balance of technical breadth/depth and strong interpersonal skills. As a Solutions Architect, you will partner some of the world’s largest financial services companies, AWS Sales, and several other AWS teams to craft highly scalable, flexible and resilient cloud architectures that address customer business problems and accelerate the adoption of AWS services. In collaboration with sales, you will drive revenue growth across a small set of global financial services customers. As a trusted customer advocate, the solutions architect will help organizations understand best practices around advanced cloud-based solutions, and how to migrate existing workloads to the cloud. You will have the opportunity to help shape and execute a strategy to build mindshare and broad use of AWS within enterprise customers. The ideal candidate must be self-motivated with a proven track record to connect technology to measurable business value. You should also have a demonstrated ability to think strategically about business, products, and technical challenges. Here Are Some Other Qualities We Are Looking For Enjoy working with large, global customers. You will have a passion for educating, training, designing, and building cloud solutions for a diverse and challenging set of enterprise customers. Have a strong understanding of large-scale computing solutions. 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. 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. 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.
But that's a huge paragraph; maybe better to split into multiplefor readability. The instruction says use
for prose. It doesn't forbid multiple
. So we can break into logical paragraphs: intro, other qualities, about team, why AWS. That's fine. Let