Sr Technical Account Manager, US Federal, Enterprise Support

We need to output 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. Must not include Job ID. Must not include boilerplate like EEO, application instructions, etc. Must preserve all substantive info. We need to parse the description. Key parts: - Description includes: Application deadline: Sep 29, 2026 (maybe minor metadata, can be in a short p). Not required to keep but we can include as metadata. - As part of the AWS Applied AI Solutions organization... (intro). This is prose about role. - As a Sr TAM, you will own the support strategy for a portfolio of DoD customers... (responsibilities). Then bullet list of responsibilities under "Key job responsibilities". Those are list items. - About The Team (prose). Could be part of About the role or separate? Probably "About the Team" could be part of About the role or separate section? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (includes intro and maybe About the Team). Responsibilities (list). Requirements (basic qualifications). Qualifications (preferred qualifications). Skills (maybe derived from preferred qualifications? Could combine). Benefits (benefits description). Pay (salary ranges). Schedule (travel requirement 10% or more). Also location info maybe in About the role. We must not create sections with filler like "commensurate with experience". We have actual pay ranges and schedule (travel). Benefits described. We must not repeat job title. Must not include Job ID. We must remove boilerplate: EEO, accommodation link, etc. Also remove "About AWS" sections that are generic? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About AWS" section includes inclusive team culture, mentorship, work/life balance. That might be considered boilerplate? It's generic AWS marketing. Might be considered not substantive specific to role. Probably should remove. Keep only role-specific content. Thus we keep: - Intro paragraph about AWS Applied AI Solutions organization and vision (maybe part of About the role). - As part of AWS Enterprise Support, looking for Sr TAM... (role description). - About The Team (maybe keep as part of About the role). - Responsibilities list. - Basic Qualifications (Requirements). - Preferred Qualifications (Qualifications). - Skills maybe we can extract from preferred qualifications: technical engineering experience, AWS Well-Architected Framework, Risk Management Framework, etc. Could create a Skills section summarizing those. But we must not invent or summarize away detail. We could just put the preferred qualifications under Qualifications and maybe Skills separate if we have explicit skills list. The posting does not have a separate "Skills" heading; but we can create Skills section if we have specific skill items. The preferred qualifications list includes many skill-like items. Could treat them as Qualifications. The instruction: Use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. We have: - Basic Qualifications: 5+ years design/implementation/operations/consulting with distributed applications experience; 5+ years technical engineering experience; Bachelor's degree, or certifications; Current active TS/SCI US Gov Security Clearance. These are Requirements. - Preferred Qualifications: 7+ years technical engineering experience in operational parameters and troubleshooting for three or more of: AI/ML, compute, storage, networking, databases, DevOps, big data and analytics, security, or applications development; Understanding of AWS Well-Architected Framework pillars and ability to apply them; Experience with Risk Management Framework, continuous ATO, or contributing to ATO packages; Experience delivering through cloud service brokers or under Secure Cloud Computing Architecture–style constructs; Experience with IL5/IL6 or ADC-region environments; Familiarity with DoD program office structures and roles (PM/PMO, COR, ISSM, authorizing official); Experience in a 24x7 mission-critical operational services or support environment; Experience with infrastructure-as-code, CI/CD pipelines, or DevOps practices; AWS certification(s) — Solutions Architect, Generative AI Developer, DevOps Engineer, or similar; Experience mentoring engineers or leading a technical community of practice; Professional written and oral communication skills, including experience presenting to senior decision-makers. These could be split into Qualifications and Skills. But we can put all under Qualifications. However we need a Skills section if we have specific skills. Could extract skills: AWS Well-Architected Framework, Risk Management Framework, continuous ATO, infrastructure-as-code, CI/CD, DevOps, mentoring, communication, presenting to senior decision-makers, etc. But we must not invent. We could create a Skills section listing those explicit skill items from preferred qualifications. That would be preserving detail. Thus: - Qualifications: maybe the basic qualifications? Actually we already have Requirements for basic qualifications. Qualifications could be preferred qualifications (or combined). But we need both Requirements and Qualifications sections. Let's assign: Requirements: Basic Qualifications. Qualifications: Preferred Qualifications. Skills: maybe we can pull out specific skill sets from preferred qualifications that are skill-like: "Understanding of the AWS Well-Architected Framework pillars and the ability to apply them", "Experience with the Risk Management Framework, continuous ATO, or contributing to ATO packages", "Experience delivering through cloud service brokers or under Secure Cloud Computing Architecture–style constructs", "Experience with IL5/IL6 or ADC-region environments", "Familiarity with DoD program office structures and roles", "Experience in a 24x7 mission-critical operational services or support environment", "Experience with infrastructure-as-code, CI/CD pipelines, or DevOps practices", "AWS certification(s) — Solutions Architect, Generative AI Developer, DevOps Engineer, or similar", "Experience mentoring engineers or leading a technical community of practice", "Professional written and oral communication skills, including experience presenting to senior decision-makers". That seems like skills. But note that some of these overlap with qualifications. However we can still list them. We must not create sections with filler. All these are specific. Now Benefits: The posting includes: "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 should keep that as Benefits section. Pay: Salary ranges for three locations: USA, CO, Denver - 153,600.00 - 207,800.00 USD annually; USA, VA, Arlington - same; USA, VA, Herndon - same. So we can list Pay with those ranges. Schedule: Travel 10% or more for on-site customer engagements. That's schedule. Also location: "This role is based in Arlington, VA with Herndon, VA and Denver, CO also available." Could be part of About the role or maybe a separate line. We'll include in About the role paragraph. Application deadline: Sep 29, 2026 - minor metadata; we can include in a short p at top maybe. We must not include Job ID. Now produce HTML fragment: Start with maybe a p for deadline. Then

About the role

with prose combining intro, role description, About the Team, location. Then

Responsibilities

with

• items from Key job responsibilities. Then

  Requirements

  with
  • from Basic Qualifications. Then

    Qualifications

    with
    • from Preferred Qualifications (maybe we keep as is). Then

      Skills

      with
      • for skill items extracted. Then

        Benefits

        with

        describing benefits. Then

        Pay

        with

        listing salary ranges. Then

        Schedule

        with

        travel requirement. Make sure not to include any empty sections. Let's craft. Prose for About the role: "As part of the AWS Applied AI Solutions organization, we have a vision to provide business applications, leveraging Amazon's unique experience and expertise, that are used by millions of companies worldwide to manage day-to-day operations. We will accomplish this by accelerating our customers' businesses through delivery of intuitive and differentiated technology solutions that solve enduring business challenges. We blend vision with curiosity and Amazon's real-world experience to build opinionated, turnkey solutions. Where customers prefer to buy over build, we become their trusted partner with solutions that are no-brainers to buy and easy to use. As part of AWS Enterprise Support, we're looking for a Sr Technical Account Manager (TAM) to serve as the strategic technical advisor to US Department of Defense customers. As a Sr TAM, you will own the support strategy for a portfolio of DoD customers. You'll build deep relationships with customer decision makers, understand their mission objectives, and translate those into actionable cloud strategies. You'll conduct operational reviews, lead architecture discussions, guide incident response, and proactively identify risks before they impact mission readiness. When critical issues arise, you'll be the customer's voice inside AWS, coordinating resolution across service teams and engineering leadership. This role combines broad technical depth with strategic thinking. You'll guide customers across the full AWS service portfolio — compute, storage, databases, networking, security, containers, serverless, AI/ML, and more — while always keeping their operational goals and constraints front of mind. You'll deliver value through proactive engagement: Well-Architected reviews, resilience assessments, and adoption roadmaps tailored to each customer's environment. This position will require the ability to travel 10% or more for on-site customer engagements. This role is based in Arlington, VA with Herndon, VA and Denver, CO also available. About The Team You'll join a team of Technical Account Managers supporting Department of Defense customers. We operate as a collaborative group that shares technical knowledge, conducts peer architecture reviews, and works together to solve novel problems in high-stakes environments. Your teammates and leadership are former engineers, operators, and technologists who understand that our customers' missions demand the highest standards of reliability and trust." That seems good. Now Responsibilities list items from "Key job responsibilities": - Serve as the primary technical advisor to a portfolio of DoD customers, building trusted relationships with technical and executive stakeholders - Own and execute the support strategy for a portfolio of DoD customers. - Advise mission owners on operating AI and ML workloads, including agent activation readiness, governance, and human oversight. - Conduct proactive operational reviews and health assessments to identify risks, optimize costs, and improve resilience - Lead incident management efforts as the customer's advocate — coordinating cross-team resolution and delivering root cause analysis - Guide customers through architecture decisions using the AWS Well-Architected Framework and security best practices - Develop and execute strategic cloud adoption roadmaps aligned to customer mission objectives - Collaborate with AWS service teams to influence product improvements based on customer needs - Communicate complex technical trade-offs clearly to both engineering teams and senior decision-makers Make sure each as

      • . Now Requirements (Basic Qualifications): - 5+ years of design/implementation/operations/consulting with distributed applications experience - 5+ years of technical engineering experience - Bachelor's degree, or CASP+ (CompTIA Advanced Security Practitioner) or CCSP (Certified Cloud Security Professional) or Cloud+ or CSSLP (Certified Secure Software Lifecycle Professional) -