Principal Global Account Manager, Global Financial Services
Amazon Web Services (AWS) · Jersey City, NJ · 1 mo ago
SalesFull-time
We need to output HTML fragment with sections: Use . The bullet list includes:
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.
We need to preserve all substantive info. The bullet list includes a dash before "High degree of decision making..." but it's part of bullet. We'll treat each line as bullet.
- Requirements: The posting includes "Basic Qualifications" and "Preferred Qualifications". Those could be under Requirements or Qualifications. The instructions: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put qualifications. Likely "Basic Qualifications" and "Preferred Qualifications" go under Requirements or Qualifications. Since we have both Requirements and Qualifications headings, we could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications. Or combine. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one Requirements section? But we have both headings available; we can include both if they have content. Let's see: Basic Qualifications: Bachelor's degree, or Master's degree in business, operations, human resources, adult education, organizational development, instructional design or related field. Preferred Qualifications: certification in a relevant technical field. Also there is "Amazon is an equal opportunity employer..." which is boilerplate to remove. Also there is accommodation info, also boilerplate. Also "Our inclusive culture..." etc. Those are boilerplate to remove. Also "If you have a disability..." etc. Remove.
Also there is "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."
Then location lines: "USA, NJ, Jersey City - 187,000.00 - 252,900.00 USD annually USA, NY, New York - 187,000.00 - 252,900.00 USD annually". This gives Pay info. Also there is "Company - Amazon Web Services, Inc. Job ID: A10554029" which is metadata to drop.
Thus we have Pay section: we can include Pay heading with the salary ranges. Also Benefits: we have benefits description. Schedule: not mentioned. So we omit Schedule.
Skills: Not explicitly listed; maybe we could infer but we should not invent. So omit Skills.
Qualifications: We have Preferred Qualifications (certification). Could also put under Qualifications. Requirements: Basic Qualifications.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if any other content: "About The Team" section includes subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are promotional content but could be considered "About the team". However the instruction says include section only when posting has real, specific content for it. This is about team culture, but it's generic promotional. Might be considered boilerplate? It's not standard EEO/legal but still generic. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not exactly those, but it's still fluff. However it's part of the job posting describing team culture. The instruction says "Prefer a few substantive sections over many thin ones." Could we include an "About the team" section? Not in the allowed headings list. The allowed headings are only those eight. So we cannot add a custom heading. So we must fit content into allowed headings. The "About The Team" content could go under "About the role"? But that's about role not team. Could go under "Requirements"? Not appropriate. Could go under "Qualifications"? Not appropriate. Could go under "Benefits"? Not appropriate. Could go under "Pay"? No. Could go under "Schedule"? No. So we likely omit that content because we cannot create a heading for it and we shouldn't put it elsewhere incorrectly. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we must include all content; we must preserve ALL substantive information; do NOT invent or summarize away detail. So we must preserve all substantive info. If we omit the team culture content, we lose substantive info. But maybe that content is considered boilerplate/fluff and not substantive? It's about diversity, inclusive culture, mentorship, work-life balance. Could be considered substantive but generic. However the instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid including that content under existing headings if relevant. Could we put it under "About the role"? The role description already includes a paragraph about the role; we could append the team culture info there as additional prose. That would preserve it. Similarly, "About The Team" includes "Diverse Experiences", "Why AWS?", etc. Those are generic but could be considered part of the role description. So we can incorporate them into the About the role section as additional paragraphs.
Thus we will have About the role containing:
- First paragraph: "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 maybe a paragraph about 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."
- Then "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."
- Then "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."
- Then "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."
- Then "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."
That preserves all that content.
Now Responsibilities: list as
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We need to parse description. Job title: AWS seeking a world class sales professional... but we should not repeat job title as heading. We need sections: - About the role: maybe description of role? The posting includes "Description" paragraph: "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." That's about the role. So we can put that in
under
About the role
. - Responsibilities: The bullet list after "Key job responsibilities". We need to extract each bullet as- each bullet.
Now Requirements: Basic Qualifications: "Bachelor's degree, or Master's degree in business, operations, human resources, adult education, organizational development, instructional design or related field."
Now Qualifications: Preferred Qualifications: "certification in a relevant technical field."
Now Benefits: The paragraph about 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."
Also note earlier there is mention of sign-on payments, RSUs, sales incentives as part of compensation. That could be part of Pay section. We'll include that.
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. 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 preserve the location-specific salary ranges. Could format as list.
We should not include Job ID or Company line.
Now ensure we don't include any boilerplate like equal opportunity employer, accommodation info, etc. Remove those.
Now produce HTML fragment:
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.
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.