Senior Solution Specialist / Associate Director / Director (Access Center)

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to parse the posting. The posting includes: - About The Role (section) - A Day in the Life (with subsections: Deal Strategy & Solution Engineering (50%), Growth Strategy & Product Influence (50%), Executive Engagement) - What You Need (requirements) - What You'll Bring (maybe skills/qualities) - We offer competitive benefits... Here's What We Offer (benefits) - Then EEO boilerplate etc to remove. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content goes where. "About The Role" -> heading About the role. Responsibilities: likely the "A Day in the Life" sections describing duties: Deal Strategy & Solution Engineering, Growth Strategy & Product Influence, Executive Engagement. So we can put those under Responsibilities. Requirements: "What You Need" (experience, expertise). Could be Requirements. Qualifications: maybe education (Bachelor's degree required; master's preferred) and maybe travel ability? Could be Qualifications. Skills: "What You'll Bring" (strategic thinking, hands-on solution engineering, deep understanding, confidence to present, passion). Could be Skills. Benefits: "Here's What We Offer" (PTO, parental leave, recognition, insurance, optional perks). So Benefits. Pay: Not mentioned. No salary info. So we should NOT include Pay section. Schedule: Travel up to 30-40% mentioned under What You Need? Actually travel ability is in What You Need: "Ability to travel up to 30-40% for customer meetings and internal strategy sessions." That's schedule/travel. Could be Schedule section. But schedule might refer to work schedule (full-time, part-time). Travel is not exactly schedule but could be considered schedule. The instruction: include Schedule section only if posting actually states them. It does state travel percentage. So we can include Schedule heading with that detail. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, E-Verify, disclaimer, etc. We must preserve all substantive information. We need to output HTML fragment only, no /, no markdown fences. We need to use

for headings,

• for any list of duties/requirements/benefits, and

  for prose. We need to decide what is list vs prose. We have multiple bullet-like sentences. We can convert each duty/requirement/benefit into

• . For prose paragraphs, use

  . We need to avoid filler like "commensurate with experience". Not present. Let's extract content. About The Role paragraph: "Innovaccer is seeking a Senior Solution Specialist to drive pre-sales strategy, solution design, and deal execution across our Experience product portfolio, including Access & Outreach, Contact Center Modernization, Referrals, Patient Engagement, Care Journeys, and Marketing Automation. This role is a strategic IC that blends the analytical and narrative strengths of our Growth Strategy function with the hands-on consultative and solution engineering expertise needed to win high-impact deals. You will lead the development of compelling solution narratives, mock workflows, ROI models, and executive-ready presentations, while also running demos and shaping how Innovaccer positions its Experience capabilities. You will focus deeply on Access & Outreach, bringing expertise in Access Center operations, including scheduling, registration, insurance verification, contact center workflows, and omnichannel engagement. You will support the broader Experience landscape as needed, influencing how our solutions evolve, commercialize, and scale in the market. This is a highly cross-functional, highly visible role partnering with Product, Sales, Marketing, and Customer Success teams. While you won't own customer relationships, you will join executive conversations to guide solution direction and drive deal momentum." We can put that as

  under About the role heading. Responsibilities: we have three sub-sections. Deal Strategy & Solution Engineering (50%): - Lead consultative discovery to understand customer challenges across Access, Outreach, and Experience workflows - Build solution architectures, mock workflows, and demo flows that highlight Innovaccer's differentiated value. - Conduct demos and narrative-driven walkthroughs to articulate how Innovaccer improves access operations, digital engagement, patient experience, and efficiency. - Create executive-ready pitch materials, business cases, ROI analyses, proposals, and transformation roadmaps that advance complex deals. - Partner with Sales leaders to shape deal strategy, structure commercial proposals, develop contracting frameworks, and support pricing decisions. - Provide subject-matter expertise on Access operations and patient engagement to guide customer conversations and internal alignment. Growth Strategy & Product Influence (50%): - Develop strategic narratives and GTM motions for Access & Outreach in partnership with Product. - Analyze customer needs, competitive landscape, and solution gaps to inform product teams—influencing (not owning) roadmap direction across Experience offerings. - Build reusable assets, playbooks, workflow libraries, and value frameworks for the Experience portfolio—scaling best practices across Sales, Product, and Customer Success. - Serve as a bridge between customer requirements and Innovaccer's Experience product capabilities—recommend enhancements and help shape future solution blueprints. - Support commercial packaging, bundling, and cross-product alignment across the Experience family. Executive Engagement: - Join strategic executive meetings with COOs, CAOs, Chief Experience Officers, CIOs, CMOs, and Patient Access leaders to articulate Innovaccer's POV. - Guide customers through modernization strategies without owning long-term relationships. - Translate technical capabilities into operational, clinical, and financial value for senior stakeholders. We can combine these as a list under Responsibilities heading. Could also separate subheadings but only allowed headings are the predefined ones; we cannot add extra headings. So we just list all responsibilities as

• items. Requirements: "What You Need" paragraph: "8-12+ years of experience across healthcare access operations, patient engagement, digital front-door transformation, consulting, or solution engineering Deep expertise in multiple Access Center workflow areas such as scheduling, voice agents, registration, insurance verification, call center operations, omnichannel engagement, referrals, and digital experience. Experience with Call Center technology stack Experience with Call Center transformation Demonstrated success driving complex deals in enterprise provider or health system environments. Strong ability to design and run demos, mock workflows, and solution narratives with clarity, confidence, and precision Exceptional communication and storytelling skills—able to translate workflows and technology into measurable business impact. Strong analytical and commercial acumen; ability to create ROI models, business cases, and pricing structures. Experience influencing product direction and collaborating with Product teams, without owning roadmap decisions. Ability to operate as a high-ownership individual contributor who collaborates across matrixed teams. Bachelor's degree required; master's degree (MBA, MHA) preferred. Ability to travel up to 30-40% for customer meetings and internal strategy sessions." We need to split into Requirements, Qualifications, Skills, Benefits, Schedule. We need to decide what goes where. Requirements: likely the experience and expertise items (years, deep expertise, experience with call center tech stack, transformation, demonstrated success driving complex deals). Could be Requirements. Qualifications: education (Bachelor's required; master's preferred) and maybe travel? Travel could be Schedule. Skills: communication, storytelling, analytical, ability to design demos, etc. Also "Ability to operate as a high-ownership individual contributor who collaborates across matrixed teams." That could be Skills. Let's map: Requirements (
  ): - 8-12+ years of experience across healthcare access operations, patient engagement, digital front-door transformation, consulting, or solution engineering - Deep expertise in multiple Access Center workflow areas such as scheduling, voice agents, registration, insurance verification, call center operations, omnichannel engagement, referrals, and digital experience. - Experience with Call Center technology stack - Experience with Call Center transformation - Demonstrated success driving complex deals in enterprise provider or health system environments. Qualifications (
  ): - Bachelor's degree required; master's degree (MBA, MHA) preferred. Skills (
  ): - Strong ability to design and run demos, mock workflows, and solution narratives with clarity, confidence, and precision - Exceptional communication and storytelling skills—able to translate workflows and technology into measurable business impact. - Strong analytical and commercial acumen; ability to create ROI models, business cases, and pricing structures. - Experience influencing product direction and collaborating with Product teams, without owning roadmap decisions. - Ability to operate as a high-ownership individual contributor who collaborates across matrixed teams. Schedule (

  or

  ?): Travel ability: "Ability to travel up to 30-40% for customer meetings and internal strategy sessions." Could be a

  . Benefits: from "Here's What We Offer" list: - Generous Paid Time Off: Recharge and relax with 20 days of fixed time off per year, in addition to company holidays—because we believe work-life balance fuels performance. - Best-in-Class Parental Leave: Spend quality time with your growing family. We offer one of the industry's most generous parental leave policies to support you during life's most important moments. - Recognition & Rewards: We celebrate wins—big and small. Get rewarded with monetary incentives and company-wide recognition for your impact and dedication. Your hard work won't go unnoticed. - Comprehensive Insurance Coverage: Stay covered with medical, dental, and vision insurance, plus 100% company-paid short- and long-term disability and basic life insurance. Optional perks include discounted legal aid and pet insurance. We could make each as

  • under Benefits. We must not include Pay section. Now we need to output HTML fragment with headings

    and content. Structure:

    About the role

    ...paragraph...

    Responsibilities

    • ... each responsibility ...
    ...

    Requirements

    • ... each requirement ...
    ...

    Qualifications

    • Bachelor's degree required; master's degree (MBA, MHA) preferred.

    Skills

    • ... each skill ...
    ...

    Benefits

    • ... each benefit ...
    ...

    Schedule

    Ability to travel up to 30-40% for customer meetings and internal strategy sessions.

    We must ensure we don't include any empty sections. All have content. Check for any duplicated lines: we must not repeat. Now verify we haven't missed any substantive info. From About The Role we captured all. From Responsibilities we captured all bullet points. Check if any responsibility missing: The "A Day in the Life" also had a brief intro sentence: "A Day in the Life Deal Strategy & Solution Engineering (50%) Lead consultative discovery..." Actually the heading "A Day in the Life" is not a required heading; we treat its subsections as responsibilities. The intro sentence maybe "A Day in the Life" is just a heading; we can ignore. We captured all bullet points under each sub-section. Now check Requirements: we captured years, deep expertise, call center tech stack, call center transformation, demonstrated success driving complex deals. Did we miss "Experience with Call Center technology stack" and "Experience with Call Center transformation" - we have them. We missed "Experience with Call Center technology stack" and "Experience with Call Center transformation" - we have them as separate items. We also missed "Experience with Call Center technology stack" and "Experience with Call Center transformation" - yes. We also missed "Experience with Call Center technology stack" and "Experience with Call Center transformation"