Principal Product Manager - Billing
About the company
with paragraph. However they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't list About the company but we could still use About the role? Probably better to map: "WHAT YOU’LL DO" -> Responsibilities. "WHAT YOU’VE DONE" -> Requirements/Qualifications. "WHAT ADDITIONAL INFORMATION YOU MAY WANT TO KNOW" includes Travel, Work Authorization, Compensation (Pay), Benefits. Also maybe "Schedule"? Not present. So we can have sections: Responsibilities, Requirements, Pay, Benefits, and maybe About the company (optional). The instruction: Prefer a few substantive sections over many thin ones. So we could combine Travel and Work Authorization into a short paragraph under Additional Info? But they said include a section ONLY when posting has real, specific content for it. Travel and Work Authorization are specific. Could put them under a section "Additional Information". But they didn't list that as a standard heading; but we could still useAdditional Information
. However they gave examples of headings but not exclusive. Probably okay to use Additional Information. We must not include Pay/Schedule/Benefits unless posting actually states them. It does state compensation ranges and benefits. So we can have Pay and Benefits sections. We must not repeat the job title as heading. So noPrincipal Product Manager- Billing
. We must not put Job ID/requisition numbers as headings. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like responsibilities bullet points, qualifications bullet points, compensation ranges per location, benefits list. We need to use- for any list of duties/requirements/benefits, and
for prose. We need to output ONLY the HTML fragment, no /, no markdown fences. Let's extract content. Company description: "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,500 employees across the globe and are proud to be a flexible-first company—an approach that remains foundational to how we work. We empower our employees with the flexibility to manage their day-to-day work, while taking a more intentional approach to how teams come together. Through our Flying Together initiative, we are building stronger connection and collaboration by bringing teams together for meaningful in-person moments and concentrating on our presence and hiring in key locations. Our flexible-first environment continues to support productivity, inclusion, and collaboration, while evolving to create even more opportunities for connection and shared experiences across teams. 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 can keep that as About the company paragraph(s). Might be long but okay. Responsibilities (WHAT YOU’LL DO): list of bullet points. Let's extract each sentence that starts with a verb. "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 can turn each sentence into a
- . Might be many but okay. Requirements (WHAT YOU’VE DONE): 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 Knowledge, Skills, Abilities & Behaviors 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 can treat each bullet as
- . The "Knowledge, Skills, Abilities & Behaviors" is a heading inside but we can ignore or treat as part of list? Probably we can keep as a
- heading? Better to treat as a
- with bold? But we just need to output list items; we can keep that line as a
- but it's not a bullet. Might be okay.
Additional Information: Travel: up to 20%; Work Authorization: Legally authorized to work in the country of job location. The Company does not sponsor visa petitions for this position. Actual compensation ... includes salary ranges per location, bonus eligibility, benefits.
We need Pay section: include salary ranges. Should we list them as
- each location range? Could be a paragraph with the ranges. The instruction: use
- for any list of duties/requirements/benefits. Pay is not a list but could be presented as
. However we could also make a list of location ranges. Safer to use
for prose. Benefits: list of benefits. We must not include boilerplate like EEO etc. So we omit "WHAT WE STAND FOR" and following. Also remove "Helping careers take flight..." maybe keep as part of About the company. Let's craft HTML:
About the Company
Helping careers take flight. Reshaping an industry. Enable your career to be Made on Duck Creek. 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,500 employees across the globe and are proud to be a flexible-first company—an approach that remains foundational to how we work. We empower our employees with the flexibility to manage their day-to-day work, while taking a more intentional approach to how teams come together. Through our Flying Together initiative, we are building stronger connection and collaboration by bringing teams together for meaningful in-person moments and concentrating on our presence and hiring in key locations. Our flexible-first environment continues to support productivity, inclusion, and collaboration, while evolving to create even more opportunities for connection and shared experiences across teams. If working in
- for any list of duties/requirements/benefits. Pay is not a list but could be presented as
- each location range? Could be a paragraph with the ranges. The instruction: use