Principal Product Manager - Billing

We need to output HTML fragment with sections: About the role? Actually we have sections: WHO WE ARE, WHAT YOU'LL DO, WHAT YOU'VE DONE, WHAT ADDITIONAL INFORMATION YOU MAY WANT TO KNOW, WHAT WE STAND FOR. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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 those headings appropriately. The job posting includes: WHO WE ARE (company overview) could be "About the role"? Actually "About the role" is typical heading for role description. But we have "WHO WE ARE" describing company. Could treat as "About the role"? Might be better to use "About the role" for the role description (WHAT YOU'LL DO). However we need to include sections only when posting has real, specific content. We have content for responsibilities (WHAT YOU'LL DO), qualifications/requirements (WHAT YOU'VE DONE), benefits (Duck Creek Technologies offers a comprehensive benefits package...), pay (salary ranges), schedule? Not explicit schedule but maybe flexible work environment; but schedule not given. Travel up to 20% could be schedule? Not exactly. We could include "Schedule" if there is mention of flexible work environment, remote/hybrid? It says "Flexible work environment" under benefits. Not schedule. Might skip Schedule if no explicit schedule. We need to avoid boilerplate like EEO, legal, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, privacy notice, etc. Also remove "WHAT WE STAND FOR" maybe it's EEO-like but it's about inclusion; could be considered boilerplate? It's not EEO but it's about values. Might keep as "About the role"? Not sure. The instruction: remove EEO/equal-opportunity/scam-warning boilerplate. The "WHAT WE STAND FOR" is about inclusion, diversity, equity; could be considered EEO boilerplate. Safer to remove it. Also remove "Travel: up to 20%" maybe keep as part of responsibilities? It's under WHAT ADDITIONAL INFORMATION. Could be a note about travel. Could include under Responsibilities? Might be better to include as a separate section? Not among allowed headings. Could fold into a short

under Responsibilities or Requirements. The instruction: "fold minor metadata into a short

or drop it." Travel is minor metadata; we can include in a short p under Responsibilities or Requirements. Work Authorization line: also minor metadata. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the salary ranges, benefits list, responsibilities list, qualifications list. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content. We have: - About the role: could be WHO WE ARE? Or maybe a brief description of role? The posting includes "Helping careers take flight..." that's tagline. Could treat as About the role? But we have WHAT YOU'LL DO as responsibilities. So About the role could be a brief overview: maybe combine WHO WE ARE and the introductory paragraph? But we need to avoid duplication. Let's think: The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". So we can have About the role heading with a paragraph describing the role and company. Use WHO WE ARE content (company description) as About the role? Might be okay. Responsibilities: WHAT YOU'LL DO content (list of duties). Use

  • . Requirements: maybe WHAT YOU'VE DONE (education/experience) plus Knowledge, Skills, Abilities & Behaviors. Could split into Requirements and Qualifications and Skills. But we have headings for Requirements, Qualifications, Skills. We need to decide how to map. We have: - Bachelor’s or Masters Degree and/or equivalent experience relevant to functional area - 7+ years of experience in product management within SaaS or enterprise software environments - Demonstrated experience owning complex workflow – or decision-centric product domains Then "Knowledge, Skills, Abilities & Behaviors" list: - Experience designing, building, or integrating sub-ledger or General Ledger solutions within insurance or financial services environments. - Deep understanding of P&C billing operations preferred, including invoicing, payment processing, collections, commissions, disbursements, reconciliation, and regulatory and compliance considerations; hands-on experience with billing systems preferred. - Experience delivering configurable, transaction-centric platforms, including rules-driven and AI-enabled or model-informed workflows, and translating customer needs, regulatory constraints, financial controls, and analytical outputs into governed product decisions. - Strong product management fundamentals, including the ability to decompose complex billing and payment problems into structured product capabilities, prioritize initiatives using value-, risk-, and effort-based trade-offs, and operate effectively within agile, iterative delivery models. - Proven ability to partner cross-functionally with engineering, data, architecture, finance, and business leaders, communicating clearly across technical and non-technical audiences. - Demonstrated judgment and autonomy in operating within defined strategic direction and governance frameworks, proactively identifying and surfacing risks, trade-offs, and dependencies with clear recommendations. - Strong execution discipline, including organizational rigor, professional documentation and decision rationale, accountability for commitments and outcomes, and the ability to manage ambiguity and shifting priorities in complex environments. We could treat the first bullet set as Requirements (education/experience). The Knowledge, Skills, Abilities & Behaviors as Skills (or Qualifications). Since we have headings for Requirements, Qualifications, Skills, we could allocate: - Requirements: education/experience (Bachelor/Masters, 7+ years, owning complex workflow) - Qualifications: maybe the deep understanding of P&C billing operations preferred, hands-on experience with billing systems preferred, experience delivering configurable platforms, etc. Or we could combine Qualifications and Skills. Simplify: Use Requirements for education/experience, Skills for the Knowledge, Skills, Abilities & Behaviors list. Omit Qualifications if not needed. But we need to include a section only when posting has real, specific content. We have content for both. Thus:

    About the role

    ... company overview ...

    Responsibilities

    • ... each duty ...

    Requirements

    • ... education/experience ...

    Skills

    • ... each skill ...

    Benefits

    • ... benefits list ...

    Pay

    ... salary ranges ...

    We might also include Schedule? Not present; skip. We need to preserve all substantive information: The WHO WE ARE paragraph includes many sentences; we need to keep them all. Also the WHAT YOU'LL DO paragraph includes many sentences; we need to break into list items for each duty. The posting has sentences separated by periods; we need to convert each sentence into a list item? The instruction: "Use
    • for any list of duties/requirements/benefits". So we need to extract list items. We can split by sentences that start with a verb. Let's parse WHAT YOU'LL DO: Paragraph: "The Principal Product Manager, Billing defines and evolves the product strategy for Duck Creek’s billing capabilities, ensuring solutions enable accurate premium billing, payment flexibility, direct or agency billing, operational efficiency, and financial integrity. This role owns the product roadmap for billing workflows, collections, and payment experiences and translates insurer billing practices, regulatory requirements, financial controls, and data-driven insights into scalable product capabilities. Operating as an individual contributor, this principal level role exercises significant judgment and autonomy within established product strategy and governance frameworks. The role partners closely with Engineering, Architecture, Data, Finance, and customer stakeholders to deliver governed, explainable, and compliant billing solutions. Define and own the product strategy and roadmap for Duck Creek’s billing domain, including invoicing, payment processing, commissions, collections, disbursements, reconciliation, and automation capabilities. Act as the general manager for your product, owning strategy, execution, and financial outcomes. Translate insurer billing practices, payment preferences, financial controls, and regulatory considerations into clear, prioritized product capabilities and outcomes. Provide product leadership for billing experiences that support billing accuracy, payment flexibility, collections effectiveness, and operational efficiency. Lead structured product discovery to frame complex billing, payment, and financial-operations problems in partnership with customers and internal stakeholders. Serve as the primary product steward for billing and finance personas, ensuring workflows reflect real-world operational constraints, customer obligations, and servicing needs. Provide product leadership for application-level decision-support and AI-enabled capabilities that improve payment optimization, collections prioritization, anomaly detection, and exception handling within defined controls. Partner with data science and analytics teams to integrate models, scores, and insights into billing workflows in an explainable and trusted manner. Translate billing rules, payment plan structures, commissions logic, and reconciliation requirements into configurable, scalable product capabilities, balancing automation and human oversight. Guide adoption of straight-through processing while ensuring transparency, exception handling, and appropriate escalation paths. Ensure billing workflows, financial transactions, and recommendations are auditable, compliant, and aligned with internal and external governance requirements. Partner with Engineering and Architecture to ensure billing capabilities are technically sound, scalable, and aligned with platform standards. Collaborate with Product Marketing, Sales, Finance stakeholders, and Professional Services to support value articulation, enablement, and consistent product positioning." We need to make each sentence a
    • . Ensure we keep all details. Similarly for Requirements: bullet list: - Bachelor’s or Masters Degree and/or equivalent experience relevant to functional area - 7+ years of experience in product management within SaaS or enterprise software environments - Demonstrated experience owning complex workflow – or decision-centric product domains We'll make each a
    • . Skills list: each bullet from Knowledge, Skills, Abilities & Behaviors. Benefits list: from "Duck Creek Technologies offers a comprehensive benefits package, which includes:" then list items: - Flexible work environment - Medical, dental, vision, life, and disability insurance - 401(k) retirement plan with match (6% employer match up to $12,000 annually) - Flexible Spending Accounts (FSA) and Health Savings Accounts (HSA) - Paid holidays, vacation, and volunteer time - Employee Assistance Program (EAP) - Benefits eligibility and offerings may vary based on role and location. We need to keep the last sentence as a list item? It's a note; could be a
    • as well. Pay: we have salary ranges per location and Canada. Need to preserve all detail. We'll put in a

      maybe with multiple sentences. We also have "This position is also eligible for annual bonus compensation, subject to plan terms and individual eligibility." and "Final compensation will be determined based on the factors outlined above and in accordance with applicable law." Keep those. We need to remove boilerplate: The sections about AI usage in recruitment, EEO, etc. Also "WHAT WE STAND FOR" and following inclusive culture statement, privacy notice, accessibility, etc. Also "The application window for this position will remain open until the role is filled or a sufficient number of qualified candidates have been identified." That's application instructions; remove. Also "Please let us know if you encounter accessibility barriers..." remove. Also "Privacy Notice: By submitting your application..." remove. Also "Duck Creek Technologies does not accept