Senior Channel Success Manager

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, etc. Must not include sections with placeholder text. We need to parse the posting. Content: - A Note from our Founders (intro) - maybe not a section heading? Could be part of About the company? Not required to include but we could include as a paragraph? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. Probably we should include sections that match those headings if content exists. We have: - About The Role (heading). That's a section heading. We'll use

About The Role

and then content. - What You’ll Do (Responsibilities). That's responsibilities. So

Responsibilities

with list. - Role Requirements (Requirements). So

Requirements

with list. - Bonus Points (maybe Skills or Qualifications). Could be considered "Qualifications" or "Skills". We'll treat as "Qualifications" maybe? Actually Bonus Points are extra desirable qualifications. Could be under "Qualifications". We'll include as

Qualifications

with list. - Interview Process (maybe not a standard heading; but we could include as a section? Not in list but we could still include? The instruction says use those headings for section headings; but we can include other headings if needed? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings but better to stick to those. Interview Process maybe not needed; but we could omit as it's not required? However we must preserve ALL substantive information. If we omit Interview Process, we lose info. But maybe we can incorporate into a section like "Process" but not standard. Could we include as a

Interview Process

? 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)." So we can use

for any section heading; the examples are just typical. So we can include Interview Process as a heading. - Inclusion at Litem: EEO boilerplate - we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove that paragraph. - Benefits: there are two sub-sections: Benefits For Bellevue-based And Remote Roles and Benefits For Bellevue-based Roles. We need to include Benefits section with details. Also Compensation Range: $128K - $156K (Pay). Also Schedule: Flexible Hybrid Schedule: in-office 4 days a week, remote 1 day a week. Thus we need sections: About The Role, Responsibilities, Requirements, Qualifications (Bonus Points), Benefits, Pay, Schedule. Possibly also Interview Process. We must not include placeholder text like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We need to preserve all substantive information. Let's extract content. **About The Role** paragraph: "As Senior Channel Success Manager at Deposely, you will be the primary bridge between our product and our most critical channel partners: Court Reporting Agencies (CRAs). Sitting within the Customer Success organization, you will own the end-to-end success of our strategic CRA relationships, ensuring partners are technically integrated and commercially equipped to sell Deposely to their law firm clients." That's the prose. **What You’ll Do** (Responsibilities) list: - Strategic Onboarding: Lead project management of complex product integrations with our Tier 3 and Tier 4 partners, ensuring a seamless technical launch. - Sales and Marketing Enablement: Act as a force multiplier by training CRA sales teams and equipping them with the marketing resources they need to sell Deposely into law firms. - Product Feedback Loop: Capture feedback from key members and clients of CRAs and route it to engineering to drive efficiency and scale in our onboarding methodology. - Strategic Growth: Monitor key metrics across channel-led sales and usage, forecast risk, and implement targeted interventions to protect channel performance. - Process Building: Use front-line feedback to strengthen Channel Success playbooks and tools built for scale. We need to output as

  • each. **Role Requirements** list: - Proven success scaling and driving efficiency in large enterprise accounts, ideally in legal tech, fintech, or workflow SaaS - Experience across the full customer lifecycle, from onboarding through advocacy, including partnering with leadership or founders on high-stakes expansions and renewals - Strong data-driven decision-making, including building business cases and ROI models, and managing client escalations - Working knowledge of how mid-market and enterprise organizations evaluate and adopt new technology - A collaborative builder's mindset, comfortable rolling up your sleeves in a small-team environment while scaling operations - Ability to juggle varied responsibilities and exercise judgment on the best next step without a playbook - Excellent communication, empathy, and relationship-building skills - Comfort with ambiguity, fast iteration, and startup pace **Bonus Points** (Qualifications) list: - You have worked at a high-growth SaaS company before. - You have prior experience in an early-stage startup. - Familiarity or interest in the legal tech space. **Interview Process** list: - 30m introduction call - 45m video Hiring Manager interview - 45m video peer interview - 1.5h final in person Interview We could format as list. **Benefits** we have two sub-sections. We need to capture all benefits. First: Benefits For Bellevue-based And Remote Roles: - Competitive Salary & Equity: Early-stage ownership with a standard 4-year vesting schedule and a 1-year cliff. - 100% Medical/Dental/Vision Coverage: We pay 100% of premiums for employees and 50% for dependents. - Unlimited PTO: 4-week recommended minimum (and we'll bug you if your "Out of Office" gathers dust). - 12 Paid Holidays: We observe all standard holidays to give the team time to recharge. - Parental Leave: We offer 16 weeks fully paid parental leave for birthing parents or 12 weeks for non-birthing parents. Second: Benefits For Bellevue-based Roles: - Flexible Hybrid Schedule: We’re in-office 4 days a week for seamless communication, and remote 1 day a week of your choosing for uninterrupted focus. - Bellevue HQ: A modern office space with premium snacks, drinks and coffee to keep the team fueled. - Commuter Benefits: Your choice of a company-paid parking spot in downtown Bellevue or a fully loaded ORCA pass. We could combine into a single Benefits section with subheadings? But instruction says use

    for section headings; we could have subheadings maybe

    but not required. Simpler: just list all benefits as

    • . Might lose distinction but still preserve info. Could also include two

      subsections: Benefits For Bellevue-based And Remote Roles and Benefits For Bellevue-based Roles. But the instruction only mentions using

      for section headings like Benefits; but we can still use

      for subheadings. Probably okay. We'll create

      Benefits

      then maybe two

      subheadings? Not required but we can use

      for each subsection. However that would duplicate heading "Benefits". Better to keep one Benefits heading and then list all benefits. We'll include all bullet points. **Pay**: Compensation Range: $128K - $156K. That's pay. **Schedule**: Flexible Hybrid Schedule: We’re in-office 4 days a week for seamless communication, and remote 1 day a week of your choosing for uninterrupted focus. We could also include Bellevue HQ and Commuter Benefits under Benefits, not Schedule. Thus schedule section: just that bullet. Now we need to output HTML fragment only, no /, no markdown fences. Let's construct. We'll start with

      About The Role

      ...

      Then

      Responsibilities

      ...
      Then

      Requirements

      ...
      Then

      Qualifications

      ...
      (for Bonus Points) Then

      Interview Process

      ...
      Then

      Benefits

      ...
      Then

      Pay

      Compensation Range: $128K - $156K

      Then

      Schedule

      Flexible Hybrid Schedule: We’re in-office 4 days a week for seamless communication, and remote 1 day a week of your choosing for uninterrupted focus.

      Check for any duplicate or boilerplate removed: We removed EEO paragraph, also removed "A Note from our Founders" maybe we should keep? It's substantive but not a standard heading. Could we include as a

      About Litem

      ? The instruction didn't forbid. It says use

      for section headings (e.g. About the role, Responsibilities...). It didn't say we cannot have other headings. Including a brief intro might be good to preserve all substantive information. The "A Note from our Founders" and "What We’re Building" and "Our Traction" and "Impact" are substantive. We should preserve them. So we need to include those as sections perhaps. We have to preserve ALL substantive information. So we need to include the founders note, what we're building, traction, impact. Those are not covered by the standard headings but we can add sections like

      About Litem

      or

      Company Overview

      . The instruction didn't restrict to only those headings; it gave examples. So we can add. Thus we need to include sections for: - A Note from our Founders - What We’re Building - Our Traction - Impact We'll treat each as

      section with paragraphs. Let's extract each. **A Note from our Founders** paragraph: "We started Litem because we saw a massive gap between the importance of legal work and the quality of the tools lawyers use to do it. We believe that the people protecting our legal systems deserve software that is as ambitious as they are. We launched Litem with three simple goals: Solve real problems. Learn new skills. Have fun doing it. Our philosophy on team-building is centered on passion and compassion. We look for people who are "all-in" on the mission and the craft, but we keep the human aspect front and center. You’ll find that we are high-energy and ambitious, but also grounded and understanding. We take the work seriously, but we don’t take ourselves too seriously. If you're excited about building the future of legal tech, we’d love to have you with us. Mitchell and Donnie" We'll keep as a paragraph. **What We’re Building**: "We’re an early-stage team at the intersection of technology and law. We’re driven by a simple reality: legal work is vital to protecting everyday people, yet the industry’s tech is under