Partner Solutions Architect - Security, AWS Specialists and Partners
for sections: 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. Remove boilerplate.
We need to parse the description and extract content.
Let's identify sections:
- About the role: The description includes introductory paragraphs about ASP, role description, etc. We can put that under About the role.
- Responsibilities: The "Key job responsibilities" bullet list.
- Requirements: Basic Qualifications? Possibly "Basic Qualifications". Also "Preferred Qualifications". Could be under Requirements or Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills. So we need to decide which sections to include.
We have content for:
- About the role: yes.
- Responsibilities: yes.
- Requirements: Basic Qualifications (2+ years design... etc). Also maybe "Preferred Qualifications" could be under Qualifications.
- Qualifications: maybe Preferred Qualifications.
- Skills: maybe list of skills like information security, cloud computing, networking, application architecture, thought leader, customer facing, strategic thinking, influencer, CxO level, hands-on, etc.
- Benefits: The paragraph about benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention sign-on payments and RSUs. That's benefits.
- Pay: The base salary ranges for various locations. That is pay info. Should we include Pay section? Yes, we have specific salary ranges.
- Schedule: Not mentioned except 25% travel required. That's not schedule like full-time/part-time. Travel is not schedule. No explicit schedule info (e.g., full-time, hours). So we should not create Schedule section because no specific content.
We must not create sections with filler like "not specified". So omit Schedule.
Also we need to avoid duplicative lines.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we need to strip out:
- "About The Team" section with Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are generic company info; but they might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About The Team" sections are not explicitly listed as boilerplate but they are generic marketing. However they might be considered part of job description; but we need to preserve ALL substantive information; do not invent or summarize away detail. Are those substantive? They are generic AWS benefits/culture; they could be considered boilerplate but not explicitly listed. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove generic "About the team" sections. However earlier they said "Prefer a few substantive sections over many thin ones." So we could include them under About the role or maybe under a separate section like "About the Team". But we only have allowed headings list; we could put them under About the role as prose.
But we need to decide: The "About The Team" includes Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. That's quite a bit of text. It might be considered substantive but maybe not required. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it.
Thus we need to include that content somewhere. Could be under About the role (makes sense). Or we could create a separate section like "About the Team" but not in allowed headings list. The allowed headings are limited to those eight. So we must fit into those.
Thus we can put the "About The Team" content under About the role as prose.
Now we need to extract the responsibilities list:
"Key job responsibilities Partners' trusted advisor: Collaborate with AWS Engineering service teams such AWS Private Cloud (VPC), Amazon Identity and Access Management (IAM), AWS Key Management Service (KMS), Amazon GuardDuty, Amazon Security Lake, Web Application Firewall (WAF) Business partner: serve as a key member of the business development and partner management team in helping to ensure customer success on AWS Public engagement: provide thought leadership on Security solutions that benefit customers through the use of partner products that integrate with AWS Services. This takes the form of contribution to external publications such as the AWS Blogs, White-papers and public presentations at AWS Conferences and Industry Events Community player: capture and share best-practices, participate, and contribute as a member of the worldwide AWS technical community of Solution Architects, Support, and Business Development. Evangelizing a partner’s value proposition internally throughout AWS and externally with customers Establishing AWS as the partner’s preferred cloud computing platform for regulated workloads Working alongside business counterparts to develop extensive executive and senior management relationships within partner organizations Provide the architectural guidance and recommendations necessary to promote successful engagements with software partners worldwide. Serve as a key member of the AWS Independent Software Vendor (ISV) Partners team helping to define and deliver the overall go-to-market strategy for the segment."
We need to turn that into a list. Each bullet likely corresponds to each colon-separated item. Let's parse:
- Partners' trusted advisor: Collaborate with AWS Engineering service teams such AWS Private Cloud (VPC), Amazon Identity and Access Management (IAM), AWS Key Management Service (KMS), Amazon GuardDuty, Amazon Security Lake, Web Application Firewall (WAF)
- Business partner: serve as a key member of the business development and partner management team in helping to ensure customer success on AWS
- Public engagement: provide thought leadership on Security solutions that benefit customers through the use of partner products that integrate with AWS Services. This takes the form of contribution to external publications such as the AWS Blogs, White-papers and public presentations at AWS Conferences and Industry Events
- Community player: capture and share best-practices, participate, and contribute as a member of the worldwide AWS technical community of Solution Architects, Support, and Business Development. Evangelizing a partner’s value proposition internally throughout AWS and externally with customers
- Establishing AWS as the partner’s preferred cloud computing platform for regulated workloads
- Working alongside business counterparts to develop extensive executive and senior management relationships within partner organizations
- Provide the architectural guidance and recommendations necessary to promote successful engagements with software partners worldwide.
- Serve as a key member of the AWS Independent Software Vendor (ISV) Partners team helping to define and deliver the overall go-to-market strategy for the segment.
We could also include "Evangelizing a partner’s value proposition internally throughout AWS and externally with customers" as separate bullet maybe part of Community player.
We'll keep as list items.
Now Basic 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 6+ years of IT development or implementation/consulting in the software or Internet industries experience"
We need to format as list.
Preferred Qualifications:
"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 Skills: The description includes many skill mentions: "You should possess skills in information security, cloud computing, networking, and application architecture. You are seen as a thought leader, and will have customer facing skills that will be leveraged at all levels of a partner organization. You should be able to think strategically about business, product, and technical challenges. You are an influencer by nature and must be comfortable conversing at the CxO level and also be hands-on providing expertise at an engineering and product level."
Also earlier: "If you have experience in Information Security, Networking, Security Operations, Application Security, Threat Detection, or Identity and are interested in helping customers embrace cloud technologies..."
Thus we can compile a list of skills.
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."
We need to separate Pay and Benefits. Pay: base salary ranges for locations. Benefits: health insurance etc plus sign-on payments and RSUs? Actually sign-on payments and RSUs are part of compensation, could be considered Pay or Benefits. The instruction: Benefits section for benefits like health insurance etc. Pay section for salary ranges. Sign-on payments and RSUs could be part of Pay or Benefits; but we already have Pay section for base salary. We could include sign-on payments and RSUs under Benefits as part of compensation package. However the text says "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That is part of compensation; could be placed under Pay as well. But we already have Pay for base salary ranges. We could add a note under Pay: includes sign-on payments and RSUs. Or we could put them under Benefits. I'd put them under Benefits as part of total compensation.
Now we need to exclude boilerplate: The Los Angeles County applicants text, San Francisco Fair Chance Ordinance, disability accommodation, etc. Also "Amazon is an equal opportunity employer..." etc. Also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also "Company - Amazon Web Services, Inc. Job ID: A10455441". Also "USA, CA, San Francisco - 151,000.00 - 204,300.00 USD annually" etc. Those are Pay.
We also need to remove duplicated lines.
Now we need to output HTML fragment only.
Let's craft:
About the role
... combine introductory paragraphs and About The Team content.
We need to ensure we don't repeat job title.
Let's extract the introductory paragraphs:
"Description This position is part of the AWS Specialist and Partner Organization (ASP). Specialists own the end-to-end go-to-market strategy for their respective technology domains, providing the business and technical expertise to help our customers succeed. Partner teams own the strategy, recruiting, development, and growth of our key technology and consulting partners. Together they provide our customers with the expertise and scale needed to build innovative solutions for their most complex challenges. Amazon Web Services is leading the next paradigm shift in computing and is looking for a world class candidate for the role of Partner Solution Architect, Security, within our Amazon Specialists and Partner organization (ASP) to work with our strategic security Independent Software Vendors (ISVs) If you have experience in Information Security, Networking, Security Operations, Application Security, Threat Detection, or Identity and are interested in helping customers embrace cloud technologies, come and talk to us. You will work across the security industry and be in a position to help forge the next decade of innovation. Specialist Partner Solutions Architects work with AWS' partners product, engineering, alliance, and GTM teams to help accelerate product development and our shared customers cloud journey. As a trusted technical advisor they engage in a wide range of activities providing technical advice to partners, customers, and the greater security community. They present AWS publicly within their domain and are the conduit between AWS service teams, customers, and partners. This role will focus on working
. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip out: - "About The Team" section with Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are generic company info; but they might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About The Team" sections are not explicitly listed as boilerplate but they are generic marketing. However they might be considered part of job description; but we need to preserve ALL substantive information; do not invent or summarize away detail. Are those substantive? They are generic AWS benefits/culture; they could be considered boilerplate but not explicitly listed. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove generic "About the team" sections. However earlier they said "Prefer a few substantive sections over many thin ones." So we could include them under About the role or maybe under a separate section like "About the Team". But we only have allowed headings list; we could put them under About the role as prose. But we need to decide: The "About The Team" includes Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. That's quite a bit of text. It might be considered substantive but maybe not required. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. Thus we need to include that content somewhere. Could be under About the role (makes sense). Or we could create a separate section like "About the Team" but not in allowed headings list. The allowed headings are limited to those eight. So we must fit into those. Thus we can put the "About The Team" content under About the role as prose. Now we need to extract the responsibilities list: "Key job responsibilities Partners' trusted advisor: Collaborate with AWS Engineering service teams such AWS Private Cloud (VPC), Amazon Identity and Access Management (IAM), AWS Key Management Service (KMS), Amazon GuardDuty, Amazon Security Lake, Web Application Firewall (WAF) Business partner: serve as a key member of the business development and partner management team in helping to ensure customer success on AWS Public engagement: provide thought leadership on Security solutions that benefit customers through the use of partner products that integrate with AWS Services. This takes the form of contribution to external publications such as the AWS Blogs, White-papers and public presentations at AWS Conferences and Industry Events Community player: capture and share best-practices, participate, and contribute as a member of the worldwide AWS technical community of Solution Architects, Support, and Business Development. Evangelizing a partner’s value proposition internally throughout AWS and externally with customers Establishing AWS as the partner’s preferred cloud computing platform for regulated workloads Working alongside business counterparts to develop extensive executive and senior management relationships within partner organizations Provide the architectural guidance and recommendations necessary to promote successful engagements with software partners worldwide. Serve as a key member of the AWS Independent Software Vendor (ISV) Partners team helping to define and deliver the overall go-to-market strategy for the segment." We need to turn that into a list. Each bullet likely corresponds to each colon-separated item. Let's parse: - Partners' trusted advisor: Collaborate with AWS Engineering service teams such AWS Private Cloud (VPC), Amazon Identity and Access Management (IAM), AWS Key Management Service (KMS), Amazon GuardDuty, Amazon Security Lake, Web Application Firewall (WAF) - Business partner: serve as a key member of the business development and partner management team in helping to ensure customer success on AWS - Public engagement: provide thought leadership on Security solutions that benefit customers through the use of partner products that integrate with AWS Services. This takes the form of contribution to external publications such as the AWS Blogs, White-papers and public presentations at AWS Conferences and Industry Events - Community player: capture and share best-practices, participate, and contribute as a member of the worldwide AWS technical community of Solution Architects, Support, and Business Development. Evangelizing a partner’s value proposition internally throughout AWS and externally with customers - Establishing AWS as the partner’s preferred cloud computing platform for regulated workloads - Working alongside business counterparts to develop extensive executive and senior management relationships within partner organizations - Provide the architectural guidance and recommendations necessary to promote successful engagements with software partners worldwide. - Serve as a key member of the AWS Independent Software Vendor (ISV) Partners team helping to define and deliver the overall go-to-market strategy for the segment. We could also include "Evangelizing a partner’s value proposition internally throughout AWS and externally with customers" as separate bullet maybe part of Community player. We'll keep as list items. Now Basic 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 6+ years of IT development or implementation/consulting in the software or Internet industries experience" We need to format as list. Preferred Qualifications: "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 Skills: The description includes many skill mentions: "You should possess skills in information security, cloud computing, networking, and application architecture. You are seen as a thought leader, and will have customer facing skills that will be leveraged at all levels of a partner organization. You should be able to think strategically about business, product, and technical challenges. You are an influencer by nature and must be comfortable conversing at the CxO level and also be hands-on providing expertise at an engineering and product level." Also earlier: "If you have experience in Information Security, Networking, Security Operations, Application Security, Threat Detection, or Identity and are interested in helping customers embrace cloud technologies..." Thus we can compile a list of skills. 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." We need to separate Pay and Benefits. Pay: base salary ranges for locations. Benefits: health insurance etc plus sign-on payments and RSUs? Actually sign-on payments and RSUs are part of compensation, could be considered Pay or Benefits. The instruction: Benefits section for benefits like health insurance etc. Pay section for salary ranges. Sign-on payments and RSUs could be part of Pay or Benefits; but we already have Pay section for base salary. We could include sign-on payments and RSUs under Benefits as part of compensation package. However the text says "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That is part of compensation; could be placed under Pay as well. But we already have Pay for base salary ranges. We could add a note under Pay: includes sign-on payments and RSUs. Or we could put them under Benefits. I'd put them under Benefits as part of total compensation. Now we need to exclude boilerplate: The Los Angeles County applicants text, San Francisco Fair Chance Ordinance, disability accommodation, etc. Also "Amazon is an equal opportunity employer..." etc. Also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also "Company - Amazon Web Services, Inc. Job ID: A10455441". Also "USA, CA, San Francisco - 151,000.00 - 204,300.00 USD annually" etc. Those are Pay. We also need to remove duplicated lines. Now we need to output HTML fragment only. Let's craft:
About the role
... combine introductory paragraphs and About The Team content.
We need to ensure we don't repeat job title. Let's extract the introductory paragraphs: "Description This position is part of the AWS Specialist and Partner Organization (ASP). Specialists own the end-to-end go-to-market strategy for their respective technology domains, providing the business and technical expertise to help our customers succeed. Partner teams own the strategy, recruiting, development, and growth of our key technology and consulting partners. Together they provide our customers with the expertise and scale needed to build innovative solutions for their most complex challenges. Amazon Web Services is leading the next paradigm shift in computing and is looking for a world class candidate for the role of Partner Solution Architect, Security, within our Amazon Specialists and Partner organization (ASP) to work with our strategic security Independent Software Vendors (ISVs) If you have experience in Information Security, Networking, Security Operations, Application Security, Threat Detection, or Identity and are interested in helping customers embrace cloud technologies, come and talk to us. You will work across the security industry and be in a position to help forge the next decade of innovation. Specialist Partner Solutions Architects work with AWS' partners product, engineering, alliance, and GTM teams to help accelerate product development and our shared customers cloud journey. As a trusted technical advisor they engage in a wide range of activities providing technical advice to partners, customers, and the greater security community. They present AWS publicly within their domain and are the conduit between AWS service teams, customers, and partners. This role will focus on working