Product Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections to include based on content.
We have:
- About The Role: prose description.
- Who You Are: list of traits (Data-Driven, Technically Proficient, etc.) Could be considered Qualifications or Skills. Might be better as Qualifications (since they are desired attributes). Or Skills.
- What We Need: list of duties (Gain a deep understanding..., Create buy-in..., etc.) That's responsibilities.
- Requirements: list of bullet points (Minimum of 5 years..., Familiarity..., Experience..., Experience..., Strong analytical...). That's requirements.
- Benefits: list.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (or Skills), Benefits.
We need to avoid repeating job title as heading. No Job ID.
We must not include filler like "commensurate with experience". Not present.
We must output only HTML fragment.
We'll structure:
About the role
... (the prose from About The Role)
Responsibilities
- ... each item from What We Need
Requirements
- ... each from Requirements
Qualifications
- ... each from Who You Are Benefits
- ... each from Benefits
- Gain a deep understanding of customer experience, identify and fill product gaps and generate new ideas that grow market share, improve customer experience and drive growth
- Create buy-in for the product vision both internally and with key external partners
- Develop product pricing and positioning strategies
- Translate product strategy into detailed requirements and prototypes
- Scope and prioritize activities based on business and customer impact
- Work closely with engineering teams to deliver with quick time-to-market and optimal resources
- Drive product launches including working with public relations team, executives, and other product management team members
- Evaluate promotional plans to ensure that they are consistent with product line strategy and that the message is effectively conveyed
- Act as a product evangelist to build awareness and understanding
- Represent the company by visiting customers to solicit feedback on company products and services
- Support the product function globally
- Minimum of 5 years of experience in product management, with a focus on data-driven products, ideally in the insurance or financial services industry.
- Familiarity with data architecture, data management, and analytics platforms, with a proven ability to work closely with engineering teams.
- Experience managing products in an Agile environment, including writing user stories, managing backlogs, and facilitating sprint planning sessions.
- Experience in managing end-to-end product life cycles, including developing and prioritizing product roadmaps and ensuring alignment with business goals.
- Strong analytical and critical thinking skills, with the ability to make
maybe under Benefits? But it's not a benefit; it's a statement. Could be included as a
after Benefits? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include that diversity statement somewhere. It's not under a heading; we could put it as a
after Benefits or before. Since we have no specific section for it, we could just add a
after Benefits (or before). The instruction says to use
for prose. So we can add a
containing that statement. Also there is a location requirement paragraph: "Location Requirement Candidates must reside in an eligible U.S. state throughout employment. We are unable to hire candidates residing in California, Alaska, Hawaii, U.S. territories, or outside the United States." That's substantive; we need to include it. Could be a
maybe under a heading? There's no heading for location; but we could include as a
after Benefits or before. Since no specific section, we can just add a
. Also there is an opening paragraph about Reserv: "About Reserv Reserv is an insurtech creating and incubating cutting-edge AI and automation technology to bring efficiency and simplicity to claims. Founded by insurtech veterans with deep experience in SaaS and digital claims, Reserv is venture-backed by Bain Capital and Altai Ventures and began operations in May 2022. We are focused on automating highly manual tasks to tackle long-standing problems in claims and set a new standard for TPAs, insurance technology providers, and adjusters alike. We have ambitious (but attainable!) goals and need people who can work in an evolving environment. If building a leading TPA and the prospect of tackling the long-standing challenges of the claims role sounds exciting, we can't wait to meet you." That's substantive; we should include it as a
maybe before About the role? Since we have About the role heading, we could put that as a
under About the role? But About the role heading is for role description; the company overview could be separate. However instructions: 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 only use those headings when we have content. We could add a About Reserv? Not in list. Better to keep as a
before the About the role heading, as prose. Thus final HTML:
About Reserv Reserv is an insurtech creating and incubating cutting-edge AI and automation technology to bring efficiency and simplicity to claims. Founded by insurtech veterans with deep experience in SaaS and digital claims, Reserv is venture-backed by Bain Capital and Altai Ventures and began operations in May 2022. We are focused on automating highly manual tasks to tackle long-standing problems in claims and set a new standard for TPAs, insurance technology providers, and adjusters alike. We have ambitious (but attainable!) goals and need people who can work in an evolving environment. If building a leading TPA and the prospect of tackling the long-standing challenges of the claims role sounds exciting, we can't wait to meet you.
About the role
As the Senior Product Manager, Data at Reserv, you will be at the forefront of driving the development and innovation of our data-centric products. Working at the intersection of business, technology, and customer experience, you will be responsible for managing data products that support our insurance services and operations. You will lead the strategy, execution, and delivery of data solutions, leveraging insights to improve decision-making, enhance operational efficiency, and provide value to our customers. In this role, you will collaborate closely with engineering, data science, operations, and business teams to ensure our data products align with the company’s goals. You will oversee the product lifecycle, from gathering requirements to launching new features, and continuously optimize product performance to meet evolving market needs.