Technical Account Manager, AWS Enterprise Support, Strategic Industries
Amazon Web Services (AWS) · Dallas, TX · 1 mo ago
ConsultingFull-time
We need to output HTML fragment with sections: About the role? The description includes many paragraphs. We need to extract sections: About the role (maybe from description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading only if content exists. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate: EEO, legal, accommodation links, etc. Also remove duplicated lines, navigation, cookie, etc. Must preserve all substantive info.
We need to decide what content belongs to each section.
Let's parse the posting:
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 basically the role description. Could be "About the role" or "Responsibilities". Then we have sections: "About The Team", "About AWS Diverse Experiences", "Why AWS?" with subpoints: Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Then "Basic Qualifications", "Preferred Qualifications". Then benefits and pay info later.
We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can combine some.
We have "About The Team" and "About AWS Diverse Experiences" maybe under "About the role"? Or we could create "About the team" but not allowed heading. So we could put that content under "About the role" or maybe "Responsibilities". Probably best to put the initial descriptive paragraphs under "About the role". Then responsibilities could be derived from the duties described: being principal technical advisor, voice of customer, work with engineers, proactive strategies, advocacy, strategic guidance, etc. But we must not invent or summarize away detail; we must preserve all substantive info. So we could list responsibilities as bullet list from the description.
Let's extract responsibilities bullet points:
- Support customers’ creative and transformative spirit of innovation across all technologies (Compute, Storage, Database, Big Data, Application-level services, Networking, Serverless, etc.)
- Act as principal technical advisor and ‘voice of the customer’ for organizations ranging from start-ups to Fortune 500 enterprises.
- Work with appropriate engineers and service teams to see issues through to resolution (not hands-on troubleshooting).
- Work proactively to help craft and execute strategies to drive customers' adoption and use of AWS services (EC2, S3, DynamoDB & RDS databases, Lambda, CloudFront CDN, IoT, etc.)
- Effectively 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 to help plan and build solutions using best practices.
- Proactively keep customers’ AWS environments operationally healthy and resilient.
- Understand customers’ business/operational needs and technical challenges through close relationships.
- Help customers achieve greatest value from AWS.
- Ability to travel 10% or more as needed.
That seems comprehensive.
Now "About the role" could include introductory paragraphs about AWS Global Services, team, etc. But we might duplicate some content. However we must preserve all substantive info; we can include them in About the role section as paragraphs.
Next, "About The Team" and "About AWS Diverse Experiences" and "Why AWS?" sections: these are about company culture, benefits, etc. Could go under "About the role" as well, but maybe better to put under "About the role" or maybe "Qualifications"? Not exactly. The allowed headings do not include "About the team" or "Why AWS". So we need to fit them somewhere. Perhaps we can put them under "About the role" as additional paragraphs describing the team and culture. That's acceptable as long as we don't create extra headings.
Then "Basic Qualifications" and "Preferred Qualifications" map to "Requirements" and "Qualifications"? The spec says we can use headings: Requirements, Qualifications, Skills. Basic Qualifications likely map to Requirements. Preferred Qualifications could map to Qualifications or Skills. We have also "Skills" maybe from preferred qualifications? But we can treat Basic Qualifications as Requirements, Preferred Qualifications as Qualifications. Skills maybe not explicitly listed; we could omit Skills heading if no specific skills list beyond qualifications.
We need to preserve all substantive info: Basic Qualifications list:
- 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
Preferred Qualifications:
- Experience with AWS services or other cloud offerings
- Experience in internal enterprise or external customer-facing environment as a technical lead
We also have "Los Angeles County applicants: ..." and other legal stuff which we must remove as boilerplate. Also EEO statements, accommodation links, etc. Must remove.
We also have pay info: "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. Learn more about our benefits at https://amazon.jobs/en/benefits."
Then location-specific salary ranges:
USA, CA, San Francisco - 151,000.00 - 204,300.00 USD annually
USA, CA, Sunnyvale - 151,000.00 - 204,300.00 USD annually
USA, GA, Atlanta - 131,300.00 - 177,600.00 USD annually
USA, NY, New York - 144,500.00 - 195,400.00 USD annually
USA, TX, Dallas - 131,300.00 - 177,600.00 USD annually
USA, VA, Arlington - 131,300.00 - 177,600.00 USD annually
USA, VA, Herndon - 131,300.00 - 177,600.00 USD annually
USA, WA, Seattle - 131,300.00 - 177,600.00 USD annually
We need to include Pay section if posting actually states them. Yes, they state salary ranges. So we should create a Pay section with those details. Should we include the note about sign-on payments and RSUs? Yes, preserve.
Benefits section: they list comprehensive benefits. So we should create Benefits section with that info.
Schedule: they mention travel 10% or more as needed. That's not a schedule but maybe we could put under Schedule? The spec says include Schedule section only if posting actually states them. Travel requirement is not a schedule; but maybe we could treat as Schedule? However they didn't specify work hours, shift, etc. So better not to create Schedule section unless there is explicit schedule info. There's no mention of work hours, remote, etc. So we omit Schedule.
Skills: we could create Skills section if there is explicit list of skills. Not really; we have qualifications. Could omit Skills.
Now we need to output only HTML fragment, no /, no markdown.
We'll structure:
for each heading only if content exists. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate: EEO, legal, accommodation links, etc. Also remove duplicated lines, navigation, cookie, etc. Must preserve all substantive info.
We need to decide what content belongs to each section.
Let's parse the posting:
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 basically the role description. Could be "About the role" or "Responsibilities". Then we have sections: "About The Team", "About AWS Diverse Experiences", "Why AWS?" with subpoints: Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Then "Basic Qualifications", "Preferred Qualifications". Then benefits and pay info later.
We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can combine some.
We have "About The Team" and "About AWS Diverse Experiences" maybe under "About the role"? Or we could create "About the team" but not allowed heading. So we could put that content under "About the role" or maybe "Responsibilities". Probably best to put the initial descriptive paragraphs under "About the role". Then responsibilities could be derived from the duties described: being principal technical advisor, voice of customer, work with engineers, proactive strategies, advocacy, strategic guidance, etc. But we must not invent or summarize away detail; we must preserve all substantive info. So we could list responsibilities as bullet list from the description.
Let's extract responsibilities bullet points:
- Support customers’ creative and transformative spirit of innovation across all technologies (Compute, Storage, Database, Big Data, Application-level services, Networking, Serverless, etc.)
- Act as principal technical advisor and ‘voice of the customer’ for organizations ranging from start-ups to Fortune 500 enterprises.
- Work with appropriate engineers and service teams to see issues through to resolution (not hands-on troubleshooting).
- Work proactively to help craft and execute strategies to drive customers' adoption and use of AWS services (EC2, S3, DynamoDB & RDS databases, Lambda, CloudFront CDN, IoT, etc.)
- Effectively 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 to help plan and build solutions using best practices.
- Proactively keep customers’ AWS environments operationally healthy and resilient.
- Understand customers’ business/operational needs and technical challenges through close relationships.
- Help customers achieve greatest value from AWS.
- Ability to travel 10% or more as needed.
That seems comprehensive.
Now "About the role" could include introductory paragraphs about AWS Global Services, team, etc. But we might duplicate some content. However we must preserve all substantive info; we can include them in About the role section as paragraphs.
Next, "About The Team" and "About AWS Diverse Experiences" and "Why AWS?" sections: these are about company culture, benefits, etc. Could go under "About the role" as well, but maybe better to put under "About the role" or maybe "Qualifications"? Not exactly. The allowed headings do not include "About the team" or "Why AWS". So we need to fit them somewhere. Perhaps we can put them under "About the role" as additional paragraphs describing the team and culture. That's acceptable as long as we don't create extra headings.
Then "Basic Qualifications" and "Preferred Qualifications" map to "Requirements" and "Qualifications"? The spec says we can use headings: Requirements, Qualifications, Skills. Basic Qualifications likely map to Requirements. Preferred Qualifications could map to Qualifications or Skills. We have also "Skills" maybe from preferred qualifications? But we can treat Basic Qualifications as Requirements, Preferred Qualifications as Qualifications. Skills maybe not explicitly listed; we could omit Skills heading if no specific skills list beyond qualifications.
We need to preserve all substantive info: Basic Qualifications list:
- 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
Preferred Qualifications:
- Experience with AWS services or other cloud offerings
- Experience in internal enterprise or external customer-facing environment as a technical lead
We also have "Los Angeles County applicants: ..." and other legal stuff which we must remove as boilerplate. Also EEO statements, accommodation links, etc. Must remove.
We also have pay info: "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. Learn more about our benefits at https://amazon.jobs/en/benefits."
Then location-specific salary ranges:
USA, CA, San Francisco - 151,000.00 - 204,300.00 USD annually
USA, CA, Sunnyvale - 151,000.00 - 204,300.00 USD annually
USA, GA, Atlanta - 131,300.00 - 177,600.00 USD annually
USA, NY, New York - 144,500.00 - 195,400.00 USD annually
USA, TX, Dallas - 131,300.00 - 177,600.00 USD annually
USA, VA, Arlington - 131,300.00 - 177,600.00 USD annually
USA, VA, Herndon - 131,300.00 - 177,600.00 USD annually
USA, WA, Seattle - 131,300.00 - 177,600.00 USD annually
We need to include Pay section if posting actually states them. Yes, they state salary ranges. So we should create a Pay section with those details. Should we include the note about sign-on payments and RSUs? Yes, preserve.
Benefits section: they list comprehensive benefits. So we should create Benefits section with that info.
Schedule: they mention travel 10% or more as needed. That's not a schedule but maybe we could put under Schedule? The spec says include Schedule section only if posting actually states them. Travel requirement is not a schedule; but maybe we could treat as Schedule? However they didn't specify work hours, shift, etc. So better not to create Schedule section unless there is explicit schedule info. There's no mention of work hours, remote, etc. So we omit Schedule.
Skills: we could create Skills section if there is explicit list of skills. Not really; we have qualifications. Could omit Skills.
Now we need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
... paragraphs ...
Responsibilities
- ... each responsibility ...
Requirements
- ... basic qualifications ...
Qualifications
- ... preferred qualifications ...
Benefits
... benefits description ...
Pay
... base salary range info + location-specific ranges ...
We must ensure we don't include filler like "commensurate with experience". Not present. We must not repeat job title. Not include Job ID. We must remove boilerplate: EEO, accommodation links, legal statements about Los Angeles County, San Francisco Fair Chance, etc. Also remove "Our inclusive culture empowers Amazonians..." maybe that's part of Why AWS? but it's not boilerplate; it's substantive about culture. We can keep it under About the role or maybe as part of Benefits? It's about inclusive culture. Could be part of About the role description. We'll keep it. We must also remove duplicated lines. Ensure we don't duplicate. Now craft the About the role paragraph(s). Combine the initial paragraphs plus About The Team, About AWS Diverse Experiences, Why AWS? (Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance). Also maybe the "If you wish to be at the forefront of innovation, come join us!" is a call to action; we can keep. Let's gather all non-boilerplate substantive paragraphs: 1. 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