Technical Account Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Let's extract content: Intro: "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" section. Then "Work You'll Do/Responsibilities" heading. Then list of 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: (then list) - 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. Then after that there is a list of skills (maybe duplicate). Actually after responsibilities they 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". This seems like skills/competencies. Then "The Team AI & Engineering leverages cutting-edge engineering capabilities..." That's description of team. Could be part of About the role or separate? Might be "About the team". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Could put team description under About the role or maybe under Responsibilities? Probably About the role. Then "Qualifications Required" heading. Then 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. - Ability to travel 10%, on average, based on the work you do and the clients and industries/sectors you serve Then "The wage range for this role takes into account..." That's Pay section. Provide range: $137,500 to $229,100. Also some explanation about not typical to be hired at top etc. We should preserve all substantive info. So include Pay section with that paragraph. Then "Recruiting tips From developing a stand out resume..." That's application instructions? It's about recruiting tips, maybe considered boilerplate? It's not exactly application instructions but could be considered extra. The instruction says remove application instructions. This is recruiting tips, maybe considered application instructions? Safer to remove? It's not directly "how to apply" but still maybe considered extra. I'd remove it as it's not core job description. Then "Benefits This position is aligned with the Project Delivery Model. To view the associated benefit package, please reference this document USBenefitsJourneyProjectandCenterTAM". That's a benefits reference but no actual benefits listed. The instruction: never create Benefits section unless posting actually states them. It only references a document, not listing benefits. So we should not create Benefits section because no specific benefits listed. However later there is also "You may also be eligible to participate in a discretionary annual incentive program..." That's a benefit (annual incentive). Also earlier: "Our people and culture..." etc. That's culture description, not benefits. The discretionary annual incentive program is a benefit. Also mention of reasonable accommodations etc. That's more policy. But we have a specific benefit: discretionary annual incentive program. Also maybe "Professional development" etc. That's also a benefit. The posting includes sections: "Our people and culture", "Our purpose", "Professional development", "Qualified applicants with criminal histories..." etc. Those are not benefits per se but could be considered culture. The instruction: only include Benefits if posting actually states them. It does state discretionary annual incentive program and professional development opportunities. So we can include Benefits section with those items. We need to avoid duplication. Also need to remove duplicated lines like "Meticulous attention to detail and quality of work product" appears twice. We should keep only once. Also remove duplicated lines like "Deloitte is committed to providing reasonable accommodations for people with disabilities." appears twice. Keep once. Also remove "Our purpose" etc? Not required headings but could be part of About the role? Might be extra. The instruction: Prefer a few substantive sections over many thin ones. So we could combine culture/purpose into About the role or maybe omit if not needed. But we must preserve ALL substantive information. So we need to include that info somewhere. Could add a section "About the role" that includes intro, team description, purpose, culture, professional development? But that may become too large. However we must preserve all substantive info; we can include them as paragraphs under About the role. But we must not create sections with filler. So we can have About the role containing all descriptive paragraphs: intro, PDM description, team description, purpose, culture, professional development, fair chance etc. That's okay. Responsibilities section: list of duties. Qualifications section: list of qualifications. Skills section: list of skills/competencies (the list after responsibilities). Could combine with Qualifications? But they are separate headings allowed. We'll keep Skills. Pay section: wage range paragraph. Benefits section: discretionary annual incentive program, professional development opportunities, maybe also mention of reasonable accommodations? That's more policy. But we can include those as benefits? Might be okay. Schedule: not mentioned except travel 10% average. That's not schedule. No schedule info. So we omit Schedule. Now produce HTML. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Not include Job ID. Let's craft. First, About the role: combine intro paragraphs. Paragraphs: - "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." - Team description: "The Team AI & Engineering leverages cutting-edge engineering capabilities to build, deploy, and operate integrated/verticalized sector solutions in software, data, AI, network, and hybrid cloud infrastructure. These solutions are powered by engineering for business advantage, transforming mission-critical operations. We enable clients to stay ahead with the latest advancements by transforming engineering teams and modernizing technology & data platforms. Our delivery models are tailored to meet each client's unique requirements." - Purpose: "Deloitte's purpose is to make an impact that matters for our people, clients, and communities. At Deloitte, purpose is synonymous with how we work every day. It defines who we are. Our purpose comes through in our work with clients that enables impact and value in their organizations, as well as through our own investments, commitments, and actions across areas that help drive positive outcomes for our communities." - Culture: "Our inclusive culture empowers our people to be who they are, contribute their unique perspectives, and make a difference individually and collectively. It enables us to leverage different ideas and perspectives, and bring more creativity and innovation to help solve our clients' most complex challenges. This makes Deloitte one of the most rewarding places to work. Deloitte is committed to providing reasonable accommodations for people with disabilities. If you require a reasonable accommodation to participate in the recruiting process, please direct your inquiries to the Global Call Center (GCC) at USTalentCICInbox@deloitte.com." - Professional development: "From entry-level employees to senior leaders, we believe there's always room to learn. We offer opportunities to build new skills, take on leadership opportunities and connect and grow through mentorship. From on-the-job learning experiences to formal development programs, our professionals have a variety of opportunities to continue to grow throughout their career." - Fair chance: "Qualified applicants with criminal histories, including arrest or conviction records, will be considered for employment in accordance with the requirements of applicable state and local laws, including the Los Angeles County Fair Chance Ordinance for Employers, City of Los Angeles's Fair Chance Initiative for Hiring Ordinance, San Francisco Fair Chance Ordinance, and the California Fair Chance Act." We could combine reasonable accommodations line only once. Now Responsibilities: list items. We need to capture all responsibilities bullet points. List: - Lead the technical relationship with strategic Google Public Sector customers. - Own cloud adoption planning, operational health, executive engagement, and complex escalations while coordinating across Google product, engineering, support, and delivery teams. - 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. Also there is "The successful candidate would possess these skills:" but that's more skills; we already have skills section. Now Skills: list from after responsibilities. We need to deduplicate. 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 - 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 "Meticulous attention