Senior Solutions Architect, Retail, Consumer Goods & Restaurants, AWS
Amazon Web Services (AWS) · Miami, FL · 1 mo ago
ConsultingFull-time
We need to output HTML fragment with sections: headings 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 as heading. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Diverse Experiences" maybe not a standard heading; but we can include as part of About the role? It's more like encouragement to apply; maybe we can treat as part of About the role or a separate section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. "Diverse Experiences" is specific content encouraging candidates to apply; but it's not a standard heading list. Could be part of About the role or maybe a separate "About the Team"? Actually there is "About The Team" later. So we have sections: About the role (description), Responsibilities (Key job responsibilities), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe not separate; but we could combine with Requirements/Qualifications). Benefits (they mention benefits: health insurance, 401(k) matching, paid time off, parental leave, etc). Pay (they list salary ranges per location). Schedule (they mention Work/Life Harmony: flexible hours, remote work supported, work autonomy, flexible hours self-defined). So we have content for Benefits, Pay, Schedule.
We must not include sections like "About the role" if we have content; yes we have description. "Responsibilities": we have key job responsibilities bullet list. "Requirements": Basic Qualifications. "Qualifications": Preferred Qualifications. "Skills": maybe not needed separately; but we could include if there is explicit skills list; not really. Could omit Skills section.
We must not repeat job title as heading. Must not put Job ID as heading.
We must output only HTML fragment, no /, no markdown fences.
We need to use
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 as heading. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Diverse Experiences" maybe not a standard heading; but we can include as part of About the role? It's more like encouragement to apply; maybe we can treat as part of About the role or a separate section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. "Diverse Experiences" is specific content encouraging candidates to apply; but it's not a standard heading list. Could be part of About the role or maybe a separate "About the Team"? Actually there is "About The Team" later. So we have sections: About the role (description), Responsibilities (Key job responsibilities), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe not separate; but we could combine with Requirements/Qualifications). Benefits (they mention benefits: health insurance, 401(k) matching, paid time off, parental leave, etc). Pay (they list salary ranges per location). Schedule (they mention Work/Life Harmony: flexible hours, remote work supported, work autonomy, flexible hours self-defined). So we have content for Benefits, Pay, Schedule.
We must not include sections like "About the role" if we have content; yes we have description. "Responsibilities": we have key job responsibilities bullet list. "Requirements": Basic Qualifications. "Qualifications": Preferred Qualifications. "Skills": maybe not needed separately; but we could include if there is explicit skills list; not really. Could omit Skills section.
We must not repeat job title as heading. Must not put Job ID as heading.
We must output only HTML fragment, no /, no markdown fences.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
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, pay ranges, schedule/flexibility info.
We must remove boilerplate: EEO statement, accommodation link, etc. Also remove "Diverse Experiences" maybe not boilerplate but it's a encouragement; but we could incorporate into About the role paragraph. The instruction: remove duplicated lines, and application instructions. "Diverse Experiences" is not application instructions but it's a note encouraging candidates; we could keep as part of About the role. However it's a separate paragraph; we could keep it as a
under About the role.
Also remove "Why AWS?" etc? That's promotional but maybe considered boilerplate? It's not EEO but it's generic marketing; but we need to preserve substantive information. The "Why AWS?" section includes description of AWS; that's substantive about company but maybe not required? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why AWS?" is not those; it's company description. Might be considered substantive? It's generic but could be kept. However we need to avoid too many thin sections. Could incorporate into About the role or About the Team? There's also "About The Team" later. So we could keep "About The Team" as a section? The instruction says use headings for sections like About the role, Responsibilities, etc. Not explicitly About The Team, but we could treat as About the role? Might be better to have About the role (description) and About the Team separate? The instruction only lists certain headings; but we can still use other headings? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could also use other headings if needed, but better to stick to those. So we can map content to those sections.
Thus:
- About the role: combine the initial description paragraph ("As a trusted customer advocate...") plus maybe the "Why AWS?" and "Inclusive Team Culture" etc? But those are more about company; maybe we can put them under About the role as well. However we also have "About The Team" later; we could treat that as About the role as well? Might be duplication. Safer: Use About the role for the initial description paragraph (the first paragraph). Use Responsibilities for key job responsibilities. Use Requirements for Basic Qualifications. Use Qualifications for Preferred Qualifications. Use Benefits for benefits paragraph. Use Pay for salary ranges. Use Schedule for work/life harmony details.
We must not include filler like "commensurate with experience". Not present.
Now we need to extract specifics.
Let's parse the posting.
Description paragraph:
"As a trusted customer advocate, Solutions Architects help organizations understand best practices around advanced cloud-based solutions, and provide advice on strategies for migrating existing workloads to the cloud. You’ll help drive successful business outcomes across a broad set of enterprise customers in Retail, Consumer Goods & Restaurants through your passion for educating, training, designing and building cloud solutions. You will have the opportunity to help shape and execute a strategy to build deep adoption and broad use of AWS within your enterprise customers, and you will do this by mobilizing resources within AWS and working with our extensive partner network."
That's the description.
Then "Work/Life Harmony" paragraph: "Our team is focused on balancing life with our work, and we do this via work autonomy and by prioritizing solutions and processes that enable us to scale faster than the business. While there may be an opportunity to work from an office (location dependent), working remotely is supported, and often times encouraged. Work hours are flexible and typically self-defined."
That's schedule/flexibility.
Then "Key job responsibilities" bullet list:
- In partnership with the sales team, formulate and execute a sales strategy to exceed revenue objectives through the adoption of AWS
- As a key member of the business development and sales team, ensure success in building and migrating applications, software and services on the AWS platform
- Educate customers of all sizes on the value proposition of AWS, and participate in deep architectural discussions to ensure solutions are designed for successful deployment in the cloud
- Conduct one-to-few and one-to-many training sessions to transfer knowledge to customers considering or already using AWS
- Capture and share best-practice knowledge amongst the AWS solutions architect community
- Author or otherwise contribute to AWS customer-facing publications such as whitepapers
- Build deep relationships with senior technical individuals within customers to enable them to be cloud advocates
- Act as a technical liaison between customers, service engineering teams and support
Then "A day in the life" heading? Actually after responsibilities there is "A day in the life" then "Diverse Experiences" etc. But we can ignore "A day in the life" as it's just a heading with no content? Actually after that heading there is "Diverse Experiences" paragraph: "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."
That's encouragement; we could incorporate into About the role or maybe a separate section but not required. We'll keep as part of About the role maybe after description.
Then "Why AWS?" paragraph: description of AWS.
Then "Inclusive Team Culture" paragraph.
Then "Mentorship & Career Growth" paragraph.
Then "Work/Life Balance" paragraph (similar to Work/Life Harmony but more generic). Actually we already have Work/Life Harmony earlier; there is also Work/Life Balance later repeating similar content. Might be duplicate; we should deduplicate.
Then "About The Team" paragraph: description of team.
Then "Basic Qualifications" bullet list:
- Knowledge of AWS services, market segments, customer base and industry verticals
- 10+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
- 5+ years of design, implementation, or consulting in applications and infrastructures experience
Then "Preferred Qualifications" bullet list:
- Experience and technical expertise (design and implementation) in cloud computing technologies
- Experience migrating or transforming legacy customer solutions to the cloud
- Experience in written and oral communication, including the ability to communicate with all levels in the organization (technical, business, executive)
- Experience implementing innovative learning and development solutions in a fast-paced global environment
- Ability to design and implement generative AI and agentic solutions that drive business outcomes
Then EEO boilerplate etc.
Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits."
Then location salary ranges:
- USA, GA, Atlanta - 153,600.00 - 207,800.00 USD annually
- USA, IL, Chicago - 153,600.00 - 207,800.00 USD annually
- USA, NY, New York - 169,000.00 - 228,600.00 USD annually
- USA, TX, Dallas - 153,600.00 - 207,800.00 USD annually
Then "Company - Amazon Web Services, Inc. Job ID: A10530387"
We need to preserve all substantive info. So we need to include the benefits list, the salary ranges, the work/life harmony/flexibility info.
We must not include boilerplate like EEO, accommodation link, etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe considered a link; but it's part of benefits description; we could keep the sentence but maybe it's okay. It's not boilerplate; it's a reference. Might keep.
We must not include duplicated lines. There's duplicate work/life harmony and work/life balance; we should combine or keep one. We'll keep the Work/Life Harmony paragraph (first) and maybe ignore the later Work/Life Balance as duplicate.
Also "A day in the life" heading with no content after? Actually after that heading there is "Diverse Experiences". So we could treat "A day in the life" as a heading but no specific content; better to ignore it and just treat Diverse Experiences as part of About the role.
Now we need to output HTML.
Structure:
About the role
... description ...
... Diverse Experiences encouragement ...
... Why AWS? ...
... Inclusive Team Culture ...
... Mentorship & Career Growth ...
... About The Team ...
But that may be many thin sections; but we can combine into one with multiple sentences? The instruction: Prefer a few substantive sections over many thin ones. So we should avoid many thin sections. Perhaps we should keep About the role as a single
containing all those paragraphs combined (with appropriate spacing).
- for any list of duties/requirements/benefits. Use
for prose. 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, pay ranges, schedule/flexibility info. We must remove boilerplate: EEO statement, accommodation link, etc. Also remove "Diverse Experiences" maybe not boilerplate but it's a encouragement; but we could incorporate into About the role paragraph. The instruction: remove duplicated lines, and application instructions. "Diverse Experiences" is not application instructions but it's a note encouraging candidates; we could keep as part of About the role. However it's a separate paragraph; we could keep it as a
under About the role. Also remove "Why AWS?" etc? That's promotional but maybe considered boilerplate? It's not EEO but it's generic marketing; but we need to preserve substantive information. The "Why AWS?" section includes description of AWS; that's substantive about company but maybe not required? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why AWS?" is not those; it's company description. Might be considered substantive? It's generic but could be kept. However we need to avoid too many thin sections. Could incorporate into About the role or About the Team? There's also "About The Team" later. So we could keep "About The Team" as a section? The instruction says use headings for sections like About the role, Responsibilities, etc. Not explicitly About The Team, but we could treat as About the role? Might be better to have About the role (description) and About the Team separate? The instruction only lists certain headings; but we can still use other headings? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could also use other headings if needed, but better to stick to those. So we can map content to those sections. Thus: - About the role: combine the initial description paragraph ("As a trusted customer advocate...") plus maybe the "Why AWS?" and "Inclusive Team Culture" etc? But those are more about company; maybe we can put them under About the role as well. However we also have "About The Team" later; we could treat that as About the role as well? Might be duplication. Safer: Use About the role for the initial description paragraph (the first paragraph). Use Responsibilities for key job responsibilities. Use Requirements for Basic Qualifications. Use Qualifications for Preferred Qualifications. Use Benefits for benefits paragraph. Use Pay for salary ranges. Use Schedule for work/life harmony details. We must not include filler like "commensurate with experience". Not present. Now we need to extract specifics. Let's parse the posting. Description paragraph: "As a trusted customer advocate, Solutions Architects help organizations understand best practices around advanced cloud-based solutions, and provide advice on strategies for migrating existing workloads to the cloud. You’ll help drive successful business outcomes across a broad set of enterprise customers in Retail, Consumer Goods & Restaurants through your passion for educating, training, designing and building cloud solutions. You will have the opportunity to help shape and execute a strategy to build deep adoption and broad use of AWS within your enterprise customers, and you will do this by mobilizing resources within AWS and working with our extensive partner network." That's the description. Then "Work/Life Harmony" paragraph: "Our team is focused on balancing life with our work, and we do this via work autonomy and by prioritizing solutions and processes that enable us to scale faster than the business. While there may be an opportunity to work from an office (location dependent), working remotely is supported, and often times encouraged. Work hours are flexible and typically self-defined." That's schedule/flexibility. Then "Key job responsibilities" bullet list: - In partnership with the sales team, formulate and execute a sales strategy to exceed revenue objectives through the adoption of AWS - As a key member of the business development and sales team, ensure success in building and migrating applications, software and services on the AWS platform - Educate customers of all sizes on the value proposition of AWS, and participate in deep architectural discussions to ensure solutions are designed for successful deployment in the cloud - Conduct one-to-few and one-to-many training sessions to transfer knowledge to customers considering or already using AWS - Capture and share best-practice knowledge amongst the AWS solutions architect community - Author or otherwise contribute to AWS customer-facing publications such as whitepapers - Build deep relationships with senior technical individuals within customers to enable them to be cloud advocates - Act as a technical liaison between customers, service engineering teams and support Then "A day in the life" heading? Actually after responsibilities there is "A day in the life" then "Diverse Experiences" etc. But we can ignore "A day in the life" as it's just a heading with no content? Actually after that heading there is "Diverse Experiences" paragraph: "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." That's encouragement; we could incorporate into About the role or maybe a separate section but not required. We'll keep as part of About the role maybe after description. Then "Why AWS?" paragraph: description of AWS. Then "Inclusive Team Culture" paragraph. Then "Mentorship & Career Growth" paragraph. Then "Work/Life Balance" paragraph (similar to Work/Life Harmony but more generic). Actually we already have Work/Life Harmony earlier; there is also Work/Life Balance later repeating similar content. Might be duplicate; we should deduplicate. Then "About The Team" paragraph: description of team. Then "Basic Qualifications" bullet list: - Knowledge of AWS services, market segments, customer base and industry verticals - 10+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience - 5+ years of design, implementation, or consulting in applications and infrastructures experience Then "Preferred Qualifications" bullet list: - Experience and technical expertise (design and implementation) in cloud computing technologies - Experience migrating or transforming legacy customer solutions to the cloud - Experience in written and oral communication, including the ability to communicate with all levels in the organization (technical, business, executive) - Experience implementing innovative learning and development solutions in a fast-paced global environment - Ability to design and implement generative AI and agentic solutions that drive business outcomes Then EEO boilerplate etc. Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits." Then location salary ranges: - USA, GA, Atlanta - 153,600.00 - 207,800.00 USD annually - USA, IL, Chicago - 153,600.00 - 207,800.00 USD annually - USA, NY, New York - 169,000.00 - 228,600.00 USD annually - USA, TX, Dallas - 153,600.00 - 207,800.00 USD annually Then "Company - Amazon Web Services, Inc. Job ID: A10530387" We need to preserve all substantive info. So we need to include the benefits list, the salary ranges, the work/life harmony/flexibility info. We must not include boilerplate like EEO, accommodation link, etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe considered a link; but it's part of benefits description; we could keep the sentence but maybe it's okay. It's not boilerplate; it's a reference. Might keep. We must not include duplicated lines. There's duplicate work/life harmony and work/life balance; we should combine or keep one. We'll keep the Work/Life Harmony paragraph (first) and maybe ignore the later Work/Life Balance as duplicate. Also "A day in the life" heading with no content after? Actually after that heading there is "Diverse Experiences". So we could treat "A day in the life" as a heading but no specific content; better to ignore it and just treat Diverse Experiences as part of About the role. Now we need to output HTML. Structure:
About the role
... description ...
... Diverse Experiences encouragement ...
... Why AWS? ...
... Inclusive Team Culture ...
... Mentorship & Career Growth ...
... About The Team ...
But that may be many thin sections; but we can combine into onewith multiple sentences? The instruction: Prefer a few substantive sections over many thin ones. So we should avoid many thin sections. Perhaps we should keep About the role as a single
containing all those paragraphs combined (with appropriate spacing).