Sr. ISV Account Manager, Developer AI
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep details like bullet points exactly as in text.
Let's extract bullet points:
Key job responsibilities (list):
- The Sr. Account Manager is responsible for teaming up with all aspects of the customer’s organization. This includes C-level executives, engineering, product, AI, IT/operations, partner org, and sales.
- Skills required to build relationships across an account include creative systems thinking, visioning, and executing via collaboration with an extended team to address all ISV customer's needs.
- The Sr. Account Manager is responsible for selling at the most strategic (C-level) within the account and implementing a broad strategy for earning customer acceptance and service implementation.
- The Sr. Account Manager works collaboratively with all appropriate AWS resources (Executives, Partner, Support, Solution Architect) to support customer interests, and will understand how to strongly advocate for the customer in harmony with what the AWS business needs.
- In addition to new service adoption and new line of business development, this role includes dotted line responsibility for partnership and technical collaboration
A day in the life (list):
- Exceed annual revenue and win targets
- Drive levers for growth of the business: inclusive of Account Plans, GTM programs to drive adoption of our ISV partners’ products, working closely with marketing and the partner teams
- Engage and direct functional teams such as demand generation and curate a healthy sales pipeline
- Collaborate with partners to oversee enablement trainings and account prospecting workshops
- In partnership with Sales Ops, manage all operational aspects of the business; SFDC, etc.
- Develop long-term strategic relationships with AWS Executives and Partner management teams
- Embrace and drive the Amazon culture; lead through our Leadership Principles
- Increase and foster very high customer satisfaction.
- In normal business times there will be moderate travel
Skills required to build relationships across an account include creative systems thinking, visioning, and executing via collaboration with an extended team to address all ISV customer's needs. (Already in responsibilities but we can treat as Skills section.)
But we also have "Skills required to build relationships across an account include creative systems thinking, visioning, and executing via collaboration with an extended team to address all ISV customer's needs." That's a skill.
We also have "public cloud technical acumen" mentioned earlier: "has public cloud technical acumen". Also "has led a large team of extended resources". Also "extensive track record of building and nurturing senior level relationships with complex customers". Also "hands-on approach to developing new opportunities". Also "Must have experience managing high revenue, strategically important customers."
We need to capture all substantive info.
Let's parse the description paragraphs for details:
Paragraph 1: "The AWS ISV sales team is responsible for serving the needs of medium to large ISV customers. Our team takes pride in leading customers through an accelerated and innovative cloud and AI journey and in creating long-term business relationships of value and trust. The Sr. Account Manager is responsible for creating and executing the account strategy, and leading the extended team so both the customer and AWS grow. In addition to being customers, the ISVs partner with AWS on Go-To-Market programs, and our respective sales teams work together in the field. The Sr. Account Manager will work closely with the AWS Partner Team to ensure they are developing programs that are aligned with the ISV customers' strategy. It is critical that the Sr. Account Manager has an extensive track record of building and nurturing senior level relationships with complex customers, has a hands-on approach to developing new opportunities, has public cloud technical acumen, and has led a large team of extended resources. As part of the AWS ISV sales team, you will have the opportunity to work alongside a motivated team that values and encourages diversified perspectives and ideas to best equip customers with the most innovative and comprehensive solutions. The individual will have extensive big account experience building and nurturing CxO relationships as they will manage the relationship with some of the most important and influential AWS customers and deliver ground-breaking solutions to help their customers achieve the game-changing benefits of the cloud at scale. Must have experience managing high revenue, strategically important customers."
That's a lot of prose for About the role.
Then "Key job responsibilities" heading.
Then bullet list (we captured).
Then "A day in the life" heading.
Then bullet list.
Then "About The Team" heading with subsections: Why AWS?, Diverse Experiences, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are prose.
Then "Basic Qualifications" heading.
Then "Preferred Qualifications" heading.
Then EEO etc (remove).
Then Los Angeles County applicants etc (remove? It's boilerplate? It's specific to location but maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The LA County and SF Fair Chance Ordinance might be considered legal boilerplate. Probably remove.
Then "Our inclusive culture empowers Amazonians..." (maybe keep? It's part of inclusive culture but maybe duplicate. Might be considered boilerplate. Safer to remove.
Then accommodation link (maybe remove as application instructions). Remove.
Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Remove.
Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives. 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."
That's benefits and pay.
Then location salary ranges.
Then "Company - Amazon Web Services, Inc. Job ID: A10385720" remove.
Thus we need to craft sections.
About the role: combine introductory paragraph(s) and About The Team subsections? Could be separate but we can include About the role covering description and team culture. But we have also "About The Team" heading with subsections; we could treat that as part of About the role. However we must not create thin sections; we can merge.
We need to decide sections: About the role (intro + team culture), Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe combine with responsibilities? But we have a skill bullet separate; we could create Skills section listing skill items: creative systems thinking, visioning, executing via collaboration, public cloud technical acumen, etc. But we also have many skill-like statements in responsibilities. Might be okay to have Skills section with bullet list of skills: creative systems thinking, visioning, executing via collaboration, public cloud technical acumen, building/nurturing senior level relationships, hands-on approach to developing new opportunities, leading large team of extended resources, managing high revenue strategically important customers, etc.
But we must not duplicate content. However we can include them in Skills section; responsibilities section already has some overlapping. Might be okay but could be considered duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we can keep responsibilities as duties, and skills as separate list.
Let's extract skills from text:
- extensive track record of building and nurturing senior level relationships with complex customers
- hands-on approach to developing new opportunities
- public cloud technical acumen
- led a large team of extended resources
- extensive big account experience building and nurturing CxO relationships
- experience managing high revenue, strategically important customers
- creative systems thinking
- visioning
- executing via collaboration with an extended team
- (maybe also) ability to sell at C-level, implement broad strategy, advocate for customer, etc. But those are responsibilities.
We'll create Skills section bullet list.
Benefits: list: 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, parental leave. Also sign-on payments, RSUs, sales incentives (these are compensation but could be part of Pay? The instruction: Pay section only if posting actually states them. It states base salary range and mentions sign-on payments, RSUs, sales incentives as part of package. So we could include those in Pay section. Benefits section could be health insurance etc. We'll separate.
Pay: base salary range for locations, plus mention of sign-on payments, RSUs, sales incentives.
Schedule: none.
Now craft HTML.
We'll have:
About the role
... (combined intro and team culture paragraphs). Need to preserve all substantive info from intro and About The Team subsections.
Let's gather intro paragraphs:
Paragraph 1: The AWS ISV sales team is responsible for serving the needs of medium to large ISV customers. Our team takes pride in leading customers through an accelerated and innovative cloud and AI journey and in creating long-term business relationships of value and trust. The Sr. Account Manager is responsible for creating and executing the account strategy, and leading the extended team so both the customer and AWS grow. In addition to being customers, the ISVs partner with AWS on Go-To-Market programs, and our respective sales teams work together in the field. The Sr. Account Manager will work closely with the AWS Partner Team to ensure they are developing programs that are aligned with the ISV customers' strategy. It is critical that the Sr. Account Manager has an extensive track record of building and nurturing senior level relationships with complex customers, has a hands-on approach to developing new opportunities, has public cloud technical acumen, and has led a large team of extended resources. As part of the AWS ISV sales team, you will have the opportunity to work alongside a motivated team that values and encourages diversified perspectives and ideas to best equip
for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep details like bullet points exactly as in text. Let's extract bullet points: Key job responsibilities (list): - The Sr. Account Manager is responsible for teaming up with all aspects of the customer’s organization. This includes C-level executives, engineering, product, AI, IT/operations, partner org, and sales. - Skills required to build relationships across an account include creative systems thinking, visioning, and executing via collaboration with an extended team to address all ISV customer's needs. - The Sr. Account Manager is responsible for selling at the most strategic (C-level) within the account and implementing a broad strategy for earning customer acceptance and service implementation. - The Sr. Account Manager works collaboratively with all appropriate AWS resources (Executives, Partner, Support, Solution Architect) to support customer interests, and will understand how to strongly advocate for the customer in harmony with what the AWS business needs. - In addition to new service adoption and new line of business development, this role includes dotted line responsibility for partnership and technical collaboration A day in the life (list): - Exceed annual revenue and win targets - Drive levers for growth of the business: inclusive of Account Plans, GTM programs to drive adoption of our ISV partners’ products, working closely with marketing and the partner teams - Engage and direct functional teams such as demand generation and curate a healthy sales pipeline - Collaborate with partners to oversee enablement trainings and account prospecting workshops - In partnership with Sales Ops, manage all operational aspects of the business; SFDC, etc. - Develop long-term strategic relationships with AWS Executives and Partner management teams - Embrace and drive the Amazon culture; lead through our Leadership Principles - Increase and foster very high customer satisfaction. - In normal business times there will be moderate travel Skills required to build relationships across an account include creative systems thinking, visioning, and executing via collaboration with an extended team to address all ISV customer's needs. (Already in responsibilities but we can treat as Skills section.) But we also have "Skills required to build relationships across an account include creative systems thinking, visioning, and executing via collaboration with an extended team to address all ISV customer's needs." That's a skill. We also have "public cloud technical acumen" mentioned earlier: "has public cloud technical acumen". Also "has led a large team of extended resources". Also "extensive track record of building and nurturing senior level relationships with complex customers". Also "hands-on approach to developing new opportunities". Also "Must have experience managing high revenue, strategically important customers." We need to capture all substantive info. Let's parse the description paragraphs for details: Paragraph 1: "The AWS ISV sales team is responsible for serving the needs of medium to large ISV customers. Our team takes pride in leading customers through an accelerated and innovative cloud and AI journey and in creating long-term business relationships of value and trust. The Sr. Account Manager is responsible for creating and executing the account strategy, and leading the extended team so both the customer and AWS grow. In addition to being customers, the ISVs partner with AWS on Go-To-Market programs, and our respective sales teams work together in the field. The Sr. Account Manager will work closely with the AWS Partner Team to ensure they are developing programs that are aligned with the ISV customers' strategy. It is critical that the Sr. Account Manager has an extensive track record of building and nurturing senior level relationships with complex customers, has a hands-on approach to developing new opportunities, has public cloud technical acumen, and has led a large team of extended resources. As part of the AWS ISV sales team, you will have the opportunity to work alongside a motivated team that values and encourages diversified perspectives and ideas to best equip customers with the most innovative and comprehensive solutions. The individual will have extensive big account experience building and nurturing CxO relationships as they will manage the relationship with some of the most important and influential AWS customers and deliver ground-breaking solutions to help their customers achieve the game-changing benefits of the cloud at scale. Must have experience managing high revenue, strategically important customers." That's a lot of prose for About the role. Then "Key job responsibilities" heading. Then bullet list (we captured). Then "A day in the life" heading. Then bullet list. Then "About The Team" heading with subsections: Why AWS?, Diverse Experiences, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are prose. Then "Basic Qualifications" heading. Then "Preferred Qualifications" heading. Then EEO etc (remove). Then Los Angeles County applicants etc (remove? It's boilerplate? It's specific to location but maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The LA County and SF Fair Chance Ordinance might be considered legal boilerplate. Probably remove. Then "Our inclusive culture empowers Amazonians..." (maybe keep? It's part of inclusive culture but maybe duplicate. Might be considered boilerplate. Safer to remove. Then accommodation link (maybe remove as application instructions). Remove. Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Remove. Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives. 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." That's benefits and pay. Then location salary ranges. Then "Company - Amazon Web Services, Inc. Job ID: A10385720" remove. Thus we need to craft sections. About the role: combine introductory paragraph(s) and About The Team subsections? Could be separate but we can include About the role covering description and team culture. But we have also "About The Team" heading with subsections; we could treat that as part of About the role. However we must not create thin sections; we can merge. We need to decide sections: About the role (intro + team culture), Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe combine with responsibilities? But we have a skill bullet separate; we could create Skills section listing skill items: creative systems thinking, visioning, executing via collaboration, public cloud technical acumen, etc. But we also have many skill-like statements in responsibilities. Might be okay to have Skills section with bullet list of skills: creative systems thinking, visioning, executing via collaboration, public cloud technical acumen, building/nurturing senior level relationships, hands-on approach to developing new opportunities, leading large team of extended resources, managing high revenue strategically important customers, etc. But we must not duplicate content. However we can include them in Skills section; responsibilities section already has some overlapping. Might be okay but could be considered duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we can keep responsibilities as duties, and skills as separate list. Let's extract skills from text: - extensive track record of building and nurturing senior level relationships with complex customers - hands-on approach to developing new opportunities - public cloud technical acumen - led a large team of extended resources - extensive big account experience building and nurturing CxO relationships - experience managing high revenue, strategically important customers - creative systems thinking - visioning - executing via collaboration with an extended team - (maybe also) ability to sell at C-level, implement broad strategy, advocate for customer, etc. But those are responsibilities. We'll create Skills section bullet list. Benefits: list: 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, parental leave. Also sign-on payments, RSUs, sales incentives (these are compensation but could be part of Pay? The instruction: Pay section only if posting actually states them. It states base salary range and mentions sign-on payments, RSUs, sales incentives as part of package. So we could include those in Pay section. Benefits section could be health insurance etc. We'll separate. Pay: base salary range for locations, plus mention of sign-on payments, RSUs, sales incentives. Schedule: none. Now craft HTML. We'll have:
About the role
... (combined intro and team culture paragraphs). Need to preserve all substantive info from intro and About The Team subsections. Let's gather intro paragraphs: Paragraph 1: The AWS ISV sales team is responsible for serving the needs of medium to large ISV customers. Our team takes pride in leading customers through an accelerated and innovative cloud and AI journey and in creating long-term business relationships of value and trust. The Sr. Account Manager is responsible for creating and executing the account strategy, and leading the extended team so both the customer and AWS grow. In addition to being customers, the ISVs partner with AWS on Go-To-Market programs, and our respective sales teams work together in the field. The Sr. Account Manager will work closely with the AWS Partner Team to ensure they are developing programs that are aligned with the ISV customers' strategy. It is critical that the Sr. Account Manager has an extensive track record of building and nurturing senior level relationships with complex customers, has a hands-on approach to developing new opportunities, has public cloud technical acumen, and has led a large team of extended resources. As part of the AWS ISV sales team, you will have the opportunity to work alongside a motivated team that values and encourages diversified perspectives and ideas to best equip