Sr Manager - Vendor management

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Content: - Intro paragraph about Expedia Group, mission, etc. That's about the company, not necessarily a section. Could be part of "About the role"? Actually "About the role" heading is for description of role. The intro includes "At Expedia Group, we help travelers explore the world..." That's more about company. Could be placed under a heading like "About the role"? Might be okay. But we need to follow instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. We need to preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Thus we need to identify sections: - About the role: we have description of role: "This Role, You Will ..." bullet list of duties. That's responsibilities. - Responsibilities: we can list duties. - Requirements/Qualifications: we have "Experience And Qualifications" paragraph with bullet-like sentences. - Skills: maybe we can extract skills from that. - Benefits: we have "Benefits And Perks" paragraph listing benefits. - Pay: we have "The total cash range for this position in Seattle is $155,000.00 to $217,000.00. Employees in this role have the potential to increase their pay up to $248,000.00, which is the top of the range, based on ongoing, demonstrated, and sustained performance in the role. Starting pay for this role will vary based on multiple factors, including location, available budget, and an individual’s knowledge, skills, and experience. Pay ranges may be modified in the future." Thus we have pay specifics. - Schedule: not mentioned. So we should NOT include Schedule section. We also have "Introduction to the Team" etc. That could be part of About the role or maybe a separate section like "About the Team". But only allowed headings are the given list. We could put team intro under About the role or maybe under Responsibilities? Probably better to include under About the role as prose. We need to remove boilerplate: EEO, accommodation requests, etc. Also remove "Learn more about life at Expedia Group at https://careers.expediagroup.com/life." That's maybe not boilerplate but could be considered a link; but it's part of Benefits section? It's after Benefits. Might be considered extra but it's not boilerplate; but it's a link to learn more. Might be okay to keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to life at Expedia Group is not necessarily boilerplate; it's more like a promotional link. Might be okay to keep but it's not a duty/requirement/benefit. It's more like a call to action. Could be considered application instruction? Not exactly. Safer to drop it? The instruction says remove application instructions. That link is not an application instruction but a "Learn more about life". Might be considered navigation. I'd drop it to be safe. Also remove "Accommodation requests" etc. That's EEO/accommodation boilerplate. Remove "About Expedia Group" etc? That's company description; could be considered boilerplate? It's not EEO but it's about the company. Might be okay to keep as part of About the role? But it's somewhat generic. However we need to preserve ALL substantive information; does that include company description? It's substantive about the employer. Might be okay to keep under About the role. But we need to avoid duplication: there is also later "About Expedia Group" paragraph repeating similar info. That's duplicated lines; we should drop duplicates. Thus we need to craft HTML:

  About the role

  At Expedia Group, we help travelers explore the world, one journey at a time. As a global travel company powered by passionate people, trusted partnerships, and leading technology, we connect travelers, partners, and advertisers through our consumer brands, B2B network, and travel advertising business. Here, you'll do meaningful work that helps millions of people discover, book, and experience travel with more ease, confidence, and joy. Our five Behaviors—Traveler First, Think Big, Operate with Excellence, Ownership Mindset, and Succeed Together—help foster a supportive environment where people can grow their careers and have the flexibility, benefits, and support to do their best work. Join us and build for travelers everywhere.

  Then maybe a

  Introduction to the Team

  but not allowed heading. Could incorporate into About the role as another paragraph. Then Responsibilities: list duties. We need to extract duties from "This Role, You Will ..." bullet list. Let's list them: - Build and maintain strong relationships with outsourced partners. - Administer communication frameworks across diverse internal and external groups. - Serve as a contractual expert for internal and external business stakeholders. - Provide guidance and support regarding the terms and conditions of contractual agreements. - Negotiate contractual changes as required in support of the business. - Act as the primary escalation point for vendor performance and contract compliance. - Identify potential risks in vendor relationships and develop mitigation strategies. - Encourage vendors to adopt innovative practices and continuous improvement initiatives. - Partner with Legal and Procurement in support of contract negotiations. - Identify opportunities to optimize the vendor footprint and outsourcing spend. - Maintain a strong understanding of global Contact Center outsourcing partners, including their capabilities, footprint, pricing models, and regional needs. - Facilitate discussions and drive resolution related to disputes, performance challenges, and other contract-affecting situations. - Develop policies and procedures to support vendor and supplier relationship governance. - Produce content requirements, facilitate executive performance reviews, and manage action items. - Coordinate, schedule, and facilitate all facets of Partner Business Reviews. - Drive consistent messaging and strategy to outsourced partners. We need to put these in
  • . Then Experience And Qualifications: we have paragraph: "Naturally inquisitive with excellent communication skills. A collaborative partner who works effectively with suppliers and across internal functions. You see the bigger picture. You understand how everything we do impacts customer experience. Skilled at identifying key messages and communicating them effectively. You are numerate. You can size and prioritise opportunity where you find it. Bachelor’s Degree (MBA or equivalent desired). You are excellent at building and maintaining relationships, both internally and externally." We can turn into a list under Requirements or Qualifications. The headings: Requirements, Qualifications, Skills. We need to decide which to use. The content includes both experience and qualifications. Could split: Requirements (education, experience) and Skills (communication, numeracy, relationship building). But we must not create sections with filler. We have real content for each. We could do:

    Requirements

    • Bachelor’s Degree (MBA or equivalent desired)

    Skills

    • Naturally inquisitive with excellent communication skills
    • A collaborative partner who works effectively with suppliers and across internal functions
    • See the bigger picture; understand how everything we do impacts customer experience
    • Skilled at identifying key messages and communicating them effectively
    • Numerate; able to size and prioritise opportunity
    • Excellent at building and maintaining relationships, both internally and externally
    But we need to preserve all substantive information; we should not lose any nuance. The original sentences are separate; we can keep them as list items. Alternatively we could have a single

    Experience And Qualifications

    but not allowed heading; we must use one of the allowed headings. Could use Qualifications for the degree and maybe experience; Skills for the rest. We also have "Experience And Qualifications" heading in original; we could map to Qualifications. Thus:

    Qualifications

    • Bachelor’s Degree (MBA or equivalent desired)
    But we also have experience: "Naturally inquisitive with excellent communication skills." etc. Those are more skills/experience. Thus we could have:

    Requirements

    • Bachelor’s Degree (MBA or equivalent desired)

    Skills

    • Naturally inquisitive with excellent communication skills
    • A collaborative partner who works effectively with suppliers and across internal functions
    • See the bigger picture; understand how everything we do impacts customer experience
    • Skilled at identifying key messages and communicating them effectively
    • Numerate; able to size and prioritise opportunity
    • Excellent at building and maintaining relationships, both internally and externally
    Now Benefits: we have paragraph: "Expedia Group offers benefits and perks designed to support employees and their families, including medical, dental, and vision coverage, paid time off, an Employee Assistance Program, wellness and travel reimbursement, travel discounts, and International Airlines Travel Agent Network (IATAN) membership." We can make a
    • list. Pay: we have paragraph with details. We'll put under

      Pay

      and then

      with the details. We should not include Schedule. We also need to remove duplicated lines: The "About Expedia Group" appears twice; we can keep one version maybe under About the role. We also need to remove the "Learn more about life at Expedia Group at https://careers.expediagroup.com/life." and accommodation requests, EEO, etc. Now we need to output only HTML fragment, no /, no markdown. Let's craft. We'll start with

      About the role

      and include the intro paragraph plus maybe team intro. Team intro: "Introduction to the Team The Product Team creates high-quality end-to-end experiences for travelers, partners, and Expedia Group. Our customer-first mindset focuses on developing products that encourage loyalty and repeat business from our travelers and partners. We partner closely with teams across Expedia Group to achieve growth and results for our customers and company. Within the Product organization, Traveler and Partner Service Platform (TPSP) is a service function supporting the business through strategic vendor management. This role helps ensure business continuity and growth through the strategic management of Expedia Group’s supply base." We can include that as a paragraph after the intro. Thus About the role section will have two paragraphs: first about company mission, second about team. Now Responsibilities:

      Responsibilities

      with each duty. Now Qualifications:

      Qualifications

      with Bachelor’s Degree. Now Skills:

      Skills

      with the skill statements. Now Benefits:

      Benefits

      with list. Now Pay:

      Pay