Solutions Architect, Commercial Midmarket
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove Los Angeles County specifics? That's legal/EEO? It's about accommodations, maybe considered EEO. Probably remove that block. Also remove "Amazon is an equal opportunity employer..." etc. Remove "If you have a disability..." etc. Remove "If the country/region you’re applying in isn’t listed..." Remove "Our inclusive culture..." maybe keep? It's about culture but could be considered boilerplate. Safer to remove generic culture statements unless they are specific. The posting includes sections: Description (intro), About The Team (with subpoints: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance). Those could be considered "About the role" or maybe "About the team". We need to decide headings. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content matches. We have responsibilities: "Key job responsibilities" list. Also "A day in the life" could be part of responsibilities or separate but we can include under Responsibilities. Qualifications: Basic Qualifications and Preferred Qualifications. Skills maybe not separate. Benefits: there is a paragraph about benefits (health insurance etc). Pay: there is salary range info. Schedule: not mentioned. So we should not include Schedule heading. Benefits: we have details. Pay: we have salary ranges. Also we have location specifics: USA, CA, Culver City - range; USA, WA, Seattle - same range. Could include under Pay.
We need to preserve all substantive information. So we need to include the description paragraphs, About The Team subpoints, responsibilities list, day in the life paragraph, qualifications, benefits, pay.
We must not include boilerplate like "Amazon is an equal opportunity employer..." etc. Also remove Los Angeles County specifics. Also remove "Our inclusive culture empowers Amazonians..." maybe borderline but it's generic; better to remove.
We must not invent or summarize away detail. So we need to keep the exact text? We can keep substance but not necessarily verbatim? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the info but can rephrase? Safer to keep the original sentences but we can format as lists.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
About the role
... description paragraphs ...
Maybe combine intro and About The Team? Could be separate sections: About the role (intro + About The Team). But we have About The Team heading in original; we could treat that as part of About the role. However instruction says use headings like About the role, Responsibilities, etc. So we can have About the role containing the initial description and About The Team subsections as paragraphs or maybe nested? Could also addAbout the team
but not in list; but they said e.g. About the role, Responsibilities... but not limited to those? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those examples; we can also use other headings if needed but better to follow examples. So we can put About the role covering the description and team info.
Responsibilities: include "Key job responsibilities" list and "A day in the life" paragraph.
Requirements: maybe combine Basic Qualifications and Preferred Qualifications? Could have Requirements heading containing both basic and preferred. Or we could have Qualifications heading for basic and preferred. The examples include Requirements and Qualifications separate. We could put Requirements for basic qualifications, Qualifications for preferred. Or combine. Let's do: Requirements
for Basic Qualifications list. Qualifications
for Preferred Qualifications list.
Skills: not explicitly listed; we could omit.
Benefits: include benefits paragraph.
Pay: include salary range info.
Schedule: not present, omit.
We must not include headings with filler. So ensure each heading has substantive content.
Now we need to strip out boilerplate: remove "Amazon is an equal opportunity employer..." etc. Also remove Los Angeles County specifics. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc. Also remove "Our inclusive culture empowers Amazonians..." maybe part of About The Team but it's generic; we could keep the subpoints under About The Team: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are specific headings within About The Team. We could keep them as paragraphs under About the role. But we need to preserve the content under those headings. The text includes:
About The Team
Diverse Experiences
[paragraph]
Why AWS?
[paragraph]
Inclusive Team Culture
[paragraph]
Mentorship & Career Growth
[paragraph]
Work/Life Balance
[paragraph]
We should keep those as maybe inside? But we only allowed for section headings. However we can still use for main sections and use
for section headings. However we can still use for main sections and use
for the subheadings text? Could embed subheadings as or just as part of paragraph. The instruction didn't forbid other headings, but said use with bold text.
Thus About the role section will contain paragraphs: the initial description, then maybe a with leading bold.
Let's extract the text.
Description paragraph:
"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. Join us and help us grow. Amazon Web Services is looking for a highly motivated Solutions Architect to help accelerate customer adoption. This is an excellent opportunity to join Amazon’s world class technical teams, working with some of the best and brightest engineers, architects and technical managers while also developing your skills and furthering your career within one of the most innovative and progressive technology companies anywhere. As a Solutions Architect in the AWS Commercial Midmarket group you will work directly with Small and Medium Business customers. We are looking for individuals who are motivated by the opportunity to work backwards from these customers' needs and help them gain competitive edge using AWS. As an experienced technologist and key member of the Account team you will help influence customers' architectural choices across broad use cases involving security, compute, storage networking as well as advanced scenarios involving serverless, analytics, and AI/ML. As a part of the role, you will provide exceptional technical design guidance and thought leadership. You will lead efforts to capture and share best-practice knowledge with the AWS solution architect community. You will also gain the opportunity to learn from, collaborate with, and educate some of the brightest technical minds in the industry today across the breadth of enterprise architecture."
That's the description.
Now About The Team subpoints:
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:
Key job responsibilities list:
- 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.
Then "A day in the life" paragraph:
"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 Requirements (Basic Qualifications):
List:
- 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
- 4+ years of IT development or implementation/consulting in the software or Internet industries experience
Now Qualifications (Preferred Qualifications):
List:
- 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: "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."
Now Pay:
We have salary ranges: "USA, CA, Culver City - 131,300.00 - 177,600.00 USD annually" and "USA, WA, Seattle - 131,300.00 - 1 for section headings (e.g. About the role, Responsibilities...). It didn't say we cannot use other heading levels. Safer to keep them as
About The Team
then subpoints.
But to avoid extra headings, we could just treat the About The Team content as series of