Jobs · Advertising · New York

Global Account Manager, AWS Industries, Automotive & Manufacturing, Sales

Amazon Web Services (AWS) · New York, United States · 4 days ago
AdvertisingFull-time
The user wants me to reformat a job posting into clean semantic HTML. I need to follow the rules carefully: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use
  • for lists,

    for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings - fold into short

    or drop 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include section ONLY when posting has real specific content - never emit heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless posting actually states them 9. Prefer few substantive sections over many thin ones 10. Output ONLY HTML fragment - no /, no markdown code fences Let me analyze the job posting content: - Description/About the role: There's a description paragraph about AWS seeking a sales professional for global customer relationship with Automotive & Manufacturing customer. Also "Why AWS?" section with Mentorship & Career Growth and Work/Life Balance. - Key job responsibilities: List of responsibilities - About The Team: Description of AWS Industries and Automotive & Manufacturing IBU team - Basic Qualifications: List of basic qualifications - Preferred Qualifications: List of preferred qualifications - Pay: Base salary ranges for different locations - Benefits: Comprehensive benefits listed - Company: Amazon Web Services, Inc. - Job ID: A10586856 I need to structure this into appropriate sections. Let me map: - "About the role" - for the initial description and Why AWS sections - "Responsibilities" - for Key job responsibilities - "About the team" - for About The Team - "Requirements" or "Qualifications" - for Basic Qualifications and Preferred Qualifications (could combine or separate) - "Pay" - for base salary ranges - "Benefits" - for benefits listed The posting has real content for all these sections. I should include them. For Job ID and Company, I'll fold into a short

    at the end or beginning. Let me write the HTML:

    About the role

    AWS is seeking a sales professional to manage a global customer relationship with one of our large global Automotive & Manufacturing customers. You will define and execute a CXO relationship strategy within the account, including engaging with a dedicated account team, AWS senior leaders for executive sponsorship, coordinating executive business reviews, and maintaining customer satisfaction. The Global Account Manager ("GAM") will partner with the customer to build strategic relationships, articulate a clear vision, and deliver business value. The successful GAM will develop and execute a broad strategy for earning customer trust and driving AWS solution and service adoption across the customer's Digital Technology, Operations, Line of Business (LoB), and Research & Development leadership. The GAM will work with all appropriate AWS resources (Executives, Solution Architects, Customer Solutions Managers, Industry Specialists, Marketing, Partners, Support, Service Teams and Professional Services) to deliver customer outcomes. This is an Individual Contributor role, but necessitates an account leader mindset, and may included dotted line responsibility for downstream sales, technical and industry specialist resources. The GAM will also effectively leverage existing programs and mechanisms, innovate and scale new mechanisms, and develop formal case studies and other forms of references highlighting outcomes and solutions running on AWS.

    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.

    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.

    Responsibilities

    • Contributing to, and leading, within an AWS customer account team.
    • Identifying and building trusted advisor relationships with key influencers and decision-makers, specifically CxOs at the customer, across Line of Business (LoB), Functional (R&D, Engineering, Manufacturing, Supply Chain), and Digital & IT.
    • Working closely with internal AWS teams (executives, solution architects, industry specialists, marketing, partners, enterprise support, service teams and professional services), as well as external SI and ISV partners, to support the best business solution(s) for customers.
    • Defining a CXO relationship strategy within the customer, coordinating executive business reviews, and maintaining customer satisfaction levels.
    • Displaying strong leadership presence and being able to command a room in a meeting.
    • Should be seen as an authority in communicating via email, phone, and face to face, and comfortable writing executive briefing documents for, and communicating with, the most senior executives at the company.
    • Operating with significant autonomy and discretion. A high degree of decision making is required in routine customer engagement, business judgment is critical.
    • Managing a global sales pipeline via Salesforce and facilitating all stages of a sale.
    • Participating and leading in the negotiation and closing of legal agreements, such as Enterprise Agreements (EAs), and contracts, such as Private Pricing Addendums (PPAs).
    • Maintaining knowledge of AWS's broad solution and service offerings, corresponding to solving customers' business problems.
    • Defining product and solution requirements by understanding and evangelizing the needs of customers, including feedback via PFR's or the service teams.
    • Working with marketing and communications to develop formal references, PR and case studies highlighting impactful customer activity and workloads running on AWS.

    About the team

    The AWS Industries (AWSI) and Automotive & Manufacturing Industry Business Unit (IBU) team is committed to helping industry customers enable their digital transformation journeys. Our primary goal is to meet customers where they are in their cloud journey and work backwards from their industry specific needs to transform their business and their entire industry. Our team speaks the language of our industry customers, which means that we focus on business outcomes and industry use cases on behalf of our customers, whether that is how we build products and solutions, how we sell, how we deliver, or how we partner.

    Qualifications

    Basic Qualifications

    • 8+ years of sales experience
    • Experience managing and growing complex business relationship at scale
    • Experience as primary account manager of a global federated enterprise working with multiple business units and influencing governance and policy or equivalent
    • Experience producing executive-level written materials and presenting to executive audiences
    • Experience with CRM tools like Salesforce
    • Experience working with Data & AI related technologies, including, but not limited to, AI/ML, GenAI, Analytics, Database, and/or Storage

    Preferred Qualifications

    • MBA, or Bachelor's degree
    • Experience building and managing large and high performance teams
    • Experience in manufacturing, process, or industrial engineering
    • 6+ years of commercial agreements experience
    • Experience in executive level engagement with SVP/VP/C-Suite
    • Experience with AWS or cloud technologies
    • Experience creating and implementing long-term transformational account strategies in a customer-facing role or equivalent

    Pay

    The base salary range for this position varies by location. 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, IL, Chicago: $142,800 - $193,200 annually
    • USA, MI, Detroit: $142,800 - $193,200 annually
    • USA, NY, New York: $157,100 - $212,600 annually
    • USA, VA, Arlington: $142,800 - $193,200 annually

    Benefits

    Amazon 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
    • Parental leave

    Learn more about our benefits at https://amazon.jobs/en/benefits.

    Company: Amazon Web Services, Inc. | Job ID: A10586856

    Wait, I need to check the rules again. The user said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use h3 for main sections. I used h4 for subsections like "Why AWS?", "Mentorship & Career Growth", "Work/Life Balance", "Basic Qualifications", "Preferred Qualifications". That's fine - h4 is not prohibited, but the rule says use h3 for section headings. It doesn't say I can't use h4 for subsections. But to be safe, maybe I should keep everything at h3 level? The example includes "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule" as h3. So I should use h3 for those main sections. For subsections like "Why AWS?" maybe I can use h3 as well? But that would create many h3 sections. The rule says "use

    for section headings". It doesn't forbid h4. I think using h4 for subsections is acceptable semantic HTML. However, the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests those are the section headings they want. I'll keep my structure but ensure main sections are h3. Subsections can be h4 or just strong text. I'll keep h4 for clarity. Also, I need to remove EEO boilerplate. The posting includes: "Amazon is an equal opportunity employer and does not discriminate on the basis of protected veteran status, disability, or other legally protected status. Our inclusive culture empowers Amazonians to deliver the best results for our customers. If you have a disability and need a workplace accommodation or adjustment during the application and hiring process, including support for the interview or onboarding process, please visit https://amazon.jobs/content/en/how-we-hire/accommodations for more information. If the country/region you're applying in isn't listed, please contact your Recruiting Partner." This is EEO

Similar jobs