Sales Manager

We need to produce HTML fragment with sections: About the role? Actually the posting includes sections: "What Makes Us Unique At Cloudbeds" (company description), "How You'll Make an Impact", "What You Bring to the Team", "What Sets You Up for Success", "Bonus Skills to Stand Out", "What to Expect - Your Journey with Us", "Company Awards to Check Out!", "Discover our Benefits". Also "Everyone is Welcome - A Culture of Inclusion" but that's EEO boilerplate, we should remove. Also "Learn more online at cloudbeds.com" maybe not needed? It's not a section heading; we can include as paragraph maybe but it's not required. We must not repeat job title as heading. The job title is "Sales Manager". We must not put Job ID etc. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can use other headings if they match content? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when appropriate. But we can also use other headings if they are present? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely they want us to map sections to those standard headings. However the posting has sections like "What Makes Us Unique At Cloudbeds" (company overview), "How You'll Make an Impact" (responsibilities), "What You Bring to the Team" (maybe duties?), "What Sets You Up for Success" (requirements/qualifications), "Bonus Skills to Stand Out" (skills), "What to Expect - Your Journey with Us" (maybe about team/culture), "Company Awards to Check Out!" (awards), "Discover our Benefits" (benefits). We need to decide which sections to include. We must include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to include sections with actual content. We should remove boilerplate: EEO, accommodation contact, staffing agency note, etc. Also remove "Learn more online at cloudbeds.com" maybe not needed but it's not boilerplate; it's a call to action. Might be considered application instruction? It's not exactly instruction to apply, but could be considered promotional. Safer to remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." "Learn more online at cloudbeds.com" is not application instruction, but could be considered navigation? It's a link to learn more; maybe we keep as paragraph? Not sure. Safer to keep as a paragraph under About the role? But it's not about role. Could be omitted. We need to preserve ALL substantive information; do not invent or summarize away detail. Thus we need to extract each bullet list etc. Let's parse content: **What Makes Us 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. **How You'll Make an Impact: As a Sales Manager , you'll play a pivotal role in expanding Cloudbeds' presence. You will be responsible for identifying and acquiring new business opportunities, building strong relationships with prospects, and showcasing how Cloudbeds’ industry-leading SaaS solutions are transforming the hospitality space. This is a hunting role focused on acquiring new clients.** That's responsibilities. **What You Bring to the Team:** (list) - Assess market trends and opportunities in your assigned territory to identify and engage new prospects. - Prepare targeted lead lists and engage in proactive outreach, including a high volume of cold-calling, to drive sales. - Identify and communicate potential partnership opportunities to our Partnerships team to strengthen Cloudbeds’ market position. - Deliver impactful product demonstrations, both virtually and in person, to highlight how Cloudbeds can solve key challenges for hospitality businesses. - Attend local events and visit properties to connect with potential customers (less than 10% travel required). - Serve as the face of Cloudbeds in your local market, representing the brand with confidence and expertise. **What Sets You Up for Success:** (list) - A self-motivated, results-oriented mindset with a passion for business development. - Experience in selling technology solutions into the hotel or hospitality industry - Excitement for new technology with a strong technical aptitude. - Proven expertise in outbound sales strategies, especially cold-calling and network building. - Excellent communication skills, with the ability to inspire and persuade potential clients. - Demonstrated sales and negotiation skills, with a history of exceeding targets. - Strong organizational and time-management abilities. - A willingness to challenge the status quo and think outside the box to drive success. **Bonus Skills to Stand Out:** (list) - Good knowledge of PMS technology - Operational experience in the hospitality or lodging industry - Multilingual capabilities **What to Expect - Your Journey with Us** (paragraph) - Behind Cloudbeds' revolutionary technology is a team of redefining what's possible in hospitality. - We're 650+ employees across 40+ countries, bringing together elite engineers, AI architects, world-class designers, and hospitality veterans to solve challenges others haven't dared to tackle. - Our diverse team speaks 30+ languages, but we all share one language: a passion for innovation and travel. - From pioneering breakthroughs in machine learning to revolutionizing how hotels operate, we're not just watching the future of hospitality unfold – we're coding it, designing it, writing it and shipping it. - If you're ready to work alongside some of the brightest minds in tech who are obsessed with using AI to transform a trillion-dollar industry, this is your chance to be part of something extraordinary. - Learn more online at cloudbeds.com **Company Awards to Check Out!** (list) - Best All-In-One Hotel Management System | HotelTechAwards (2025) - Overall 10 Best Places to Work | HotelTechAwards (2025) - Most Loved Workplace® Certified (2024) - Top 10 People’s Choice(2024) - Deloitte Technology Fast 500 (2024) **Discover our Benefits:** (list) - Remote First, Remote Always - PTO in accordance with local labor requirements - Monthly Wellness Fridays - enjoy an extra long weekend every month - Full 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. **Everyone is Welcome - A Culture of Inclusion** (EEO) -> remove. Now we need to map to headings. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. Let's map: - About the role: could be the company overview "What Makes Us Unique At Cloudbeds" plus maybe "What to Expect - Your Journey with Us"? But "About the role" usually describes the role itself, not company. However we have "How You'll Make an Impact" which is responsibilities. So we could use:

About the role

maybe combine company overview? But the instruction says use those headings as examples; we can use them if they fit. We have content for: - Responsibilities: "How You'll Make an Impact" - Requirements/Qualifications: "What Sets You Up for Success" (maybe qualifications) and "What You Bring to the Team" (maybe duties). Actually "What You Bring to the Team" looks like responsibilities/duties. Could be under Responsibilities as well. But we already have responsibilities section. Could combine. - Skills: "Bonus Skills to Stand Out" - Benefits: "Discover our Benefits" - Possibly Awards: not a standard heading; maybe we can omit or put under About the role? But awards are substantive; we could include as a separate section with heading

Awards

but not in the list. The instruction says use those headings (e.g.) but not limited to? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also use other headings if needed? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but the examples are those. To be safe, we should map content to those headings where possible, and maybe omit sections that don't fit (like Awards). However we must preserve ALL substantive information; we cannot omit awards if they are substantive. So we need to include them somewhere. Could we put awards under About the role? That would be mixing but still preserving. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine awards into About the role or maybe under a section like "Company Overview". But we don't have a heading for company overview; we could use About the role to include company overview and awards. However About the role is supposed to be about the role, but we can stretch? Might be better to create a section heading like "About Cloudbeds" but that's not in the list. The instruction says use those headings; maybe we should stick to them and put awards under Benefits? No. Alternatively, we could create a section heading

Awards

even though not in the list; the instruction didn't forbid other headings, just gave examples. It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That could be interpreted as "when you need a section heading, use

tag". The examples are just typical headings you might use. So we can use any heading we want, as long as it's

. So we can use headings like "What Makes Us Unique At Cloudbeds", "How You'll Make an Impact", etc. But they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those specific headings if they exist. But we can also use others if needed. I'd lean to using the provided headings where appropriate, and for other sections we can still use

with appropriate titles. Thus we will produce:

About Cloudbeds

(or About the role?). Let's use "About Cloudbeds" as heading for company overview and awards. But we need to avoid repeating job title as heading. That's fine. We'll produce sections: - About Cloudbeds (company overview + awards) - Responsibilities (combining How You'll Make an Impact and What You Bring to the Team) - Requirements / Qualifications (What