Sales Director- NORAM
maybe under an "About the company"? Not required. The 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. 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. IMPORTANT: 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include. The posting includes:
- Intro paragraph about company culture and mission (At SiteMinder we believe...). This is substantive; we could put under an
About the company? Not listed but we can use About the role? Actually "About The Sales Director- NORAM Role..." is a heading. We could treat that as About the role. So we can have About the role
with the paragraph(s) describing the role.
- Then "What You Have..." which is qualifications/requirements. Could be Requirements or Qualifications. We'll use Requirements
with list.
- Then "What You'll Do..." which is responsibilities. Use Responsibilities
with list.
- Then "Our Perks & Benefits…" which is benefits. Use Benefits
with list.
- Also there is mention of "Hybrid working model (3/4 days per week) in our Dallas office", "Hybrid role, must be covered from Dallas, open to candidates willing to relocate (relocation support provided)". That's schedule/location info. Could be Schedule? The posting does not give explicit schedule like full-time, but mentions hybrid working model. Could be considered Schedule? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state hybrid working model, so we could include Schedule section. However they said prefer a few substantive sections over many thin ones. Could incorporate schedule info into Benefits or About the role? Might be better to include a Schedule section. But we need to see if they want separate Schedule heading. The examples given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have Schedule.
But we also have "Hybrid role, must be covered from Dallas, open to candidates willing to relocate (relocation support provided)" which is location/relocation. Could be part of Schedule or maybe a separate note. We'll include in Schedule.
Also there is mention of "Equity packages", "Mental health and well-being initiatives", "Generous parental (including secondary) leave policy", "Paid birthday, study and volunteering days off every year", "Employee Resource Groups (ERG)". Those are benefits.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove application instructions: "Does this job sound like you? If yes, we'd love for you to be part of our team! Please send a copy of your resume and our Talent Acquisition team will be in touch. When you apply, please tell us the pronouns you use and any adjustments you may need during the interview process. We encourage people from underrepresented groups to apply." That's application instructions; we must remove.
Also remove duplicated lines? Not seeing duplicates.
Now we need to preserve all substantive information. Let's extract content.
Intro paragraph: "At SiteMinder we believe the individual contributions of our employees are what drive our success. That’s why we hire and encourage diverse teams that include and respect a variety of voices, identities, backgrounds, experiences and perspectives. Our diverse and inclusive culture enables our employees to bring their unique selves to work and be proud of doing so. It’s in our differences that we will keep revolutionising the way for our customers. We are better together! What We Do… We’re people who love technology but know that hoteliers just want things to be simple. So since 2006 we’ve been constantly innovating our world-leading hotel commerce platform to help accommodation owners find and book more guests online - quickly and simply. We’ve helped everyone from boutique hotels to big chains, enabling travellers to book igloos, cabins, castles, holiday parks, campsites, pubs, resorts, Airbnbs, and everything in between. And today, we’re the world’s leading open hotel commerce platform, supporting 56,000 hotels in 150+ countries - with over 140 million reservations processed by SiteMinder’s technology every year."
We could keep that as a paragraph under About the role? Or maybe a separate About the company. But instructions only list certain headings; we could still use About the role for role description, but the intro is about company. Could we include it as a paragraph before any heading? The instruction: Output ONLY the HTML fragment — no /. It didn't forbid having a leading
before headings. It said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we must have headings for everything; we can have prose paragraphs not under a heading? Probably okay but better to wrap in a heading like About the role? However About the role heading should contain role-specific info, not company overview. But we could still include company overview under About the role as part of role description. Might be okay.
Alternatively we could add a heading "About the company" but not in the list; but they said use for section headings (e.g. About the role, Responsibilities...). The e.g. implies those are examples, not exclusive. So we could use About the company. Safer to stick to examples? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings; we can use others if needed but they gave examples. I'd stick to those to be safe.
Thus we can have:
About the role
containing both company overview and role description? Might be mixing.
Better: Have About the role
with the role description paragraph(s) from "About The Sales Director- NORAM Role..." and maybe also include the earlier company overview as a preceding
not under a heading. That is acceptable.
Let's extract role description: "About The Sales Director- NORAM Role... The Sales Director- NORAM will be responsible for developing and executing strategic go-to-market plans to drive revenue growth and market share. This leadership role requires a visionary strategist with a deep understanding of market dynamics, competitor landscape, and customer needs. The Regional Sales Director will collaborate with cross-functional teams, including sales, marketing, product, and revenue operations, to ensure alignment and successful execution of regional strategies."
We'll put that as prose under About the role.
Now Requirements: "What You Have... Experience in the hospitality tech sectorExtensive senior leadership experience in sales, ideally overseeing multiple geo-based segments within a high-growth SaaS sales environment.Proven ability to build, manage, and scale a high-performing sales team to achieve significant revenue growth.In-depth understanding of the markets, familiarity with local cultures, and business environments.Strong business acumen, including the ability to study market intelligence data and translate into actionable strategies and sales plans.Outstanding communication, negotiation, and interpersonal skills with the ability to influence and build relationships at all levels of the organisation.Ability to thrive in a fast-paced, dynamic environment with the flexibility to adapt quickly to changing priorities and market conditions."
We need to split into list items. The text is concatenated without spaces; we need to separate by sentences. Let's parse:
- Experience in the hospitality tech sector
- Extensive senior leadership experience in sales, ideally overseeing multiple geo-based segments within a high-growth SaaS sales environment.
- Proven ability to build, manage, and scale a high-performing sales team to achieve significant revenue growth.
- In-depth understanding of the markets, familiarity with local cultures, and business environments.
- Strong business acumen, including the ability to study market intelligence data and translate into actionable strategies and sales plans.
- Outstanding communication, negotiation, and interpersonal skills with the ability to influence and build relationships at all levels of the organisation.
- Ability to thrive in a fast-paced, dynamic environment with the flexibility to adapt quickly to changing priorities and market conditions.
We'll make
- for each.
Now Responsibilities: "What You'll Do... Strategic Leadership Develop and implement comprehensive go-to-market strategies tailored to the regional markets.Provide vision and direction to the go-to-market teams to achieve demanding revenue targets.Lead, motivate, and develop a high-performing go-to-market team, providing guidance, support, and coaching to drive individual and team success.Create and foster a positive and collaborative team environment that attracts, develops, and retains high-calibre talent.Work closely with other senior executives and cross-functional teams, including marketing, product, finance, and onboarding, to ensure alignment and drive business success. Revenue Growth Develop and spearhead the implementation of go-to-market strategies to drive revenue and customer growth across the region.Set and achieve revenue and market share targets for the region.Develop and execute plans to penetrate new markets, expand the customer base, and drive sales growth.Represent the company at industry events, conferences, and customer meetings to enhance brand visibility, network, and generate leads.Identify new business opportunities and market trends, staying ahead of industry developments and positioning the company for future growth.Develop and monitor key performance indicators (KPIs) to track sales performance, identify areas for improvement, and implement corrective actions as needed. Team Management Manage and mentor a high-performing team of sales, marketing, and operations professionals.Foster a collaborative and results-oriented culture.Oversee recruitment, training, and development of regional staff. Customer Relationships Build and maintain strong relationships with key clients, partners, and stakeholders.Ensure high levels of customer satisfaction and address any issues or concerns promptly. Operational Excellence Manage the regional sales budget and allocate resources effectively for maximum ROI.Drive sales process optimisation and continuous improvement initiatives to enhance efficiency and effectiveness across the sales organisation.Ensure seamless collaboration between sales and other departments to enhance the customer journey.Continually strive to improve the customer experience through improved processes, people development and technology"
We need to split into list items. There are sections: Strategic Leadership, Revenue Growth, Team Management, Customer Relationships, Operational Excellence. Each has multiple sentences. We could make each bullet a responsibility. Let's parse:
Strategic Leadership:
- Develop and implement comprehensive go-to-market strategies tailored to the regional markets.
- Provide vision and direction to the go-to-market teams to achieve demanding revenue targets.
- Lead, motivate, and develop a high-performing go-to-market team, providing guidance, support, and coaching to drive individual and team success.
- Create and foster a positive and collaborative team environment that attracts, develops, and retains high-calibre talent.
- Work closely with other senior executives and cross-functional teams, including marketing, product, finance, and onboarding
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. 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. IMPORTANT: 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - Intro paragraph about company culture and mission (At SiteMinder we believe...). This is substantive; we could put under an
About the company? Not listed but we can use About the role? Actually "About The Sales Director- NORAM Role..." is a heading. We could treat that as About the role. So we can have About the role
with the paragraph(s) describing the role.
- Then "What You Have..." which is qualifications/requirements. Could be Requirements or Qualifications. We'll use Requirements
with list.
- Then "What You'll Do..." which is responsibilities. Use Responsibilities
with list.
- Then "Our Perks & Benefits…" which is benefits. Use Benefits
with list.
- Also there is mention of "Hybrid working model (3/4 days per week) in our Dallas office", "Hybrid role, must be covered from Dallas, open to candidates willing to relocate (relocation support provided)". That's schedule/location info. Could be Schedule? The posting does not give explicit schedule like full-time, but mentions hybrid working model. Could be considered Schedule? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state hybrid working model, so we could include Schedule section. However they said prefer a few substantive sections over many thin ones. Could incorporate schedule info into Benefits or About the role? Might be better to include a Schedule section. But we need to see if they want separate Schedule heading. The examples given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have Schedule.
But we also have "Hybrid role, must be covered from Dallas, open to candidates willing to relocate (relocation support provided)" which is location/relocation. Could be part of Schedule or maybe a separate note. We'll include in Schedule.
Also there is mention of "Equity packages", "Mental health and well-being initiatives", "Generous parental (including secondary) leave policy", "Paid birthday, study and volunteering days off every year", "Employee Resource Groups (ERG)". Those are benefits.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove application instructions: "Does this job sound like you? If yes, we'd love for you to be part of our team! Please send a copy of your resume and our Talent Acquisition team will be in touch. When you apply, please tell us the pronouns you use and any adjustments you may need during the interview process. We encourage people from underrepresented groups to apply." That's application instructions; we must remove.
Also remove duplicated lines? Not seeing duplicates.
Now we need to preserve all substantive information. Let's extract content.
Intro paragraph: "At SiteMinder we believe the individual contributions of our employees are what drive our success. That’s why we hire and encourage diverse teams that include and respect a variety of voices, identities, backgrounds, experiences and perspectives. Our diverse and inclusive culture enables our employees to bring their unique selves to work and be proud of doing so. It’s in our differences that we will keep revolutionising the way for our customers. We are better together! What We Do… We’re people who love technology but know that hoteliers just want things to be simple. So since 2006 we’ve been constantly innovating our world-leading hotel commerce platform to help accommodation owners find and book more guests online - quickly and simply. We’ve helped everyone from boutique hotels to big chains, enabling travellers to book igloos, cabins, castles, holiday parks, campsites, pubs, resorts, Airbnbs, and everything in between. And today, we’re the world’s leading open hotel commerce platform, supporting 56,000 hotels in 150+ countries - with over 140 million reservations processed by SiteMinder’s technology every year."
We could keep that as a paragraph under About the role? Or maybe a separate About the company. But instructions only list certain headings; we could still use About the role for role description, but the intro is about company. Could we include it as a paragraph before any heading? The instruction: Output ONLY the HTML fragment — no /. It didn't forbid having a leading
before headings. It said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we must have headings for everything; we can have prose paragraphs not under a heading? Probably okay but better to wrap in a heading like About the role? However About the role heading should contain role-specific info, not company overview. But we could still include company overview under About the role as part of role description. Might be okay.
Alternatively we could add a heading "About the company" but not in the list; but they said use for section headings (e.g. About the role, Responsibilities...). The e.g. implies those are examples, not exclusive. So we could use About the company. Safer to stick to examples? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings; we can use others if needed but they gave examples. I'd stick to those to be safe.
Thus we can have:
About the role
containing both company overview and role description? Might be mixing.
Better: Have About the role
with the role description paragraph(s) from "About The Sales Director- NORAM Role..." and maybe also include the earlier company overview as a preceding
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings; we can use others if needed but they gave examples. I'd stick to those to be safe.
Thus we can have:
About the role
containing both company overview and role description? Might be mixing.
Better: Have About the role
with the role description paragraph(s) from "About The Sales Director- NORAM Role..." and maybe also include the earlier company overview as a preceding
not under a heading. That is acceptable. Let's extract role description: "About The Sales Director- NORAM Role... The Sales Director- NORAM will be responsible for developing and executing strategic go-to-market plans to drive revenue growth and market share. This leadership role requires a visionary strategist with a deep understanding of market dynamics, competitor landscape, and customer needs. The Regional Sales Director will collaborate with cross-functional teams, including sales, marketing, product, and revenue operations, to ensure alignment and successful execution of regional strategies." We'll put that as prose under About the role. Now Requirements: "What You Have... Experience in the hospitality tech sectorExtensive senior leadership experience in sales, ideally overseeing multiple geo-based segments within a high-growth SaaS sales environment.Proven ability to build, manage, and scale a high-performing sales team to achieve significant revenue growth.In-depth understanding of the markets, familiarity with local cultures, and business environments.Strong business acumen, including the ability to study market intelligence data and translate into actionable strategies and sales plans.Outstanding communication, negotiation, and interpersonal skills with the ability to influence and build relationships at all levels of the organisation.Ability to thrive in a fast-paced, dynamic environment with the flexibility to adapt quickly to changing priorities and market conditions." We need to split into list items. The text is concatenated without spaces; we need to separate by sentences. Let's parse: - Experience in the hospitality tech sector - Extensive senior leadership experience in sales, ideally overseeing multiple geo-based segments within a high-growth SaaS sales environment. - Proven ability to build, manage, and scale a high-performing sales team to achieve significant revenue growth. - In-depth understanding of the markets, familiarity with local cultures, and business environments. - Strong business acumen, including the ability to study market intelligence data and translate into actionable strategies and sales plans. - Outstanding communication, negotiation, and interpersonal skills with the ability to influence and build relationships at all levels of the organisation. - Ability to thrive in a fast-paced, dynamic environment with the flexibility to adapt quickly to changing priorities and market conditions. We'll make
- for each. Now Responsibilities: "What You'll Do... Strategic Leadership Develop and implement comprehensive go-to-market strategies tailored to the regional markets.Provide vision and direction to the go-to-market teams to achieve demanding revenue targets.Lead, motivate, and develop a high-performing go-to-market team, providing guidance, support, and coaching to drive individual and team success.Create and foster a positive and collaborative team environment that attracts, develops, and retains high-calibre talent.Work closely with other senior executives and cross-functional teams, including marketing, product, finance, and onboarding, to ensure alignment and drive business success. Revenue Growth Develop and spearhead the implementation of go-to-market strategies to drive revenue and customer growth across the region.Set and achieve revenue and market share targets for the region.Develop and execute plans to penetrate new markets, expand the customer base, and drive sales growth.Represent the company at industry events, conferences, and customer meetings to enhance brand visibility, network, and generate leads.Identify new business opportunities and market trends, staying ahead of industry developments and positioning the company for future growth.Develop and monitor key performance indicators (KPIs) to track sales performance, identify areas for improvement, and implement corrective actions as needed. Team Management Manage and mentor a high-performing team of sales, marketing, and operations professionals.Foster a collaborative and results-oriented culture.Oversee recruitment, training, and development of regional staff. Customer Relationships Build and maintain strong relationships with key clients, partners, and stakeholders.Ensure high levels of customer satisfaction and address any issues or concerns promptly. Operational Excellence Manage the regional sales budget and allocate resources effectively for maximum ROI.Drive sales process optimisation and continuous improvement initiatives to enhance efficiency and effectiveness across the sales organisation.Ensure seamless collaboration between sales and other departments to enhance the customer journey.Continually strive to improve the customer experience through improved processes, people development and technology" We need to split into list items. There are sections: Strategic Leadership, Revenue Growth, Team Management, Customer Relationships, Operational Excellence. Each has multiple sentences. We could make each bullet a responsibility. Let's parse: Strategic Leadership: - Develop and implement comprehensive go-to-market strategies tailored to the regional markets. - Provide vision and direction to the go-to-market teams to achieve demanding revenue targets. - Lead, motivate, and develop a high-performing go-to-market team, providing guidance, support, and coaching to drive individual and team success. - Create and foster a positive and collaborative team environment that attracts, develops, and retains high-calibre talent. - Work closely with other senior executives and cross-functional teams, including marketing, product, finance, and onboarding