Sr. Product Manager, Data Integrations
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content: About Lively (company description) could be "About the role"? Actually "About the role" is not present; we have "THE ROLE" heading but that's not a standard list; but we could treat that as "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have: - About Lively (company overview) could go under "About the role"? Might be better as a brief intro paragraph before sections. But they said do NOT repeat the job title as a heading; we can have a
about Lively. Then we have responsibilities list under "WHAT YOU'LL DO". That's responsibilities. Then we have "WHAT WE'RE LOOKING FOR" which includes Required Qualifications and What Sets You Apart (preferred). So we can have Requirements (maybe Required Qualifications) and Skills (maybe What Sets You Apart). Also we have "Benefits & Perks" section. Pay: there is a salary range: $165,000 USD - $195,000 USD. So we need a Pay section. Schedule: not mentioned; remote-first, but no explicit schedule. Should we include Schedule? Only if posting actually states them. It mentions remote-first company, but not schedule specifics. Probably we should not include Schedule because no explicit schedule. Benefits: we have Benefits & Perks. Thus sections: About the role (maybe we can put company overview), Responsibilities, Requirements, Skills, Benefits, Pay. We must not include headings with filler. Ensure we preserve all substantive info. We need to use
for each section heading. Inside each, use - for lists,
for prose.
We must not include boilerplate like EEO, navigation, cookie, legal, scam-warning, duplicated lines, application instructions. Also remove "Please note: As a majority of our engineering team sits in Pacific time..." that's a note about timezone preference; that's substantive? It's a preference; we could include it under Responsibilities or maybe as a note. It's not boilerplate; it's a preference. We'll keep it.
We need to preserve all substantive information: that includes the note about timezone preference.
We must not invent or summarize away detail.
Let's extract content:
About Lively paragraph: "Lively 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 about the company; we can put under About the role (or maybe a separate "About Lively" but instruction only allows certain headings; we can use About the role to include this.
Then responsibilities: list under "WHAT YOU'LL DO". The responsibilities are a long list with headings like Integration Ownership, AI-Assisted Data Onboarding & Validation, Enrollment & Eligibility Data, Reliability, Data Quality & Scale, Integration Strategy, Requirements & Discovery, Partner & Implementation Enablement, Stakeholder Stewardship, Roadmap Ownership, Performance Tracking, AI Fluency in Practice, Market Awareness. Each has description.
We need to output as a list (
- ) each responsibility item. Should we keep the subheadings inside each li? Probably we can include them as part of the li text, maybe bold? But we cannot add extra HTML beyond
- and
. We can include the heading as plain text inside li.
Thus each li will contain the responsibility heading and its description.
We need to preserve all details.
Then Requirements: Required Qualifications list (bullet points). We'll output as
- each.
Then What Sets You Apart: list of preferred qualifications; we can put under Skills.
Then Benefits & Perks: list.
Then Pay: salary range.
We must not include duplicated lines, boilerplate like "We encourage you to apply even if you do not meet all of the qualifications..." that's application instruction; remove.
Also remove "Benefits & Perks" heading? We'll keep as Benefits section.
Also remove "WHY LIVELY" etc? That's promotional; but it's substantive? It's about why Lively; maybe we can incorporate into About the role? But it's not required heading; we could include as part of About the role paragraph. However it's not duplicate; we could keep as a separate paragraph under About the role.
But instruction: include a section ONLY when the posting has real, specific content for it. The "WHY LIVELY" is specific content; we could incorporate into About the role or maybe a separate section like "About Lively". Since we only have allowed headings, we could put it under About the role as well.
We must not include "Lively Inc. participates in the E-Verify program..." that's legal boilerplate; remove.
Also remove links.
Now craft HTML.
Structure:
About the role
... (company overview + why Lively)
Responsibilities
- Integration Ownership — Own the data exchanged between Lively and its partners: what moves, in what form, on what cadence, and what happens when something goes wrong. Define the contracts that both sides build against.
- AI-Assisted Data Onboarding & Validation — Own the AI agent experiences that accelerate getting partner and customer data into Lively: interpreting unfamiliar file structures, mapping fields, catching errors before they propagate, explaining what went wrong in language a non-technical administrator can act on, and recommending fixes. Define where the agent acts, where it advises, and where a human must approve.
- Enrollment & Eligibility Data — Own the enrollment data lifecycle end to end, including how changes, corrections, and exceptions are handled, and how Lively proves its records match the partner's.
- Reliability, Data Quality & Scale — Own the non-functional requirements of Lively's data integration platform: throughput, latency, availability, recovery, and the guarantee that data is never silently lost or partially applied. Define how failures are detected, communicated, and resolved. Plan capacity for the benefits industry's seasonal enrollment peaks and for growth in partner and record volume. Set the accuracy bar AI-assisted validation must clear before production use.
- Integration Strategy — Set the multi-year direction for how Lively connects to its ecosystem: the target architecture, the migration path from today's model, the role AI plays in reducing integration effort, and the build/buy/partner decisions that get us there.
- Requirements & Discovery — Translate partner needs, customer commitments, and regulatory constraints into clear, complete requirements — including the edge cases and failure paths, not only the intended flow.
- Partner & Implementation Enablement — Support the technical onboarding of new partners from specification through go-live, and reduce the time and effort each new connection takes.
- Stakeholder Stewardship — Act as the primary SME for your areas, fielding questions from implementation, customer success, sales, and leadership. Communicate vision, roadmap, and progress to internal and external audiences.
- Roadmap Ownership — Sequence complex, multi-quarter integration work into delivery milestones, balancing customer commitments, partner dependencies, and platform health.
- Performance Tracking — Define and monitor the metrics that describe integration health, onboarding effort, and AI agent accuracy, and use them to direct investment.
- AI Fluency in Practice — Use AI tooling in your own product work — research, specification, data analysis, prototyping — and raise the bar for how the product organization does the same.
- Market Awareness — Track how the benefits, payroll, and data-interoperability landscape is evolving, including where AI is changing what integration work costs, and identify partnership and standardization opportunities.
Requirements
- 5+ years of product management experience, with meaningful time owning integrations, data exchange, or platform APIs as a primary product surface
- Experience owning the exchange of structured business data between organizations — whether by file, API, or both — including the formats, cadence, and correctness guarantees each side depends on
- Demonstrated ownership of API products, including how they are designed, documented, evolved, and eventually retired without disrupting the partners built on them
- Strong judgment about data reliability at scale — you think in terms of what happens when a feed is late, incomplete, duplicated, or wrong, and you design for those cases deliberately
- Experience working directly with external technical partners — you can hold a substantive conversation with a partner's engineering team and represent Lively's position credibly without an engineer in the room
- Technical depth sufficient to be self-sufficient — you investigate data questions yourself rather than routing every one to engineering, and engineers regard your specifications as complete
- Experience handling sensitive personal or financial data under a regulated framework, with an instinct for privacy, security, and auditability
- Excellent analytical and problem-solving skills, with the ability to synthesize complex data into clear product decisions
- Outstanding communication skills — you can align engineers, partners, and executives on a shared direction
- Strong familiarity with Agile methodologies and standard product tooling
- Bachelor's degree in a technical or business field, or equivalent practical experience
Skills
- Benefits or health insurance domain experience — HSA/FSA/HRA plans, benefits compliance, IRS regulations, or the administration workflows behind them
- Ecosystem familiarity with payroll providers, HR platforms, benefits administration systems, carriers, or third-party administrators
- Fluency with industry data standards used in benefits, insurance, healthcare, or financial services exchange
- Experience modernizing a legacy integration surface — migrating partners onto a new model without breaking the old one
- Experience evaluating integration and connectivity vendors, and owning the build/buy/partner decision
- Experience building AI-powered product experiences, including designing for reliability and user trust
- Experience spanning both B2B (employer/broker-facing) and B2C (employee-facing) products
- Leadership experience, including mentoring or developing junior PMs
- Growth mindset and high self-motivation — you identify the next problem rather than waiting for it to be assigned
Benefits
- Competitive salaries
- Stock options
- Medical, dental, vision, life and disability coverage
- An HSA with employer contribution
- FSA
- Paid parental leave
- Medical travel benefits
- 401k plan
- Flexible vacation policy
- Lifestyle spending accounts
- More!
Pay
$165,000 USD - $195,0
for prose. We must not include boilerplate like EEO, navigation, cookie, legal, scam-warning, duplicated lines, application instructions. Also remove "Please note: As a majority of our engineering team sits in Pacific time..." that's a note about timezone preference; that's substantive? It's a preference; we could include it under Responsibilities or maybe as a note. It's not boilerplate; it's a preference. We'll keep it. We need to preserve all substantive information: that includes the note about timezone preference. We must not invent or summarize away detail. Let's extract content: About Lively paragraph: "Lively 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 about the company; we can put under About the role (or maybe a separate "About Lively" but instruction only allows certain headings; we can use About the role to include this. Then responsibilities: list under "WHAT YOU'LL DO". The responsibilities are a long list with headings like Integration Ownership, AI-Assisted Data Onboarding & Validation, Enrollment & Eligibility Data, Reliability, Data Quality & Scale, Integration Strategy, Requirements & Discovery, Partner & Implementation Enablement, Stakeholder Stewardship, Roadmap Ownership, Performance Tracking, AI Fluency in Practice, Market Awareness. Each has description. We need to output as a list (
- ) each responsibility item. Should we keep the subheadings inside each li? Probably we can include them as part of the li text, maybe bold? But we cannot add extra HTML beyond
- and
. We can include the heading as plain text inside li. Thus each li will contain the responsibility heading and its description. We need to preserve all details. Then Requirements: Required Qualifications list (bullet points). We'll output as
- each.
Then What Sets You Apart: list of preferred qualifications; we can put under Skills.
Then Benefits & Perks: list.
Then Pay: salary range.
We must not include duplicated lines, boilerplate like "We encourage you to apply even if you do not meet all of the qualifications..." that's application instruction; remove.
Also remove "Benefits & Perks" heading? We'll keep as Benefits section.
Also remove "WHY LIVELY" etc? That's promotional; but it's substantive? It's about why Lively; maybe we can incorporate into About the role? But it's not required heading; we could include as part of About the role paragraph. However it's not duplicate; we could keep as a separate paragraph under About the role.
But instruction: include a section ONLY when the posting has real, specific content for it. The "WHY LIVELY" is specific content; we could incorporate into About the role or maybe a separate section like "About Lively". Since we only have allowed headings, we could put it under About the role as well.
We must not include "Lively Inc. participates in the E-Verify program..." that's legal boilerplate; remove.
Also remove links.
Now craft HTML.
Structure:
About the role
... (company overview + why Lively)
Responsibilities
- Integration Ownership — Own the data exchanged between Lively and its partners: what moves, in what form, on what cadence, and what happens when something goes wrong. Define the contracts that both sides build against.
- AI-Assisted Data Onboarding & Validation — Own the AI agent experiences that accelerate getting partner and customer data into Lively: interpreting unfamiliar file structures, mapping fields, catching errors before they propagate, explaining what went wrong in language a non-technical administrator can act on, and recommending fixes. Define where the agent acts, where it advises, and where a human must approve.
- Enrollment & Eligibility Data — Own the enrollment data lifecycle end to end, including how changes, corrections, and exceptions are handled, and how Lively proves its records match the partner's.
- Reliability, Data Quality & Scale — Own the non-functional requirements of Lively's data integration platform: throughput, latency, availability, recovery, and the guarantee that data is never silently lost or partially applied. Define how failures are detected, communicated, and resolved. Plan capacity for the benefits industry's seasonal enrollment peaks and for growth in partner and record volume. Set the accuracy bar AI-assisted validation must clear before production use.
- Integration Strategy — Set the multi-year direction for how Lively connects to its ecosystem: the target architecture, the migration path from today's model, the role AI plays in reducing integration effort, and the build/buy/partner decisions that get us there.
- Requirements & Discovery — Translate partner needs, customer commitments, and regulatory constraints into clear, complete requirements — including the edge cases and failure paths, not only the intended flow.
- Partner & Implementation Enablement — Support the technical onboarding of new partners from specification through go-live, and reduce the time and effort each new connection takes.
- Stakeholder Stewardship — Act as the primary SME for your areas, fielding questions from implementation, customer success, sales, and leadership. Communicate vision, roadmap, and progress to internal and external audiences.
- Roadmap Ownership — Sequence complex, multi-quarter integration work into delivery milestones, balancing customer commitments, partner dependencies, and platform health.
- Performance Tracking — Define and monitor the metrics that describe integration health, onboarding effort, and AI agent accuracy, and use them to direct investment.
- AI Fluency in Practice — Use AI tooling in your own product work — research, specification, data analysis, prototyping — and raise the bar for how the product organization does the same.
- Market Awareness — Track how the benefits, payroll, and data-interoperability landscape is evolving, including where AI is changing what integration work costs, and identify partnership and standardization opportunities.
Requirements
- 5+ years of product management experience, with meaningful time owning integrations, data exchange, or platform APIs as a primary product surface
- Experience owning the exchange of structured business data between organizations — whether by file, API, or both — including the formats, cadence, and correctness guarantees each side depends on
- Demonstrated ownership of API products, including how they are designed, documented, evolved, and eventually retired without disrupting the partners built on them
- Strong judgment about data reliability at scale — you think in terms of what happens when a feed is late, incomplete, duplicated, or wrong, and you design for those cases deliberately
- Experience working directly with external technical partners — you can hold a substantive conversation with a partner's engineering team and represent Lively's position credibly without an engineer in the room
- Technical depth sufficient to be self-sufficient — you investigate data questions yourself rather than routing every one to engineering, and engineers regard your specifications as complete
- Experience handling sensitive personal or financial data under a regulated framework, with an instinct for privacy, security, and auditability
- Excellent analytical and problem-solving skills, with the ability to synthesize complex data into clear product decisions
- Outstanding communication skills — you can align engineers, partners, and executives on a shared direction
- Strong familiarity with Agile methodologies and standard product tooling
- Bachelor's degree in a technical or business field, or equivalent practical experience
Skills
- Benefits or health insurance domain experience — HSA/FSA/HRA plans, benefits compliance, IRS regulations, or the administration workflows behind them
- Ecosystem familiarity with payroll providers, HR platforms, benefits administration systems, carriers, or third-party administrators
- Fluency with industry data standards used in benefits, insurance, healthcare, or financial services exchange
- Experience modernizing a legacy integration surface — migrating partners onto a new model without breaking the old one
- Experience evaluating integration and connectivity vendors, and owning the build/buy/partner decision
- Experience building AI-powered product experiences, including designing for reliability and user trust
- Experience spanning both B2B (employer/broker-facing) and B2C (employee-facing) products
- Leadership experience, including mentoring or developing junior PMs
- Growth mindset and high self-motivation — you identify the next problem rather than waiting for it to be assigned
Benefits
- Competitive salaries
- Stock options
- Medical, dental, vision, life and disability coverage
- An HSA with employer contribution
- FSA
- Paid parental leave
- Medical travel benefits
- 401k plan
- Flexible vacation policy
- Lifestyle spending accounts
- More!
Pay
$165,000 USD - $195,0
- each.
Then What Sets You Apart: list of preferred qualifications; we can put under Skills.
Then Benefits & Perks: list.
Then Pay: salary range.
We must not include duplicated lines, boilerplate like "We encourage you to apply even if you do not meet all of the qualifications..." that's application instruction; remove.
Also remove "Benefits & Perks" heading? We'll keep as Benefits section.
Also remove "WHY LIVELY" etc? That's promotional; but it's substantive? It's about why Lively; maybe we can incorporate into About the role? But it's not required heading; we could include as part of About the role paragraph. However it's not duplicate; we could keep as a separate paragraph under About the role.
But instruction: include a section ONLY when the posting has real, specific content for it. The "WHY LIVELY" is specific content; we could incorporate into About the role or maybe a separate section like "About Lively". Since we only have allowed headings, we could put it under About the role as well.
We must not include "Lively Inc. participates in the E-Verify program..." that's legal boilerplate; remove.
Also remove links.
Now craft HTML.
Structure:
- and