Sr. Project Manager, Implementation

We need to output HTML fragment with sections for headings present in posting: About the role, About you, What success looks like, maybe Benefits? There's mention of compensation but not specific numbers. The instruction: include a section ONLY when 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. There's mention of compensation: "Our compensation is grounded in industry data and designed to be competitive, transparent, and performance-driven." That's vague, not specific numbers. So we should not create Pay section. Benefits? Not listed. Schedule? Not listed. So we only include sections that have substantive content: About the role, About you, What success looks like. Possibly also a short paragraph for metadata like Job ID? Not present. There's a line about recruiting process etc. That's boilerplate? It's about hiring process, maybe we should remove as boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The recruiting process description maybe not boilerplate but could be considered part of posting. However it's not a section heading. We could keep as a paragraph under maybe "About the role"? But it's after the role description. It's about hiring process, not role. Might be considered boilerplate? It's not EEO etc. It's about hiring timeline. Could keep as a paragraph maybe under a generic "About the hiring process"? But we shouldn't create sections unless there's real content. Could just include as a

after the sections. The instruction: Output ONLY the HTML fragment. So we can have multiple sections:

About the role

then content (maybe

paragraphs and

• for lists). Need to parse the role description into prose and lists. Let's extract About the role content: "The Sr. Project Manager, Implementation (SPM) owns our largest and most complex customer implementations. This role establishes the customer-facing implementation plan and sets clear expectations around scope, timelines, milestones, dependencies, and customer responsibilities. Internally, the role coordinates and project manages across teams of subject matter experts, serving as both translator, specification creator, and activities manager to ensure work is completed accurately and on time against commitments. As the central point of contact for the client and accountable for delivery, the Senior PM oversees complex implementations, sets the pace and sequencing of implementation, proactively identifies and mitigates risks, and adjusts plans as needed to deliver a successful customer launch. They manage multiple internal and external stakeholders to get projects live on time and within budget. They live PetDesk's value of customer excellence daily, keeping the customer at the center of every decision, even amid complexity. Apply if you're excited to:" Then a list of bullet points starting with "Lead end-to-end execution..." etc. Those are bullet items. We need to convert bullet list to
  • . The bullet points are sentences starting with verbs. We'll list each. Let's capture them: - Lead end-to-end execution of large, multi-product implementations, customers with more than three solutions purchased at once), and implementations with particularly complex or challenging onboarding projects - Lead customer project meetings and provide clear, confident communication around progress, decisions, risks, upcoming milestones, and customer responsibilities - Own escalation handling for active implementations (e.g., slipping milestones, stakeholder misalignment, unresolved blockers) to prevent churn that originates during implementation, ensuring issues are triaged, routed, customer is connected with, responses are tracked and resolved against defined SLA response and resolution targets - Translate customer priorities and clinic workflows into clear implementation requirements and ensure those requirements are understood by the teams responsible for delivery - Partner closely with dedicated Build and Customer Enablement teams to facilitate the appropriate configuration of PetDesk solutions and ensure customers receive the training and support needed to successfully launch - Influence and coordinate across AE, Build, Customer Enablement, Strategic Account Management, Customer Success, Support, and executive stakeholders (internally and with the client) to ensure work is completed by agreed-upon milestones - Use tools consistently to maintain accurate project information and proactively communicate status to internal and external stakeholders - Continuously identify opportunities to improve implementation processes, leveraging AI and other tools to increase efficiency, consistency, and visibility Note there is a stray parenthesis after "once)" maybe a typo but we keep as is. Now About you section: starts with "About you:" then list of requirements. We need to parse into prose and list. Content after "About you:": "4+ years of experience managing complex, multi-stakeholder, multi-product implementations or similar customer-facing projects Hands-on experience using Klient PSA, Wrike, or another complex project management platform for daily activity management, time tracking and internal visibility Demonstrated track record of delivering large-scale, multi-product implementations and go-lives on schedule and in less than 60 days Strong cross-functional project leadership skills, with the ability to influence and drive accountability across teams without direct authority Excellent organizational and prioritization skills, with the ability to actively manage multiple (typically 15-25) complex projects simultaneously and daily Strong written and verbal communication skills, including the ability to set clear expectations and lead effective virtual meetings with customers and internal stakeholders, always creating clear next steps with scheduled date/time Ability to quickly discuss and understand how practice management software solutions and incumbent provider approach and customer preferences would influence workflows, technical dependencies to create the desired experiences in our software Ability to translate customer preference and workflows into build specs for internal teams to create on time, within scope and to customer specification Demonstrated experience using AI to build, streamline, or optimize processes Strong customer orientation and the ability to balance customer priorities with internal business and operational requirements Dedicated, quiet workspace and ready to be "camera-on" during calls with strong internet stability Experience working in veterinary or healthcare SaaS implementations preferred Working knowledge of VoIP/telephony technology and network requirements a plus" These are bullet points; we can make
    • . Now What success looks like section: starts with "What success looks like:" then a list of bullet points (some long sentences). We'll parse. Content: "Customers and internal teams share a clear understanding of scope, timelines, milestones, responsibilities, and requirements throughout implementation, and internal teams consistently deliver against those commitments Large, multi-product implementations launch on the agreed timeline A portfolio of 3+ concurrent projects is actively and visibly managed, with clear ownership, status, risks, dependencies, and next steps documented and up to date Partnerships with Build and Customer Enablement Subject-Matter Experts are proactive, and choreographed with the right configuration and training activities completed at the right points in the customer journey Risks or delays are identified early, communicated transparently, and actively managed rather than becoming surprises for the customer, giving customers and internal stakeholders high confidence that the Senior Project Manager understands the plan, is driving execution, and will keep the project moving forward Customers and internal stakeholders have high confidence that the Senior Project Manager understands the plan, is driving execution, and will keep the project moving forward Project status, risks, decisions, dependencies, and milestones are documented and up to date across the entire project portfolio The PM actively brings AI-driven approaches and process improvements into their work and shares them with the team, reflecting a culture of curiosity and continuous learning Surfaces process or workflow breakdowns proactively with a recommended fix, rather than working around them or waiting to be asked Projects move efficiently and with a unified, coordinated experience from AE handoff through launch and customer enablement, targeting completion within 60 days whenever possible Meets or exceeds the team's target for customer satisfaction (CSAT) at key touchpoints across the journey No implementation-stage churn (churn within first 100 days post-signature): at-risk signals (slipping milestones, stakeholder misalignment, unresolved blockers) are caught and addressed before launch across the portfolio" We'll make
      • . Now after that there is a paragraph about PetDesk combines..., recruiting process, etc. That's likely boilerplate or not needed. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The recruiting process description maybe not boilerplate but could be considered part of posting. However it's not under a heading; we could keep as a

        after the sections. But it's somewhat generic. Might be considered boilerplate? It's about hiring process, not role. The instruction says remove application instructions. This is not application instructions but hiring process. Might be okay to keep. However to be safe, we could omit it because it's not directly about role, and the instruction says remove duplicated lines and application instructions. This is not application instructions but could be considered generic company description. I'd keep it as a

        maybe under a heading? There's no heading. Could just include as a

        after the sections. But we must not invent sections. So we can just output the three sections with their content, and then a final

        for the remaining descriptive paragraph(s) if we want to keep them. However the instruction says "Preserve ALL substantive information". So we should keep that info. It's substantive about company and hiring process. So we should include it as a

        after the sections. Thus final HTML:

        About the role

        The Sr. Project Manager, Implementation (SPM) owns our largest and most complex customer implementations. This role establishes the customer-facing implementation plan and sets clear expectations around scope, timelines, milestones, dependencies, and customer responsibilities. Internally, the role coordinates and project manages across teams of subject matter experts, serving as both translator, specification creator, and activities manager to ensure work is completed accurately and on time against commitments. As the central point of contact for the client and accountable for delivery, the Senior PM oversees complex implementations, sets the pace and sequencing of implementation, proactively identifies and mitigates risks, and adjusts plans as needed to deliver a successful customer launch. They manage multiple internal and external stakeholders to get projects live on time and within budget. They live PetDesk's value of customer excellence daily, keeping the customer at the center of every decision, even amid complexity. Apply if you're excited to:

        • Lead end-to-end execution of large, multi-product implementations, customers with more than three solutions purchased at once), and implementations with particularly complex or challenging onboarding projects
        • Lead customer project meetings and provide clear, confident communication around progress, decisions, risks, upcoming milestones, and customer responsibilities
        • Own escalation handling for active implementations (e.g., slipping milestones, stakeholder misalignment, unresolved blockers) to prevent churn that originates during implementation, ensuring issues are triaged, routed, customer is connected with, responses are tracked and resolved against defined SLA response and resolution targets
        • Translate customer priorities and clinic workflows into clear implementation requirements and ensure those requirements are understood by the teams responsible for delivery
        • Partner closely with dedicated Build and Customer Enablement teams to facilitate the appropriate configuration of PetDesk solutions and ensure customers receive the training and support needed to successfully launch
        • Influence and coordinate across AE, Build, Customer Enablement, Strategic Account Management, Customer Success, Support, and executive stakeholders (internally and with the client) to ensure work is completed by agreed-upon milestones
        • Use tools consistently to maintain accurate project information and proactively communicate status to internal and external stakeholders
        • Continuously identify opportunities to improve implementation processes, leveraging AI and other tools to increase efficiency, consistency, and visibility

        About you

        • 4+ years of experience managing complex, multi-stakeholder, multi-product implementations or similar customer-facing projects
        • Hands-on experience using Klient PSA, Wrike, or another complex project management platform for daily activity management, time tracking and internal visibility
        • Demon