Sr Partner Sales Manager, Global Financial Services (GFS) IBU

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 where there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the description. Key parts: - Description paragraph: "As a Partner Sales Manager, you will have the exciting opportunity to deliver on our strategy to build mind share of Amazon Web Services and grow adoption of cloud-based solutions in our fast growing and dynamic enterprise segment. In the role, you will establish and maintain C-level, sales, Strategy and product relationships with strategic consulting GSI/SI partners as well as leading co sell with our ISV technology partners to drive AWS services revenue with AWS account teams and customers. By establishing and growing business and technical relationships, and managing the day-to-day interactions with these accounts, you will be responsible for creating and closing opportunities with partners that drive top line AWS revenue growth and overall market adoption with AWS customers. You will possess both a business background that enables you to engage at the CXO level, as well as a sales background that enables you to easily interact with enterprise customers and sales executives to support the AWS and SI sales processes. You should also have a demonstrated ability to think strategically about business, product, and technical challenges, with the ability to build and convey compelling value propositions. You should be a self-starter who is prepared to develop and execute against partner account plans and a territory coverage plan and consistently deliver on revenue targets. The position also requires a strong technical Cloud acumen, along with working knowledge of software architecture and the GenAi and Agentic enterprise software landscape." - Key job responsibilities: bullet list (but in paragraph). We need to extract responsibilities as list items. Responsibilities listed: - Drive revenue and market share in a defined territory within enterprise vertical with multiple account teams and partners and/or with a specific list of strategic consulting partners with defined revenue and win targets - Meet or exceed quarterly revenue targets by helping GSI/SI and ISV partners originate and work with AWS sales teams to close opportunities that drive AWS revenues with prospects and customers. - Build deep relationships with customers and strategic partner(s) appropriate to your territory to fully understand their business, solutions and technical needs - Develop and execute against a comprehensive account/territory plan supporting multiple account teams and/or specific assigned partners to drive achievement of revenue and win goals - Execute plan while working with key internal stakeholders (e.g. account teams, specialist sales teams, services teams and BD, partner marketing and partner development resources) - Develop long-term strategic relationships with key strategic GSI/SI and ISV partners - Create & articulate compelling value propositions around AWS services to customers and partners. - Maintain a robust sales pipeline - Ensure customer and partner satisfaction - Provide technical and architectural resources to assist your partners in customer engagements and their delivery of solutions to market, including assisting them with ISV partnerships - Drive business development initiatives in your territory in partnership with Partner Development resources and marketing and GTMS teams to help drive opportunities to solutions built on AWS and ensure that AWS is their preferred platform - Manage contract negotiations and AWS funding programs - A day in the life: paragraph about team. - About The Team: paragraph. - Basic Qualifications: list. - Preferred Qualifications: list. - Benefits: paragraph about benefits. - Pay: salary ranges listed: "USA, NJ, Jersey City - 157,100.00 - 212,500.00 USD annually" and "USA, NY, New York - 157,100.00 - 212,500.00 USD annually". Also mention sign-on payments, RSUs, sales incentives. - Schedule: not mentioned. We need to include sections only if real content. Potential sections: About the role (maybe from description?), Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay. We could also have "About the Team" as a section? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't list About the Team but we could treat as "About the role"? However we have description that includes role overview. Could use "About the role" for the initial description paragraph and maybe "A day in the life" and "About The Team" could be merged? But we should not invent sections; we should follow the given list. The list includes "About the role". So we can put the overview under About the role. Responsibilities: list. Requirements: maybe combine Basic and Preferred Qualifications? But they have separate headings Basic Qualifications and Preferred Qualifications. The instruction list includes "Qualifications" as a possible heading. Could we use "Qualifications" and include both basic and preferred? Might be better to have separate sections? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those are typical. We could use "Basic Qualifications" and "Preferred Qualifications" as headings if they exist. However they are not in the example list but could be used. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate, but not strictly limited. Safer to stick to those. So we can map Basic Qualifications to "Requirements" maybe? Or "Qualifications". Preferred Qualifications could be under "Qualifications" as well, but we could separate into two sub-sections? Might be okay to have one Qualifications section with both basic and preferred listed. Skills: not explicitly mentioned; we could omit. Benefits: we have benefits paragraph. Pay: we have salary range and mention sign-on payments, RSUs, sales incentives. Schedule: none. Thus output sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to preserve all substantive info. Let's extract. About the role: combine the initial description paragraph plus maybe "A day in the life" and "About The Team"? Those are substantive. Could include them as part of About the role. But we must not lose info. Let's include them as separate paragraphs under About the role. Responsibilities: list items as above. Qualifications: list Basic Qualifications and Preferred Qualifications. Basic Qualifications items: - Experience in direct field selling software or cloud solutions - Experience in technology related sales, business development or equivalent - Experience communicating results to senior leadership - Experience working with partners through account, product or program management and business development engagements - Bachelor's degree or equivalent, or experience in sales Preferred Qualifications items: - AWS Cloud Practitioner certification - Experience in direct sales - Experience working within the enterprise software development industry Benefits: paragraph: "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, restricted stock units (RSUs), and sales incentives." That's more compensation than benefits but could be under Pay. We'll keep under Pay. Pay: includes base salary range for two locations, plus sign-on payments, RSUs, sales incentives. We need to format as

• for lists. We must not include boilerplate like EEO, accommodation link, etc. Remove those. Also remove "Company - Amazon Web Services, Inc." and Job ID. Now craft HTML. Structure:

  About the role

  ... paragraphs ...

  Responsibilities

  • ...
  ...

  Qualifications

  Basic Qualifications

  maybe? But we only allowed h3 for section headings. Could we use

  for each subsection? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using other headings like

  but better to stick to h3 for sections. Could we have two sections: Basic Qualifications and Preferred Qualifications as separate h3 sections? That would be okay because they are headings. The list didn't include them but they are still headings. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. So we can use h3 for Basic Qualifications and Preferred Qualifications. That would preserve detail. Thus:

  Basic Qualifications

  ...

  Preferred Qualifications

  ...
  But then we have multiple sections; still okay. Benefits:

  Benefits

  ...

  Pay:

  Pay

  ...

  We should not include Schedule. Now write the content. About the role paragraph(s): We can combine: "As a Partner Sales Manager, you will have the exciting opportunity to deliver on our strategy to build mind share of Amazon Web Services and grow adoption of cloud-based solutions in our fast growing and dynamic enterprise segment. In the role, you will establish and maintain C-level, sales, Strategy and product relationships with strategic consulting GSI/SI partners as well as leading co sell with our ISV technology partners to drive AWS services revenue with AWS account teams and customers. By establishing and growing business and technical relationships, and managing the day-to-day interactions with these accounts, you will be responsible for creating and closing opportunities with partners that drive top line AWS revenue growth and overall market adoption with AWS customers. You will possess both a business background that enables you to engage at the CXO level, as well as a sales background that enables you to easily interact with enterprise customers and sales executives to support the AWS and SI sales processes. You should also have a demonstrated ability to think strategically about business, product, and technical challenges, with the ability to build and convey compelling value propositions. You should be a self-starter who is prepared to develop and execute against partner account plans and a territory coverage plan and consistently deliver on revenue targets. The position also requires a strong technical Cloud acumen, along with working knowledge of software architecture and the GenAi and Agentic enterprise software landscape." Then maybe add "A day in the life" paragraph: "This team is part of the AWS Global Sales organisation Driving adoption of the AWS cloud worldwide, enabling customers of all sizes to innovate and expand in the cloud. Our team empowers every customer to grow by providing tailored service, unmatched technology, and support. We dive deep to understand each customer's unique challenges, then craft innovative solutions that accelerate their success. This customer-first approach is how we built the world's most adopted cloud. Join us and help us grow." And "About The Team": "We are a team of PSMs supporting multiple global accounts across the Global Financial Services Industry Business Unit (IBU)." We could combine them into About the role section as multiple paragraphs. Now Responsibilities list items as above. Now Basic Qualifications list. Now Preferred Qualifications list. Now Benefits paragraph. Now Pay paragraph: include base salary ranges for two locations, plus sign-on payments, RSUs, sales incentives. We need to preserve the exact numbers: "USA, NJ, Jersey City - 157,100.00 - 212,500.00 USD annually" and "USA, NY, New York - 157,100.00 - 212,500.00 USD annually