Sr. ISV Account Manager, Developer AI
Amazon Web Services (AWS) · Austin, TX · 1 mo ago
AdvertisingFull-time
We need to output HTML fragment with headings 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. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the description.
Key sections:
- Description: includes overview of role, responsibilities, etc. Could map to "About the role" maybe.
- "Key job responsibilities" -> Responsibilities.
- "A day in the life" maybe also responsibilities.
- "Basic Qualifications" -> Requirements? Actually Basic Qualifications is a list of qualifications.
- "Preferred Qualifications" -> Qualifications? Or Skills? Could treat as Qualifications.
- "Skills required to build relationships across an account include creative systems thinking, visioning, and executing via collaboration..." That's skills.
- Benefits: there is a paragraph about benefits later: "Amazon also offers comprehensive benefits including health insurance ...". Also earlier: "Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives." Also "Learn more about our benefits at ..." So we have benefits content.
- Pay: "The base salary range for this position is listed below." Then lists ranges for locations. So we have pay info.
- Schedule: Not mentioned explicitly. There's mention of moderate travel, but not schedule. So we should not include Schedule section because no specific content.
- Also "About The Team" and "Why AWS?" etc. Might be considered "About the role" or separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "About The Team" could be part of About the role. "Why AWS?" maybe also part of About the role.
We must not include filler like "commensurate with experience". Not present.
We must not include duplicated lines.
We must output only HTML fragment, no /, no markdown fences.
Thus produce something like:
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. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the description.
Key sections:
- Description: includes overview of role, responsibilities, etc. Could map to "About the role" maybe.
- "Key job responsibilities" -> Responsibilities.
- "A day in the life" maybe also responsibilities.
- "Basic Qualifications" -> Requirements? Actually Basic Qualifications is a list of qualifications.
- "Preferred Qualifications" -> Qualifications? Or Skills? Could treat as Qualifications.
- "Skills required to build relationships across an account include creative systems thinking, visioning, and executing via collaboration..." That's skills.
- Benefits: there is a paragraph about benefits later: "Amazon also offers comprehensive benefits including health insurance ...". Also earlier: "Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives." Also "Learn more about our benefits at ..." So we have benefits content.
- Pay: "The base salary range for this position is listed below." Then lists ranges for locations. So we have pay info.
- Schedule: Not mentioned explicitly. There's mention of moderate travel, but not schedule. So we should not include Schedule section because no specific content.
- Also "About The Team" and "Why AWS?" etc. Might be considered "About the role" or separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "About The Team" could be part of About the role. "Why AWS?" maybe also part of About the role.
We must not include filler like "commensurate with experience". Not present.
We must not include duplicated lines.
We must output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
... content ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
... salary ranges ...
We need to preserve all substantive info. Let's extract. From description: "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 about the role. Responsibilities: "Key job responsibilities 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" Then "A day in the life Exceed annual revenue and win targetsDrive 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 teamsEngage and direct functional teams such as demand generation and curate a healthy sales pipelineCollaborate with partners to oversee enablement trainings and account prospecting workshopsIn partnership with Sales Ops, manage all operational aspects of the business; SFDC, etc.Develop long-term strategic relationships with AWS Executives and Partner management teamsEmbrace and drive the Amazon culture; lead through our Leadership PrinciplesIncrease and foster very high customer satisfaction. In normal business times there will be moderate travel" We can combine responsibilities and day-in-life into Responsibilities section as list items. Requirements: Basic Qualifications: "Bachelor's degree or equivalent 7+ years of tech sales experience to enterprise customers" That's it. Preferred Qualifications: "Experience with AWS technologies" Also maybe "Diverse Experiences" etc but that's not qualification. Qualifications: Could treat Preferred Qualifications as Qualifications. Skills: "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." Also maybe "public cloud technical acumen", "hands-on approach to developing new opportunities", "led a large team of extended resources", "extensive track record of building and nurturing senior level relationships with complex customers", "extensive big account experience building and nurturing CxO relationships", "managing high revenue, strategically important customers". Also "creative systems thinking, visioning, executing via collaboration". Also "selling at the most strategic (C-level)", "implementing a broad strategy for earning customer acceptance and service implementation", "works collaboratively with all appropriate AWS resources", "understand how to strongly advocate for the customer", "new service adoption and new line of business development", "dotted line responsibility for partnership and technical collaboration", "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", "moderate travel". We need to list skills as- items.
Benefits: "Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives. 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 should include that as list items maybe.
Pay: "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." Then lists:
USA, CA, San Francisco - 157,100.00 - 212,600.00 USD annually
USA, NY, New York - 157,100.00 - 212,600.00 USD annually
USA, TX, Austin - 142,800.00 - 193,200.00 USD annually
We should include that.
Schedule: none.
We must not include boilerplate like "Amazon is an equal opportunity employer..." etc. Also remove Los Angeles County etc. Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Company - Amazon Web Services, Inc. Job ID: A10385720". Also remove "Basic Qualifications" heading? We'll convert to list.
We must not repeat job title as heading.
Now produce HTML.
We need to ensure we use
for each section heading. We'll produce:
About the role
... paragraph ...
Responsibilities
- ... ...
Requirements
- Bachelor's degree or equivalent
- 7+ years of tech sales experience to enterprise customers
Qualifications
- Experience with AWS technologies
Skills
- Creative systems thinking
- Visioning
- Executing via collaboration with an extended team
- Public cloud technical acumen
- Hands‑on approach to developing new opportunities
- Led a large team of extended resources
- Extensive track record of building and nurturing senior‑level relationships with complex customers
- Extensive big‑account experience building and nurturing CxO relationships
- Experience managing high‑revenue, strategically important customers
- Selling at the most strategic (C‑level) within the account
- Implementing a broad strategy for earning customer acceptance and service implementation
- Collaborating with AWS executives, partners, support, and solution architects
- Advocating for the customer in harmony with AWS business needs
- Driving new service adoption and new line‑of‑business development
- Managing partnership and technical collaboration (dotted line responsibility)
- Exceeding annual revenue and win targets
- Driving levers for growth: account plans, GTM programs to drive adoption of ISV partners’ products, working with marketing and partner teams
- Engaging and directing demand‑generation teams to curate a healthy sales pipeline
- Collaborating with partners to oversee enablement trainings and account prospecting workshops
- Partnering with Sales Ops to manage operational aspects (SFDC, etc.)
- Developing long‑term strategic relationships with AWS executives and partner management teams
- Embracing and driving Amazon culture; leading through