Technical Account Manager, AWS Enterprise Support, Strategic Industries
Amazon Web Services (AWS) · Santa Clara, CA · 1 mo ago
ConsultingFull-time
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. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the description and extract sections.
Let's read the description:
"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!"
Then sections: "About The Team", "About AWS Diverse Experiences", "Why AWS?" etc. But we need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which content goes where.
"About the role": likely the initial description about role, responsibilities, etc. Could include description of what TAM does.
"Responsibilities": list of duties: work with engineers, proactive strategies, advocacy, strategic guidance, keep environments healthy, understand needs, travel 10%+, etc.
"Requirements": Basic Qualifications: 3+ years technical engineering experience, experience with operational parameters and troubleshooting for three of list, Bachelor's degree.
"Qualifications": Preferred Qualifications: Experience with AWS services or other cloud offerings, experience in internal enterprise or external customer-facing environment as a technical lead.
"Skills": maybe technical acumen, customer-facing skills, ability to represent AWS, drive discussions, advocacy, strategic guidance, etc. Could extract from description.
"Benefits": The paragraph about base salary range, sign-on payments, RSUs, comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave, link to benefits.
"Pay": The base salary ranges listed for various locations. Could be separate Pay section.
"Schedule": maybe travel requirement? Not exactly schedule. Could be nothing. The posting mentions travel 10% or more as needed. That's not schedule. No explicit schedule info. So we should not create Schedule section unless there is real specific content. There's no schedule like full-time, part-time, shift. So omit Schedule.
We must not create sections with filler like "commensurate with experience". So only include sections where we have real content.
We need to output HTML fragment only, no markdown fences.
Let's craft:
for 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 remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the description and extract sections.
Let's read the description:
"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!"
Then sections: "About The Team", "About AWS Diverse Experiences", "Why AWS?" etc. But we need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which content goes where.
"About the role": likely the initial description about role, responsibilities, etc. Could include description of what TAM does.
"Responsibilities": list of duties: work with engineers, proactive strategies, advocacy, strategic guidance, keep environments healthy, understand needs, travel 10%+, etc.
"Requirements": Basic Qualifications: 3+ years technical engineering experience, experience with operational parameters and troubleshooting for three of list, Bachelor's degree.
"Qualifications": Preferred Qualifications: Experience with AWS services or other cloud offerings, experience in internal enterprise or external customer-facing environment as a technical lead.
"Skills": maybe technical acumen, customer-facing skills, ability to represent AWS, drive discussions, advocacy, strategic guidance, etc. Could extract from description.
"Benefits": The paragraph about base salary range, sign-on payments, RSUs, comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave, link to benefits.
"Pay": The base salary ranges listed for various locations. Could be separate Pay section.
"Schedule": maybe travel requirement? Not exactly schedule. Could be nothing. The posting mentions travel 10% or more as needed. That's not schedule. No explicit schedule info. So we should not create Schedule section unless there is real specific content. There's no schedule like full-time, part-time, shift. So omit Schedule.
We must not create sections with filler like "commensurate with experience". So only include sections where we have real content.
We need to output HTML fragment only, no markdown fences.
Let's craft:
About the role
... paragraph summarizing role description ...
But we must preserve ALL substantive information; do not invent or summarize away detail. That means we should not summarize; we need to keep the details. However we can keep the original sentences but maybe break into paragraphs. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the content verbatim (or close) but we can format into HTML. We should not omit any details. So we need to include the full description text (excluding boilerplate). That is a lot. But we can keep it as paragraphs. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out those parts. Let's identify boilerplate: - "Amazon is an equal opportunity employer and does not discriminate on the basis of protected veteran status, disability, or other legally protected status." -> EEO boilerplate, remove. - "Los Angeles County applicants: Job duties for this position include: work safely and cooperatively with other employees, supervisors, and staff; adhere to standards of excellence despite stressful conditions; communicate effectively and respectfully with employees, supervisors, and staff to ensure exceptional customer service; and follow all federal, state, and local laws and Company policies. Criminal history may have a direct, adverse, and negative relationship with some of the material job duties of this position. These include the duties and responsibilities listed above, as well as the abilities to adhere to company policies, exercise sound judgment, effectively manage stress and work safely and respectfully with others, exhibit trustworthiness and professionalism, and safeguard business operations and the Company’s reputation. Pursuant to the Los Angeles County Fair Chance Ordinance, we will consider for employment qualified applicants with arrest and conviction records. Pursuant to the San Francisco Fair Chance Ordinance, we will consider for employment qualified applicants with arrest and conviction records." -> This is legal/EEO/Fair Chance boilerplate, remove. - "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." -> accommodation boilerplate, remove. - "Learn more about our benefits at https://amazon.jobs/en/benefits." -> maybe keep as part of benefits? It's a link; could be considered part of benefits. It's not boilerplate; it's a reference. Might keep. - "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). 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." -> This is benefits and pay info; keep. - Then list of locations with salary ranges. Keep as Pay. - "Company - Amazon Web Services, Inc. Job ID: A10517599" -> Job ID, remove. - Also "About The Team", "About AWS Diverse Experiences", "Why AWS?" etc. Those are sections but not in allowed headings. We need to decide where to place that content. The allowed headings are limited; we must not create headings outside those. So we need to fold that content into existing allowed sections if possible, or drop if not relevant? The instruction: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it". So we must use only the allowed headings. If there is content that doesn't fit any, we could either omit or incorporate into existing sections if relevant. The "About The Team", "About AWS Diverse Experiences", "Why AWS?" are generic company info; could be considered part of "About the role" maybe? Or we could drop as boilerplate? It's not exactly boilerplate but it's promotional. Might be considered part of "About the role". The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we should keep it. But we need to place it somewhere. Probably under "About the role" as an overview. Thus "About the role" section will contain the initial paragraphs about AWS Global Services, the team, the role, plus the "About The Team", "About AWS Diverse Experiences", "Why AWS?" sections. Now "Responsibilities": we need to list duties. The description includes many responsibilities: work with engineers/service teams to see issues through resolution, proactively craft and execute strategies to drive adoption and use of AWS 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. We should put these as- items.
"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.
We can put as
- .
"Qualifications": Preferred Qualifications: Experience with AWS services or other cloud offerings; Experience in internal enterprise or external customer-facing environment as a technical lead.
"Skills": Could extract from description: technical acumen, customer-facing skills, ability to represent AWS within a customer’s environment, drive discussions with senior leadership regarding incidents, trade-offs, support and risk management, provide advocacy and strategic technical guidance, help plan and build solutions using best practices, proactively keep customers’ AWS environments operationally healthy and resilient, understand business/operational needs and technical challenges, help achieve greatest value from AWS. Also maybe ability to travel 10%+.
We can list as
- .
"Benefits": The paragraph about base salary range, sign-on payments, RSUs, comprehensive benefits including health insurance..., 401(k) matching, paid time off, parental leave. Also link to benefits.
We should keep that as
maybe with
- for benefits list.
"Pay": The base salary ranges for each location. Could be a
- with each location and range.
We must not include "Schedule" as no specific schedule info.
Now we need to ensure we don't repeat content across sections unnecessarily, but we must preserve all substantive info. If we mention something in Responsibilities and also in Skills, that's duplication but maybe okay. However we should aim to not duplicate unnecessarily. But the instruction says preserve ALL substantive information; does not forbid duplication. However better to avoid duplication but still keep info somewhere.
Let's extract the exact text blocks.
Original description (first paragraph) up to "come join us!" includes many details. We'll need to keep that but maybe split.
Let's copy the relevant sections:
Intro:
"AWS Global Services includes