Onboarding Project Lead, Healthcare

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate. We need to parse the posting. First paragraph: "The Healthcare Onboarding Project Lead guides new customers through the work required to begin using an Inmar Healthcare solution successfully. You will organize the plan, create clarity across customer and internal teams, coordinate configuration and testing, communicate risks and decisions, and help everyone reach launch readiness. This is a hands-on, project leadership role for someone who follows through, learns quickly, communicates clearly, and stays composed when the playbook does not yet cover every scenario. Prior healthcare software experience can help, but it is not the only path. We care more about evidence that you can organize work, build trust, learn unfamiliar systems, surface risk, and deliver commitments." That's about the role. Then "About Customer Success Our Customer Success team is focused on helping customers easily achieve the value of our products. We aim for every interaction to create confidence, reduce customer effort, and demonstrate that we understand the customer's business." That's maybe part of About the role or separate? Could be "About Customer Success" but not a required heading; we can incorporate into About the role. Then "What You Will Own" list of duties. That's responsibilities. Then "What Success Looks Like" with timeline. Could be part of responsibilities or maybe a separate section? Could be "Expectations" but not in list. We could treat as part of responsibilities. Then "Capabilities You Bring On Day One" list of capabilities. That's skills/qualifications. Then "Helpful Experience, Not Required" list. That's qualifications/preferred. Then "How We Work" values. Could be part of About the role or maybe not needed. Then "A Realistic Preview" details about role. Could be responsibilities. Then "Required Qualifications" bullet list. Then "Preferred Qualifications" bullet list. Then "As An Inmar Associate, You ..." values. Then benefits paragraph: "At Inmar, we put people first ... Our comprehensive and competitive benefits package ..." then list of benefits. We need Benefits section if present. Yes we have benefits details. Pay and Schedule: Not mentioned. So we should NOT include Pay or Schedule sections. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have content for About the role (intro + About Customer Success + How We Work maybe). Responsibilities (What You Will Own, What Success Looks Like, A Realistic Preview). Requirements (maybe Required Qualifications). Qualifications (maybe Preferred Qualifications? Actually Requirements vs Qualifications ambiguous. Usually Requirements = required qualifications; Qualifications = preferred? But we have both Required and Preferred. Could map Required Qualifications to Requirements section, Preferred Qualifications to Qualifications section. Skills: Capabilities You Bring On Day One (skills). Also Helpful Experience, Not Required could be part of Qualifications or Skills? Might be part of Qualifications. We need to avoid filler. Ensure we preserve all substantive info. Let's extract content. About the role: combine first paragraph + About Customer Success + How We Work? The "How We Work" is a set of values; could be part of About the role or separate but we don't have a heading for values. We could include in About the role as prose. Responsibilities: list from "What You Will Own" (bullet points), "What Success Looks Like" (timeline), "A Realistic Preview" (details). We'll turn each bullet into

. Requirements: Required Qualifications bullet list. Qualifications: Preferred Qualifications bullet list. Skills: Capabilities You Bring On Day One bullet list. Benefits: benefits paragraph and list. We must not repeat job title. No metadata like Job ID. We must not include boilerplate like EEO, scam notice, visa sponsorship, etc. Remove those. We must preserve all substantive info; do not invent. Let's extract each piece. First paragraph: "The Healthcare Onboarding Project Lead guides new customers through the work required to begin using an Inmar Healthcare solution successfully. You will organize the plan, create clarity across customer and internal teams, coordinate configuration and testing, communicate risks and decisions, and help everyone reach launch readiness. This is a hands-on, project leadership role for someone who follows through, learns quickly, communicates clearly, and stays composed when the playbook does not yet cover every scenario. Prior healthcare software experience can help, but it is not the only path. We care more about evidence that you can organize work, build trust, learn unfamiliar systems, surface risk, and deliver commitments." About Customer Success: "Our Customer Success team is focused on helping customers easily achieve the value of our products. We aim for every interaction to create confidence, reduce customer effort, and demonstrate that we understand the customer's business." How We Work: list of values: "Customer First: Understand the customer's business, reduce effort, set expectations, and close the loop.High Challenge, High Support: Raise difficult issues directly and respectfully, use feedback, and help others succeed.Raising the Bar: Improve quality, prevent repeated issues, and leave tools and processes better than you found them.Learning in Action: Learn quickly, test assumptions, adapt, and apply lessons to the next situation.Seeking Truth Together: Surface facts and risks, ask good questions, welcome different perspectives, and update your view when evidence changes.Upholding Commitments: Create clear ownership, communicate changes early, document actions, and follow through." We could format as prose sentences. Now Responsibilities: What You Will Own bullet points: - Lead onboarding projects: Guide customers from kickoff through launch and handoff. - Build and maintain the project plan, milestones, actions, decisions, dependencies, and readiness criteria. - Turn customer needs into launch-ready requirements: Listen carefully, establish and maintain the intended workflow, document requirements and commitments, and coordinate accurate account setup, data, access, and integration needs. - Validate readiness and support adoption: Coordinate or perform configuration checks, data validation, QA/UAT, training, and launch-readiness reviews. Make sure unresolved issues have a clear owner and plan. - Create confidence through communication: Provide clear status, next steps, risks, decisions, and required actions. Escalate early when scope, timing, quality, or the customer experience is at risk. - Improve the onboarding model: Capture customer feedback and lessons learned. Turn new scenarios into clearer playbooks, templates, checklists, and handoffs so the next customer has an easier experience. What Success Looks Like: - First 90 days: Build working knowledge of the product, customer workflows, onboarding process, tools, and partner teams. Shadow and co-lead projects, maintain accurate plans and action logs, communicate clearly, and begin owning standard workstreams with coaching. - By 6 months: Independently lead standard onboarding projects through agreed milestones and launch readiness. Customers and internal partners know what is happening, what comes next, who owns each action, and where risk requires attention. Documentation and validation prevent avoidable rework. - By 12 months: Manage a portfolio of onboarding work with predictable execution and sound judgment. Customers are prepared and confident at launch, handoffs are complete, and recurring lessons from new scenarios are converted into practical improvements for the team. A Realistic Preview: - You will manage more than one onboarding effort at a time. Priorities and dependencies can change. - This role supports a new product. Some customer scenarios will be unfamiliar, and parts of the playbook will continue to evolve. - The role includes hands-on documentation, configuration checks, data validation, testing, and follow-up. It is not only meetings and status reports. - You will depend on teams you do not manage. Success requires clear ownership, respectful challenge, and early escalation. - Customers may be navigating operational change while learning the product. Your organization and communication should make that experience easier. - Occasional travel may be required for team events or strategic customer onboarding meetings. Now Required Qualifications bullet list: - Bachelor's degree preferred - 3 to 6 years of client facing experience in healthcare, software, fintech, or a related professional services environment - Experience supporting onboarding, implementations, integrations, or operational launches - Demonstrated ability to lead workstreams and drive outcomes across cross functional teams - Strong organizational skills and attention to detail - Ability to manage multiple onboarding efforts simultaneously while meeting deadlines - Excellent written and verbal communication skills - Proficient in Google Workspace and Microsoft Office - Ability to translate client needs into operational and technical requirements Preferred Qualifications bullet list: - Experience in Healthcare operations, pharmacy services, healthcare technology platforms, or regulated environments - Familiarity with healthcare data structures, claims processing, financial transactions, or system integrations - Experience working within Salesforce or similar CRM systems - Experience performing QA and UAT testing - Understanding of compliance, privacy, or regulatory considerations within Healthcare Capabilities You Bring On Day One bullet list: - Evidence that you can coordinate multi-step work involving several people, dependencies, and deadlines. - Clear, audience-aware written and verbal communication, including the ability to explain status, decisions, risks, and next steps. - Strong organization and follow-through. You create plans, document commitments, maintain details, and close loops. - Sound judgment about when to solve, when to ask, and when to escalate. - Ability to learn unfamiliar software, processes, and customer workflows quickly and apply feedback. - A customer-service mindset that balances empathy, accuracy, clarity, and ownership. - Comfort working with data, system settings, testing, and quality checks. Deep technical expertise is not required for this role, but you will be leading pharmacy software onboarding projects that have some technical components. Helpful Experience, Not Required bullet list (maybe part of Qualifications or Skills). We could include under Qualifications as additional preferred? But we already have Preferred Qualifications. Could treat as part of Qualifications (maybe "Additional Helpful Experience"). But we need to avoid duplication. We'll include under Qualifications as extra bullet points. Now Benefits: Paragraph: "At Inmar, we put people first and that means empowering our associates to thrive at every stage of life and career. Our comprehensive and competitive benefits package is thoughtfully designed to support a wide range of lifestyles and life stages. Eligible Associates Have Access To" Then list: - Medical, Dental, and Vision insurance - Basic and Supplemental Life Insurance options - 401(k) retirement plans with company match - Health Spending Accounts (HSA/FSA) - Flexible time off and 11 paid holidays - Family-building benefits, including Maternity, Adoption, and Parental Leave - Tuition Reimbursement and certification support, reflecting our commitment to lifelong learning - Wellness and Mental Health counseling services - Concierge and work/life support resources - Adoption Assistance Reimbursement - Perks and discount programs Also note: "Please note that eligibility for some benefits may depend on your job classification and length of employment. Benefits are subject to change and may be governed by specific plan or program terms." That's substantive but maybe boilerplate? It's about benefits; we can include as a note. We should not include EEO, scam notice, visa sponsorship, etc. Now construct HTML. We'll have sections:

About the role

... combine paragraphs.

Responsibilities

• ... each bullet.

Requirements

• ... required qualifications.

Qualifications

• ... preferred qualifications + helpful experience.

Skills

• ... capabilities.

Benefits

... intro paragraph.

• ... each benefit.

... note about eligibility.

We must not include Pay or Schedule. Make sure we preserve all substantive info; no extra. Let's craft the About the role paragraph