Senior Mid-Market Implementation Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Actually we need to use headings for 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: About Us, equal opportunity, AI tools, etc. Also remove duplicated lines, navigation, legal, EEO, scam-warning. Also remove application instructions (none present). Must not create sections with filler like "commensurate with experience". Pay section: we have compensation details: "Target cash compensation ranges from $104,000 - $127,000, including a fixed annual salary and a performance-based bonus paid quarterly. This role also includes a stock option grant, subject to board approval. Actual compensation will be commensurate with the candidate's skill level, experience, and specific work location." The phrase "Actual compensation will be commensurate..." is filler? It says "commensurate with experience" which is placeholder-like. According to rule: 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. The posting does state compensation range and stock option grant, so we can include Pay section with that info, but we must avoid filler like "Actual compensation will be commensurate...". We can omit that sentence or rephrase? We must preserve ALL substantive information; do NOT invent or summarize away detail. The sentence "Actual compensation will be commensurate with the candidate's skill level, experience, and specific work location." is somewhat substantive but it's basically saying it's variable. It's somewhat filler but still info. However rule says never emit a heading followed by filler/placeholder text like "commensurate with experience". That phrase appears. So we should avoid including that sentence. We can include the range and stock option grant. That's substantive. So Pay section:

Pay

Target cash compensation ranges from $104,000 - $127,000, including a fixed annual salary and a performance-based bonus paid quarterly. This role also includes a stock option grant, subject to board approval.

Benefits: we have list of perks: Time Off (Unlimited PTO, Holidays + Canary Days, Birthday Holiday), Travel & Office Flexibility (Office Exchange travel stipend, Canary Hotel Experience credit, Preferred Hotels Discount), Growth & Community (Self Improvement Club monthly budget, Professional Development learning stipend, Referral Program cash bonus). We should format as

• ... maybe nested? Could just list each bullet. We'll keep as list items. Schedule: No explicit schedule info (like full-time, remote). Not present, so we should not create Schedule section. About The Role: we have description. Should be under

  About the role

  with paragraphs. Responsibilities: The bullet list under "What You’ll Do". We'll make

  Responsibilities

  with
  • each. Requirements: The bullet list under "What We’re Looking For". We'll make

    Requirements

    with
    • . Qualifications: Might be overlapping with Requirements. The posting includes "Bachelor's degree (BS/BA)" etc. That's qualifications. Could treat as Qualifications section. But we already have Requirements. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to split into Requirements and Qualifications and Skills maybe. The posting includes "Bachelor's degree (BS/BA)" under What We’re Looking For, plus experience, communication abilities, etc. Could separate: Requirements: maybe the experience and skills; Qualifications: education; Skills: maybe communication, tech proficiency, etc. But we must not create thin sections. We need to decide based on content. We have: Bachelor's degree (BS/BA) - qualification. 2-3 years of proven experience in account management or customer success, preferably within a B2B SaaS environment - requirement/experience. Excellent communication abilities and presentation skills, capable of building trust and rapport with diverse stakeholders - skill. Proven track record managing a portfolio of concurrent implementations and delivering to go-live on time - requirement/experience. Charisma + consultative mindset: sets success criteria up front, drives adoption, and spots expansion opportunities - skill/quality. Ability to manage multiple accounts simultaneously and prioritize tasks effectively - skill. Collaborative nature, adept at working with cross-functional teams including Product, Marketing, Sales, and Operations - skill. Proficiency with technology and adaptability to dynamic environments - skill. Hands-on experience scoping and managing third-party systems and coordinating technical teams and external vendors - requirement/experience. Highly organized and rigorous about time management and prioritization across competing deadlines - skill. Hospitality and/or travel tech experience a plus - qualification/plus. We could make Qualifications: Bachelor's degree (BS/BA); Hospitality and/or travel tech experience a plus. Requirements: 2-3 years experience, proven track record managing portfolio, hands-on experience scoping/managing third-party systems. Skills: communication abilities, charisma/consultative mindset, ability to manage multiple accounts, collaborative nature, proficiency with technology, highly organized, etc. But we must avoid filler. All these are substantive. We'll create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We must not include Schedule. Now we need to ensure we preserve all substantive information from About Us? Actually we removed About Us as boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not explicitly listed to remove, but it's likely considered boilerplate? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Us is not in that list, but earlier they said "Preserve ALL substantive information". About Us is substantive about company. However the earlier part: "You reformat a job posting into clean, well-structured semantic HTML." Usually we include About Us? The instruction didn't say to remove About Us. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not those. So we should keep About Us? But they also said "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They didn't list About Us as a heading to use. So we likely should not create a heading for About Us; maybe we can include it as a paragraph before the role? But they said "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." They didn't forbid other headings besides those listed, but they gave examples. Probably they expect only those headings. So we should not include About Us as a separate heading; maybe we can incorporate it into a brief intro paragraph before About the role? But they said preserve ALL substantive information. If we drop About Us, we lose substantive info. However maybe About Us is considered boilerplate? It's marketing fluff but still substantive about company. The instruction about removing boilerplate only mentions cookie/navigation/legal/EEO/equal-opportunity/scam-warning. So About Us is not boilerplate per that list. But they also said "Prefer a few substantive sections over many thin ones." Could we include About Us as a paragraph under a generic

      without heading? Possibly yes. The output is just HTML fragment; we can have a

      about the company then headings. Thus we will output:

      About Us paragraph (the content). Then

      About the role

      with paragraph. Then

      Responsibilities

      with list. Then

      Requirements

      with list. Then

      Qualifications

      with list. Then

      Skills

      with list. Then

      Benefits

      with list. Then

      Pay

      with paragraph. We must ensure we don't include any filler like "commensurate with experience". We omitted that sentence. Now let's extract About Us paragraph: The About Us block: "Think about your last hotel stay. Did you skip the front desk line with mobile check-in? Message the staff for extra pillows? Order a late-night snack with a tap on your phone? Then you’ve likely run into Canary in the wild. Canary Technologies is the leading agentic AI platform for hotel and guest management, powering the digital infrastructure for more than 20,000 hotels in 125+ countries. The world's most renowned hospitality brands, including Marriott International, Four Seasons and Wyndham Hotels & Resorts, partner with us to increase revenue, improve operations and elevate the guest experience. We’ve executed the largest deployment of autonomous AI systems in hospitality, building technology that fundamentally redefines how guests and hotels interact. It’s made us one of the top-funded hotel technology companies in the world, with nearly $200M raised to date. Canary has been recognized as a 2024 and 2025 Deloitte Technology Fast 500™ company, Inc. 5000 fastest-growing company, and swept the 2026 HotelTechAwards, including Best Place to Work, #1 Guest Experience Platform, and the Hotelier’s Choice Award. We’re scaling our team to bring innovation to life faster than ever. We're growing quickly, and we're looking for people who are passionate about their work, want to grow with us and are ready to take on more responsibility along the way. We value rigor and velocity in equal measure: high standards, fast pace, real ownership. If that's the environment you're looking for, this is the place for you. Come join us! Let’s shape the future of hospitality together." We'll keep that as a

      . Now About the role paragraph: The block after "About The Role": "The Senior Mid-Market Implementation Manager owns the onboarding and go-live of Canary's most complex, higher-value hotel and hotel-group clients. This is a portfolio position: you will run multiple mid-market deployments in parallel, each with several stakeholders, custom configurations, and integrations to property systems (PMS, payment, and other third-party platforms). You will set mutual success criteria up front, coordinate cross-functional and vendor teams, and keep timelines moving through complexity, escalations, and change while identifying and driving expansion of the Canary relationship. This is a high-visibility, customer-facing role for an experienced implementation professional who can operate independently, navigate ambiguity, and act as a trusted advisor to senior hotel operators." We'll put that as

      under About the role. Now Responsibilities: list items from "What You’ll Do". Let's extract each bullet: - Own end-to-end onboarding for a portfolio of mid-market and multi-property clients — from kickoff through go-live and initial adoption — running several deployments in parallel without letting timelines slip - Scope, configure, and deploy Canary's full product suite to each property's operational setup, including complex, non-standard configurations across hotel groups and portfolios - Lead integrations to customer systems (PMS, payment, and other third-party platforms): scope technical requirements, coordinate internal technical teams and outside vendors, and keep the project moving when integrations are delayed or complex - Establish mutual success criteria and a joint deployment plan with the customer up front, then drive product