Sr. Product Manager, Data Integrations

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Lively" description, then "THE ROLE", then "WHAT YOU'LL DO" (responsibilities), then "WHAT WE'RE LOOKING FOR" (requirements), then "What Sets You Apart" (maybe qualifications/skills), then "WHY LIVELY" (benefits? maybe culture), then compensation, then "Benefits & Perks". Also there is EEO etc which we must remove. We must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real specific content. The posting includes: About Lively (company description) - could be "About the role"? Actually "About Lively" is about company, not role. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. Likely sections: About the role (maybe the description of the role), Responsibilities (WHAT YOU'LL DO), Requirements (WHAT WE'RE LOOKING FOR), Qualifications (maybe What Sets You Apart?), Skills (maybe also part of What Sets You Apart?), Benefits (Benefits & Perks), Pay (compensation range), Schedule (maybe remote-first, timezone preference). Also there is "WHY LIVELY" maybe culture but not required heading; we could incorporate into About the role or drop if not matching headings. We should not create sections with filler. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but organized under those headings. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. At end there is E-Verify link etc - that's legal boilerplate; remove. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: About Lively paragraph: "About LivelyLively set out to raise the bar on benefit solutions, because we believe no one should have to sacrifice personal wellness for financial wellness. While traditional benefits focus more on transactions and less on the humans using them, Lively harnesses user-centric design and innovative technology to deliver an effortless experience for employers and account holders alike. Our modern HSA is consistently top-rated, and we have since expanded our offerings to provide a full suite of other benefits and services for companies, consumers, and financial institutions.Lively is a remote-first company, headquartered in San Francisco with employees across the US. Come join us and help make getting the value out of your benefits as simple as it should be." That's company overview; could go under "About the role"? Actually "About the role" maybe includes role description. But we have "THE ROLE" paragraph describing role. Let's extract that: THE ROLE: "Lively is hiring a Senior Product Manager to own how data moves between our platform and the systems our customers and partners rely on — payroll and HR platforms, benefits administration systems, carriers, and third-party administrators. You will own enrollment and eligibility data, file-based and API-based exchange, and the integration roadmap that connects Lively to its ecosystem.You will also own the AI agent experiences that sit on top of that data layer, with a focus on onboarding and validation: agents that help customers and partners get their data into Lively correctly the first time, interpret what arrives, surface problems in plain language, and propose corrections. Integration work at Lively is increasingly AI-assisted, and this role decides where that assistance belongs and where human review stays mandatory.Alongside this, you will shape Lively's forward data integration strategy: how our connectivity model evolves as the ecosystem moves toward real-time exchange, where we invest in building versus partnering, and how we make each additional integration cheaper and faster than the last.This is a technically grounded product role. You will work closely with engineering on system behavior, data design, and agent behavior, and you will be the person partners and internal teams come to when they need to understand how the data actually flows. You will own large initiatives end-to-end and operate as the primary subject matter expert for your areas.Please note: As a majority of our engineering team sits in Pacific time, candidate preference will be given to those in the Pacific and Mountain timezones." That's role description. WHAT YOU'LL DO: list of responsibilities (bulleted). We need to put each as

• . The responsibilities are listed in order of anticipated time investment, each with a heading like "Integration Ownership — ..." etc. We'll keep the text. WHAT WE'RE LOOKING FOR: Required Qualifications list. We'll put as
  • . What Sets You Apart: list of desirable qualifications/experience. Could be under "Qualifications" or "Skills". The instruction includes Qualifications and Skills headings. We could put "What Sets You Apart" under Qualifications (maybe as additional qualifications) and Skills maybe separate? But we have to avoid filler. We could combine them into Qualifications section (since they are qualifications/skills). Or we could have Qualifications for required, Skills for preferred. The posting has "Required Qualifications" and then "What Sets You Apart" (preferred). So we can map Required Qualifications to Requirements section, and What Sets You Apart to Qualifications section (or Skills). But we also have Skills heading; maybe we put preferred skills there. Let's decide: Use Requirements for required qualifications. Use Qualifications for "What Sets You Apart" (preferred qualifications). Use Skills maybe empty? Better to omit Skills if no specific content. But we could put some skills from that list under Skills. However the instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section called Qualifications (or Skills). But we must use headings exactly as given? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we can use only those that have content. So we can choose to use Qualifications for the "What Sets You Apart" list, and maybe not use Skills if no distinct skill list. However the "What Sets You Apart" includes many items that are skills/experience. Could treat as Qualifications. We'll not use Skills. Benefits: we have "Benefits & Perks" list. So Benefits section. Pay: compensation range: "$165,000 USD - $195,000 USD". Also note base salary listed is a range. We'll put that. Schedule: remote-first, timezone preference. The posting mentions remote-first, headquarters SF, candidate preference for Pacific and Mountain timezones. So we can put schedule info: remote-first, preference for Pacific/Mountain timezones. Also there is "WHY LIVELY" culture description; we could incorporate into About the role or maybe drop as not matching headings. But we must preserve ALL substantive information. So we need to include that content somewhere. Could add a section "About the role" that includes both company overview and why Lively? Actually "About the role" is supposed to be about the role, but we could also include company description there. However we have separate "About Lively" paragraph. We could put that under "About the role" heading as a brief about the company/context. The instruction: About the role heading (e.g. About the role). It didn't forbid including company description there. We'll put the About Lively paragraph under About the role. Then we also have "WHY LIVELY" paragraph: "Healthcare and financial benefits affect everyone — and most platforms in this space are still frustratingly hard to use. Lively exists to change that. You'll work on products that matter, with a team that cares about craft, velocity, and outcomes. What you can expect: A fast-paced, AI-augmented product environment where you'll work with cutting-edge tools daily Meaningful ownership — this is not a role where you're handed a backlog and told to groom it A collaborative, intellectually honest culture where good ideas win regardless of seniority Direct impact on products used by thousands of employers and millions of employeesCompetitive compensation, comprehensive benefits (yes, we eat our own cooking), and remote-friendly flexibility The base salary listed is a range for this position. Actual pay will depend on the candidate’s location and experience.: $165,000 USD - $195,000 USD We encourage you to apply even if you do not meet all of the qualifications, but feel you would be a good fit for the position." This includes some repetition of compensation and benefits. We already have compensation and benefits sections. The rest is cultural description; we could incorporate into About the role or maybe a separate section but we don't have a heading for culture. Could add to About the role as well. We must not include boilerplate like "We encourage you to apply even if you do not meet all of the qualifications..." That's application instruction; we should remove that line. Also "We encourage you to apply even if you do not meet all of the qualifications, but feel you would be a good fit for the position." That's application instruction; remove. Also "The base salary listed is a range for this position. Actual pay will depend on the candidate’s location and experience." That's part of compensation description; we can keep in Pay section maybe. We must remove duplicated lines. Ensure we don't repeat. Now craft HTML. Structure:

    About the role

    About LivelyLively set out to raise the bar on benefit solutions, because we believe no one should have to sacrifice personal wellness for financial wellness. While traditional benefits focus more on transactions and less on the humans using them, Lively harnesses user-centric design and innovative technology to deliver an effortless experience for employers and account holders alike. Our modern HSA is consistently top-rated, and we have since expanded our offerings to provide a full suite of other benefits and services for companies, consumers, and financial institutions.Lively is a remote-first company, headquartered in San Francisco with employees across the US. Come join us and help make getting the value out of your benefits as simple as it should be.

    Healthcare and financial benefits affect everyone — and most platforms in this space are still frustratingly hard to use. Lively exists to change that. You'll work on products that matter, with a team that cares about craft, velocity, and outcomes. What you can expect: A fast-paced, AI-augmented product environment where you'll work with cutting-edge tools daily Meaningful ownership — this is not a role where you're handed a backlog and told to groom it A collaborative, intellectually honest culture where good ideas win regardless of seniority Direct impact on products used by thousands of employers and millions of employeesCompetitive compensation, comprehensive benefits (yes, we eat our own cooking), and remote-friendly flexibility

    But note we duplicated "Competitive compensation, comprehensive benefits..." which we will also have in Benefits and Pay sections. Might be duplication; we should avoid repeating same content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. However we can avoid duplication by not repeating the same sentence; but we need to keep the info somewhere. The "WHY LIVELY" includes that sentence; we already have Benefits and Pay sections covering compensation and benefits. So we could omit that sentence from About the role to avoid duplication, but then we would be omitting substantive info (the sentence about competitive compensation etc). However that info is already captured elsewhere; but the instruction says preserve ALL substantive information; if we omit it, we lose that piece. But we could keep it in Benefits and Pay sections; the sentence is essentially summarizing those. It might be considered duplication but still substantive. Safer to keep it somewhere; we could keep it in Benefits section as part of description. But