Sr. Technical Account Manager, TAM
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info, remove boilerplate: EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. Also remove "Amazon is an equal opportunity employer..." etc. Also remove Los Angeles County specifics? Those are legal boilerplate; they might be considered EEO/legal. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should drop those paragraphs about LA County, San Francisco Fair Chance, disability accommodation, etc. Also drop "Our inclusive culture empowers Amazonians..." maybe keep as part of culture? It's not boilerplate but maybe part of inclusive team culture. It's okay.
We need to include sections only when posting has real specific content. So we need sections: About the role? Actually description includes overview; we could have a section "About the role" with prose summarizing role. But we must not repeat job title. Could use "About the role" heading.
Responsibilities: from "Key job responsibilities" bullet list (though not bullet but sentences). We'll make
- each responsibility.
About The Team: could be a section "About the Team" with subsections? Could keep as one section with paragraphs.
Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth: these are subheadings within About The Team. Should we make them separate sections? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are possible headings. But we can also use other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use other headings as needed but must be . Probably we should stick to those categories where applicable. So we could have sections: About the role, Responsibilities, About the Team (maybe not in list but okay), Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth, Basic Qualifications, Preferred Qualifications, Benefits, Pay.
We need to include Pay section only if posting states them. Yes salary ranges listed. So include Pay.
Benefits: posting mentions comprehensive benefits including health insurance etc. So include Benefits.
Schedule: not mentioned besides travel 10% or more. Not a schedule. So we skip Schedule.
Requirements: maybe combine Basic and Preferred Qualifications? Could have Requirements section with Basic Qualifications. But we have separate Basic Qualifications and Preferred Qualifications. Could combine into Requirements and Preferred? The instruction: use headings like Requirements, Qualifications, Skills. We could have Basic Qualifications under Requirements, Preferred Qualifications under Qualifications. Or we could have Requirements (basic) and Preferred Qualifications (preferred). Let's do: Requirements
for Basic Qualifications. Preferred Qualifications
for Preferred.
Skills: not explicitly listed; we could omit.
Now we need to preserve all substantive info. Let's extract.
Description paragraph: "Would you like to join one of the fastest-growing organizations within Amazon Web Services (AWS) and help customers across all industries and sizes—including Automotive, Financial Services, Energy, Healthcare, Industrial and Manufacturing, Media and Entertainment, Telecom, Big Data, and more—gain the best value and service from AWS? At AWS Enterprise Support, we're looking for a Sr. Technical Account Manager (TAM) to support and influence our customers' creative and transformative spirit of innovation across all technology areas, including Compute, Storage, Database, Big Data, AI/ML, 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—serving as their advocate to AWS product teams."
We'll put that in
under About the role.
Key job responsibilities: list sentences:
- As a Senior TAM, you will craft and execute technical cloud strategies to drive customers adoption and use of AWS services.
- Your technical acumen and customer-facing skills will enable you to effectively represent AWS at our customer, and drive discussions with senior leadership regarding operational excellence, cloud maturity, support, and risk management.
- You will provide advocacy and strategic technical guidance to plan and build solutions using best practices, and proactively keep the customers AWS environments operationally healthy.
- 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! (maybe fluff but keep?)
We'll make each as
- .
About The Team: paragraphs:
- 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.
- 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 cloud.
- 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 and AmazeCon conferences, inspire us to never stop embracing our uniqueness.
- Mentorship and 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.
We could keep these as subheadings within About the Team, but we could also make separate sections for each. Since we have headings for Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth, we could make them separate sections. That seems okay.
Basic Qualifications: list:
- 5+ years of design/implementation/operations/consulting with distributed applications experience
- 5+ years of technical engineering experience
Preferred Qualifications:
- Experience in a 24x7 operational services or support environment
- Experience in internal enterprise or external customer-facing environment as a technical lead
- Experience with AWS services or other cloud offerings
- Understanding of the AWS Well-Architected Framework pillars and ability to properly apply them to existing or new customer architecture, implementations, and/or solutions
Benefits: 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 part of compensation; could be in Benefits or Pay. We'll include in Benefits maybe.
Pay: list of salary ranges per location. We need to preserve all. Could present as
- each location range.
We should not include duplicated lines. The posting repeats salary ranges for each location; we keep them all.
We must not include Job ID or requisition numbers as headings; we can drop them.
We must not include application instructions.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ...
...
About the Team
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.
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 cloud.
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 and AmazeCon conferences, inspire us to never stop embracing our uniqueness.
Mentorship and 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.
Requirements
- 5+ years of design/implementation/operations/consulting with distributed applications experience
- 5+ years of technical engineering experience
Preferred Qualifications
- Experience in a 24x7 operational services or support environment
- Experience in internal enterprise or external customer-facing environment as a technical lead
- Experience with AWS services or other cloud offerings
- Understanding of the AWS Well-Architected Framework pillars and ability to properly apply them to existing or new customer architecture, implementations, and/or solutions
Benefits
Your Amazon package will include sign-on payments and restricted stock units (RSUs). 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.
Pay
- USA, CA, Mountain View - 176,600.00 - 239,000.00 USD annually
- USA, CA, SAN FRANCISCO - 176,600.00 - 239,000.00 USD annually
- USA, CA, San Diego - 153,600.00 - 207,800.00 USD annually
- USA, GA, Atlanta - 153,600.00 - 20
for prose. We must preserve all substantive info, remove boilerplate: EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. Also remove "Amazon is an equal opportunity employer..." etc. Also remove Los Angeles County specifics? Those are legal boilerplate; they might be considered EEO/legal. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should drop those paragraphs about LA County, San Francisco Fair Chance, disability accommodation, etc. Also drop "Our inclusive culture empowers Amazonians..." maybe keep as part of culture? It's not boilerplate but maybe part of inclusive team culture. It's okay. We need to include sections only when posting has real specific content. So we need sections: About the role? Actually description includes overview; we could have a section "About the role" with prose summarizing role. But we must not repeat job title. Could use "About the role" heading. Responsibilities: from "Key job responsibilities" bullet list (though not bullet but sentences). We'll make
- each responsibility.
About The Team: could be a section "About the Team" with subsections? Could keep as one section with paragraphs.
Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth: these are subheadings within About The Team. Should we make them separate sections? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are possible headings. But we can also use other headings if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use other headings as needed but must be
. Probably we should stick to those categories where applicable. So we could have sections: About the role, Responsibilities, About the Team (maybe not in list but okay), Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth, Basic Qualifications, Preferred Qualifications, Benefits, Pay. We need to include Pay section only if posting states them. Yes salary ranges listed. So include Pay. Benefits: posting mentions comprehensive benefits including health insurance etc. So include Benefits. Schedule: not mentioned besides travel 10% or more. Not a schedule. So we skip Schedule. Requirements: maybe combine Basic and Preferred Qualifications? Could have Requirements section with Basic Qualifications. But we have separate Basic Qualifications and Preferred Qualifications. Could combine into Requirements and Preferred? The instruction: use headings like Requirements, Qualifications, Skills. We could have Basic Qualifications under Requirements, Preferred Qualifications under Qualifications. Or we could have Requirements (basic) and Preferred Qualifications (preferred). Let's do:
Requirements
for Basic Qualifications.Preferred Qualifications
for Preferred. Skills: not explicitly listed; we could omit. Now we need to preserve all substantive info. Let's extract. Description paragraph: "Would you like to join one of the fastest-growing organizations within Amazon Web Services (AWS) and help customers across all industries and sizes—including Automotive, Financial Services, Energy, Healthcare, Industrial and Manufacturing, Media and Entertainment, Telecom, Big Data, and more—gain the best value and service from AWS? At AWS Enterprise Support, we're looking for a Sr. Technical Account Manager (TAM) to support and influence our customers' creative and transformative spirit of innovation across all technology areas, including Compute, Storage, Database, Big Data, AI/ML, 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—serving as their advocate to AWS product teams." We'll put that inunder About the role. Key job responsibilities: list sentences: - As a Senior TAM, you will craft and execute technical cloud strategies to drive customers adoption and use of AWS services. - Your technical acumen and customer-facing skills will enable you to effectively represent AWS at our customer, and drive discussions with senior leadership regarding operational excellence, cloud maturity, support, and risk management. - You will provide advocacy and strategic technical guidance to plan and build solutions using best practices, and proactively keep the customers AWS environments operationally healthy. - 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! (maybe fluff but keep?) We'll make each as
- .
About The Team: paragraphs:
- 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.
- 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 cloud.
- 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 and AmazeCon conferences, inspire us to never stop embracing our uniqueness.
- Mentorship and 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.
We could keep these as subheadings within About the Team, but we could also make separate sections for each. Since we have headings for Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth, we could make them separate sections. That seems okay.
Basic Qualifications: list:
- 5+ years of design/implementation/operations/consulting with distributed applications experience
- 5+ years of technical engineering experience
Preferred Qualifications:
- Experience in a 24x7 operational services or support environment
- Experience in internal enterprise or external customer-facing environment as a technical lead
- Experience with AWS services or other cloud offerings
- Understanding of the AWS Well-Architected Framework pillars and ability to properly apply them to existing or new customer architecture, implementations, and/or solutions
Benefits: 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 part of compensation; could be in Benefits or Pay. We'll include in Benefits maybe.
Pay: list of salary ranges per location. We need to preserve all. Could present as
- each location range.
We should not include duplicated lines. The posting repeats salary ranges for each location; we keep them all.
We must not include Job ID or requisition numbers as headings; we can drop them.
We must not include application instructions.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ... ...
About the Team
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.
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 cloud.
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 and AmazeCon conferences, inspire us to never stop embracing our uniqueness.
Mentorship and 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.
Requirements
- 5+ years of design/implementation/operations/consulting with distributed applications experience
- 5+ years of technical engineering experience
Preferred Qualifications
- Experience in a 24x7 operational services or support environment
- Experience in internal enterprise or external customer-facing environment as a technical lead
- Experience with AWS services or other cloud offerings
- Understanding of the AWS Well-Architected Framework pillars and ability to properly apply them to existing or new customer architecture, implementations, and/or solutions
Benefits
Your Amazon package will include sign-on payments and restricted stock units (RSUs). 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.
Pay
- USA, CA, Mountain View - 176,600.00 - 239,000.00 USD annually
- USA, CA, SAN FRANCISCO - 176,600.00 - 239,000.00 USD annually
- USA, CA, San Diego - 153,600.00 - 207,800.00 USD annually
- USA, GA, Atlanta - 153,600.00 - 20
- each location range.
We should not include duplicated lines. The posting repeats salary ranges for each location; we keep them all.
We must not include Job ID or requisition numbers as headings; we can drop them.
We must not include application instructions.
Now produce HTML fragment.
Structure: