Lead Principal Technical Account Manager

for prose. So we need to convert responsibilities into list items. Probably each bullet under Responsibilities can be a

• for each major responsibility area (Customer Engagement, Issue Resolution, Account Management and Governance, Technical Delivery Management, Innovation and Continuous Improvement, Planning & Execution, Collaboration & Partnership, Problem Solving, Continuous Learning, Continuous Improvement, Performance and Development). That captures content. Qualifications: There's a "Qualifications" heading with a disclaimer and then range and benefit info. Actually qualifications include disclaimer about immunization etc. Also there is "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $103,800 - $234,600 per year." That's Pay info. Also benefits list. So we need sections: Qualifications (maybe include disclaimer), Pay, Benefits. Schedule not present. Skills not explicit; maybe we can omit Skills. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. Also remove "About Us" maybe? The "About Us" paragraph could be considered About the role? Actually About Us is company description; could be omitted as boilerplate? It's not required but could be considered part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not exactly boilerplate but could be considered company overview; maybe we keep as part of About the role? The job description already has description of role; we could treat that as About the role. The "About Us" paragraph is more about Oracle; could be considered boilerplate? Not exactly legal; but it's generic marketing. Might be okay to keep? Safer to omit as not directly about role. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine About the role (the initial job description paragraphs) and maybe include the "About Us" as part of About the role? But it's not about the role. I'd omit it. Thus sections: - About the role: prose from first paragraph(s) before "Responsibilities". That includes: "Serves as the main contact for complex contracts, providing expert business processes, product/service (e.g., hardware, applications, software) functionality, and/or implementation knowledge. Drives efforts to provide services and educates customers on ways to leverage Oracle services. Reviews service requests, anticipates and identifies potential crises, takes the lead in resolving issues, and owns connecting and/or escalating issues to relevant teams to reach solutions. Drives the development and management of plans, actively engaging in review and update documentation, and leverages understanding and collaborates across teams to anticipate and identify opportunities to propose and lead the delivery of opportunities and contract renewals and reports results. Serves as an expert and drives ongoing maintenance, leads others to act as a liaison between teams, and recommends opportunities to improve customer ability to adopt product and service changes. Collaborates with peers across teams and departments to lead the adoption of innovative ways of delivering services, serves as a role model for driving innovation, experiments with new approaches, and provides input on decisions made the development of new services and/or processes, influencing others across teams to remain up-to-date with technological business, and industry trends." We can put that in

  . - Responsibilities:

  • each area. We need to capture the details under each responsibility area? Could condense but must preserve ALL substantive information; not invent or summarize away detail. If we just list area headings, we lose detail. We need to include the details. Could make each responsibility area a
  • containing a

    with its description? But instruction: Use

    • for any list of duties/requirements/benefits, and

      for prose. So we can have

      • where inside
      • we can have

        for prose. That's acceptable. Thus for each responsibility area, we create

      • ...text...

      . That preserves details. Similarly for Qualifications: we have disclaimer paragraph. Could be

      . Also maybe we need to include "Career Level - IC5" as qualification? That's metadata; could be included in Qualifications as a

      . Also "Range and benefit information provided..." is Pay, not Qualifications. Thus Qualifications section: include disclaimer paragraph and Career Level. Pay section: include hiring range and bonus etc. Benefits section: list benefits. Schedule: not present, omit. Skills: not present, omit. Now produce HTML fragment. Let's extract details precisely. First, About the role text: I'll copy the initial paragraph(s) before "Responsibilities". The text: "Job Description Serves as the main contact for complex contracts, providing expert business processes, product/service (e.g., hardware, applications, software) functionality, and/or implementation knowledge. Drives efforts to provide services and educates customers on ways to leverage Oracle services. Reviews service requests, anticipates and identifies potential crises, takes the lead in resolving issues, and owns connecting and/or escalating issues to relevant teams to reach solutions. Drives the development and management of plans, actively engaging in review and update documentation, and leverages understanding and collaborates across teams to anticipate and identify opportunities to propose and lead the delivery of opportunities and contract renewals and reports results. Serves as an expert and drives ongoing maintenance, leads others to act as a liaison between teams, and recommends opportunities to improve customer ability to adopt product and service changes. Collaborates with peers across teams and departments to lead the adoption of innovative ways of delivering services, serves as a role model for driving innovation, experiments with new approaches, and provides input on decisions made the development of new services and/or processes, influencing others across teams to remain up-to-date with technological business, and industry trends." Note there is "Job Description" at start; we can ignore that as it's not needed. We'll start after that. Now Responsibilities sections: We have headings: Customer Engagement: (with sub-bullets) Issue Resolution: Account Management and Governance: Technical Delivery Management: Innovation and Continuous Improvement: Core Responsibilities (with subheadings Planning & Execution, Collaboration & Partnership, Problem Solving, Continuous Learning, Continuous Improvement, Performance and Development) We need to capture each subheading's prose. Let's extract each. Customer Engagement paragraph: "Serves as the main point of contact for highly complex contracts, providing business process, product/service (e.g., hardware, applications, software) functionality, and/or implementation expertise in an advisory manner. Acts as a role model for other Technical Account Managers (TAMs).Drives efforts to provide timely services, ensuring alignment with their practices, procedures, contractual budgets, providing expert-level insight on the development, utilization, and revision of contractual agreements.Maintains customer relations, communicating with key leaders across internal and external teams and lines of business to ensure satisfaction. Provides updates on customer status to senior leadership.Educates customers on the most effective and efficient way to leverage Oracle services, products, and tools, leading others to take innovative approaches and providing feedback on customer organization performance and assisting in the development of support strategies." Issue Resolution paragraph: "Reviews service requests and guides others to identify relevant information to gather from appropriate parties and takes the lead to determine next steps.Anticipates and identifies potential crises or concerns and takes the lead in resolving customer issues and incidents in a timely manner, leveraging extensive expertise and knowledge of available resources and other customer experiences across Oracle to develop innovative solutions and mitigate future challenges.Takes ownership of connecting and escalating high-impact issues to relevant teams or management, demonstrating foresight in identifying and reporting critical pain points and minimizing business impact." Account Management and Governance paragraph: "Drives the development and management of service delivery and project plans throughout their lifecycle and ensures positive margins according to governance and account management expectations and contracted terms, mentoring others.Implements goals for maintaining accurate and up-to-date customer account information, contracts, and service history, addressing any gaps or needs for additional information.Ensures adherence to the schedule for conducting account planning and reviews, closely monitoring, and communicating the status of highly complex projects including identification of risks and mitigation recommendations.Actively engages in reviewing and updating documentation, partnering with senior team members and leadership to maintain contract cost analysis, resource allocation, scheduling, and scope management, providing assistance to others working to meet contract revenue and margin objectives.Leverages understanding of business needs and collaborates across teams to anticipate and identify opportunities to propose and lead the delivery of new opportunities and contract renewals and reports results to key leaders." Technical Delivery Management paragraph: "Leading the review of and advises customers on optimal use and health or their Oracle product/service investment, serving as an expert and driving ongoing maintenance to optimize and ensure effectiveness and performance of the product and/or service.Serves as a role model for collaborating with cross-functional teams, influencing the execution and development of technical delivery plans.Leads others to act as a liaison between customers, internal, and external teams.Recommends opportunities to others to increase customer understanding and improve their ability to adopt product and service changes according to policies and best practices." Innovation and Continuous Improvement paragraph: "Collaborates extensively with peers across teams and lines of business to lead the adoption of innovative ways to deliver service to customers and optimize overall product and service utilization to achieve ROI goals, influencing roadmaps and customer decision making.Serves as a role model for driving innovation, identifying ways to experiment with new approaches, and seeking opportunities to share knowledge of product, service, and/or support information or issues.Anticipates and leads others to identify and capitalize on opportunities for enhanced value for services.Provides input on decisions made when developing new services and/or processes, influencing others across teams to stay abreast of technological, business, and industry trends." Now Core Responsibilities subheadings: Planning & Execution: "Manages and provides direction on timelines, deliverables, and budgets when applicable for critical high-impact projects or initiatives that impact the line of business, ensuring timely completion and adherence to requirements. Anticipates and plans for shifts in resources or timelines based on changing business priorities, ensuring optimal outcomes." Collaboration & Partnership: "Influences cross-functional leaders and external stakeholders to gain alignment on strategic objectives. Fosters partnerships with key business leaders, stakeholders, and/or customers, identifying opportunities for expanding partnerships and promoting long-term organizational success. Champions transparency and inclusivity by actively seeking, listening to, and incorporating diverse perspectives." Problem Solving: "Leads specialized, advanced problem-solving efforts, serving as an escalation point for complex issues. Guides others to leverage innovative data-driven techniques to address ambiguous or novel issues, identify root causes, and drives the implementation of solutions that prevent future issues." Continuous Learning: "Leverages deep industry knowledge and expertise to serve as a thought leader within the organization. Contributes to the advancement of the field or industry through thought leadership (e.g., conference presentations, white papers, research contributions). Maintains and evolves expertise in relevant areas by proactively monitoring emerging trends, technologies, and industry standards, ensuring the organization remains current with best practices. Champions continuous learning and knowledge sharing, promoting professional development across teams. Applies new knowledge to drive advancement and mentors others to do the same." Continuous Improvement: "Develops innovative solutions and drives the implementation of ideas that increase the