Sr. GenAI Specialist Solutions Architect, SLG/EDU Specialist SA
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the job description.
Key sections:
- Description (intro) about role: paragraphs.
- Key job responsibilities: list of bullet points.
- About The Team: paragraphs.
- Basic Qualifications: list.
- Preferred Qualifications: list.
- Pay: The base salary range listed: "USA, TX, Dallas - 153,600.00 - 207,800.00 USD annually" etc. Also mention sign-on payments and RSUs, benefits. So we have Pay info.
- Benefits: mention comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave, etc. Also link to benefits page.
- Schedule: Not mentioned explicitly. No schedule info. So we should not create Schedule section.
- Skills: Not explicit separate list; but we could embed in qualifications. Probably not needed.
We need to decide sections: About the role (intro), Responsibilities, Requirements (maybe Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay. Could also have About The Team as part of About the role? But we could make separate section "About the Team". However instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not mandatory to use exactly those; we can use those headings if content exists. We should not create sections with filler.
Thus we can have:
About the role
with intro paragraphs.
Responsibilities
with - list.
Requirements
with Basic Qualifications list.
Qualifications
with Preferred Qualifications list.
Benefits
with benefits description.
Pay
with salary range and mention of sign-on payments and RSUs.
We should not include Schedule.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, basic qualifications, preferred qualifications, benefits details, pay details.
We must remove boilerplate: EEO, accommodation link, etc. Also remove duplicated lines, application instructions. Also remove "About The Team" maybe we can incorporate into About the role? But we have content about team: "Diverse Experiences..." etc. That is substantive. Could be its own section "About the Team". However the allowed headings list does not include About the Team, but we could still use it? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we could incorporate About the Team content into About the role or maybe a separate section "About the Team". Since they didn't forbid other headings, but they gave examples. I'd include a section "About the Team" as it's substantive.
But we need to avoid too many thin sections. We have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, About the Team. That's 7 sections; maybe okay.
We need to ensure we don't repeat job title as heading. Not using.
We need to not put Job ID as heading; we can drop it or put in a short
. Probably drop it.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
Intro paragraphs:
"AWS Specialist Solutions Architects (SSAs) are technologists with deep domain-specific expertise, able to address advanced concepts and feature designs. As part of the AWS sales organization, SSAs work with customers who have complex challenges that require expert-level knowledge to solve. SSAs craft scalable, flexible, and resilient technical architectures that address those challenges. This might involve guiding customers as they refactor an application or designing entirely new cloud-based systems. Specialist SAs play a critical role in capturing customer feedback, advocating for roadmap enhancements, and anticipating customer requirements as they work backwards from their needs. As domain experts, SSAs also participate in field engagement and enablement, producing content such as whitepapers, blogs, and workshops for customers, partners, and the AWS Technical Field. GenAI Specialist Solutions Architects combine technical skills in AIML, business acumen, and technical sales skills. They are focused on supporting customers throughout the engagement lifecycle and work closely with the teams that support implementation including AWS Sellers, Professional Services and Partners. SSAs unblock customers and help them get to production faster. Joining AWS as a Specialist Solutions Architect will give you opportunities to work on interesting and challenging problems, collaborate with a group of skilled practitioners focused on delivering outcomes for our customers, and be part of a diverse and inclusive community committed to being Earth’s Best Employer. SSAs help build and scale go-to-market plans that turn AWS ideas into multi-billion-dollar businesses in State & Local Government and Education Industry. Our teams include specialist sales, and specialist solutions architecture, working together to provide customer-obsessed solutions that help people run their businesses more effectively. We pride ourselves on thinking big, delivering exceptional results for our customers, and working across AWS as #OneTeam. As a Specialist Solution Architect on the GenAI team, you will have the opportunity to work across key GenAI-related services like Amazon Bedrock, Amazon Kiro, Amazon Sagemaker, Amazon Quick to develop architecture, proof-of-concepts, prototypes, and demos to help customers build, deploy, and consume GenAI models in production. Your work will have a direct impact on enabling customer builds and leveraging GenAI models, GenAI AWS revenue, and developing our services and informing product roadmaps via market and customer signals. This position can be based in Washington DC, Seattle or Dallas Fort Worth."
That's a lot; we can keep as paragraphs.
Responsibilities bullet list:
- Serve as a trusted technical advisor on Generative AI solutions (Amazon Bedrock, Amazon Q, SageMaker, and related AI/ML services) for strategic Education, State & Local Government, and GovTech/EdTech customers
- Lead architecture design sessions, technical deep-dives, and proof-of-concept engagements for complex GenAI opportunities
- Provide expert-level guidance on GenAI architectures, model selection, fine-tuning strategies, RAG patterns, and responsible AI implementation
- Partner with account teams on strategic account planning, contributing GenAI domain expertise to accelerate the sales cycle and improve solution accuracy
- Present at AWS Summits, re:Invent, and industry conferences on GenAI topics relevant to public sector customers
- Create and publish external-facing content (blogs, whitepapers, demos, workshops, GitHub repos) showcasing GenAI best practices for EDU/SLG/XTECH use cases
- Deliver internal enablement sessions aligned with EDU/SLG/XTECH customer requirements and organizational tech goals
- Build the team's external credibility and visibility as recognized EDU/SLG GenAI domain experts through internal enablement sessions and mentoring field members
- Channel customer requirements, pain points, and feature requests to AWS service teams (Bedrock, SageMaker, Amazon Q); advocate for public sector-specific capabilities and compliance requirements
- Partner with service teams on beta programs, roadmap reviews, and closed-loop feedback to ensure EDU/SLG customer needs shape product development
- Contribute to internal knowledge bases, newsletters, and Highspot content that scale specialist impact across the organization
- Obtain SA Associate certification within 6 months and SA Pro certification within 18 months (role requirements)
- Stay current on rapidly evolving GenAI services, emerging architectures, and competitive landscape
Basic Qualifications list:
- Bachelor's degree
- 5+ years of design, implementation, or consulting in applications and infrastructures experience
- 8+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
Preferred Qualifications list:
- Cloud Technology Certification (such as Solutions Architecture, Cloud Security Professional or Cloud DevOps Engineering)
- Knowledge of AWS services, market segments, customer base and industry verticals
- Experience working with end user or developer communities
- Knowledge of cloud architecture
- Knowledge of software development tools and methodologies
Benefits description:
"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."
Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's part of compensation.
Pay section:
"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 ..."
Then specific ranges:
"USA, TX, Dallas - 153,600.00 - 207,800.00 USD annually
USA, VA, Arlington - 153,600.00 - 207,800.00 USD annually
USA, WA, Seattle - 153,600.00 - 207,800.00 USD annually"
We should include that.
About The Team section:
"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."
We need to preserve all substantive info. This is a lot but okay.
We must remove boilerplate: EEO statement, accommodation link,
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the job description. Key sections: - Description (intro) about role: paragraphs. - Key job responsibilities: list of bullet points. - About The Team: paragraphs. - Basic Qualifications: list. - Preferred Qualifications: list. - Pay: The base salary range listed: "USA, TX, Dallas - 153,600.00 - 207,800.00 USD annually" etc. Also mention sign-on payments and RSUs, benefits. So we have Pay info. - Benefits: mention comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave, etc. Also link to benefits page. - Schedule: Not mentioned explicitly. No schedule info. So we should not create Schedule section. - Skills: Not explicit separate list; but we could embed in qualifications. Probably not needed. We need to decide sections: About the role (intro), Responsibilities, Requirements (maybe Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay. Could also have About The Team as part of About the role? But we could make separate section "About the Team". However instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not mandatory to use exactly those; we can use those headings if content exists. We should not create sections with filler. Thus we can have:
About the role
with intro paragraphs.Responsibilities
with- list.
Requirements
with Basic Qualifications list.Qualifications
with Preferred Qualifications list.Benefits
with benefits description.Pay
with salary range and mention of sign-on payments and RSUs. We should not include Schedule. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, basic qualifications, preferred qualifications, benefits details, pay details. We must remove boilerplate: EEO, accommodation link, etc. Also remove duplicated lines, application instructions. Also remove "About The Team" maybe we can incorporate into About the role? But we have content about team: "Diverse Experiences..." etc. That is substantive. Could be its own section "About the Team". However the allowed headings list does not include About the Team, but we could still use it? The instruction: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we could incorporate About the Team content into About the role or maybe a separate section "About the Team". Since they didn't forbid other headings, but they gave examples. I'd include a section "About the Team" as it's substantive. But we need to avoid too many thin sections. We have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, About the Team. That's 7 sections; maybe okay. We need to ensure we don't repeat job title as heading. Not using. We need to not put Job ID as heading; we can drop it or put in a short
. Probably drop it. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Intro paragraphs: "AWS Specialist Solutions Architects (SSAs) are technologists with deep domain-specific expertise, able to address advanced concepts and feature designs. As part of the AWS sales organization, SSAs work with customers who have complex challenges that require expert-level knowledge to solve. SSAs craft scalable, flexible, and resilient technical architectures that address those challenges. This might involve guiding customers as they refactor an application or designing entirely new cloud-based systems. Specialist SAs play a critical role in capturing customer feedback, advocating for roadmap enhancements, and anticipating customer requirements as they work backwards from their needs. As domain experts, SSAs also participate in field engagement and enablement, producing content such as whitepapers, blogs, and workshops for customers, partners, and the AWS Technical Field. GenAI Specialist Solutions Architects combine technical skills in AIML, business acumen, and technical sales skills. They are focused on supporting customers throughout the engagement lifecycle and work closely with the teams that support implementation including AWS Sellers, Professional Services and Partners. SSAs unblock customers and help them get to production faster. Joining AWS as a Specialist Solutions Architect will give you opportunities to work on interesting and challenging problems, collaborate with a group of skilled practitioners focused on delivering outcomes for our customers, and be part of a diverse and inclusive community committed to being Earth’s Best Employer. SSAs help build and scale go-to-market plans that turn AWS ideas into multi-billion-dollar businesses in State & Local Government and Education Industry. Our teams include specialist sales, and specialist solutions architecture, working together to provide customer-obsessed solutions that help people run their businesses more effectively. We pride ourselves on thinking big, delivering exceptional results for our customers, and working across AWS as #OneTeam. As a Specialist Solution Architect on the GenAI team, you will have the opportunity to work across key GenAI-related services like Amazon Bedrock, Amazon Kiro, Amazon Sagemaker, Amazon Quick to develop architecture, proof-of-concepts, prototypes, and demos to help customers build, deploy, and consume GenAI models in production. Your work will have a direct impact on enabling customer builds and leveraging GenAI models, GenAI AWS revenue, and developing our services and informing product roadmaps via market and customer signals. This position can be based in Washington DC, Seattle or Dallas Fort Worth." That's a lot; we can keep as paragraphs. Responsibilities bullet list: - Serve as a trusted technical advisor on Generative AI solutions (Amazon Bedrock, Amazon Q, SageMaker, and related AI/ML services) for strategic Education, State & Local Government, and GovTech/EdTech customers - Lead architecture design sessions, technical deep-dives, and proof-of-concept engagements for complex GenAI opportunities - Provide expert-level guidance on GenAI architectures, model selection, fine-tuning strategies, RAG patterns, and responsible AI implementation - Partner with account teams on strategic account planning, contributing GenAI domain expertise to accelerate the sales cycle and improve solution accuracy - Present at AWS Summits, re:Invent, and industry conferences on GenAI topics relevant to public sector customers - Create and publish external-facing content (blogs, whitepapers, demos, workshops, GitHub repos) showcasing GenAI best practices for EDU/SLG/XTECH use cases - Deliver internal enablement sessions aligned with EDU/SLG/XTECH customer requirements and organizational tech goals - Build the team's external credibility and visibility as recognized EDU/SLG GenAI domain experts through internal enablement sessions and mentoring field members - Channel customer requirements, pain points, and feature requests to AWS service teams (Bedrock, SageMaker, Amazon Q); advocate for public sector-specific capabilities and compliance requirements - Partner with service teams on beta programs, roadmap reviews, and closed-loop feedback to ensure EDU/SLG customer needs shape product development - Contribute to internal knowledge bases, newsletters, and Highspot content that scale specialist impact across the organization - Obtain SA Associate certification within 6 months and SA Pro certification within 18 months (role requirements) - Stay current on rapidly evolving GenAI services, emerging architectures, and competitive landscape Basic Qualifications list: - Bachelor's degree - 5+ years of design, implementation, or consulting in applications and infrastructures experience - 8+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience Preferred Qualifications list: - Cloud Technology Certification (such as Solutions Architecture, Cloud Security Professional or Cloud DevOps Engineering) - Knowledge of AWS services, market segments, customer base and industry verticals - Experience working with end user or developer communities - Knowledge of cloud architecture - Knowledge of software development tools and methodologies Benefits description: "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." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's part of compensation. Pay section: "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 ..." Then specific ranges: "USA, TX, Dallas - 153,600.00 - 207,800.00 USD annually USA, VA, Arlington - 153,600.00 - 207,800.00 USD annually USA, WA, Seattle - 153,600.00 - 207,800.00 USD annually" We should include that. About The Team section: "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." We need to preserve all substantive info. This is a lot but okay. We must remove boilerplate: EEO statement, accommodation link,