Advanced Support Payments

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. We must not repeat job title. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive information. We need to parse the posting and extract sections. Let's read the posting: "What Makes Cloudbeds Unique At Cloudbeds, we're not just building software, we’re transforming hospitality. Our intelligently designed platform powers properties across 150 countries, processing billions in bookings annually. From independent properties to hotel groups, we help hoteliers transform operations and uplevel their commercial strategy through a unified platform that integrates with hundreds of partners. And we do it with a completely remote team. Imagine working alongside global innovators to build AI-powered solutions that solve hoteliers' biggest challenges. Since our founding in 2012, we've become the World's Best Hotel PMS Solutions Provider and landed on Deloitte's Technology Fast 500 again in 2024, but we're just getting started." That's about the company, could be "About the role"? Actually it's about the company. Could be "About Cloudbeds" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for description of role? But the posting includes "How You'll Make an Impact:" which is responsibilities. Then "Our Advanced Support Team:" maybe more responsibilities. Then "What You Bring to the Team:" which is responsibilities/requirements. Then "What Sets You Up for Success:" which is qualifications/requirements. Then "Bonus Skills to Stand Out (Optional):" which is skills. Then "What to Expect - Your Journey with Us" maybe about company culture. Then "Discover our Benefits:" which is benefits. Then "Everyone is Welcome - A Culture of Inclusion" is EEO boilerplate; we should remove that. Also "Company Awards:" maybe not needed. Also "Learn more online at cloudbeds.com" maybe not needed. We need to include only sections with real specific content. Let's extract: - About the role: maybe we can use the introductory paragraph about Cloudbeds? But that's about company not role. However we could still put under About the role a summary of role? The posting doesn't have a dedicated "About the role" heading; but we can create one using the initial description? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings if appropriate. We need to include a section only when posting has real specific content for it. So we need to decide which sections have content. We have content for Responsibilities: "How You'll Make an Impact:" bullet points (serve as advanced point of contact, proactively support, investigate and resolve, act as product advocate, educate customers, track and report). Also "Our Advanced Support Team:" maybe more responsibilities. We have content for Requirements/Qualifications: "What You Bring to the Team:" (list of responsibilities again) but also "What Sets You Up for Success:" (hospitality operations experience, few years payments/fintech, comfortable with numbers, strong problem-solving, excellent communication). That's qualifications. We have Bonus Skills: "Knowledge of PCI compliance and chargeback rules, Fluency in Spanish or Portuguese" -> Skills. We have Benefits: "Discover our Benefits: Remote First, Remote Always PTO in accordance with local labor requirements Monthly Wellness Fridays - enjoy an extra-long weekend every month Fully Paid Parental Leave Home office stipend based on country of residency Professional development courses in Cloudbeds University Access to professional development, including manager training, upskilling and knowledge transfer" We have Pay: not mentioned. No salary info. So we should NOT include Pay section. Schedule: not mentioned. So no Schedule. We also might have "About the role": maybe we can include a short paragraph describing the role from the intro? The intro is more about company. But we could treat "What Makes Cloudbeds Unique" as about the company, not role. However we could still include an "About the role" section using the description under "How You'll Make an Impact:"? That's responsibilities. Better to not create About the role if no specific content. But we need at least some sections. The instruction: "Prefer a few substantive sections over many thin ones." So we can include Responsibilities, Qualifications, Skills, Benefits. Possibly also "About the role" if we can derive a brief description: "As an Advanced Support Coach for Payments, you'll be the go-to expert for CB Pay issues: chargebacks, payouts, disputes, and reconciliation..." That is actually from the responsibilities section. But we could put that as role summary under About the role. However the instruction says: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid using About the role heading with a summary. So we could include About the role with a short paragraph summarizing the role: maybe combine the first two paragraphs after "How You'll Make an Impact:"? Actually the role description: "As an Advanced Support Coach for Payments, you'll be the go-to expert for CB Pay issues: chargebacks, payouts, disputes, and reconciliation, the kind of cases where real money, and real trust, are on the line. You won't just be reactive: you'll also help hoteliers get set up for success with payments from day one through proactive onboarding and enablement. You'll be a product advocate too, feeding what you learn from real payment issues back to our product team so the next customer doesn't hit the same wall. This role sits at the intersection of hospitality, fintech, and genuine customer care, and you'll need to be comfortable working through incomplete information to get to the right answer." That is a good summary for About the role. Thus we can have:

About the role

As an Advanced Support Coach for Payments, you'll be the go-to expert for CB Pay issues: chargebacks, payouts, disputes, and reconciliation, the kind of cases where real money, and real trust, are on the line. You won't just be reactive: you'll also help hoteliers get set up for success with payments from day one through proactive onboarding and enablement. You'll be a product advocate too, feeding what you learn from real payment issues back to our product team so the next customer doesn't hit the same wall. This role sits at the intersection of hospitality, fintech, and genuine customer care, and you'll need to be comfortable working through incomplete information to get to the right answer.

Then Responsibilities: we can list bullet points from "What You Bring to the Team:" and maybe also from "How You'll Make an Impact:" but avoid duplication. Let's extract unique responsibilities: From "How You'll Make an Impact:" we already used some in About the role; but we can still list responsibilities as bullet points: - Serve as the advanced point of contact for CB Pay issues, including chargebacks, payouts, disputes, and reconciliation - Proactively support hoteliers through payments onboarding and enablement, not just reactive troubleshooting - Investigate and resolve complex payment issues, working through incomplete or unclear information to get to the right answer - Act as a product advocate, feeding what you learn from real payment issues back to Product and Engineering - Educate customers on payments best practices to reduce future disputes and chargebacks - Track and report on case outcomes and payments-related trends Also maybe "Our Advanced Support Team:" doesn't add new responsibilities. Thus Responsibilities section with

• . Qualifications: from "What Sets You Up for Success:": - Hospitality operations experience, ideally with a track record of growth in the role - A few years of experience in payments or fintech - Comfortable working with numbers and reporting - Strong problem-solving skills, able to dig deep into complex, technical payment issues - Excellent written and verbal communication skills We could also include "What You Bring to the Team:" but that overlaps with responsibilities; but we can treat as qualifications? However it's more about what you bring (responsibilities). We'll keep qualifications as above. Skills: Bonus Skills: - Knowledge of PCI compliance and chargeback rules - Fluency in Spanish or Portuguese We could also include "Strong problem-solving skills" etc but those are qualifications. Benefits: from "Discover our Benefits:": - Remote First, Remote Always - PTO in accordance with local labor requirements - Monthly Wellness Fridays - enjoy an extra-long weekend every month - Fully Paid Parental Leave - Home office stipend based on country of residency - Professional development courses in Cloudbeds University - Access to professional development, including manager training, upskilling and knowledge transfer We should not include EEO etc. Now we need to output only HTML fragment, no or , no markdown fences. Thus:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Qualifications

  ...

  Skills

  ...

  Benefits

  ...
  We should not include Pay or Schedule. Check for any repeated content: Ensure we didn't include boilerplate. Check that we preserved all substantive information: Did we miss any? Let's review original posting for any other substantive info not covered: - "What Makes Cloudbeds Unique At Cloudbeds, we're not just building software, we’re transforming hospitality. Our intelligently designed platform powers properties across 150 countries, processing billions in bookings annually. From independent properties to hotel groups, we help hoteliers transform operations and uplevel their commercial strategy through a unified platform that integrates with hundreds of partners. And we do it with a completely remote team. Imagine working alongside global innovators to build AI-powered solutions that solve hoteliers' biggest challenges. Since our founding in 2012, we've become the World's Best Hotel PMS Solutions Provider and landed on Deloitte's Technology Fast 500 again in 2024, but we're just getting started." This is company info; not required to include but could be part of About the role? Might be considered "About the role" but it's about company. However we already have About the role summary; we could add a sentence about company remote nature etc. But the instruction: "Preserve ALL substantive information". Does that mean we must include all substantive info from posting, not just role-specific? It says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include company description as well. Where to put? Could be under About the role? Or maybe we could add another section like "About Cloudbeds" but not allowed headings. However we could incorporate into About the role as a brief intro: "At Cloudbeds, we're not just building software, we’re transforming hospitality..." That is substantive. So we should include that in About the role paragraph. Thus About the role paragraph should combine company description and role summary. Let's craft:

  At Cloudbeds, we're not just building software, we’re transforming hospitality. Our intelligently designed platform powers properties across 150 countries, processing billions in bookings annually. From independent properties to hotel groups, we help hoteliers transform operations and uplevel their commercial strategy through a unified platform that integrates with hundreds of partners. And we do it with a completely remote team. Imagine working alongside global innovators to build AI-powered solutions that solve hoteliers' biggest challenges. Since our founding in 2012, we've become the World's Best Hotel PMS Solutions Provider and landed on Deloitte's Technology Fast 500 again in 2024, but we're just getting started. As an Advanced Support Coach for Payments