Client Delivery Manager

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to extract content from posting. Let's parse: About Us: description of company. Could be "About the role"? Actually "About Us" is company description. 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" maybe includes overview. But we have "Position Overview". That could be under "About the role". We'll create

About the role

with paragraph(s) containing Position Overview and maybe About Us? The instruction: do NOT repeat the job title as a heading (the page already shows it). So we can include company description as part of About the role? Might be okay. We need to include sections only when posting has real specific content. We have: - About Us (company description) - Position Overview (role description) - Requirements (list of bullet-like statements) - Tools (list) - Qualifications (list) - Skills (list) - Attributes (list) - Experience (list) - Desired Behaviors (list) - Added Skills That Will Help (list) We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no explicit Benefits, Pay, Schedule content. So we should NOT create those sections. We have Responsibilities? The posting includes "Oversee Activities" etc. Could be considered responsibilities. Also "Position Overview" includes responsibilities. We could put responsibilities under a Responsibilities heading. We have Requirements heading: we have a "Requirements" section with bullet points. We have Qualifications heading: we have "Qualifications" section with bullet points (Skills, Attributes, Experience, Desired Behaviors, Added Skills). Might need to split? But we can combine under Qualifications. We have Skills heading: we have a "Skills" subsection under Qualifications. Could also separate. We need to avoid filler like "commensurate with experience". There's phrase "College degree preferred in a related field or commensurate work experience". That's filler? It's somewhat generic but still specific? It says "commensurate work experience". Might be considered filler? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should avoid including that line if it's just filler. However it's part of Qualifications. Could we rephrase? We must preserve ALL substantive information; do NOT invent or summarize away detail. But we can omit filler lines? The instruction says never emit a heading followed by filler/placeholder text. It doesn't say we must keep filler lines; we could drop them if they are filler. However "preserve ALL substantive information" suggests we should keep substantive info, but we can drop filler. The line "College degree preferred in a related field or commensurate work experience" includes "commensurate work experience" which is filler. Might be okay to keep the first part? But we cannot split? Might be safer to keep the whole line? But then we have filler text. The instruction says never emit a heading followed by filler/placeholder text. It doesn't say we cannot have filler inside a section; just that we shouldn't have a heading with only filler. So having a section with substantive content plus some filler lines is okay. So we can keep it. We need to output only HTML fragment, no markdown. Let's structure:

About the role

Thrive is a rapidly growing technology solutions provider focusing upon Cloud, Cyber Security, Networking, Disaster Recovery and Managed Services. Our corporate culture, engineering talent, customer-centric approach, and focus upon "next generation" services help us stand out amongst our peers. Thrive is on the look-out for individuals who don't view their weekdays spent at "a job", but rather look to develop valuable skills that ignite their passion and lead to a CAREER. If you're attracted to a "work hard, play hard" environment, seeking the guidance, training and experience necessary to build a lucrative career, then welcome to THRIVE!!

The Client Delivery Manager (CDM) is a customer-facing role responsible for building strategic relationships and driving measurable success outcomes for Thrive clients. The CDM serves as the primary point of contact for assigned accounts, ensuring that clients realize full value from contracted services while managing contract P&L and identifying growth opportunities. The ideal candidate combines ITIL/ITSM expertise with strong business acumen and a passion for customer success.

Responsibilities

• Build strategic relationships with key client stakeholders
• Identify current pain points and desired outcomes affected by services under contract
• Provide measurable value to the customer (Value Realization)
• Solve complex customer problems by partnering with Thrive resources to meet customer expectations
• Help customers optimize utilization of existing and available products and/or services
• Ensure best practice adoption across the customer environment
• Lead future lifetime value through higher product adoption, customer satisfaction, and overall health scores (including advocacy and reference-ability)
• Manage contract P&L to deliver to expectations and improve year over year
• Expand revenue in accounts through opportunity identification
• Prepare and drive successful contract renewals
• Manage customer onboarding activities
• Facilitate training and enablement
• Drive customer advocacy initiatives
• Manage and resolve escalations promptly

Requirements

• Understands Customer Business Problems
• Ideal candidate would have a strong mixture of ITIL and business acumen leaning on ITIL as the foundation

But the Requirements section originally had a bunch of bullet-like statements under "Requirements" heading: Actually the text after "Requirements" includes many bullet-like lines: "Understands Customer Business Problems Build strategic relationships with key client stakeholdersIdentify current pain points and desired outcomes affected by services under contractProvide measurable value to the customer (Value Realization) Drive Customer Success Outcomes Solve complex customer problems by partnering with Thrive resources to meet customer expectationsHelp customers optimize utilization of existing and available products and/or servicesEnsure best practice adoption across the customer environmentLead future lifetime value through higher product adoption, customer satisfaction, and overall health scores (including advocacy and reference-ability)Manage contract P&L to deliver to expectations and improve year over yearExpand revenue in accounts through opportunity identificationPrepare and drive successful contract renewalsIdeal candidate would have a strong mixture of ITIL and business acumen leaning on ITIL as the foundation Oversee Activities Manage customer onboarding activitiesFacilitate training and enablementDrive customer advocacy initiativesManage and resolve escalations promptly Tools ServiceNow PlatformCustomerGauge Key Performance Indicators (KPIs) NPS / CSATRetentionNRR / GRR (FY27)Engagement (account activity, executive/POC engagement)". This is messy; seems they mixed responsibilities and tools. Actually the original formatting lost line breaks. We need to parse intelligently. Let's re-examine the original text: "Requirements Understands Customer Business Problems Build strategic relationships with key client stakeholdersIdentify current pain points and desired outcomes affected by services under contractProvide measurable value to the customer (Value Realization) Drive Customer Success Outcomes Solve complex customer problems by partnering with Thrive resources to meet customer expectationsHelp customers optimize utilization of existing and available products and/or servicesEnsure best practice adoption across the customer environmentLead future lifetime value through higher product adoption, customer satisfaction, and overall health scores (including advocacy and reference-ability)Manage contract P&L to deliver to expectations and improve year over yearExpand revenue in accounts through opportunity identificationPrepare and drive successful contract renewalsIdeal candidate would have a strong mixture of ITIL and business acumen leaning on ITIL as the foundation Oversee Activities Manage customer onboarding activitiesFacilitate training and enablementDrive customer advocacy initiativesManage and resolve escalations promptly Tools ServiceNow PlatformCustomerGauge Key Performance Indicators (KPIs) NPS / CSATRetentionNRR / GRR (FY27)Engagement (account activity, executive/POC engagement) Qualifications Skills Customer relationship managementBusiness operationsChange management (end-to-end)Process improvementProject management (scoping, planning, milestone tracking, documentation)Risk management Attributes Customer-centric attitude and proactive approachTeam player: capable of working with and across functional teamsResults oriented: takes accountability as customer advocate and Thrive business ownerDigitally fluent: understands basic AI and workflow principlesActive listener: attentive to both customer and internal partnersLearning agility: willing to advance current knowledge level Experience 5+ years of digital experience as a CDM (Managed Services experience a plus)Strong general business acumen (financial/P&L acumen a plus)ITIL/ITSM, Lean Six Sigma, and other relevant industry certificationsCollege degree preferred in a related field or commensurate work experienceGeneral understanding of technology and managed services Desired Behaviors Teamwork: works well across customer and Thrive environmentsAdaptability: embraces constant changeHonest and high integrityStrong work ethic (dependable, confident)Willingness to learn and continuously improveWillingness to lean in (run to the fire)Ownership and accountabilityInitiative: proactive - acts without waiting to be told Added Skills That Will Help Agile methodologySix Sigma" It seems the posting is poorly formatted; we need to extract meaningful sections. We have headings: Requirements, Tools, Qualifications, Skills, Attributes, Experience, Desired Behaviors, Added Skills That Will Help. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Thus we can put: - About the role: company description + position overview. - Responsibilities: the "Oversee Activities" list plus maybe the earlier "Drive Customer Success Outcomes" etc. Actually those are responsibilities. - Requirements: maybe the "Understands Customer Business Problems" etc? But that seems more like responsibilities. However we can treat the bullet list under Requirements as requirements (maybe they are actually responsibilities). But we need to follow the posting: there is a "Requirements" heading then a block of text that seems to be responsibilities again. Then "Tools" heading then list. Then "Qualifications" heading then list of Skills, Attributes, Experience, Desired Behaviors, Added Skills. Thus we can create:

About the role

(company description + position overview)

Responsibilities

(list from "Oversee Activities" plus maybe the earlier "Drive Customer Success Outcomes" etc? Actually those earlier lines are under Requirements but they look like responsibilities. We'll include them under Responsibilities as well.)

Requirements

(maybe the "Ideal candidate would have a strong mixture of ITIL and business acumen leaning on ITIL as the foundation"? That's more like qualification. But we can put nothing? Better to put the "Ideal candidate would have a strong mixture..." as a requirement.) But we also have "Tools" which could be under Skills or Requirements? Not exactly. Could be under Skills? But we have Skills heading allowed. We could put Tools under Skills. Qualifications: we can combine Skills, Attributes, Experience, Desired Behaviors, Added Skills into Qualifications section. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Skills (maybe Tools). But we cannot have both Qualifications and Skills if they overlap; but we can have both if they have distinct content. However we have limited allowed headings; we can use Qualifications and Skills both. Let's extract content precisely. First, About Us paragraph: "Thrive is a rapidly growing technology solutions provider focusing upon Cloud, Cyber Security, Networking, Disaster Recovery and Managed Services. Our