HELOC Closing & Delivery Manager

We need to output HTML fragment with sections: About the role (but we already have ABOUT THE ROLE heading; we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes sections: ABOUT OUR COMPANY, ABOUT OUR WORKPLACE, ABOUT THE ROLE, WHAT YOU’LL DO AT SPLASH (responsibilities), WHAT YOU’LL BRING TO SPLASH (requirements/qualifications/skills), NICE TO HAVE (maybe skills), COMPENSATION (pay). Also maybe benefits? Not explicit benefits aside from earlier mention of health insurance, competitive salaries, quarterly meet-ups, engagement tools. That's in ABOUT OUR WORKPLACE. Could be considered Benefits. We need to include sections only when posting has real specific content. So we can have sections: About the role (maybe combine ABOUT THE ROLE and ABOUT OUR COMPANY/WORKPLACE? Actually About the role is separate heading; we need to use

for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We should not repeat job title as heading. The page already shows it, so we don't output a heading for the job title. We need to include

for each section we output. We need to use

for prose,

• for lists. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to decide which sections to include: - About the role: could include description of role from ABOUT THE ROLE paragraph. That's substantive. - Responsibilities: from WHAT YOU’LL DO AT SPLASH (list of duties). That's many bullet-like sentences; we can turn into
  • . - Requirements / Qualifications / Skills: from WHAT YOU’LL BRING TO SPLASH (associate's or bachelor's, experience, etc.) plus NICE TO HAVE (nice to have). Could split into Requirements (mandatory) and Skills (nice to have) or Qualifications. The instruction says prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But they ask to use headings like Requirements, Qualifications, Skills. We could output Requirements (mandatory) and Skills (nice to have). Qualifications maybe same as Requirements. To avoid thin sections, we could output Requirements (includes education, experience, knowledge) and Skills (nice to have). Or we could output Requirements and Qualifications as same content? Better to follow instruction: use headings when posting has real specific content. We have both mandatory and nice-to-have; we can make two sections: Requirements (mandatory) and Skills (nice to have). That seems appropriate. - Benefits: from ABOUT OUR WORKPLACE mentions great health insurance, competitive salaries, unique benefits like quarterly meet-ups and access to engagement tools. Also maybe remote-first etc. That's substantive. So we can include Benefits section. - Pay: from COMPENSATION: base salary range $69,000 to $85,000 annually. That's specific. So include Pay. - Schedule: from ABOUT THE ROLE: "This is a remote role that requires 1–4 days per month in our downtown Cleveland office to support operational processes." That's schedule info. So include Schedule. We should not include sections like About the company? Not required headings. Could include About the role only. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. We could also include About the company as a

    maybe not as heading. But we could incorporate that into About the role? Probably better to keep About the role section only containing the role description; company info could be placed as a

    before sections? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." It doesn't forbid other headings like About the company, but the list of suggested headings is just examples. However they say "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections. It's safer to only use those headings. So we will not include About the company or About the workplace as separate headings; we can fold relevant info into Benefits or About the role? The About the role section should contain description of role; we can include a brief sentence about the company mission maybe not needed. But we must preserve ALL substantive information. If we omit company description, we lose substantive info. So we need to include that info somewhere. Could we put it in a

    without a heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities...). It doesn't say we cannot have other headings, but they gave examples. It might be okay to have a heading like About the company, but they didn't list it. Safer to embed that info in a

    before the first heading, maybe as an introductory paragraph. That would preserve info without extra heading. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can fold minor metadata into a short

    . Company description might be considered not minor metadata; it's substantive. But we could still put it in a

    without a heading; that's allowed. The instruction didn't forbid

    without heading. So we can start with a

    containing the company overview and workplace description. Then headings for sections. Thus output:

    ABOUT OUR COMPANY: ... ABOUT OUR WORKPLACE: ...

    (combined). Ensure we remove boilerplate like EEO etc. There's none. Then

    About the role

    with paragraph from ABOUT THE ROLE. Then

    Responsibilities

    with
    • items from WHAT YOU’LL DO AT SPLASH. Then

      Requirements

      with
      • items from WHAT YOU’LL BRING TO SPLASH (mandatory). Then maybe

        Skills

        with nice-to-have. Then

        Benefits

        with
        • items from ABOUT OUR WORKPLACE (health insurance, competitive salaries, quarterly meet-ups, engagement tools). Also remote-first maybe. Then

          Pay

          with paragraph from COMPENSATION. Then

          Schedule

          with paragraph about remote role requiring 1-4 days per month in Cleveland office. We must ensure we don't create sections with filler like "commensurate with experience". Not present. We must preserve all substantive information: need to include details like "Associate’s or bachelor’s degree, or equivalent work experience." etc. Let's extract. Company overview: ABOUT OUR COMPANY:The crushing weight of debt is something that we believe holds people back from reaching their dreams and making a splash in the world. So in 2013, after seeing our friends and family struggle with student loans, we created Splash Financial.Over the years, our mission has expanded to include helping people with other forms of debt - such as refinancing credit cards, which are at all time highs in the US. And we’ve been able to refinance $6+ Billion in loans through our network of Splash, powered credit union and bank partners who leverage our marketplace and automated loan processing technology. And we’ve raised over $135 million from investors like partners of DST Global, Citi Ventures, TruStage Ventures, Northwestern Mutual Future Ventures, Detroit Venture Partners, and more.But at our core, we’re still that little company from Cleveland with a big dream: to make people more powerful than their debt and we’re just getting started.. ABOUT OUR WORKPLACE:Splash is remote-first, and proud of it — though our collections team works in-person at our Arizona location.We spend our days simplifying financial products and getting them into the hands of people who need them most. Right now, we’re focused on building financial technologies that fundamentally transform how the industry lends.Although Splash has been around since 2013, we still operate like a startup — fast-paced, nimble, and full of heart. We’re good people who care deeply about doing meaningful work and we approach challenges with creativity, passion, and urgency.And to hire the best, we provide the best: great health insurance, competitive salaries, and unique benefits like quarterly meet-ups and access to engagement tools that keep us connected — even from afar. At Splash, everything we do is guided by our values:Own It – We take full accountability and follow through on commitments.Raise the Bar – We move fast, innovate faster, and push through barriers.Say the Hard Thing – We speak up with honesty, respect, and a desire to solve problems and make things better.Elevate Each Other – We win as a team by lifting each other up.These values show up in how we work and how we connect — whether we’re collaborating on big projects or bonding over everyday moments. Yes, we even have Slack channels for #kids-and-pets and #food because we believe being human makes us better teammates. We need to preserve all that. We'll combine into one

          . Might be long but okay. Now About the role paragraph: ABOUT THE ROLE:Splash Financial is seeking a HELOC Closing & Delivery Manager to manage day-to-day closing and investor delivery for our new HELOC lending platform. This individual contributor will coordinate accurate, timely closings and loan delivery, serving as the primary point of contact for borrowers, settlement agents, and investor partners from clear-to-close through loan sale.Working with the Director, HELOC Operations, this person will help establish and document the workflows that support the program as it grows. The role reports to the Director, HELOC Operations and may have an opportunity to help build and lead a closing team as origination volume increases. We are hiring for this role in the Cleveland, OH area only. This is a remote role that requires 1–4 days per month in our downtown Cleveland office to support operational processes. We'll put that in

          under About the role. Responsibilities: WHAT YOU’LL DO AT SPLASH: includes several paragraphs each starting with a bold heading? Actually the text includes headings like Process Documentation & Improvement, Pre-Closing File Review & Readiness, Closing Coordination & Communication, Funding, Post-Closing & Investor Delivery, Pipeline, Quality & Continuous Improvement. Each has multiple sentences. We'll turn each sentence into

        • maybe grouping under each heading? But we can just make a flat list of duties. However to preserve structure, we could keep headings as inside
        • ? But instruction: use
          • for any list of duties/requirements/benefits. It doesn't forbid adding extra markup inside
          • . So we can keep the headings as part of the
          • text. Thus we will create
            with each duty sentence as
            • . Let's extract sentences: Process Documentation & Improvement - Help develop and document HELOC closing and investor-delivery checklists, LOS workflows, remote online notarization (RON) and eClosing procedures, and quality-control standards in partnership with the Director, HELOC Operations. - Identify recurring issues in the closing-to-sale process and recommend improvements as the program grows. Pre-Closing File Review & Readiness