Jobs · Consulting · California

Technical Account Manager, AWS Enterprise Support, Strategic Industries

Amazon Web Services (AWS) · San Jose, CA · 1 mo ago
ConsultingFull-time
We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, duplicate lines, application instructions, EEO etc. We need to parse the description. Let's extract content: First paragraph: "AWS Global Services includes experts from across AWS who help our customers design, build, operate, and secure their cloud environments. Customers innovate with AWS Professional Services, upskill with AWS Training and Certification, optimize with AWS Support and Managed Services, and meet objectives with AWS Security Assurance Services. Our expertise and emerging technologies include AWS Partners, AWS Sovereign Cloud, AWS International Product, and the Generative AI Innovation Center. You’ll join a diverse team of technical experts in dozens of countries who help customers achieve more with the AWS cloud. Would you like to join one of the fastest-growing organizations within Amazon Web Services (AWS) and help customers of all industries and sizes including Automotive, Financial Services, Energy, Big Data, and more gain the best value and service from AWS? At AWS Enterprise Support we’re looking for a Technical Account Manager (TAM) to support our customers’ creative and transformative spirit of innovation across all technologies, including Compute, Storage, Database, Big Data, Application-level services, Networking, Serverless and more. This is not a sales role, but rather an opportunity to be the principal technical advisor and ‘voice of the customer to organizations ranging from start-ups to Fortune 500 enterprises. The TAM role is not directly hands on keyboard within the customer’s environment for troubleshooting customer support issues, rather you will work with appropriate engineers and service teams to see issues through to resolution. More importantly you will work proactively to help craft and execute strategies to drive our customers' adoption and use of AWS services, including EC2, S3, DynamoDB & RDS databases, Lambda, CloudFront CDN, IoT, and many more. Your technical acumen and customer-facing skills will enable you to effectively represent AWS within a customer’s environment, and drive discussions with senior leadership regarding incidents, trade-offs, support and risk management. You will provide advocacy and strategic technical guidance to help plan and build solutions using best practices, and proactively keep your customers’ AWS environments operationally healthy and resilient. The close relationships developed with your customers will allow you to understand their business/operational needs and technical challenges, and help them achieve the greatest value from AWS. This position will require the ability to travel 10% or more as needed. The TAM is the centerpiece of value to our Enterprise Support customers. If you wish to be at the forefront of innovation, come join us!" That's the description. Then "About The Team" heading but content: "About AWS 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?" with subpoints: "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", "Mentorship & Career Growth", "Work/Life Balance". Those are sections but they are generic corporate culture; they might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why AWS?" sections are not necessarily boilerplate but they are generic marketing. However they contain substantive info about culture, benefits? Might be considered part of Benefits? But they are not specific benefits like health insurance etc. The instruction: "Prefer a few substantive sections over many thin ones." So we may combine culture info into maybe "About the team" or "About AWS". But we need to decide which sections to include. We have Basic Qualifications, Preferred Qualifications, then EEO statements, then Los Angeles County specifics, then San Francisco Fair Chance, then accommodation link, then recruiting partner note, then base salary range and benefits description. We need to include sections: About the role (maybe from description), Responsibilities (maybe from description), Requirements (basic qualifications), Qualifications (preferred qualifications), Skills (maybe from responsibilities?), Benefits (benefits description), Pay (salary range), Schedule (travel requirement). Also maybe "About the Team" could be a section but not required. We must not create sections with filler like "commensurate with experience". We have actual salary ranges and benefits. We must not repeat job title as heading. We must not include Job ID. We must preserve all substantive info; do not invent or summarize away detail. Thus we need to extract each piece exactly as in text, but we can format as

or

  • . Must not lose any detail. Let's list substantive info blocks: 1. Overview / About the role: The long paragraph describing AWS Global Services, role, etc. Could be considered "About the role". We'll put that as

    content. 2. Responsibilities: The description includes many responsibilities: support customers' creative and transformative spirit, act as principal technical advisor, work with engineers/service teams to see issues through resolution, work proactively to craft and execute strategies to drive adoption and use of AWS services (list services), provide advocacy and strategic technical guidance to help plan and build solutions using best practices, proactively keep customers' AWS environments operationally healthy and resilient, develop close relationships to understand business/operational needs and technical challenges, help them achieve greatest value from AWS, travel 10% or more as needed. Also maybe "drive discussions with senior leadership regarding incidents, trade-offs, support and risk management." That's also responsibility. We need to capture all those as list items. 3. Requirements / Basic Qualifications: "3+ years of technical engineering experience", "Experience with operational parameters and troubleshooting for three (3) of the following: compute/storage/networking/CDN/databases/DevOps/big data and analytics/security/applications development in a distributed systems environment", "Bachelor's degree". That's it. 4. Preferred Qualifications: "Experience with AWS services or other cloud offerings", "Experience in internal enterprise or external customer-facing environment as a technical lead". Also maybe "Amazon is an equal opportunity employer..." but that's EEO boilerplate, remove. 5. Skills: Not explicitly listed separate; maybe we can infer from responsibilities: technical acumen, customer-facing skills, ability to represent AWS, drive discussions, advocacy, strategic technical guidance, etc. But we should not invent. If there is no explicit "Skills" section, we should not create one. The instruction: include a section ONLY when the posting has real, specific content for it. There's no explicit "Skills" heading. So we skip Skills. 6. Benefits: The 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 and restricted stock units (RSUs)." That's also part of compensation/benefits. So we include that. 7. Pay: The base salary ranges listed for various locations. We need to preserve all those lines. They are: USA, CA, Mountain View - 151,000.00 - 204,300.00 USD annually USA, CA, SAN JOSE - 151,000.00 - 204,300.00 USD annually USA, CA, San Francisco - 151,000.00 - 204,300.00 USD annually USA, CA, San Jose - 151,000.00 - 204,300.00 USD annually USA, CA, Santa Clara - 151,000.00 - 204,300.00 USD annually USA, TX, Dallas - 131,300.00 - 177,600.00 USD annually USA, WA, Seattle - 131,300.00 - 177,600.00 USD annually We should keep them as list items. 8. Schedule: Travel requirement: "This position will require the ability to travel 10% or more as needed." That's schedule. Also maybe "Work/Life Balance" etc but that's generic; we can ignore as not specific. We also have "About The Team" and "Why AWS?" sections with content about diverse experiences, inclusive culture, mentorship, work/life balance. Those could be considered "About the team" but not required. The instruction: Prefer a few substantive sections over many thin ones. Could combine them into a single "About the team" section with bullet points. However we need to decide if we include them. They are substantive (not boilerplate). They describe culture, mentorship, work/life balance. Might be worth including as "About the team". But we already have "About the role". Could we add "About the team" as a section? The instruction says include a section ONLY when the posting has real, specific content for it. There is content: "About AWS Diverse Experiences..." etc. So we could include an "About the team" section. But we must not create sections with filler like "commensurate with experience". The content is specific. Thus we could have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule, About the team. That's many sections but each has content. Alternatively we could merge "About the team" into "About the role" but that might dilute. Given instruction: "Prefer a few substantive sections over many thin ones." Having many sections may be considered thin if each has little content. But each has decent content. We could combine "About the team" and "Why AWS?" into a single section "About AWS" with bullet points. Let's extract that content: - "About AWS 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 AWS values curiosity and connection. Our employee-led and company-sponsored affinity groups promote inclusion and empower our people to take pride in what makes us unique. Our inclusion events foster stronger, more collaborative teams. Our continual innovation is fueled by the bold ideas, fresh perspectives, and passionate voices our teams bring to everything we do." - "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 flexible work hours and arrangements are part of our culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve in the

Similar jobs