Principal Global Account Manager, Global Financial Services

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. We must not repeat job title as heading. Remove boilerplate, duplicate lines, application instructions, EEO, etc. We need to parse the description. Key parts: - Description: AWS is seeking a world class sales professional to help manage the customer relationship with one of the largest customers in our Global Financial Services vertical, focused on growing business and defining the cloud computing industry in the world’s largest, most strategic, multinational Fortune 100 Financial Services companies. - Key job responsibilities: bullet list (starting with Identifying and building trusted advisor relationships... etc). We'll need to extract each bullet. - About The Team: includes subsections: Diverse Experiences, Why AWS? (with subpoints: Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance). This is more about company culture; maybe we can put under "About the role"? But we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. "About the role" could contain the initial description paragraph and maybe about the team? Usually "About the role" includes overview of role. We'll put the description paragraph there. "Responsibilities": list of key job responsibilities. "Requirements": maybe basic qualifications? The posting has Basic Qualifications and Preferred Qualifications. Those could go under Requirements or Qualifications. We have both Requirements and Qualifications sections. We need to decide mapping. Usually "Requirements" = basic qualifications, "Qualifications" = preferred qualifications or skills. But we also have Skills section. Could put technical skills etc. However the posting doesn't list specific skills besides certification in a relevant technical field (preferred). Could treat that as Skills. We have Benefits: described: comprehensive benefits including health insurance..., 401(k) matching, paid time off, parental leave. Also mention sign-on payments, RSUs, sales incentives. That's compensation/benefits. Pay: The base salary range listed: USA, NJ, Jersey City - 187,000.00 - 252,900.00 USD annually; USA, NY, New York - 187,000.00 - 252,900.00 USD annually. So we have pay info. Schedule: Not mentioned. So we should not include Schedule section. We must not include sections with filler like "commensurate with experience". We have actual pay ranges. We must not include Job ID etc. We can drop. We must not include boilerplate like EEO, accommodations, etc. We need to preserve all substantive information. So we need to include the description paragraph, responsibilities list, basic qualifications, preferred qualifications, benefits, pay. We also have "About The Team" with subpoints: Diverse Experiences, Why AWS? (Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance). This is substantive but not exactly role responsibilities. Could be placed under "About the role" as additional context. Or we could create a separate section like "About the team" but not in allowed headings list. The allowed headings are only those listed. So we must fit into those sections. Probably we can include the team info under "About the role" as part of role overview. We must not repeat job title as heading. We must output only HTML fragment, no /, no markdown. We'll structure:

About the role

AWS is seeking a world class sales professional to help manage the customer relationship with one of the largest customers in our Global Financial Services vertical, focused on growing business and defining the cloud computing industry in the world’s largest, most strategic, multinational Fortune 100 Financial Services companies.

About the team: Diverse Experiences – AWS values diverse experiences. Even if you do not meet all of the qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying. Why AWS? Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses. Inclusive Team Culture: Here at AWS, it’s in our nature to learn and be curious. Our employee-led affinity groups foster a culture of inclusion that empower us to be proud of our differences. Ongoing events and learning experiences, including our Conversations on Race and Ethnicity (CORE) and AmazeCon (diversity) conferences, inspire us to never stop embracing our uniqueness. Mentorship & Career Growth: We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional. Work/Life Balance: We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve in the cloud.

But we need to be careful not to include too much fluff? It's substantive. Then Responsibilities:

Responsibilities

• Identifying and building trusted advisor relationships with key influencers and decision-makers, specifically CxOs, at the customer.
• Working closely with internal AWS teams (executives, solution architects, business development, marketing, partners, enterprise support, service teams and professional services), as well as external SI and ISV partners, to support the best business solution for customers.
• Defining a CXO relationship strategy within the customer, coordinating executive business reviews, and maintaining customer satisfaction levels.
• Operating with significant autonomy and discretion. - High degree of decision making is required in routine customer engagement, business judgment is critical.
• Managing the sales pipeline via Salesforce and facilitating all stages of a sale.
• Participates and leads in the negotiation and closing of legal agreements, such as EAs, and contracts, such as PPAs.
• Maintains an operating knowledge of AWS’s service catalog and is able to relate them to solving customers’ business problems.
• Helps define product requirements by understanding and evangelizing the needs of customers.
• Working with marketing and communications to develop formal references, PR and case studies highlighting impactful customer activity and workloads running on AWS.

Note: The bullet "Operating with significant autonomy and discretion. - High degree of decision making is required in routine customer engagement, business judgment is critical." Might be two sentences; we can keep as one bullet. Now Requirements: Basic Qualifications.

Requirements

• Bachelor's degree, or Master's degree in business, operations, human resources, adult education, organizational development, instructional design or related field

But also maybe we could include "certification in a relevant technical field" as preferred? Actually that's under Preferred Qualifications. We'll put that under Qualifications or Skills. Qualifications: Preferred Qualifications.

Qualifications

• Certification in a relevant technical field

Skills: maybe we can include "sales pipeline management via Salesforce", "negotiation of legal agreements", "relationship building with CxOs", etc. But those are already responsibilities. Could leave Skills empty? Better not to create empty section. We could combine Skills with Qualifications? But we have both sections allowed. If we don't have specific skills beyond those, maybe we omit Skills section. Benefits: We have description of benefits.

Benefits

• 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
• Sign-on payments
• Restricted stock units (RSUs)
• Sales incentives

Pay: Salary ranges.

Pay

• USA, NJ, Jersey City: $187,000.00 - $252,900.00 USD annually
• USA, NY, New York: $187,000.00 - $252,900.00 USD annually

We should not include Schedule. We must ensure we don't include any boilerplate like EEO, accommodations, etc. We removed those. Check for duplicate lines: we have not duplicated. Check for any mention of "Amazon is an equal opportunity employer" etc - removed. Check for "If you have a disability..." - removed. Check for "Learn more about our benefits at https://amazon.jobs/en/benefits." - we should remove that as it's application instruction/link. So we should not include that line. Check for "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." - removed. Check for "Company - Amazon Web Services, Inc." - maybe we could include as metadata? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we could include a short paragraph with company name? It's minor metadata; we could drop it. Probably drop. Check for "Job ID: A10554029" - drop. Now ensure we haven't invented or summarized away detail. We preserved all substantive info: description, responsibilities, basic qualifications, preferred qualifications (certification), benefits (list), pay ranges. We omitted "Diverse Experiences" etc? Actually we included them in About the role paragraph. We paraphrased but kept substance. We must not summarize away detail; we kept the substance but rephrased? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Summarizing away detail might be considered summarizing. Safer to keep the original sentences verbatim, maybe as separate bullet points or paragraphs. We can include them as separate

elements without summarizing. Thus for About the role we could have:

AWS is seeking a world class sales professional to help manage the customer relationship with one of the largest customers in our Global Financial Services vertical, focused on growing business and defining the cloud computing industry in the world’s largest, most strategic, multinational Fortune 100 Financial Services companies.

Then we could add a separate

for About the team content, but we need to keep it under About the role section? Could add another

after that. We'll include the About the team content as separate paragraphs, preserving original wording. Let's extract the About the team content exactly: "About The Team About the team Diverse Experiences AWS values diverse experiences. Even if you do not meet all of the qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying. Why AWS? Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses. Inclusive Team Culture Here at AWS, it’s in our nature to learn and be curious. Our employee-led affinity groups foster a culture of inclusion that