Implementation Manager

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. We need to parse the posting. Key sections: - About the role: description of role, leading implementations, etc. Could be "About the role" or maybe "Overview". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections accordingly. We need to extract content for each. Let's parse the posting: First paragraph: "Counterpart: Value-based care, at the point of care. At Counterpart Health, we are transforming healthcare and improving patient care with our innovative primary care tool, Counterpart Assistant. By supporting Primary Care Physicians (PCPs), we are able to deliver improved outcomes to our patients at a lower cost through early diagnosis and longitudinal care management of chronic conditions. We are hiring an Implementation Manager on the Counterpart Assistant team. In this role, you will lead the customer-facing work of bringing new provider practices and TINs from late-stage prospects through successful launch on Counterpart Assistant. You will partner closely with account management to hand off new customers, own the customer relationship through implementation, and drive each launch to completion on time and at quality. You will independently lead multiple concurrent implementations and the cross-functional work that makes each launch happen. Partnering with account management, support, product, and engineering internally and with providers, office managers, and clinical leads on the customer side: you will drive accountability across every stakeholder and deliver results through influence. Beyond running individual launches, you will help shape the implementation playbook itself — identifying what slows launches down, proposing changes, and driving improvements that reduce time-to-launch and lift customer satisfaction." That's about the role. Then "Strong project management fundamentals, clear customer communication, working knowledge of clinical data, and technical fluency will let you keep complex, multi-stakeholder launches on track." Then "As An Implementation Manager, You Will" bullet list (actually sentences). Let's extract responsibilities: - Own the customer relationship through implementation: you are the primary point of contact for the customer's technical implementation from project kickoff to post go live steady state. - Lead end-to-end project plans for multiple concurrent, multi-step implementations, keeping internal and customer teams aligned on scope, timeline, and status. - Partner cross-functionally with account management, support, product, and engineering to unblock issues, coordinate handoffs, and keep implementations moving on schedule. - Own the outcomes of each implementation: surface risks early, drive resolution across teams, and hold each launch accountable to its target date and quality bar. - Apply technical judgment to monitor and address potential integration issues that arise during implementations, working alongside product and engineering to ensure a successful integration and product launch. - Drive continuous improvement of the implementation process: define and refine the playbook, tooling, and templates that reduce time-to-launch and raise the quality bar for every customer experience. - Represent the customer's voice internally — capture feedback and pain points from implementations and channel them to product, engineering, and support to improve future launches. Then "Success In This Role Looks Like" with bullet points (over first 90 days, first 6 months, over time). That could be part of responsibilities or qualifications? Might be "Expectations". Could be placed under "Responsibilities" or maybe "Qualifications". But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (first part). Responsibilities: we have the bullet list under "As An Implementation Manager, You Will". Also the success metrics could be part of responsibilities or maybe "Requirements". But we can treat them as part of Responsibilities (what success looks like). Or we could create a separate section "Expectations" but not allowed; we must stick to given headings. So we can include success metrics under Responsibilities as well. Then "You Should Get In Touch If You" list: that's qualifications/requirements. Let's extract: - 5-8 years of experience leading technical product implementations in a customer-facing role, with a strong track record of on-time, high-quality launches — and of running multiple implementations in parallel. - 2+ years of experience in healthcare technology implementations working with provider practices, ideally including EHR standard integrations. - Exceptional customer-facing skills — you build trust quickly with providers, office managers, and clinical leads, communicate clearly under pressure, and manage escalations calmly and directly. - Expert in project management: you set the plan, track it, and drive accountability across internal and customer teams that don't report to you. - Strong technical judgment and are comfortable diagnosing potential integration issues and scope creep of the overall project. - Strong communicator, clearly documenting project status and potential risks internally and externally. - Motivated by process improvement: you notice friction in the way work gets done, propose better approaches, and drive them to adoption without needing a mandate. - Lead through influence, not authority: you know how to align stakeholders, resolve conflict, and hold the room accountable to outcomes. These are qualifications/requirements/skills. We can split: Requirements (years of experience), Qualifications (maybe similar), Skills (customer-facing, project management, technical judgment, communication, process improvement, influence). But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section maybe "Requirements". Or we could have "Requirements" for experience, "Skills" for abilities. Let's decide. We have Benefits section: detailed benefits overview. Must include only if posting actually states them. Yes, there is a Benefits Overview with subpoints. So we will create a Benefits section with

• items. Pay: The posting includes "A reasonable estimate of the base salary range for this role is: $96,200—$125,000 USD". That's pay info. So we need a Pay section with that info. Schedule: Not mentioned. No schedule info (remote-first culture mentioned but not schedule). So we should not create Schedule section. We also have "About Counterpart Health" description. That could be part of About the role or maybe a separate "About the company". But headings list only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could incorporate company description into About the role or maybe not needed. The About the role section could include both role and company context. We'll include company description in About the role. Now we need to strip boilerplate: EEO, equal-opportunity, scam-warning, Diversity & Inclusion, San Francisco Fair Chance Ordinance, E-Verify, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove "Final pay is based on several factors..." maybe part of Pay but we already have salary range; we can keep that as part of Pay? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The final pay sentence is somewhat generic but still substantive? It says "Final pay is based on several factors including but not limited to internal equity, market data, and the applicant’s education, work experience, certifications, etc." That's generic but still info about pay determination. Could include in Pay section. However we must avoid filler like "commensurate with experience". This sentence is somewhat generic but not filler like "varies". It's still substantive. We'll include. Also remove "And much more!" maybe keep as part of benefits? It's vague; better to omit as it's filler. We'll keep only concrete benefits listed. Now produce HTML. Structure:

  About the role

  ... (company description + role overview)

  Responsibilities

  • ... each responsibility
  Maybe also include success metrics as part of responsibilities? Could add as li.

  Requirements

  • ... experience requirements

  Skills

  • ... skills

  Benefits

  • ... benefits

  Pay

  ... salary range and pay determination

  We must not include Schedule. Now craft content. About the role paragraph: combine company description and role overview. Company description: "Counterpart Health is transforming healthcare and improving patient care with its innovative primary care tool, Counterpart Assistant. By supporting Primary Care Physicians (PCPs), the company delivers improved outcomes at lower cost through early diagnosis and longitudinal care management of chronic conditions. Counterpart Health is a subsidiary of Clover Health, founded in 2018 with the vision of building a clinically intuitive, AI‑enabled solution that fits within physicians’ workflows." Role overview: "We are hiring an Implementation Manager on the Counterpart Assistant team. In this role, you will lead the customer‑facing work of bringing new provider practices and TINs from late‑stage prospects through successful launch on Counterpart Assistant. You will partner closely with account management to hand off new customers, own the customer relationship through implementation, and drive each launch to completion on time and at quality. You will independently lead multiple concurrent implementations and the cross‑functional work that makes each launch happen. Partnering with account management, support, product, and engineering internally and with providers, office managers, and clinical leads on the customer side, you will drive accountability across every stakeholder and deliver results through influence. Beyond running individual launches, you will help shape the implementation playbook itself — identifying what slows launches down, proposing changes, and driving improvements that reduce time‑to‑launch and lift customer satisfaction." Add also "Strong project management fundamentals, clear customer communication, working knowledge of clinical data, and technical fluency will let you keep complex, multi‑stakeholder launches on track." Now responsibilities list: - Own the customer relationship through implementation: you are the primary point of contact for the customer's technical implementation from project kickoff to post‑go‑live steady state. - Lead end‑to‑end project plans for multiple concurrent, multi‑step implementations, keeping internal and customer teams aligned on scope, timeline, and status. - Partner cross‑functionally with account management, support, product, and engineering to unblock issues, coordinate handoffs, and keep implementations moving on schedule. - Own the outcomes of each implementation: surface risks early, drive resolution across teams, and hold each launch accountable to its target date and quality bar. - Apply technical judgment to monitor and address potential integration issues that arise during implementations, working alongside product and engineering to ensure a successful integration and product launch. - Drive continuous improvement of the implementation process: define and refine the playbook, tooling, and templates that reduce time‑to‑launch and raise the quality bar for every customer experience. - Represent the customer's voice internally — capture feedback and pain points from implementations and channel them to product, engineering, and support to improve future launches. - Over the first 90 days, you will hit the ground running: shadowing active implementations, learning the moving parts of the process (standard EHR integrations, internal system configurations and project plans), and taking ownership of your first launch. - Within the first 6 months, you will be the customer‑facing lead on multiple concurrent implementations, delivering launches on time and with a high customer satisfaction bar; customers will describe you as trusted, responsive, and a reason they feel confident in Counterpart. - Over time, your performance will be measured by the consistency, speed, and on‑target delivery of customer implementations, by the strength of the relationships you build with customer stakeholders throughout the process, and by the cumulative improvements you drive into the implementation playbook itself. Now requirements list (experience): - 5‑8 years of experience leading technical product implementations in a customer‑facing role, with a strong track record of on‑time, high‑quality launches and of running multiple implementations in parallel. - 2+ years of experience in healthcare technology implementations working with provider practices, ideally including EHR standard integrations. Now