Head of Partner Sales, AWS Industries, Energy and Utilities , AWS Industries Partner Sales
for headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the description.
Key sections:
- Description: includes overview, responsibilities (LEADERSHIP, SALES, ALLIANCES, OPERATIONS), "A day in the life", "About The Team". Also Basic Qualifications, Preferred Qualifications.
- Benefits: described: "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."
- 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 salary ranges per location.
- Schedule: Not explicitly mentioned. No schedule info. So we should not create Schedule section.
- Skills: Not explicitly listed as separate; but we could infer from qualifications. However we should not invent. The instruction: "Prefer a few substantive sections over many thin ones." We can combine Requirements and Qualifications maybe. But they said use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include a section only when posting has real, specific content for it. So we need to decide which sections have content.
- About the role: we have description overview (first paragraph). That is substantive.
- Responsibilities: we have LEADERSHIP, SALES, ALLIANCES, OPERATIONS, plus "A day in the life". That's substantive.
- Requirements: Basic Qualifications maybe.
- Qualifications: Preferred Qualifications maybe.
- Skills: Not explicitly separate; could be omitted if no specific skill list. The posting mentions "Experience with customer relationship management, especially C-suite level customer engagement", "Experience owning and delivering a revenue target", "Experience with metrics reporting and defining strategy for senior executives", "Experience leading partner, channel, or co-sell sales motions at scale", "Experience selling cloud, SaaS, or enterprise technology, and familiarity with AWS Marketplace, cloud migrations, and Generative AI use cases." Those could be considered skills. But we already have Requirements and Qualifications sections. Might be okay to omit Skills if no explicit list. However we could treat some of those as skills. But to be safe, we can omit Skills section if not explicitly listed as a separate bullet list. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We have Basic Qualifications and Preferred Qualifications; we can put them under Requirements and Qualifications respectively.
- Benefits: we have content.
- Pay: we have content (salary ranges). So include Pay.
- Schedule: none, omit.
Now we need to format.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
...overview...
Responsibilities
- LEADERSHIP — Organizational Strategy & Scale: ...
...
But we need to preserve all substantive information; not invent or summarize away detail. So we need to include the details from each bullet.
We have responsibilities broken into LEADERSHIP, SALES, ALLIANCES, OPERATIONS, plus "A day in the life". Also maybe "About The Team" could be part of About the role? But we already have About the role overview; we could include About The Team as part of About the role or separate? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not create extra headings like "About The Team". We can embed that content in About the role paragraph.
Thus we need to incorporate all substantive info from the description into these sections.
Let's extract:
About the role overview paragraph:
"The Partner Sales Manager (PSM) leads a team of quota-carrying sales professionals responsible for driving partner-delivered revenue across an industry-aligned territory. This is a people-management role that carries a team revenue number and demands pipeline generation, disciplined deal execution, and the ability to cultivate strategic executive relationships with both Customers and Partners that convert into closed revenue. Success requires setting strategic direction for the team, managing a portfolio of deals in flight, and building trusted advisor status with partners and customers through consistent engagement, co-sell motions, and a persistent focus on customer outcomes. The role also owns ongoing reporting and the continued redefinition of the way AWS engages in the partner selling motion. The PSM team operates at the intersection of industry technology, AWS Marketplace, cloud migrations, consulting and tech partners, and Generative AI. The team identifies and advances high-value opportunities by engaging customer stakeholders and sales teams, accelerating pipeline velocity, increasing partner-led deal flow, and delivering measurable revenue impact quarter over quarter. The ideal candidate is a proven sales leader who consistently delivers team goals and raises the bar on the talent around them. You treat every challenge as an opportunity to develop your people and sharpen the team's execution, leveraging internal AI tools to accelerate the org's productivity, mobilizing the right partners across AWS to drive outcomes, and building the kind of team that sets the standard for how partner selling is done. This leader will lead the Energy and Utilities Partner Sales global team."
That's the overview.
Now Responsibilities: we have headings LEADERSHIP, SALES, ALLIANCES, OPERATIONS, plus "A day in the life". We need to capture each bullet's content.
LEADERSHIP — Organizational Strategy & Scale:
- Set the strategic direction for a global partner sales organization in Energy and Utilities, defining the multi-year vision and translating it into the goals, coverage model, and priorities the team executes against.
- Build the mechanisms that scale the organization's impact: design and codify repeatable selling motions, operating rhythms, and go-to-market plays that raise the productivity of every seller and let the business grow through process and tooling, not headcount.
- Reshape how the organization operates to compound results over time, using data and field signal to decide where to invest, where to simplify, and where to place bigger bets.
- Lead, coach, and develop a team of Partner Sales Managers.
SALES — Revenue Ownership & Co-Sell Execution:
- Achieve revenue targets by driving partner-originated and partner-assisted opportunities across an industry-aligned territory with quota accountability, consistently meeting assigned goals, progressing deal stages, managing pipeline hygiene, and utilizing partner funding programs to accelerate pipeline velocity.
- Execute co-sell motions with Global System Integrators / System Integrators (GSI/SI) and Independent Software Vendor (ISV) partners.
- Support migration business value by partnering with GSI/SI firms to position cloud migration solutions, including mainframe modernization, data center exits, and application rationalization, while engaging customer stakeholders including procurement and business leaders to drive deal progression.
ALLIANCES — Strategic Partner Development & Industry Ecosystem Building:
- Cultivate strategic relationships that unlock new line-of-business personas in customer accounts; drive net-new pipeline creation through structured account planning, business reviews, and scale sales campaigns in collaboration with the One Partner Team, aligning specific partners to high-priority workloads and use cases.
- Shape deals with partners leveraging Marketplace that address critical industry priorities, including regulatory compliance, data modernization, security, and digital transformation, while positioning partner solutions to solve customer needs and supporting PPA demand plans.
- Drive customer adoption of the Marketplace.
OPERATIONS — Execution Rigor & Cross-Functional Orchestration:
- Role model Amazon Leadership Principles and drive impactful outcomes through the OneTeam approach; demonstrate proficiency with AI tools to produce quality documents, leverage AI insights for forecasting and leadership alignment, and maintain operational excellence in CRM hygiene, program utilization tracking, and forecast accuracy.
- Consistently achieve goals and proactively mitigate risks; triage and escalate blockers to maximize revenue realization, share field feedback to address execution gaps, and engage stakeholders to meet customer and partner needs.
"A day in the life":
- You lead the team's operating cadence: inspecting pipeline, coaching your PSMs through their most strategic deals, and stepping into executive conversations with partners and customers where senior sponsorship moves a deal forward.
- You spend your time developing your people, unblocking deals, aligning cross-functional AWS teams behind partner-led opportunities, and setting the strategy that determines where the team invests its energy next.
Now Basic Qualifications:
- 10+ years of direct sales and partner sales leadership experience
- Experience with customer relationship management, especially C-suite level customer engagement
- Experience owning and delivering a revenue target for a team or territory.
- 10+ Years owning metrics reporting and defining strategy for senior executives.
Preferred Qualifications:
- 5+ years of solving problems with technology in the Energy & Utilities industries experience
- Experience leading partner, channel, or co-sell sales motions at scale.
- Experience selling cloud, SaaS, or enterprise technology, and familiarity with AWS Marketplace, cloud migrations, and Generative AI use cases.
- Track record of building and scaling high-performing sales teams, including developing internal talent into more senior roles.
- Experience operating in a matrixed environment and orchestrating cross-functional teams toward a shared revenue outcome.
- MBA, JD, or equivalent advanced degree or experience.
Now Benefits:
- 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. (But we should remove application instructions? The instruction says remove application instructions. The link to learn more about benefits might be considered application instruction? It's not exactly application instruction but it's a link. Might be okay to keep as part of benefits description. However we should remove duplicated lines and boilerplate. The link is not boilerplate; it's a reference. Might keep.
Now 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 list:
USA, NJ, Jersey City - 205,600.00 - 278,200.00 USD annually
USA, NY, New York - 205,600.00 - 278,200.00 USD annually
USA, TX, Austin - 186,900.00 - 252,900.00 USD annually
USA, TX, Dallas - 186,900
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the description. Key sections: - Description: includes overview, responsibilities (LEADERSHIP, SALES, ALLIANCES, OPERATIONS), "A day in the life", "About The Team". Also Basic Qualifications, Preferred Qualifications. - Benefits: described: "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." - 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 salary ranges per location. - Schedule: Not explicitly mentioned. No schedule info. So we should not create Schedule section. - Skills: Not explicitly listed as separate; but we could infer from qualifications. However we should not invent. The instruction: "Prefer a few substantive sections over many thin ones." We can combine Requirements and Qualifications maybe. But they said use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include a section only when posting has real, specific content for it. So we need to decide which sections have content. - About the role: we have description overview (first paragraph). That is substantive. - Responsibilities: we have LEADERSHIP, SALES, ALLIANCES, OPERATIONS, plus "A day in the life". That's substantive. - Requirements: Basic Qualifications maybe. - Qualifications: Preferred Qualifications maybe. - Skills: Not explicitly separate; could be omitted if no specific skill list. The posting mentions "Experience with customer relationship management, especially C-suite level customer engagement", "Experience owning and delivering a revenue target", "Experience with metrics reporting and defining strategy for senior executives", "Experience leading partner, channel, or co-sell sales motions at scale", "Experience selling cloud, SaaS, or enterprise technology, and familiarity with AWS Marketplace, cloud migrations, and Generative AI use cases." Those could be considered skills. But we already have Requirements and Qualifications sections. Might be okay to omit Skills if no explicit list. However we could treat some of those as skills. But to be safe, we can omit Skills section if not explicitly listed as a separate bullet list. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We have Basic Qualifications and Preferred Qualifications; we can put them under Requirements and Qualifications respectively. - Benefits: we have content. - Pay: we have content (salary ranges). So include Pay. - Schedule: none, omit. Now we need to format. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:
About the role
...overview...
Responsibilities
- LEADERSHIP — Organizational Strategy & Scale: ... ...