Technical Account Manager

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. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove recruiting tips? That might be considered boilerplate? It's not required but maybe not substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Recruiting tips maybe not required but could be considered not substantive? Might be considered optional but we can keep if it's substantive? It says "Prefer a few substantive sections over many thin ones." Recruiting tips is generic advice, maybe not needed. Also "Our people and culture", "Our purpose", "Professional development", "Qualified applicants with criminal histories", "Fair Chance Hiring and Ban-the-Box Notices", "You may also be eligible to participate in a discretionary annual incentive program", "This position is aligned with the Project Talent Model." Those are likely boilerplate or not specific to role. We should keep only substantive role-specific content: responsibilities, qualifications, skills, benefits, pay, schedule? The posting mentions travel 10% average. That's schedule? It's travel requirement. Could be under Schedule? Not exactly schedule but maybe we can put under "Travel" but we only have allowed headings. Could put under Schedule if we interpret schedule as work schedule/travel. But we should only create Schedule if posting actually states them. It does state travel 10% average. So we can include Schedule section with that detail. Benefits: The posting mentions "This position is aligned with the Project Delivery Model. To view the associated benefit package, please reference this document USBenefitsJourneyProjectandCenterTAM". Also later: "This position is aligned with the Project Talent Model. To view the associated benefit package, please reference this document (1) (5) https://resources.deloitte.com/:b:/r/sites/dnet-tod-us/Shared Documents/Benefits/BenefitsJourney_COMBINED.pdf?csf=1&web=1&e=zo0pT5." That's benefits info but just a link. We can include Benefits section with that note. Pay: The posting includes wage range: $137,500 to $229,100. Also mentions not typical to be hired at top. We can include Pay section with that range. Now we need sections: About the role? The intro paragraph: "Are you an experienced, passionate pioneer in technology who wants to work in a collaborative environment? As an experienced Sr.Technical Account Manager you will have the ability to share new ideas and collaborate on projects as a consultant without the extensive demands of travel. If so, consider an opportunity with Deloitte under our Project Delivery Talent Model. Project Delivery Model (PDM) is a talent model that is tailored specifically for long-term, onsite client service delivery." That's about the role. Could be About the role. Responsibilities: The bullet list after "Work You'll Do/Responsibilities". We need to extract responsibilities as list items. Skills: There's a list of skills after "The successful candidate would possess these skills:" then a list of bullet-like sentences. Also later there is another list of skills: "Meticulous attention to detail and quality of work product Ability to work independently and collaborate as part of a team Effective written and verbal communication skills ..." That seems duplicated. We need to preserve all substantive info but avoid duplication. We should combine unique skills. Qualifications: The "Qualifications Required" section with bullet points. We must not repeat job title as heading. Use

for each section. We must not include Job ID/requisition numbers. We must output only HTML fragment. Let's extract content. First, About the role paragraph: "Are you an experienced, passionate pioneer in technology who wants to work in a collaborative environment? As an experienced Sr.Technical Account Manager you will have the ability to share new ideas and collaborate on projects as a consultant without the extensive demands of travel. If so, consider an opportunity with Deloitte under our Project Delivery Talent Model. Project Delivery Model (PDM) is a talent model that is tailored specifically for long-term, onsite client service delivery." We can keep that as

. Responsibilities: The text after "Work You'll Do/Responsibilities The Senior Technical Account Manager leads the technical relationship with strategic Google Public Sector customers. This role owns cloud adoption planning, operational health, executive engagement, and complex escalations while coordinating across Google product, engineering, support, and delivery teams. The successful candidate would possess these skills: Lead multiple technical workstreams across complex public-sector customer environments. Serve as the primary trusted technical advisor for customer leaders and executives. Develop account-level cloud adoption plans, operational strategies, and technical roadmaps. Lead quarterly business reviews, executive sessions, and technical planning meetings. Coordinate critical launches, product releases, capacity planning, and high-priority customer events. Direct complex escalations involving Google Support, Product Engineering, and Site Reliability Engineering. Advocate for customer requirements and influence product improvements, features, and fixes. Identify risks proactively and establish clear plans for resolution. Coach junior TAMs and provide quality oversight across assigned accounts." Note: The phrase "The successful candidate would possess these skills:" seems to start responsibilities but then list. Actually that list is responsibilities. We'll treat as responsibilities list. We need to put each as

. Let's list them: - Lead multiple technical workstreams across complex public-sector customer environments. - Serve as the primary trusted technical advisor for customer leaders and executives. - Develop account-level cloud adoption plans, operational strategies, and technical roadmaps. - Lead quarterly business reviews, executive sessions, and technical planning meetings. - Coordinate critical launches, product releases, capacity planning, and high-priority customer events. - Direct complex escalations involving Google Support, Product Engineering, and Site Reliability Engineering. - Advocate for customer requirements and influence product improvements, features, and fixes. - Identify risks proactively and establish clear plans for resolution. - Coach junior TAMs and provide quality oversight across assigned accounts. Now Skills: There's a list after "The successful candidate would possess these skills:" but we already used that for responsibilities. Actually the text seems overlapping. Let's re-examine original: After responsibilities paragraph, there is "The successful candidate would possess these skills:" then list of responsibilities? Actually the list after that seems to be responsibilities. Then later there is another list: "Meticulous attention to detail and quality of work product Ability to work independently and collaborate as part of a team Effective written and verbal communication skills Meticulous attention to detail and quality of work product Ability to build and sustain professional relationships Ability to lead projects or workstreams Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment Strong interpersonal skills and professional demeanor Ability to meet deadlines Ability to mentor and provide clear guidance to others". That seems like skills/competencies. Thus we need to separate: Responsibilities list (the longer list). Skills list (the shorter list). However the first list after "The successful candidate would possess these skills:" might be responsibilities but we already used it. Let's verify: The responsibilities paragraph earlier: "The Senior Technical Account Manager leads the technical relationship with strategic Google Public Sector customers. This role owns cloud adoption planning, operational health, executive engagement, and complex escalations while coordinating across Google product, engineering, support, and delivery teams." Then immediately after that: "The successful candidate would possess these skills: Lead multiple technical workstreams across complex public-sector customer environments. Serve as the primary trusted technical advisor for customer leaders and executives. Develop account-level cloud adoption plans, operational strategies, and technical roadmaps. Lead quarterly business reviews, executive sessions, and technical planning meetings. Coordinate critical launches, product releases, capacity planning, and high-priority customer events. Direct complex escalations involving Google Support, Product Engineering, and Site Reliability Engineering. Advocate for customer requirements and influence product improvements, features, and fixes. Identify risks proactively and establish clear plans for resolution. Coach junior TAMs and provide quality oversight across assigned accounts." Thus that list is actually responsibilities (or maybe skills). But we can treat as responsibilities. Then later there is another list of skills/competencies. Thus we will have Responsibilities section with those items. Skills section will include the later list. Let's extract skills list: "Meticulous attention to detail and quality of work product Ability to work independently and collaborate as part of a team Effective written and verbal communication skills Meticulous attention to detail and quality of work product Ability to build and sustain professional relationships Ability to lead projects or workstreams Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment Strong interpersonal skills and professional demeanor Ability to meet deadlines Ability to mentor and provide clear guidance to others" Note duplication: "Meticulous attention to detail and quality of work product" appears twice. We'll deduplicate. List unique items: - Meticulous attention to detail and quality of work product - Ability to work independently and collaborate as part of a team - Effective written and verbal communication skills - Ability to build and sustain professional relationships - Ability to lead projects or workstreams - Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment - Strong interpersonal skills and professional demeanor - Ability to meet deadlines - Ability to mentor and provide clear guidance to others Now Qualifications: The "Qualifications Required" section: "Required 8+ or more years of customer-facing cloud, technical consulting, support, or transformation experience, including at least four years supporting Google Cloud implementations or programs. Experience leading complex cloud programs, executive relationships, critical launches, and technical escalations. At least 2+ years of hands-on experience with modern software-development practices, microservices, distributed systems, and APIs Executive-level communication, influence, problem-solving, and client-management skills. Active Google Cloud professional-level certification. Bachelor's or Master's degree in Computer Science, Information Technology, Engineering, or related technical field or equivalent professional experience. Ability to obtain a U.S. Government TS/SCI security clearance Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future. Ability to travel 10%, on average, based on the work you do and the clients and industries/sectors you serve" Note travel 10% appears here; we might move travel to Schedule section. But qualifications also includes travel. We'll keep travel in Schedule. Thus Qualifications list: - 8+ or more years of customer-facing cloud, technical consulting, support, or transformation experience, including at least four years supporting Google Cloud implementations or programs. - Experience leading complex cloud programs, executive relationships, critical launches, and technical escalations. - At least 2+ years of hands-on experience with modern software-development practices, microservices, distributed systems, and APIs. - Executive-level communication, influence, problem-solving, and client-management skills. - Active Google Cloud professional-level certification. - Bachelor's or Master's degree in Computer Science, Information Technology, Engineering, or related technical field or equivalent professional experience. - Ability to obtain a U.S. Government TS/SCI security clearance. - Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future. Travel 10% goes to Schedule. Now Benefits: The posting includes two references to benefit package documents. We'll include a short paragraph: "This position is aligned with the Project Delivery Model. To view the associated benefit package, please reference this document USBenefitsJourneyProjectandCenterTAM." Also later: "This position is aligned with the Project Talent Model. To view the associated benefit package, please reference this document (1) (5) https://resources.deloitte.com/:b:/r/sites/dnet-tod-us/Shared Documents/Benefits/BenefitsJourney_COMB