Senior Worldwide Specialist Solutions Architect, Containers
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content.
We need to parse the description.
Key parts:
- Description: "Are you passionate about helping businesses revolutionize their cloud journey through container technology? Join AWS's Worldwide Specialist Organization (WWSO) as a Specialist Solutions Architect! We are looking for innovative leaders to join our team of Specialist Solutions Architects. This role will have a particular focus on working with our partners, both Independent Software Vendors (ISVs) and Systems Integrators (SIs). You will act as a trusted advisor to these partners and help them drive success. Additionally, you will have the opportunity to help shape our services including Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, AWS Fargate, and Amazon Elastic Container Registry. You will demonstrate customer obsession, representing the voice of the customer as you work with product teams to evolve AWS services. You will also work directly with the most innovative and forward-thinking customers - leaders in their respective fields - earning trust to understand their requirements and turn them into reality. You will drive architectural best practices, building and operating advanced, scalable, reliable, and secure workloads by collaborating with customers, developing impactful content, and enabling the wider community to adopt the AWS portfolio. This includes acting as a strategic technical leader in the field to provide architectural guidance and recommendations necessary to promote & accelerate partner engagements worldwide."
That's about the role.
- "Key job responsibilities" bullet list:
- Work with AWS Partners to define the container components of best-in-class Go-To-Market (GTM) concepts, solutions, and initiatives.
- Design, implementation, and deployment experience with advanced containerized solutions architectures.
- Use data and customer anecdotes to provide feedback to product teams, influencing feature development and future product roadmaps.
- Provide advanced technical knowledge through container aligned GTM teams to unblock our customers’ largest and most critical business challenges.
- Steward the deployment and operations of workloads on AWS using Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Elastic Container Service (ECS), AWS Fargate, Kubernetes or other container services.
- "About The Team": paragraph.
- "Why AWS": paragraph.
- "Work/Life Balance": paragraph.
- "Inclusive Team Culture": paragraph.
- "Mentorship and Career Growth": paragraph.
- "Basic Qualifications": list.
- "Preferred Qualifications": list.
- Benefits: mention comprehensive benefits including health insurance etc. Also mention base salary range for location.
- Pay: The base salary range listed for multiple locations. Should we include Pay section? Yes, we have salary ranges. Provide as list? Could be a with each location line.
- Schedule: Not mentioned. So omit.
- Skills: Not explicit separate; maybe part of qualifications. Could combine.
We need to avoid boilerplate: EEO, accommodation link, etc. Remove duplicated lines.
We need to preserve all substantive info.
We need to output only HTML fragment, no /, no markdown fences.
We need to use for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide sections: About the role (maybe "About the role" heading). Responsibilities (Key job responsibilities). About The Team could be "About the Team". Why AWS maybe "Why AWS". Work/Life Balance maybe "Work/Life Balance". Inclusive Team Culture maybe "Inclusive Team Culture". Mentorship and Career Growth maybe "Mentorship and Career Growth". Basic Qualifications maybe "Basic Qualifications". Preferred Qualifications maybe "Preferred Qualifications". Benefits maybe "Benefits". Pay maybe "Pay". Possibly combine some sections if thin.
But we need to prefer few substantive sections over many thin ones. However we have many sections with content. Could combine some like "About the Team", "Why AWS", "Work/Life Balance", "Inclusive Team Culture", "Mentorship and Career Growth" into a single "About AWS" section? But the instruction: "Prefer a few substantive sections over many thin ones." So we could combine those culture/benefits paragraphs into one section like "About AWS" or "Company Overview". However we must preserve all substantive information; we can combine them into a single section with multiple paragraphs.
We need headings only when posting has real specific content for it. So we could have sections: About the role, Responsibilities, Qualifications (combining Basic and Preferred), Benefits & Pay (maybe separate), and About AWS (combining team, why AWS, work/life, culture, mentorship). That seems reasonable.
But we need to follow the instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use exactly those; we can use those headings if appropriate. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings when we have content. If we combine, we might still use those headings but maybe we need to include only those that have content. For example, we could have About the role, Responsibilities, Qualifications, Benefits, Pay, and maybe About AWS (but not in list). However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings where applicable.
Thus we could have:
- About the role
with prose from description.
- Responsibilities
with list.
- Qualifications
with two sub-sections? Could have Basic Qualifications and Preferred Qualifications as lists under same heading, maybe separate ? But we only allowed for section headings. Could we use for each? That would be multiple sections: Basic Qualifications and Preferred Qualifications. That's okay; they are subheadings but still . The instruction didn't forbid multiple sections. So we could have Basic Qualifications
and Preferred Qualifications
. That seems fine.
- Benefits
with list of benefits.
- Pay
with list of salary ranges per location.
We should omit Schedule as not present.
We should also include maybe "About the Team" etc. Could we incorporate that into About the role? But the description already has "About The Team", "Why AWS", etc. Those are substantive. If we omit them, we lose info. So we need to include them somewhere. Could add a section About AWS
(not in examples but okay). Or we could incorporate into About the role? But About the role already has description of role; adding team etc may be okay but might be mixing. Better to add a separate section like "About AWS". The instruction didn't forbid other headings; it just gave examples. So we can add About AWS
containing those paragraphs.
Thus final sections: About the role, Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay, About AWS.
Check for duplication: Ensure we don't repeat job title as heading. We are not.
Remove boilerplate: EEO statement, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10466306". Also remove "Our inclusive culture empowers Amazonians..." etc (that's EEO). Remove "If you have a disability..." etc. 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 application instruction? It's a link to learn more about benefits; could be considered navigation? Safer to remove the link but keep the benefits description. The benefits description includes list of benefits; we can keep that.
Also remove "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 ..." That's part of benefits/pay. We'll keep the salary ranges and benefits description but remove the sentence about sign-on payments and RSUs? That's substantive? It's about compensation; maybe keep as part of Pay? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep mention of sign-on payments and RSUs as part of Pay section. Also mention that final compensation determined based on experience etc. That's also substantive. Keep.
Now craft HTML.
We'll need to escape any special characters like &, <, >. In text we have "&" in "promote & accelerate". Need to escape as &. Also "Go-To-Market (GTM)" includes hyphens fine. Also "Amazon Elastic Kubernetes Service (Amazon EKS)" includes parentheses fine.
We'll produce:
About the role
Are you passionate about helping businesses revolutionize their cloud journey through container technology? Join AWS's Worldwide Specialist Organization (WWSO) as a Specialist Solutions Architect! We are looking for innovative leaders to join our team of Specialist Solutions Architects. This role will have a particular focus on working with our partners, both Independent Software Vendors (ISVs) and Systems Integrators (SIs). You will act as a trusted advisor to these partners and help them drive success. Additionally, you will have the opportunity to help shape our services including Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, AWS Fargate, and Amazon Elastic Container Registry. You will demonstrate customer obsession, representing the voice of the customer as you work with product teams to evolve AWS services. You will also work directly with the most innovative and forward-thinking customers - leaders in their respective fields - earning trust to understand their requirements and turn them into reality. You will drive architectural best practices, building and operating advanced, scalable, reliable, and secure workloads by collaborating with customers, developing impactful content, and enabling the wider community to adopt the AWS portfolio. This includes acting as a strategic technical leader in the field to provide architectural guidance and recommendations necessary to promote & accelerate partner engagements worldwide.
Responsibilities
- Work with AWS Partners to define the container components of best-in-class Go-To-Market (GTM) concepts, solutions, and initiatives.
- Design, implementation, and deployment experience with advanced containerized solutions architectures.
- Use data and customer anecdotes to provide feedback to product teams, influencing feature development and future product roadmaps.
- Provide advanced technical knowledge through container aligned GTM teams to unblock our customers’ largest and most critical business challenges.
- Steward the deployment and operations of workloads on AWS using Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Elastic Container Service (ECS), AWS Fargate, Kubernetes or other container services.
Basic Qualifications
- 5+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
- Knowledge of software development tools and methodologies
- Experience migrating or transforming legacy customer solutions to the cloud
- Experience with designing and building applications using container and serverless technologies
Preferred Qualifications
- 5+ years of infrastructure architecture, database architecture and networking experience
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide sections: About the role (maybe "About the role" heading). Responsibilities (Key job responsibilities). About The Team could be "About the Team". Why AWS maybe "Why AWS". Work/Life Balance maybe "Work/Life Balance". Inclusive Team Culture maybe "Inclusive Team Culture". Mentorship and Career Growth maybe "Mentorship and Career Growth". Basic Qualifications maybe "Basic Qualifications". Preferred Qualifications maybe "Preferred Qualifications". Benefits maybe "Benefits". Pay maybe "Pay". Possibly combine some sections if thin.
But we need to prefer few substantive sections over many thin ones. However we have many sections with content. Could combine some like "About the Team", "Why AWS", "Work/Life Balance", "Inclusive Team Culture", "Mentorship and Career Growth" into a single "About AWS" section? But the instruction: "Prefer a few substantive sections over many thin ones." So we could combine those culture/benefits paragraphs into one section like "About AWS" or "Company Overview". However we must preserve all substantive information; we can combine them into a single section with multiple paragraphs.
We need headings only when posting has real specific content for it. So we could have sections: About the role, Responsibilities, Qualifications (combining Basic and Preferred), Benefits & Pay (maybe separate), and About AWS (combining team, why AWS, work/life, culture, mentorship). That seems reasonable.
But we need to follow the instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use exactly those; we can use those headings if appropriate. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings when we have content. If we combine, we might still use those headings but maybe we need to include only those that have content. For example, we could have About the role, Responsibilities, Qualifications, Benefits, Pay, and maybe About AWS (but not in list). However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings where applicable.
Thus we could have:
- About the role
with prose from description.
- Responsibilities
with list.
- Qualifications
with two sub-sections? Could have Basic Qualifications and Preferred Qualifications as lists under same heading, maybe separate ? But we only allowed for section headings. Could we use for each? That would be multiple sections: Basic Qualifications and Preferred Qualifications. That's okay; they are subheadings but still . The instruction didn't forbid multiple sections. So we could have Basic Qualifications
and Preferred Qualifications
. That seems fine.
- Benefits
with list of benefits.
- Pay
with list of salary ranges per location.
We should omit Schedule as not present.
We should also include maybe "About the Team" etc. Could we incorporate that into About the role? But the description already has "About The Team", "Why AWS", etc. Those are substantive. If we omit them, we lose info. So we need to include them somewhere. Could add a section About AWS
(not in examples but okay). Or we could incorporate into About the role? But About the role already has description of role; adding team etc may be okay but might be mixing. Better to add a separate section like "About AWS". The instruction didn't forbid other headings; it just gave examples. So we can add About AWS
containing those paragraphs.
Thus final sections: About the role, Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay, About AWS.
Check for duplication: Ensure we don't repeat job title as heading. We are not.
Remove boilerplate: EEO statement, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10466306". Also remove "Our inclusive culture empowers Amazonians..." etc (that's EEO). Remove "If you have a disability..." etc. 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 application instruction? It's a link to learn more about benefits; could be considered navigation? Safer to remove the link but keep the benefits description. The benefits description includes list of benefits; we can keep that.
Also remove "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 ..." That's part of benefits/pay. We'll keep the salary ranges and benefits description but remove the sentence about sign-on payments and RSUs? That's substantive? It's about compensation; maybe keep as part of Pay? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep mention of sign-on payments and RSUs as part of Pay section. Also mention that final compensation determined based on experience etc. That's also substantive. Keep.
Now craft HTML.
We'll need to escape any special characters like &, <, >. In text we have "&" in "promote & accelerate". Need to escape as &. Also "Go-To-Market (GTM)" includes hyphens fine. Also "Amazon Elastic Kubernetes Service (Amazon EKS)" includes parentheses fine.
We'll produce:
About the role
Are you passionate about helping businesses revolutionize their cloud journey through container technology? Join AWS's Worldwide Specialist Organization (WWSO) as a Specialist Solutions Architect! We are looking for innovative leaders to join our team of Specialist Solutions Architects. This role will have a particular focus on working with our partners, both Independent Software Vendors (ISVs) and Systems Integrators (SIs). You will act as a trusted advisor to these partners and help them drive success. Additionally, you will have the opportunity to help shape our services including Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, AWS Fargate, and Amazon Elastic Container Registry. You will demonstrate customer obsession, representing the voice of the customer as you work with product teams to evolve AWS services. You will also work directly with the most innovative and forward-thinking customers - leaders in their respective fields - earning trust to understand their requirements and turn them into reality. You will drive architectural best practices, building and operating advanced, scalable, reliable, and secure workloads by collaborating with customers, developing impactful content, and enabling the wider community to adopt the AWS portfolio. This includes acting as a strategic technical leader in the field to provide architectural guidance and recommendations necessary to promote & accelerate partner engagements worldwide.
Responsibilities
- Work with AWS Partners to define the container components of best-in-class Go-To-Market (GTM) concepts, solutions, and initiatives.
- Design, implementation, and deployment experience with advanced containerized solutions architectures.
- Use data and customer anecdotes to provide feedback to product teams, influencing feature development and future product roadmaps.
- Provide advanced technical knowledge through container aligned GTM teams to unblock our customers’ largest and most critical business challenges.
- Steward the deployment and operations of workloads on AWS using Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Elastic Container Service (ECS), AWS Fargate, Kubernetes or other container services.
Basic Qualifications
- 5+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
- Knowledge of software development tools and methodologies
- Experience migrating or transforming legacy customer solutions to the cloud
- Experience with designing and building applications using container and serverless technologies
Preferred Qualifications
- 5+ years of infrastructure architecture, database architecture and networking experience
for prose. We need to decide sections: About the role (maybe "About the role" heading). Responsibilities (Key job responsibilities). About The Team could be "About the Team". Why AWS maybe "Why AWS". Work/Life Balance maybe "Work/Life Balance". Inclusive Team Culture maybe "Inclusive Team Culture". Mentorship and Career Growth maybe "Mentorship and Career Growth". Basic Qualifications maybe "Basic Qualifications". Preferred Qualifications maybe "Preferred Qualifications". Benefits maybe "Benefits". Pay maybe "Pay". Possibly combine some sections if thin. But we need to prefer few substantive sections over many thin ones. However we have many sections with content. Could combine some like "About the Team", "Why AWS", "Work/Life Balance", "Inclusive Team Culture", "Mentorship and Career Growth" into a single "About AWS" section? But the instruction: "Prefer a few substantive sections over many thin ones." So we could combine those culture/benefits paragraphs into one section like "About AWS" or "Company Overview". However we must preserve all substantive information; we can combine them into a single section with multiple paragraphs. We need headings only when posting has real specific content for it. So we could have sections: About the role, Responsibilities, Qualifications (combining Basic and Preferred), Benefits & Pay (maybe separate), and About AWS (combining team, why AWS, work/life, culture, mentorship). That seems reasonable. But we need to follow the instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use exactly those; we can use those headings if appropriate. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings when we have content. If we combine, we might still use those headings but maybe we need to include only those that have content. For example, we could have About the role, Responsibilities, Qualifications, Benefits, Pay, and maybe About AWS (but not in list). However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings where applicable.
Thus we could have:
- About the role
with prose from description.
- Responsibilities
with list.
- Qualifications
with two sub-sections? Could have Basic Qualifications and Preferred Qualifications as lists under same heading, maybe separate ? But we only allowed for section headings. Could we use for each? That would be multiple sections: Basic Qualifications and Preferred Qualifications. That's okay; they are subheadings but still . The instruction didn't forbid multiple sections. So we could have Basic Qualifications
and Preferred Qualifications
. That seems fine.
- Benefits
with list of benefits.
- Pay
with list of salary ranges per location.
We should omit Schedule as not present.
We should also include maybe "About the Team" etc. Could we incorporate that into About the role? But the description already has "About The Team", "Why AWS", etc. Those are substantive. If we omit them, we lose info. So we need to include them somewhere. Could add a section About AWS
(not in examples but okay). Or we could incorporate into About the role? But About the role already has description of role; adding team etc may be okay but might be mixing. Better to add a separate section like "About AWS". The instruction didn't forbid other headings; it just gave examples. So we can add About AWS
containing those paragraphs.
Thus final sections: About the role, Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay, About AWS.
Check for duplication: Ensure we don't repeat job title as heading. We are not.
Remove boilerplate: EEO statement, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10466306". Also remove "Our inclusive culture empowers Amazonians..." etc (that's EEO). Remove "If you have a disability..." etc. 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 application instruction? It's a link to learn more about benefits; could be considered navigation? Safer to remove the link but keep the benefits description. The benefits description includes list of benefits; we can keep that.
Also remove "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 ..." That's part of benefits/pay. We'll keep the salary ranges and benefits description but remove the sentence about sign-on payments and RSUs? That's substantive? It's about compensation; maybe keep as part of Pay? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep mention of sign-on payments and RSUs as part of Pay section. Also mention that final compensation determined based on experience etc. That's also substantive. Keep.
Now craft HTML.
We'll need to escape any special characters like &, <, >. In text we have "&" in "promote & accelerate". Need to escape as &. Also "Go-To-Market (GTM)" includes hyphens fine. Also "Amazon Elastic Kubernetes Service (Amazon EKS)" includes parentheses fine.
We'll produce:
About the role
Are you passionate about helping businesses revolutionize their cloud journey through container technology? Join AWS's Worldwide Specialist Organization (WWSO) as a Specialist Solutions Architect! We are looking for innovative leaders to join our team of Specialist Solutions Architects. This role will have a particular focus on working with our partners, both Independent Software Vendors (ISVs) and Systems Integrators (SIs). You will act as a trusted advisor to these partners and help them drive success. Additionally, you will have the opportunity to help shape our services including Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, AWS Fargate, and Amazon Elastic Container Registry. You will demonstrate customer obsession, representing the voice of the customer as you work with product teams to evolve AWS services. You will also work directly with the most innovative and forward-thinking customers - leaders in their respective fields - earning trust to understand their requirements and turn them into reality. You will drive architectural best practices, building and operating advanced, scalable, reliable, and secure workloads by collaborating with customers, developing impactful content, and enabling the wider community to adopt the AWS portfolio. This includes acting as a strategic technical leader in the field to provide architectural guidance and recommendations necessary to promote & accelerate partner engagements worldwide.
Responsibilities
- Work with AWS Partners to define the container components of best-in-class Go-To-Market (GTM) concepts, solutions, and initiatives.
- Design, implementation, and deployment experience with advanced containerized solutions architectures.
- Use data and customer anecdotes to provide feedback to product teams, influencing feature development and future product roadmaps.
- Provide advanced technical knowledge through container aligned GTM teams to unblock our customers’ largest and most critical business challenges.
- Steward the deployment and operations of workloads on AWS using Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Elastic Container Service (ECS), AWS Fargate, Kubernetes or other container services.
Basic Qualifications
- 5+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
- Knowledge of software development tools and methodologies
- Experience migrating or transforming legacy customer solutions to the cloud
- Experience with designing and building applications using container and serverless technologies
Preferred Qualifications
- 5+ years of infrastructure architecture, database architecture and networking experience
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings where applicable.
Thus we could have:
- About the role
with prose from description.
- Responsibilities
with list.
- Qualifications
with two sub-sections? Could have Basic Qualifications and Preferred Qualifications as lists under same heading, maybe separate ? But we only allowed for section headings. Could we use for each? That would be multiple sections: Basic Qualifications and Preferred Qualifications. That's okay; they are subheadings but still . The instruction didn't forbid multiple sections. So we could have Basic Qualifications
and Preferred Qualifications
. That seems fine.
- Benefits
with list of benefits.
- Pay
with list of salary ranges per location.
We should omit Schedule as not present.
We should also include maybe "About the Team" etc. Could we incorporate that into About the role? But the description already has "About The Team", "Why AWS", etc. Those are substantive. If we omit them, we lose info. So we need to include them somewhere. Could add a section About AWS
(not in examples but okay). Or we could incorporate into About the role? But About the role already has description of role; adding team etc may be okay but might be mixing. Better to add a separate section like "About AWS". The instruction didn't forbid other headings; it just gave examples. So we can add About AWS
containing those paragraphs.
Thus final sections: About the role, Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay, About AWS.
Check for duplication: Ensure we don't repeat job title as heading. We are not.
Remove boilerplate: EEO statement, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10466306". Also remove "Our inclusive culture empowers Amazonians..." etc (that's EEO). Remove "If you have a disability..." etc. 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 application instruction? It's a link to learn more about benefits; could be considered navigation? Safer to remove the link but keep the benefits description. The benefits description includes list of benefits; we can keep that.
Also remove "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 ..." That's part of benefits/pay. We'll keep the salary ranges and benefits description but remove the sentence about sign-on payments and RSUs? That's substantive? It's about compensation; maybe keep as part of Pay? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep mention of sign-on payments and RSUs as part of Pay section. Also mention that final compensation determined based on experience etc. That's also substantive. Keep.
Now craft HTML.
We'll need to escape any special characters like &, <, >. In text we have "&" in "promote & accelerate". Need to escape as &. Also "Go-To-Market (GTM)" includes hyphens fine. Also "Amazon Elastic Kubernetes Service (Amazon EKS)" includes parentheses fine.
We'll produce:
About the role
Are you passionate about helping businesses revolutionize their cloud journey through container technology? Join AWS's Worldwide Specialist Organization (WWSO) as a Specialist Solutions Architect! We are looking for innovative leaders to join our team of Specialist Solutions Architects. This role will have a particular focus on working with our partners, both Independent Software Vendors (ISVs) and Systems Integrators (SIs). You will act as a trusted advisor to these partners and help them drive success. Additionally, you will have the opportunity to help shape our services including Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, AWS Fargate, and Amazon Elastic Container Registry. You will demonstrate customer obsession, representing the voice of the customer as you work with product teams to evolve AWS services. You will also work directly with the most innovative and forward-thinking customers - leaders in their respective fields - earning trust to understand their requirements and turn them into reality. You will drive architectural best practices, building and operating advanced, scalable, reliable, and secure workloads by collaborating with customers, developing impactful content, and enabling the wider community to adopt the AWS portfolio. This includes acting as a strategic technical leader in the field to provide architectural guidance and recommendations necessary to promote & accelerate partner engagements worldwide.
Responsibilities
- Work with AWS Partners to define the container components of best-in-class Go-To-Market (GTM) concepts, solutions, and initiatives.
- Design, implementation, and deployment experience with advanced containerized solutions architectures.
- Use data and customer anecdotes to provide feedback to product teams, influencing feature development and future product roadmaps.
- Provide advanced technical knowledge through container aligned GTM teams to unblock our customers’ largest and most critical business challenges.
- Steward the deployment and operations of workloads on AWS using Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Elastic Container Service (ECS), AWS Fargate, Kubernetes or other container services.
Basic Qualifications
- 5+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
- Knowledge of software development tools and methodologies
- Experience migrating or transforming legacy customer solutions to the cloud
- Experience with designing and building applications using container and serverless technologies
Preferred Qualifications
- 5+ years of infrastructure architecture, database architecture and networking experience
Qualifications
with two sub-sections? Could have Basic Qualifications and Preferred Qualifications as- lists under same heading, maybe separate
- Work with AWS Partners to define the container components of best-in-class Go-To-Market (GTM) concepts, solutions, and initiatives.
- Design, implementation, and deployment experience with advanced containerized solutions architectures.
- Use data and customer anecdotes to provide feedback to product teams, influencing feature development and future product roadmaps.
- Provide advanced technical knowledge through container aligned GTM teams to unblock our customers’ largest and most critical business challenges.
- Steward the deployment and operations of workloads on AWS using Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Elastic Container Service (ECS), AWS Fargate, Kubernetes or other container services.
- 5+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
- Knowledge of software development tools and methodologies
- Experience migrating or transforming legacy customer solutions to the cloud
- Experience with designing and building applications using container and serverless technologies
- 5+ years of infrastructure architecture, database architecture and networking experience
? But we only allowed for section headings. Could we use for each? That would be multiple sections: Basic Qualifications and Preferred Qualifications. That's okay; they are subheadings but still . The instruction didn't forbid multiple sections. So we could have Basic Qualifications
and Preferred Qualifications
. That seems fine.
- Benefits
with list of benefits.
- Pay
with list of salary ranges per location.
We should omit Schedule as not present.
We should also include maybe "About the Team" etc. Could we incorporate that into About the role? But the description already has "About The Team", "Why AWS", etc. Those are substantive. If we omit them, we lose info. So we need to include them somewhere. Could add a section About AWS
(not in examples but okay). Or we could incorporate into About the role? But About the role already has description of role; adding team etc may be okay but might be mixing. Better to add a separate section like "About AWS". The instruction didn't forbid other headings; it just gave examples. So we can add About AWS
containing those paragraphs.
Thus final sections: About the role, Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay, About AWS.
Check for duplication: Ensure we don't repeat job title as heading. We are not.
Remove boilerplate: EEO statement, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10466306". Also remove "Our inclusive culture empowers Amazonians..." etc (that's EEO). Remove "If you have a disability..." etc. 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 application instruction? It's a link to learn more about benefits; could be considered navigation? Safer to remove the link but keep the benefits description. The benefits description includes list of benefits; we can keep that.
Also remove "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 ..." That's part of benefits/pay. We'll keep the salary ranges and benefits description but remove the sentence about sign-on payments and RSUs? That's substantive? It's about compensation; maybe keep as part of Pay? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep mention of sign-on payments and RSUs as part of Pay section. Also mention that final compensation determined based on experience etc. That's also substantive. Keep.
Now craft HTML.
We'll need to escape any special characters like &, <, >. In text we have "&" in "promote & accelerate". Need to escape as &. Also "Go-To-Market (GTM)" includes hyphens fine. Also "Amazon Elastic Kubernetes Service (Amazon EKS)" includes parentheses fine.
We'll produce:
About the role
Are you passionate about helping businesses revolutionize their cloud journey through container technology? Join AWS's Worldwide Specialist Organization (WWSO) as a Specialist Solutions Architect! We are looking for innovative leaders to join our team of Specialist Solutions Architects. This role will have a particular focus on working with our partners, both Independent Software Vendors (ISVs) and Systems Integrators (SIs). You will act as a trusted advisor to these partners and help them drive success. Additionally, you will have the opportunity to help shape our services including Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, AWS Fargate, and Amazon Elastic Container Registry. You will demonstrate customer obsession, representing the voice of the customer as you work with product teams to evolve AWS services. You will also work directly with the most innovative and forward-thinking customers - leaders in their respective fields - earning trust to understand their requirements and turn them into reality. You will drive architectural best practices, building and operating advanced, scalable, reliable, and secure workloads by collaborating with customers, developing impactful content, and enabling the wider community to adopt the AWS portfolio. This includes acting as a strategic technical leader in the field to provide architectural guidance and recommendations necessary to promote & accelerate partner engagements worldwide.
Responsibilities
Basic Qualifications
Preferred Qualifications
for each? That would be multiple sections: Basic Qualifications and Preferred Qualifications. That's okay; they are subheadings but still . The instruction didn't forbid multiple sections. So we could have Basic Qualifications
and Preferred Qualifications
. That seems fine.
- Benefits
with list of benefits.
- Pay
with list of salary ranges per location.
We should omit Schedule as not present.
We should also include maybe "About the Team" etc. Could we incorporate that into About the role? But the description already has "About The Team", "Why AWS", etc. Those are substantive. If we omit them, we lose info. So we need to include them somewhere. Could add a section About AWS
(not in examples but okay). Or we could incorporate into About the role? But About the role already has description of role; adding team etc may be okay but might be mixing. Better to add a separate section like "About AWS". The instruction didn't forbid other headings; it just gave examples. So we can add About AWS
containing those paragraphs.
Thus final sections: About the role, Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay, About AWS.
Check for duplication: Ensure we don't repeat job title as heading. We are not.
Remove boilerplate: EEO statement, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10466306". Also remove "Our inclusive culture empowers Amazonians..." etc (that's EEO). Remove "If you have a disability..." etc. 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 application instruction? It's a link to learn more about benefits; could be considered navigation? Safer to remove the link but keep the benefits description. The benefits description includes list of benefits; we can keep that.
Also remove "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 ..." That's part of benefits/pay. We'll keep the salary ranges and benefits description but remove the sentence about sign-on payments and RSUs? That's substantive? It's about compensation; maybe keep as part of Pay? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep mention of sign-on payments and RSUs as part of Pay section. Also mention that final compensation determined based on experience etc. That's also substantive. Keep.
Now craft HTML.
We'll need to escape any special characters like &, <, >. In text we have "&" in "promote & accelerate". Need to escape as &. Also "Go-To-Market (GTM)" includes hyphens fine. Also "Amazon Elastic Kubernetes Service (Amazon EKS)" includes parentheses fine.
We'll produce:
About the role
Are you passionate about helping businesses revolutionize their cloud journey through container technology? Join AWS's Worldwide Specialist Organization (WWSO) as a Specialist Solutions Architect! We are looking for innovative leaders to join our team of Specialist Solutions Architects. This role will have a particular focus on working with our partners, both Independent Software Vendors (ISVs) and Systems Integrators (SIs). You will act as a trusted advisor to these partners and help them drive success. Additionally, you will have the opportunity to help shape our services including Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, AWS Fargate, and Amazon Elastic Container Registry. You will demonstrate customer obsession, representing the voice of the customer as you work with product teams to evolve AWS services. You will also work directly with the most innovative and forward-thinking customers - leaders in their respective fields - earning trust to understand their requirements and turn them into reality. You will drive architectural best practices, building and operating advanced, scalable, reliable, and secure workloads by collaborating with customers, developing impactful content, and enabling the wider community to adopt the AWS portfolio. This includes acting as a strategic technical leader in the field to provide architectural guidance and recommendations necessary to promote & accelerate partner engagements worldwide.
Responsibilities
Basic Qualifications
Preferred Qualifications
sections. So we could have Basic Qualifications
and Preferred Qualifications
. That seems fine.
- Benefits
with list of benefits.
- Pay
with list of salary ranges per location.
We should omit Schedule as not present.
We should also include maybe "About the Team" etc. Could we incorporate that into About the role? But the description already has "About The Team", "Why AWS", etc. Those are substantive. If we omit them, we lose info. So we need to include them somewhere. Could add a section About AWS
(not in examples but okay). Or we could incorporate into About the role? But About the role already has description of role; adding team etc may be okay but might be mixing. Better to add a separate section like "About AWS". The instruction didn't forbid other headings; it just gave examples. So we can add About AWS
containing those paragraphs.
Thus final sections: About the role, Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay, About AWS.
Check for duplication: Ensure we don't repeat job title as heading. We are not.
Remove boilerplate: EEO statement, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10466306". Also remove "Our inclusive culture empowers Amazonians..." etc (that's EEO). Remove "If you have a disability..." etc. 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 application instruction? It's a link to learn more about benefits; could be considered navigation? Safer to remove the link but keep the benefits description. The benefits description includes list of benefits; we can keep that.
Also remove "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 ..." That's part of benefits/pay. We'll keep the salary ranges and benefits description but remove the sentence about sign-on payments and RSUs? That's substantive? It's about compensation; maybe keep as part of Pay? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep mention of sign-on payments and RSUs as part of Pay section. Also mention that final compensation determined based on experience etc. That's also substantive. Keep.
Now craft HTML.
We'll need to escape any special characters like &, <, >. In text we have "&" in "promote & accelerate". Need to escape as &. Also "Go-To-Market (GTM)" includes hyphens fine. Also "Amazon Elastic Kubernetes Service (Amazon EKS)" includes parentheses fine.
We'll produce:
About the role
Are you passionate about helping businesses revolutionize their cloud journey through container technology? Join AWS's Worldwide Specialist Organization (WWSO) as a Specialist Solutions Architect! We are looking for innovative leaders to join our team of Specialist Solutions Architects. This role will have a particular focus on working with our partners, both Independent Software Vendors (ISVs) and Systems Integrators (SIs). You will act as a trusted advisor to these partners and help them drive success. Additionally, you will have the opportunity to help shape our services including Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, AWS Fargate, and Amazon Elastic Container Registry. You will demonstrate customer obsession, representing the voice of the customer as you work with product teams to evolve AWS services. You will also work directly with the most innovative and forward-thinking customers - leaders in their respective fields - earning trust to understand their requirements and turn them into reality. You will drive architectural best practices, building and operating advanced, scalable, reliable, and secure workloads by collaborating with customers, developing impactful content, and enabling the wider community to adopt the AWS portfolio. This includes acting as a strategic technical leader in the field to provide architectural guidance and recommendations necessary to promote & accelerate partner engagements worldwide.
Responsibilities
Basic Qualifications
Preferred Qualifications
Pay
with- list of salary ranges per location.
We should omit Schedule as not present.
We should also include maybe "About the Team" etc. Could we incorporate that into About the role? But the description already has "About The Team", "Why AWS", etc. Those are substantive. If we omit them, we lose info. So we need to include them somewhere. Could add a section
About AWS
(not in examples but okay). Or we could incorporate into About the role? But About the role already has description of role; adding team etc may be okay but might be mixing. Better to add a separate section like "About AWS". The instruction didn't forbid other headings; it just gave examples. So we can addAbout AWS
containing those paragraphs. Thus final sections: About the role, Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay, About AWS. Check for duplication: Ensure we don't repeat job title as heading. We are not. Remove boilerplate: EEO statement, accommodation link, etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10466306". Also remove "Our inclusive culture empowers Amazonians..." etc (that's EEO). Remove "If you have a disability..." etc. 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 application instruction? It's a link to learn more about benefits; could be considered navigation? Safer to remove the link but keep the benefits description. The benefits description includes list of benefits; we can keep that. Also remove "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 ..." That's part of benefits/pay. We'll keep the salary ranges and benefits description but remove the sentence about sign-on payments and RSUs? That's substantive? It's about compensation; maybe keep as part of Pay? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep mention of sign-on payments and RSUs as part of Pay section. Also mention that final compensation determined based on experience etc. That's also substantive. Keep. Now craft HTML. We'll need to escape any special characters like &, <, >. In text we have "&" in "promote & accelerate". Need to escape as &. Also "Go-To-Market (GTM)" includes hyphens fine. Also "Amazon Elastic Kubernetes Service (Amazon EKS)" includes parentheses fine. We'll produce:About the role
Are you passionate about helping businesses revolutionize their cloud journey through container technology? Join AWS's Worldwide Specialist Organization (WWSO) as a Specialist Solutions Architect! We are looking for innovative leaders to join our team of Specialist Solutions Architects. This role will have a particular focus on working with our partners, both Independent Software Vendors (ISVs) and Systems Integrators (SIs). You will act as a trusted advisor to these partners and help them drive success. Additionally, you will have the opportunity to help shape our services including Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, AWS Fargate, and Amazon Elastic Container Registry. You will demonstrate customer obsession, representing the voice of the customer as you work with product teams to evolve AWS services. You will also work directly with the most innovative and forward-thinking customers - leaders in their respective fields - earning trust to understand their requirements and turn them into reality. You will drive architectural best practices, building and operating advanced, scalable, reliable, and secure workloads by collaborating with customers, developing impactful content, and enabling the wider community to adopt the AWS portfolio. This includes acting as a strategic technical leader in the field to provide architectural guidance and recommendations necessary to promote & accelerate partner engagements worldwide.