Sr. Technical Account Manager, TAM
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have description (intro) maybe as
. Then responsibilities as
Responsibilities
with- . Then About The Team maybe as
- each location range.
Schedule:
- Travel 10% or more as needed.
Now we must not repeat the job title as a heading. The job title is Sr. Technical Account Manager (TAM). We must not put that as heading.
We also must not put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can drop Job ID. Now we need to output only HTML fragment, no /, no markdown fences. Let's construct: Start with an introductory
containing the description paragraph(s) up to before responsibilities? The description includes first paragraph: "Description 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." Then maybe a second paragraph: "Key job responsibilities 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
About the Team
with subsections? Could treat subsections asor maybe separate headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if we have content. We can also have other headings? Probably not; they gave examples but we can use other headings? Safer to stick to those headings. But we have content like "About The Team" which maps to "About the role"? Actually "About the role" is a heading example; we have "About The Team". Could use About the Team
. That's okay as it's similar to examples.
We also have "Work/Life Balance", "Inclusive Team Culture", "Mentorship and Career Growth". Those could be under About the Team as subpoints maybe
or
- . Could also make separate sections but they'd be thin. Better to include them as
under About the Team. Then Basic Qualifications ->
Requirements
orQualifications
. Since they gave both Basic and Preferred Qualifications. We can combine:Requirements
with- for basic qualifications, and maybe another
Preferred Qualifications
but that's also a qualification heading. Could usePreferred Qualifications
. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Preferred Qualifications as separate headings? Might be okay. Then Benefits: we have benefits description (health insurance, 401k matching, paid time off, parental leave). Also mention sign-on payments and RSUs. So we can haveBenefits
with- .
Pay: we have base salary ranges for multiple locations. So we can have
Pay
with maybe alisting ranges. Schedule: travel 10% or more as needed. That's schedule info. So
Schedule
withabout travel. We must not include boilerplate like EEO, legal, accommodation links, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove Job ID, requisition numbers. Also remove "Amazon is an equal opportunity employer..." etc. Also remove Los Angeles County specifics etc. Also remove "If you have a disability..." etc. Also remove "Learn more about our benefits at ..." link? That's maybe boilerplate but it's about benefits; we can keep benefits description but not the link. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep benefits description but drop the link. Also remove "Company - Amazon Web Services, Inc." maybe not needed. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the responsibilities bullet points as they are (but we can condense into list items). Must not lose any detail. Let's extract responsibilities: - craft and execute technical cloud strategies to drive customers adoption and use of AWS services. - 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. - 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. (But travel goes to Schedule maybe.) Also earlier: "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." That's a responsibility. Also "As a Senior TAM, you will craft and execute technical cloud strategies to drive customers adoption and use of AWS services." Also "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." Also "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." Also maybe "If you wish to be at the forefront of innovation, come join us!" is not responsibility. Also "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." That's more about role nature; could be in description. Now About The Team content: - 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. Now Basic Qualifications: - 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 Now Benefits: - 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. (We can drop the link but keep the description.) Now Pay: - Base salary range for this position is listed below. Then list ranges per location: - 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 - 207,800.00 USD annually - USA, IL, Chicago - 153,600.00 - 207,800.00 USD annually - USA, NY, New York - 169,000.00 - 228,600.00 USD annually - USA, TX, Dallas - 153,600.00 - 207,800.00 USD annually - USA, TX, Houston - 153,600.00 - 207,800.00 USD annually - USA, VA, Arlington - 153,600.00 - 207,800.00 USD annually - USA, WA, Seattle - 153,600.00 - 207,800.00 USD annually We need to include all that info. Could present as