Client Project Manager

We need to output HTML fragment with sections: About the role? The posting includes Position Summary, Essential Duties & Responsibilities, Qualifications, Benefits. Also maybe "Security And Compliance Responsibilities" could be part of responsibilities. But we need to use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. The posting includes Position Summary (could be About the role). Essential Duties & Responsibilities (Responsibilities). Qualifications (Qualifications). Benefits (Benefits). There's no explicit Pay or Schedule content (Salary range: but incomplete). It says "Salary range:" but no numbers, so we should not create Pay section because it's not specific. Schedule: mentions remote role with opportunity to be hybrid if located in Tennessee, first week onsite, travel expenses paid. That's schedule/location info. Could be considered Schedule? The instruction: include a section ONLY when posting has real, specific content for it. The schedule info is present: remote role, hybrid option, first week onsite, travel expenses paid. That's specific enough. So we can create a Schedule section with that info. Also maybe "About the role" could be the Position Summary paragraph. We'll not repeat job title. We'll include headings: About the role, Responsibilities, Qualifications, Benefits, Schedule. Possibly also Requirements? Qualifications covers requirements. We'll not duplicate. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none. We need to include all substantive info from the posting. Let's extract: About the role (Position Summary): Lirio is a technology/software company that provides expertise in a variety of behavioral science domains (e.g., behavioral economics, social psychology, public health), data science, and machine learning to drive consumer engagement, close gaps in preventive and chronic care, and promote health and well-being across an individual’s lifespan. Lirio’s behavior change AI platform unites behavioral science with advanced artificial intelligence (AI) to deliver Precision Nudging health interventions. Precision Nudging is the application of behavioral science to health interventions personalized by AI to each individual that overcome barriers to action at the right time and place for scalable, behavior change. This is a remote role with the opportunity to be hybrid if located in Tennessee. All applicants must be authorized to work in the US without sponsorship. To ensure an excellent onboarding experience and integration into the company, new colleagues will spend their first week onsite at one of our offices in Tennessee. Travel expenses will be paid. This is a requirement. Position Summary The Client Project Manager is responsible for planning, coordinating, and managing client implementations and related delivery work in accordance with established PMO standards. This role provides structured project leadership across scope management, schedule management, change control, launch readiness, and operational handoff. The Project Manager partners with client stakeholders and internal teams to define requirements, manage dependencies, track risks and issues, facilitate decisions, escalate barriers as appropriate, and maintain accurate project documentation. The ideal candidate brings strong project management discipline, client-facing communication skills, technical fluency, healthcare or SaaS implementation experience, and the ability to drive work forward through clear ownership and accountability. But note that the Position Summary repeats some of the earlier description. We need to preserve all substantive info, but we can combine. However we must not invent or summarize away detail. We can keep the paragraphs as is, maybe split into About the role (company description) and Responsibilities (the duties). The Position Summary includes both company description and role summary. We could put company description in About the role, and the role summary (Client Project Manager responsibilities) in Responsibilities? But Responsibilities already has a detailed list. To avoid duplication, we could keep About the role as the company description (first paragraph up to "This is a requirement.") and then Responsibilities as the Essential Duties & Responsibilities list plus maybe the Position Summary role description? But the Position Summary also includes some responsibilities. Safer to include the Position Summary as part of About the role? Actually About the role should describe the role, not the company. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So About the role likely is a brief description of the role. We can use the Position Summary paragraph (starting with "Position Summary The Client Project Manager is responsible...") as About the role. The earlier company description could be considered part of About the role as well, but it's more about the company. However we can include it as part of About the role because it's still relevant to the role context. But we must not invent or summarize away detail; we can keep both paragraphs. Thus About the role will contain two paragraphs: first about Lirio company, second about the Position Summary. Responsibilities: the Essential Duties & Responsibilities section (the bullet-like paragraphs). We need to convert to

  • for any list of duties/requirements/benefits. The responsibilities are in paragraphs with sentences; we could treat each sentence as a list item? The instruction: Use
    • for any list of duties/requirements/benefits. The responsibilities are not explicitly a list but we can still format each duty as a list item to comply. However we must preserve all substantive information; converting sentences to list items is okay as long as we don't lose info. We'll split by the sentences that start with verbs: Manage Scope, Plans, and Delivery Execution ... etc. Actually the section has headings like "Manage Scope, Plans, and Delivery Execution", "Lead Governance, Change Control, and Escalation", etc. Those are subheadings not allowed; we should not create extra headings beyond the allowed ones. We could treat each paragraph under those headings as list items. But we must not invent headings. So we can just make a
      and each distinct duty sentence as
      • . Let's extract the duties: - Build and maintain project plans that define scope, milestones, workstreams, dependencies, owners, timelines, and acceptance criteria from kickoff through launch. - Manage scope in alignment with approved requirements, success criteria, timelines, and resource assumptions; identify potential scope changes and route them through the appropriate change control process. - Maintain accurate project documentation including project plans, status reports, decision logs, issue trackers, risk registers, and delivery artifacts required by PMO standards. - Provide regular visibility into project health including progress against milestones, open decisions, risks, issues, dependencies, and required leadership support. - Facilitate project governance routines including status meetings, stakeholder reviews, decision forums, risk reviews, and readiness checkpoints. - Apply change control discipline by documenting proposed changes, assessing impact to scope, schedule, cost, resources, quality, and client commitments, and coordinating approval before execution. - Use appropriate drive resolution of or use escalation authority to raise risks, unresolved decisions, resource constraints, timeline impacts, or delivery blockers to PMO leadership and accountable business owners. - Ensure decisions, approvals, assumptions, and tradeoffs are documented and communicated to affected stakeholders in a timely and consistent manner. - Partner with clients and internal subject matter experts to gather, clarify, and document business, solution design, technical, and operational requirements. - Coordinate resource planning and competing priorities across internal teams by identifying required roles, timing, dependencies, constraints, and capacity needs to support project execution. - Manage launch readiness activities, including readiness criteria, testing support, defect or issue triage, operational preparation, client approvals, and go/no-go inputs. - Support transition from implementation to operations by coordinating handoff materials, support expectations, open items, ownership changes, and post-launch monitoring needs. - Collaborate across Account Management, Customer Operations, Product, Engineering, Data, Support, Sales, and Business Development to align execution, resolve blockers, and support integrated delivery outcomes. - Follow established PMO processes, templates, documentation expectations, reporting cadences, governance checkpoints, and delivery standards. - Identify opportunities to improve implementation delivery, operational handoffs, project controls, documentation quality, and cross-functional coordination. - Perform other duties as assigned. Also there is a "Security And Compliance Responsibilities" paragraph: Colleagues are responsible for protecting Lirio, our clients, and the people we serve by complying with information security policies, procedures, laws, guidelines, contracts, and regulations. This role may access or work with sensitive or confidential information and may work with PHI/ePHI depending on client assignments. Colleagues are required to complete privacy and security training, report suspected or known incidents and comply with applicable attestations and agreements. We could include that as part of Responsibilities as well (maybe as separate list items). We'll add items: - Comply with information security policies, procedures, laws, guidelines, contracts, and regulations to protect Lirio, clients, and the people we serve. - May access or work with sensitive or confidential information and may work with PHI/ePHI depending on client assignments. - Complete privacy and security training, report suspected or known incidents, and comply with applicable attestations and agreements. Now Qualifications: we need to list as
        • . The qualifications paragraph includes multiple sentences. We'll extract each bullet: - Bachelor’s degree preferred or equivalent combination of education and relevant experience. - 3–5 years of experience in project management, implementation management, client/vendor management, consulting, SaaS implementation, or client-facing delivery preferably in healthcare or other protected data environments. - Proven ability to manage multi-phase projects with parallel, interdependent workstreams, defined scope, structured governance, documented risks, and measurable delivery milestones. - Proven ability to manage multiple active projects requiring cross-functional collaboration and dependencies. - Experience applying project controls, including scope management, change control, resource planning, risk and issue management, escalation, launch readiness, and implementation-to-operations handoffs. - Strong client-facing communication skills with the ability to translate requirements, communicate progress, manage expectations, and facilitate decisions with stakeholders. - Working knowledge of integrated systems, SaaS/PaaS environments, APIs, data integrations, and reporting concepts. - Experience with Agile delivery practices, technical documentation, business analytics, issue triage, and user acceptance testing preferred. - Demonstrated ability to operate with ownership, organization, collaboration, sound judgment, and adherence to established standards. Benefits: list as
          • . The benefits paragraph: "Medical (HSA available) Dental Vision Short-term & long-term disability (company-paid) Life & AD&D (company-paid) 401K with company match 10 paid holidays, quarterly company closure dates, + holiday week company closure Flexible time off policy Work from home 6 weeks paid parental leave Salary range:" Actually the benefits list ends before Salary range: which is incomplete. So we list benefits up to parental leave. Also "Work from home" is a benefit. We'll parse: - Medical (HSA available) - Dental - Vision - Short-term & long-term disability (company-paid) - Life & AD&D (company-paid) - 401K with company match - 10 paid holidays, quarterly company closure dates, + holiday week company closure - Flexible time off policy - Work from home - 6 weeks paid parental leave We should not include Salary range because it's not specific. Schedule: we have remote role with opportunity to be hybrid if located in Tennessee, first week onsite at one of our offices in Tennessee, travel expenses paid. Also maybe mention that all applicants must be authorized to work in the US without sponsorship. That's more a requirement but could be in Schedule? Actually it's a requirement about work authorization. Could be placed in Requirements/Qualifications but we already have qualifications. Could add a note in Schedule? Better to add a separate requirement? But we don't have a Requirements section; we could add a note in Qualifications? However the instruction: Use sections only when posting has real, specific content. The work authorization is a requirement. Could be placed