Manager, Customer Experience Operations

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate. We need to parse description. First, there is an introductory paragraph about Vector Solutions. That's likely "About the role"? Actually "About the role" could be description of role and team. The posting includes description of team and role. So we can put that in

About the role

with paragraphs. Then "What You'll Do" is responsibilities. So

Responsibilities

with list items for each bullet. Then "Requirements" section: "What You'll Need:" includes bullet list. That's requirements. Then there is "What You Can Expect From Us": benefits. So

Benefits

with list. Then "What We Value": maybe could be Qualifications? Actually values are not qualifications. Could be "Qualifications" maybe not needed. There's no explicit qualifications separate from requirements. Could treat "What We Value" as maybe "Qualifications"? But better to follow instruction: include sections only when posting has real specific content. Values could be placed under "Qualifications"? But they are not qualifications. Could create a section "Culture" but not in allowed list. Allowed list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have About the role, Responsibilities, Requirements, Benefits. No Pay or Schedule specifics (except ability to work between 9pm-6am Philippine time). That's schedule info. So we can include Schedule section with that detail. Also maybe Pay not mentioned, so omit. Skills: maybe we can extract skills from requirements: hands-on experience administering a customer success platform, analytical skills, communication, etc. Could create Skills section. But we must not invent content; we can list skills that are explicitly mentioned. The posting mentions: "Hands-on experience administering a customer success platform: building workflows, configuring health scores, and designing journeys, plays, and segmentation." "Strong analytical skills, with the ability to explain how a number was derived and why a trend is real." "Clear communication with stakeholders at every level, including the ability to disagree productively." "Experience working directly with executive stakeholders, including presenting recommendations and defending tradeoffs to a C-level audience." "Working knowledge of Salesforce and how it supports CX workflows." "Demonstrated use of AI to streamline workflows, including building or operating agents in a production setting." Those could be skills. Qualifications: maybe education: Bachelor’s degree in Business, Operations, Marketing, or related field (Master’s degree a plus). Also experience: 5+ years in CX Ops, etc. Those could be qualifications. But we already have Requirements covering experience and education. To avoid duplication, we could treat Requirements as the list of needed experience/skills, and Qualifications as education. But instruction: prefer few substantive sections over many thin ones. Could combine education into Requirements. But we have separate sections allowed; we can include Qualifications for education. Let's decide: We'll have About the role, Responsibilities, Requirements (experience), Qualifications (education), Skills (specific abilities), Benefits, Schedule. Check for duplication: Requirements currently includes bullet list: 5+ years experience, hands-on experience administering a customer success platform, Bachelor’s degree, Experience supporting large-scale SaaS customer operations environments, Demonstrated use of AI, Experience in CX Ops/SaaS, Working knowledge of Salesforce, Strong analytical skills, Track record of taking cross-functional initiatives, Comfortable working without a defined spec, Clear communication, Experience working directly with executive stakeholders, Ability to work between 9:00 pm to 6:00 am Philippine Standard time and other hours as needed. That's a mix of experience, skills, schedule. We could split: Requirements: experience (years, SaaS, etc). Qualifications: education. Skills: specific abilities (administering CSP, analytical, communication, Salesforce, AI). Schedule: ability to work certain hours. But we must preserve all info; splitting is okay as long as we don't lose or duplicate. Let's extract: Experience bullets: - 5+ years in Customer Experience Operations, Customer Success Operations, or a related operations role with increasing scope. - Experience supporting large-scale SaaS customer operations environments. - Experience in customer experience operations or customer success operations in a SaaS environment. (somewhat duplicate) - Experience working directly with executive stakeholders, including presenting recommendations and defending tradeoffs to a C-level audience. Education: - Bachelor’s degree in Business, Operations, Marketing, or related field (Master’s degree a plus). Skills: - Hands-on experience administering a customer success platform: building workflows, configuring health scores, and designing journeys, plays, and segmentation. - Working knowledge of Salesforce and how it supports CX workflows. - Strong analytical skills, with the ability to explain how a number was derived and why a trend is real. - Demonstrated use of AI to streamline workflows, including building or operating agents in a production setting. - Clear communication with stakeholders at every level, including the ability to disagree productively. - Comfortable working without a defined spec: you shape the approach in unclear situations and build the alignment needed to move. - Track record of taking cross-functional initiatives from ambiguity to a measurable outcome, with hands on the build as well as the plan. Schedule: - Ability to work between 9:00 pm to 6:00 am Philippine Standard time and other hours as needed. Now Responsibilities bullets from "What You'll Do": - Process Architecture: Own the operational design of the customer lifecycle journey: the process and system build that makes onboarding, adoption, support, renewal, and expansion run, and keep it working as the business changes. - Build workflows that hold up at scale across CX functions, including onboarding playbooks, escalation paths, and proactive outreach frameworks. - Find the friction that costs the business time and remove it through automation or self-service. - AI and Automation: Use AI to compress manual work across CX operations and build and run agents that handle recurring workflows end to end. - Evaluate where AI belongs in a process and where it does not, and make that case to stakeholders with evidence. - CX Systems Ownership: Serve as the subject matter expert and hands-on administrator for our CX platform stack, including our customer success platform and Salesforce. - Configure health scores, churn risk signals, journeys, plays, and segmentation, and tune them as CX strategy changes. - Keep the customer data inside our CX platforms accurate enough that plays fire correctly and health scores can be trusted. - Own the CX requirements when these systems connect to the sales and marketing stack, partnering with Marketing Ops and Revenue Ops on delivery. - Insight and Measurement: Build the operational reporting and dashboards CX teams run on day to day: customer health, churn risk signals, adoption, and team activity. - Turn those into decisions the Customer Success, Services, and Renewals teams can act on. - Explain how a metric was derived and what makes a trend real. - Cross-Functional Leadership and Mentorship: Own cross-functional CX initiatives end to end: the process and system design, the agreement on who does what by when, and the follow-through to done. - Work directly with the Chief Customer Officer and CX leadership on recommendations, tradeoffs, and progress, in a form an executive can act on. - Mentor colleagues across Customer Operations and raise the operating bar of the team around you. - Support rollout of new CX processes with the documentation and system changes that make them stick. - Other duties as assigned. Now About the role: The initial paragraphs describing Vector Solutions and the Customer Operations Team and the role. Let's capture: "Vector Solutions is a leading, AI-enabled, performance platform powering safe, compliant, and efficient operations for the public, educational, and commercial sectors. We bring training, safety, and workforce operations together to boost readiness, reduce risk, and drive high-performance results for the everyday heroes who count on us. Our Customer Operations Team powers the growth of the post-acquisition buyer lifecycle, from implementation through to retention and expansion of our customer base. The team will leverage data, process and systems to drive the productivity and performance of our Customer Services, Renewal Management, Customer Success Management, and Implementation teams. We are seeking a Manager, Customer Experience Operations to be a senior individual contributor who owns how our customer operations run: the processes our CX teams follow, the systems that carry them, and the insight that tells us whether they are working. As a trusted partner to the Director of Data & CX Ops, this role drives process, technology, and AI initiatives that enable our Customer Success, Services, and Renewals teams to deliver measurable business outcomes. While not directly managing a team, this individual leads through cross-functional influence, subject-matter expertise, and mentorship. We will level the role at Manager or Senior Manager based on the depth of experience you bring." That's about the role. Now Benefits: "What You Can Expect From Us" list: - Friendly, open, and casual work environment - Hybrid work with 1 onsite day per week - Health HMO coverage up to P200K - Free dependent upon regularization (maybe "Free dependent upon regularization"? unclear; keep as is) - Group life insurance up to P1M coverage - PTO max of 20 days per year - Employee Resource Groups We should keep as list. Now we need to output HTML fragment with sections. Use

for each section heading. Use

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

  for prose. We must not include markdown fences. We'll produce something like:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • Bachelor’s degree in Business, Operations, Marketing, or related field (Master’s degree a plus).

  Skills

  • ...
  ...

  Benefits

  • ...
  ...

  Schedule

  Ability to work between 9:00 pm to 6:00 am Philippine Standard time and other hours as needed.

  We must ensure no empty sections. Now check for duplication: Ensure we didn't repeat any content inadvertently. Let's craft each list. About the role paragraph: combine the two paragraphs maybe into one

  . Responsibilities list: each bullet as

• . Might be long but okay. Requirements list: include experience bullets (excluding education, skills, schedule). Let's list: - 5+ years in Customer Experience Operations, Customer Success Operations, or a related operations role with increasing scope. - Experience supporting large-scale SaaS customer operations environments. - Experience in customer experience operations or customer success operations in a SaaS environment. - Experience working directly with executive stakeholders, including presenting recommendations and defending tradeoffs to a C-level audience. Potential duplicate of the second and third; but we keep both as they appear. Qualifications list: education bullet. Skills list: items: - Hands-on experience administering a customer success platform: building workflows, configuring health scores, and designing journeys, plays, and segmentation. - Working knowledge of Salesforce and how it supports CX workflows. - Strong analytical skills, with the ability to explain how a number was derived and why a trend is real. - Demonstrated use of AI to streamline workflows, including building or operating agents in a production setting. - Clear communication with stakeholders at every level, including the ability to disagree productively. - Comfortable working without a defined spec: you shape the approach in unclear situations and build the alignment needed to move. - Track record of taking cross-functional initiatives from ambiguity to a measurable outcome, with hands on the build as well as the plan. Benefits list: items as