Senior Product Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for lists,

  for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate. Include only sections with real content. We need to parse the posting. Key info: - About Vertical Insure: description of company, location, hybrid model, etc. That's "About the role" maybe? Actually "About the role" could be description of role and company. We'll put a section "About the role" with prose summarizing company and role. - Why This Role Matters: could be part of About the role or separate? Could be part of About the role. We'll combine. - What You'll Do: list of responsibilities. So "Responsibilities" section with bullet list. - Who You Are: qualifications/experience. Could be "Requirements" or "Qualifications". We'll separate: maybe "Requirements" for mandatory experience, "Qualifications" for preferred? But we have "Who You Are" includes required experience and skills. Also "Experience That Goes the Extra Mile" is preferred/nice-to-have. Could treat as "Skills" or "Preferred Qualifications". We'll create sections: "Requirements" (mandatory), "Preferred Qualifications" (extra mile), "Skills" maybe overlapping. But instruction: prefer few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one "Requirements" section, and maybe "Skills" separate? However we have "Experience That Goes the Extra Mile" which is nice-to-have; could be part of "Qualifications". We'll create sections: "About the role", "Responsibilities", "Qualifications", "Benefits", "Pay", "Schedule". Possibly also "Skills" but we can incorporate skills into Qualifications. We must not create sections with filler like "commensurate with experience". We have actual content for Pay: salary range $120k-$160k. Benefits: comprehensive benefits package listed. Schedule: hybrid model: in-office Tuesdays and Thursdays, Minneapolis, local candidates only. Thus we have content for Benefits, Pay, Schedule. Now we need to extract specifics: About the role: combine company description and role purpose. From posting: "Sr. Product Manager About Vertical InsureLocation: Minneapolis, MN (Hybrid - in office Tuesdays and Thursdays) Vertical Insure is the leading embedded insurance platform built for vertical SaaS platforms. We offer customized insurance options tailored to each business and its customers, adding value and generating new revenue without extra overhead. Our approach is simple; we are removing the burden from buying insurance by embedding it into our partners’ existing product flow making financial protection effortless and timely. The Senior Product Manager owns one or more of our insurance verticals for their whole life: the protection products live today, the software partners who embed them, and the next products and channels that make each vertical bigger. This role sits on the Product team and works across Sales, Strategic Business Development, Implementation, Marketing, Engineering, and our Insurance team.Our Minneapolis office operates on a hybrid model, with in-office collaboration on Tuesdays and Thursdays. At this time, we're only considering local candidates. Why This Role MattersOur partners are software platforms, and each one lives inside a vertical we have to understand as well as they do. That means how the platform goes to market, what value it delivers to its customers, where an insurance product adds to that value, and how to help the platform explain that value to its own customers. In Events, that is knowing why a venue management platform cares about certificates of insurance, and being able to hand its sales team the words that make a wedding venue want the offer turned on. The Senior Product Manager is the company's domain expert for the verticals they own. Sales, Marketing, Implementation, and Insurance all look to this person for the answer on how the vertical works and why partners say yes or no." We'll turn that into prose. Responsibilities: from "What You'll Do" bullet points (though not bullet in text but paragraphs). We'll extract each bullet as list items. What You'll Do sections: - Vertical Ownership - Own the scorecard for each vertical you carry: revenue, attach and conversion rates, partner activations, and margin - Set the vertical roadmap and the reasoning behind it, and manage change across the company as priorities move - Maintain the vertical playbook: coverage types and carriers, channel nuances, partner history, test results, and the reasons behind past decisions - Domain and Partner Expertise - Learn how the platforms in your vertical go to market, what their customers pay them for, and where an insurance offer fits their workflow - Know the distinct buyers inside a vertical and the moment each one feels the exposure - Give Sales, Product Marketing, and partners the product detail, buyer problems, and value narratives they need to sell the offer to their own customers - Product-Market Fit Discovery - Partner with the Insurance team to define underwriting requirements, coverage structure, pricing assumptions, and constraints for new and existing insurance products - Actively gather and synthesize feedback from sales, implementation, partners, clients, carriers, claims, and end customers - Iterate on product design and positioning based on market signals, performance data, and qualitative feedback - Conversion and Growth - Leverage Testing & Optimization best practices to run experiments on offer placement, pricing, packaging, and messaging, and ship what wins - Find where a required or optional offer converts in a partner's workflow and design pragmatic embedded integrations for it - New Products and Partners - Take new product types from candidate to live: success metrics, launch criteria, and go-to-market readiness - Prototype and validate offer experiences quickly using AI-assisted design and prototyping tools - Work with Engineering to identify platform gaps a new product or channel exposes, and decide when new functionality is required versus configured - Own the product relationship with platform partners and support Strategic Business Development in partner evaluations We'll turn each bullet into

• . Qualifications: from "Who You Are" and maybe "Experience That Goes the Extra Mile". We'll separate mandatory vs preferred? But we can combine into Qualifications with bullet list. Who You Are: - 8+ years of product management experience in B2B or B2B2C SaaS, with time owning a product line or business unit end to end - Able to learn a new industry quickly and speak its language with people who have worked in it for twenty years. You will do this more than once - Track record of growing a live product through conversion, pricing and packaging, and experimentation, and the judgment to know when customer conversations beat the A/B test - Comfortable with unit economics; you can talk attach rate, take rate, and loss ratio with Finance and with a carrier - Ability to thrive in an ambiguous environment and make informed decisions based on partial data, balancing experimentation with business goals - Proven track record of successfully managing and influencing diverse stakeholders, including C-level executives, both internal and partners - Excellent written and verbal communication skills to effectively convey complex ideas to both technical and non-technical audiences Experience That Goes the Extra Mile (preferred): - Event technology, venue management, ticketing, or rental management software - Insurtech, embedded insurance, or fintech, especially products sold inside someone else's checkout - Channel or partner-led go-to-market, where a third party sells or explains your product to their own customers - An active insurance producer license, or willingness to obtain one - Product analytics (Mixpanel, Amplitude, Heap, Pendo, or similar) and proficiency with data (SQL, reporting tools) We'll include these as bullet list under Qualifications (maybe separate sections: Requirements and Preferred Qualifications). But to keep few sections, we could have one Qualifications section containing both required and preferred, but we could label within list? Better to split: Requirements (mandatory) and Preferred Qualifications (nice-to-have). That's two sections, still okay. But we also have Skills maybe overlapping; we could incorporate skills into Qualifications. Thus sections: About the role, Responsibilities, Requirements, Preferred Qualifications, Benefits, Pay, Schedule. Check if any section missing content: Benefits: "We offer a comprehensive benefits package, including health, dental, life insurance, gym membership, flexible PTO, 401(k), and more." That's concrete. Pay: "The estimated base salary for this role is: $120,000 - $160,000 per year. Salary will be dependent on the level of experience, job-related knowledge, and skills." Schedule: "Our Minneapolis office operates on a hybrid model, with in-office collaboration on Tuesdays and Thursdays. At this time, we're only considering local candidates." Also location: Minneapolis, MN (Hybrid - in office Tuesdays and Thursdays). We'll include location in schedule or about role? Probably schedule section includes hybrid model and location. Now produce HTML fragment. We must not include or . Just the fragment. We'll do:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  ...

  Preferred Qualifications

  ...

  Benefits

  ...
  (or

  but list is fine)

  Pay

  ...

  Schedule

  ...

  Make sure to preserve all substantive info, no invention. Let's craft prose for About the role: combine company description and role purpose. We'll write: Vertical Insure is the leading embedded insurance platform built for vertical SaaS providers, offering customized insurance options that add value and generate revenue for partners without extra overhead. The Senior Product Manager owns one or more insurance verticals end‑to‑end — overseeing live protection products, the software partners that embed them, and the next products and channels that grow each vertical. This role sits on the Product team and collaborates with Sales, Strategic Business Development, Implementation, Marketing, Engineering, and the Insurance team. The Minneapolis office follows a hybrid model (in‑office Tuesdays and Thursdays) and the company is currently considering only local candidates. That seems good. Now Responsibilities list: we need to capture each bullet. We'll produce list items exactly as described. We'll need to ensure we don't lose any detail. Let's list them: Vertical Ownership: - Own the scorecard for each vertical you carry: revenue, attach and conversion rates, partner activations, and margin - Set the vertical roadmap and the reasoning behind it, and manage change across the company as priorities move - Maintain the vertical playbook: coverage types and carriers, channel nuances, partner history, test results, and the reasons behind past decisions Domain and Partner Expertise: - Learn how the platforms in your vertical go to market, what their customers pay them for, and where an insurance offer fits their workflow - Know the distinct buyers inside a vertical and the moment each one feels the exposure - Give Sales, Product Marketing, and partners the product detail, buyer problems, and value narratives they need to sell the offer to their own customers Product-Market Fit Discovery: - Partner with the Insurance team to define underwriting requirements, coverage structure, pricing assumptions, and constraints for new and existing insurance products - Actively gather and synthesize feedback from sales, implementation, partners, clients, carriers, claims, and end customers - Iterate on product design and positioning based on market signals, performance data, and qualitative feedback Conversion and Growth: - Leverage Testing & Optimization best practices to run experiments on offer placement, pricing, packaging, and messaging, and ship what wins - Find where a required or optional offer converts in a partner's workflow and design pragmatic embedded integrations for it New Products and Partners: - Take new product types from candidate to live: success metrics, launch criteria, and