Solutions Architect, Commercial Midmarket
for headings. Use - for lists. Use
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate, navigation, EEO, etc. Keep substantive info.
We need to parse the description.
Key parts:
- Intro: "AWS Global Sales drives adoption..." etc. This is description of team. Could be "About the role" or "About the team". We need sections only when there is real specific content.
We have sections: "Key job responsibilities" (list). "A day in the life" (prose). "About The Team" with subheadings: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are sub-sections under About The Team. Could we treat "About The Team" as a section with subsections? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings like About the team, Responsibilities, Qualifications, etc. For subheadings maybe we can still use but they'd be same level; but we can embed them as
maybe. Simpler: produce sections: About the team (with paragraphs covering Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance). Responsibilities (list). Qualifications (Basic Qualifications and Preferred Qualifications). Benefits (the paragraph about benefits). Pay (salary ranges). Possibly Schedule not present, so omit.
We must not include sections with filler like "commensurate with experience". Not present.
We need to preserve all substantive info; do not invent or summarize away detail. So we need to include the bullet points from responsibilities, the day in the life paragraph, the basic qualifications list, preferred qualifications list, benefits paragraph, pay ranges.
We must remove boilerplate: EEO statement, accommodation link, etc. Also remove "Amazon is an equal opportunity employer..." and the accommodation link. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Company - Amazon Web Services, Inc. Job ID: A10558638". Also remove "Our team empowers every customer..." maybe part of intro but we can include in About the team? Actually that is part of description of AWS Global Sales. Could be part of About the team or About the role. We'll include in About the team paragraph.
We need to ensure we don't repeat job title as heading. The job title is "Solutions Architect". Not to be used as heading.
Now produce HTML.
Structure:
About the team
... (intro about AWS Global Sales drives adoption... plus team description)
Maybe then subpoints as paragraphs.
But we have multiple subheadings under About The Team: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. We could treat each as as well, but that would be many sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine them into one About the team section with paragraphs covering each topic.
Thus:
About the team
AWS Global Sales drives adoption of the AWS cloud worldwide, enabling customers of all sizes to innovate and expand in the cloud. Our team empowers every customer to grow by providing tailored service, unmatched technology, and committed support. We dive deep to understand each customer's unique challenges, then craft innovative solutions that accelerate their success. This customer-first approach is how we built the world's most adopted cloud.
Diverse Experiences: AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying.
Why AWS?: Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses.
Inclusive Team Culture: AWS values curiosity and connection. Our employee-led and company-sponsored affinity groups promote inclusion and empower our people to take pride in what makes us unique. Our inclusion events foster stronger, more collaborative teams. Our continual innovation is fueled by the bold ideas, fresh perspectives, and passionate voices our teams bring to everything we do.
Mentorship & Career Growth: We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional.
Work/Life Balance: We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve.
Now Responsibilities:
We have "Key job responsibilities" list bullet points:
- Serve as a key member of the Solutions Architecture team in helping to ensure customer success in building applications and services on the AWS platform.
- Scope each customer engagement, with attention towards clear and well-defined objectives and success criteria.
- Own each engagement, and help ensure a timely and successful delivery of value.
- Capture and share best-practice knowledge amongst the solution architect community.
- Understand the AWS market segments, customer base, and industry verticals.
- Understand and use of salesforce.com and other internal Amazon systems.
Also there is "A day in the life" paragraph.
We could make Responsibilities section with - for those bullet points. Then maybe a separate section "Typical day" with paragraph.
But instruction: Prefer a few substantive sections over many thin ones. Could combine Responsibilities and A day in the life into one section? But they are distinct. Could have Responsibilities (list) and then a paragraph for day in the life under same section? Might be okay.
Better: Have
Responsibilities
with - list. Then after that, maybe a
for "A day in the life". But that would be mixing list and prose under same heading; still okay.
Alternatively, separate sections: Responsibilities and Typical Day. But that adds another heading. Might be okay if both substantive.
Given instruction to prefer few sections, maybe combine.
Let's do:
Responsibilities
- Serve as a key member of the Solutions Architecture team in helping to ensure customer success in building applications and services on the AWS platform.
- Scope each customer engagement, with attention towards clear and well-defined objectives and success criteria.
- Own each engagement, and help ensure a timely and successful delivery of value.
- Capture and share best-practice knowledge amongst the solution architect community.
- Understand the AWS market segments, customer base, and industry verticals.
- Understand and use of salesforce.com and other internal Amazon systems.
A typical day as an AWS Solutions Architect blends strategic customer engagements with technical deep-dives. You might start with a workshop helping a customer architect their generative AI solution, followed by collaborating with account teams to develop approaches for an upcoming migration project. After lunch, you'll lead a technical discovery session with a customer exploring analytics solutions, then spend time reviewing architectural designs and providing best practice guidance. The day might end with contributing to internal knowledge-sharing sessions or preparing for upcoming customer presentations. Each day brings unique challenges and opportunities to help customers innovate on AWS.
Now Qualifications:
We have Basic Qualifications (list) and Preferred Qualifications (list). Could combine into Qualifications section with two sublists? Or separate Basic and Preferred. Might be okay to have two subheadings but they'd be again. Could do Qualifications
then Basic Qualifications
etc but we only allowed for section headings per instruction? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use for each major section and inside use
or
. For Basic and Preferred we could just have two under same heading with preceding labels.
Thus:
Qualifications
Basic Qualifications
- 2+ years of design, implementation, or consulting in applications and infrastructures experience
- 4+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
- 10+ years of IT development or implementation/consulting in the software or Internet industries experience
Preferred Qualifications
- Experience working within software development or Internet-related industries
- Experience migrating or transforming legacy customer solutions to the cloud
- Experience working with AWS technologies from a dev/ops perspective
Now Benefits:
Paragraph: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits."
We should keep the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not boilerplate; it's part of benefits description. Might keep it. However, it's a link; we can keep as plain text or as . The instruction didn't forbid links. We'll keep as plain URL.
Thus:
Benefits
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.
Now Pay:
We have salary ranges for three locations: Chicago, Austin, Dallas each same range. We should include that.
Thus:
Pay
USA, IL, Chicago - $131,300.00 - $177,600.00 USD annually
USA, TX, Austin - $131,300.00 - $177,600.00 USD annually
USA, TX, Dallas - $131,300.00 - $177,600.00 USD annually
We could also mention that base salary range listed below, sign-on payments and RSUs. 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
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate, navigation, EEO, etc. Keep substantive info. We need to parse the description. Key parts: - Intro: "AWS Global Sales drives adoption..." etc. This is description of team. Could be "About the role" or "About the team". We need sections only when there is real specific content. We have sections: "Key job responsibilities" (list). "A day in the life" (prose). "About The Team" with subheadings: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are sub-sections under About The Team. Could we treat "About The Team" as a section with subsections? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings like About the team, Responsibilities, Qualifications, etc. For subheadings maybe we can still use but they'd be same level; but we can embed them as
maybe. Simpler: produce sections: About the team (with paragraphs covering Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance). Responsibilities (list). Qualifications (Basic Qualifications and Preferred Qualifications). Benefits (the paragraph about benefits). Pay (salary ranges). Possibly Schedule not present, so omit. We must not include sections with filler like "commensurate with experience". Not present. We need to preserve all substantive info; do not invent or summarize away detail. So we need to include the bullet points from responsibilities, the day in the life paragraph, the basic qualifications list, preferred qualifications list, benefits paragraph, pay ranges. We must remove boilerplate: EEO statement, accommodation link, etc. Also remove "Amazon is an equal opportunity employer..." and the accommodation link. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Company - Amazon Web Services, Inc. Job ID: A10558638". Also remove "Our team empowers every customer..." maybe part of intro but we can include in About the team? Actually that is part of description of AWS Global Sales. Could be part of About the team or About the role. We'll include in About the team paragraph. We need to ensure we don't repeat job title as heading. The job title is "Solutions Architect". Not to be used as heading. Now produce HTML. Structure:
About the team
... (intro about AWS Global Sales drives adoption... plus team description)
Maybe then subpoints as paragraphs. But we have multiple subheadings under About The Team: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. We could treat each as as well, but that would be many sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine them into one About the team section with paragraphs covering each topic.
Thus:
About the team
AWS Global Sales drives adoption of the AWS cloud worldwide, enabling customers of all sizes to innovate and expand in the cloud. Our team empowers every customer to grow by providing tailored service, unmatched technology, and committed support. We dive deep to understand each customer's unique challenges, then craft innovative solutions that accelerate their success. This customer-first approach is how we built the world's most adopted cloud.
Diverse Experiences: AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying.
Why AWS?: Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses.
Inclusive Team Culture: AWS values curiosity and connection. Our employee-led and company-sponsored affinity groups promote inclusion and empower our people to take pride in what makes us unique. Our inclusion events foster stronger, more collaborative teams. Our continual innovation is fueled by the bold ideas, fresh perspectives, and passionate voices our teams bring to everything we do.
Mentorship & Career Growth: We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional.
Work/Life Balance: We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve.
Now Responsibilities: We have "Key job responsibilities" list bullet points: - Serve as a key member of the Solutions Architecture team in helping to ensure customer success in building applications and services on the AWS platform. - Scope each customer engagement, with attention towards clear and well-defined objectives and success criteria. - Own each engagement, and help ensure a timely and successful delivery of value. - Capture and share best-practice knowledge amongst the solution architect community. - Understand the AWS market segments, customer base, and industry verticals. - Understand and use of salesforce.com and other internal Amazon systems. Also there is "A day in the life" paragraph. We could make Responsibilities section with- for those bullet points. Then maybe a separate section "Typical day" with paragraph.
But instruction: Prefer a few substantive sections over many thin ones. Could combine Responsibilities and A day in the life into one section? But they are distinct. Could have Responsibilities (list) and then a paragraph for day in the life under same section? Might be okay.
Better: Have
Responsibilities
with- list. Then after that, maybe a
for "A day in the life". But that would be mixing list and prose under same heading; still okay. Alternatively, separate sections: Responsibilities and Typical Day. But that adds another heading. Might be okay if both substantive. Given instruction to prefer few sections, maybe combine. Let's do:
Responsibilities
- Serve as a key member of the Solutions Architecture team in helping to ensure customer success in building applications and services on the AWS platform.
- Scope each customer engagement, with attention towards clear and well-defined objectives and success criteria.
- Own each engagement, and help ensure a timely and successful delivery of value.
- Capture and share best-practice knowledge amongst the solution architect community.
- Understand the AWS market segments, customer base, and industry verticals.
- Understand and use of salesforce.com and other internal Amazon systems.
A typical day as an AWS Solutions Architect blends strategic customer engagements with technical deep-dives. You might start with a workshop helping a customer architect their generative AI solution, followed by collaborating with account teams to develop approaches for an upcoming migration project. After lunch, you'll lead a technical discovery session with a customer exploring analytics solutions, then spend time reviewing architectural designs and providing best practice guidance. The day might end with contributing to internal knowledge-sharing sessions or preparing for upcoming customer presentations. Each day brings unique challenges and opportunities to help customers innovate on AWS.
Now Qualifications: We have Basic Qualifications (list) and Preferred Qualifications (list). Could combine into Qualifications section with two sublists? Or separate Basic and Preferred. Might be okay to have two subheadings but they'd beagain. Could do
Qualifications
thenBasic Qualifications
etc but we only allowedfor section headings per instruction? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use
for each major section and inside use
or
- . For Basic and Preferred we could just have two
- 2+ years of design, implementation, or consulting in applications and infrastructures experience
- 4+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
- 10+ years of IT development or implementation/consulting in the software or Internet industries experience
- Experience working within software development or Internet-related industries
- Experience migrating or transforming legacy customer solutions to the cloud
- Experience working with AWS technologies from a dev/ops perspective
- under same heading with preceding
labels. Thus:
Qualifications
Basic Qualifications
Preferred Qualifications
Benefits
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.
Now Pay: We have salary ranges for three locations: Chicago, Austin, Dallas each same range. We should include that. Thus:Pay
USA, IL, Chicago - $131,300.00 - $177,600.00 USD annually
We could also mention that base salary range listed below, sign-on payments and RSUs. 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
USA, TX, Austin - $131,300.00 - $177,600.00 USD annually
USA, TX, Dallas - $131,300.00 - $177,600.00 USD annually
- list. Then after that, maybe a