Senior Product Manager – Semantic Insurance Data - Remote

We need to output HTML fragment with sections: About the role? Actually the posting includes "WHO WE ARE" and description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content. We need to extract content. We have "WHO WE ARE" description: that could be About the role? Actually "About the role" maybe corresponds to description of role? But we have "What You’ll Do" which is responsibilities. Also "WHAT YOU’VE DONE" is requirements/qualifications. Also "Knowledge, Skills, Abilities & Behaviors" is skills. Also "Work Environment & Other Requirements" includes travel, work authorization. Also compensation details: Pay section includes salary range and bonus. Also schedule: flexible-first environment, work from office/home/hybrid. So we can include Schedule. Benefits: Not explicitly listed besides flexible work environment? There's no explicit benefits like health, 401k. So we should not create Benefits section unless posting actually states them. It does not list benefits. So omit Benefits. We need to avoid repeating job title as heading. The title is "Senior Product Manager – Semantic Insurance Data". Not to be used as heading. We need to include sections: About the role (maybe from WHO WE ARE? Actually that's about company, not role. But we could treat "About the role" as summary of role? The posting includes "What You’ll Do" as responsibilities. There's no explicit "About the role" paragraph besides maybe the introductory fluff "Helping careers take flight...". That's more about company. Could we put that under About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role with content from the introductory paragraph about the company and role? The posting says "Helping careers take flight. Reshaping an industry. Enable your career to be Made on Duck Creek." Then WHO WE ARE. That's about company. Might be appropriate for About the role? Usually About the role is description of the role, but we don't have that separate; we have What You’ll Do. However we could still include About the role with the WHO WE ARE content (company overview). It's substantive. Responsibilities: from "What You’ll Do" bullet-like paragraphs. Requirements: maybe combine Required education/experience? The posting has "WHAT YOU’VE DONE: Required Bachelor’s degree..." and then list of required experience. That's qualifications. Could split into Requirements (hard requirements) and Qualifications (preferred). But we have both Required and Preferred. We could put Requirements for required, Qualifications for preferred. Or combine. The instruction: use sections as needed. We'll include Requirements (required) and Qualifications (preferred). Skills: from Knowledge, Skills, Abilities & Behaviors. Pay: from compensation details. Schedule: from Work Environment & Other Requirements (flexible-first, travel 10%, work authorization). Also schedule includes flexible work options. We must not include boilerplate like EEO, legal, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like bullet points? We'll convert to

• . For prose, use

  . We need to ensure we don't create sections with filler like "commensurate with experience". Not present. Let's extract content. WHO WE ARE paragraph: "Helping careers take flight. Reshaping an industry. Enable your career to be Made on Duck Creek. WHO WE ARE: Duck Creek Technologies is the intelligent solutions provider defining the future of the property and casualty (P&C) and general insurance industry. We are the platform upon which modern insurance systems are built, enabling the industry to capitalize on the power of the cloud to run agile, intelligent, and evergreen operations. Our modern SaaS solutions help insurers set a new standard and revolutionize how consumers interact with insurance companies. Authenticity, purpose, and transparency are core to Duck Creek, and we believe insurance should be there for individuals and businesses when, where, and how they need it most. Our market-leading solutions are available on a standalone basis or as a full suite, and all are available via Duck Creek OnDemand. With more than 1,000 successful implementations to date, Duck Creek removes the IT burden for insurers so they can focus on the business of insurance. We have a flock of more than 1,700 employees across the globe and are proud to be a Flexible-First employer. We empower our employees with the choice to work from an office, from home, or on a hybrid schedule. Our flexible-first environment fosters productivity, inclusion, collaboration, and ensures a consistent employee experience regardless of location. If working in a fast-paced, rapidly evolving company that is transforming one of the world’s oldest and largest industries sounds exciting, let us know. We are excited you are considering Duck Creek as a future employer and hope you decide to join “The Flock”! To learn more about us, visit www.duckcreek.com and follow us on our social channels for the latest information – LinkedIn and Twitter." We may want to trim the social media invitation? It's not boilerplate? It's promotional but still part of WHO WE ARE. It's substantive? Might be considered boilerplate? It's not legal/EEO. It's okay to keep. Now Responsibilities: "What You’ll Do" paragraph(s). It's a long paragraph with many sentences. We'll keep as prose maybe break into

  . Could also bullet list but it's not explicitly bullet. We'll keep as

  . Requirements (Required): "WHAT YOU’VE DONE: Required Bachelor’s degree, or equivalent experience, in Computer Science, Information Systems, Data Management, Business, Insurance, Analytics, or a related discipline.6+ years of experience in product management, technical product management, data product management, enterprise software, SaaS, insurance technology, data platforms, or related roles.Experience owning complex product domains that require alignment across business stakeholders, engineering teams, architects, data teams, and customer-facing organizations.Experience translating ambiguous business, regulatory, and technical problems into product strategy, roadmap priorities, requirements, and measurable outcomes.Experience working with data products, data platforms, semantic layers, canonical data models, APIs, metadata, data governance, analytics, AI/ML products, or enterprise integration patterns.Experience in property and casualty insurance, general insurance, InsurTech, financial services, or another complex regulated industry." Note there is missing space after period before "6+ years". We'll keep as is. Qualifications (Preferred): "Preferred Master’s degree, or equivalent experience, in Computer Science, Information Systems, Data Management, Business, Insurance, Analytics, or a related discipline.Experience across multiple property and casualty insurance domains such as underwriting, policy, claims, billing, distribution, reinsurance, or customer servicing.Experience with insurance industry software platforms and software-as-a-service solutions.Experience with agile development methodologies and product or project management tools.Experience with data governance frameworks, semantic modeling practices, or enterprise information models." Skills: "Knowledge, Skills, Abilities & Behaviors Advanced knowledge of technical product management practices, including roadmap definition, prioritization, requirements development, and success measurement.Deep understanding of property and casualty insurance business concepts, workflows, and data relationships.Knowledge of insurance concepts such as policy, claim, coverage, insured, exposure, premium, deductible, limit, endorsement, exclusion, loss event, payment, reserve, and party relationships.Understanding of semantic modeling, ontology concepts, metadata management, knowledge graphs, canonical models, data catalogs, data contracts, or enterprise information models.Knowledge of AI, LLMs, retrieval-augmented generation, agentic workflows, analytics, and automation consumption patterns.Understanding of SaaS platforms, data architectures, APIs, event-driven systems, cloud platforms, and modern software delivery practices.Ability to translate complex insurance, data, regulatory, and technical requirements into structured product capabilities.Ability to define business meaning, data relationships, consumption patterns, and quality expectations for reusable data products.Ability to assess data quality, lineage, completeness, consistency, and fitness for use in AI, analytics, and automation contexts.Ability to prioritize competing stakeholder needs and make product trade-offs in ambiguous environments.Ability to influence cross-functional teams and build alignment without direct reporting authority.Ability to communicate complex data and AI concepts to business, technical, and executive stakeholders.Ability to use AI and LLM tools to support product discovery, research, requirements development, documentation, and stakeholder communication.Ability to evaluate adoption, reuse, quality, and business impact measures for semantic data products." Work Environment & Other Requirements: "Travel: 10% Work Authorization: Must be legally authorized to work in the country of the job location" Also flexible-first environment already mentioned in WHO WE ARE. But schedule: we can include flexible work options. Pay: "Actual compensation for this role is determined based on a variety of factors, including job-related skills, experience, qualifications, internal equity, and geographic location, where permitted by law. For reference, the expected salary range for this position is generally positioned as follows based on candidate location: 153,900 – 219,800: Candidates living in the Boston, New York City–Newark, Los Angeles, San Francisco/Bay Area, Seattle, or Washington, DC metropolitan areas146,700 – 209,500: Candidates living in Chicago, Dallas–Fort Worth, Houston, Minneapolis, or Philadelphia metropolitan areas, or in Colorado, Connecticut, Maryland, Rhode Island, or Vermont139,400 – 199,100: Candidates living in Georgia, Michigan, North Carolina, New Hampshire, Oregon, or Wisconsin123,400 – 192,900: For all other U.S. locations This position is also eligible for annual bonus compensation, subject to plan terms and individual eligibility. Final compensation will be determined based on the factors outlined above and in accordance with applicable law." We need to keep that. We must not include the AI-assisted tools paragraph at end (the last part about AI tools). That's boilerplate? It's about recruitment process; maybe we should remove as it's not substantive to the role. It's near end: "Duck Creek Technologies believes in the safe, ethical, and responsible use of artificial intelligence. We may use AI-assisted tools to support parts of the recruitment process, such as reviewing applications, identifying relevant skills, and organizing candidate information. AI tools are used to assist—not replace—h". That's likely boilerplate; we should remove. Also remove "Please let us know if you encounter accessibility barriers..." etc. That's legal/EEO? It's accessibility statement; could be considered boilerplate; better to remove. Also remove "Privacy Notice: By submitting your application..." etc. Remove. Also remove "WHAT WE STAND FOR:" and following DEI statement. That's likely boilerplate; remove. Also remove "To learn more about our inclusive company culture..." etc. Remove. Also remove "Duck Creek Technologies does not accept, nor will we pay a fee for any hires resulting from unsolicited headhunter or agency resumes." That's boilerplate; remove. Also remove "Actual compensation for this role is determined..." we kept that as Pay. Now we need to output HTML fragment only. Structure:

  About the role

  ... (WHO WE ARE content)

  Responsibilities

  ... (What You’ll Do)

  Requirements

  ... (Required bullet list? We'll keep as prose but could break into

  • for each requirement. The instruction: Use
    • for any list of duties/requirements/benefits. So we should convert the required experience list into a list. The required section includes multiple items separated by periods. We'll split into list items. Similarly for Qualifications (Preferred) we can