Director of Data Analytics (P&C Insurance, Underwriting, Reinsurance)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to extract content from posting. We need to avoid repeating job title as heading; not include Job ID etc. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "Join us and Create A Better Future For Yourself!" maybe considered boilerplate? It's a tagline but not essential? Might be considered promotional; but we can keep if it's substantive? Probably it's fluff; better to drop. We need to preserve all substantive information: description, duties, qualifications, education & experience, physical demands, work environment, success in first 12 months, salary range, benefits details. We need to map to sections: About the role (maybe overview), Responsibilities (essential duties), Requirements (maybe qualifications), Skills (maybe specific skills), Benefits, Pay, Schedule. We need to decide which sections to include based on content. Let's parse posting: - Description Department: Church Insurance Job Type: Regular Full Time Education Level: BA/BS or combination of education and experience Required Years Experience: 10 - Then paragraph about CIC. - Then "We are seeking a proactive, business-minded Director of Data Analytics / Data Scientist to partner with management..." That's about role. - Then "ESSENTIAL DUTIES AND RESPONSIBILITIES include the following. Other duties may be assigned." Then list of duties with subheadings: Rate making & Rate Indications, Reserving & Reserve Indications, Reinsurance Renewal & Structure, Cause of Loss & Trend Studies, Reporting & Ad-Hoc Analysis, Communication & Implementation. - Then "Effective performance of the essential functions of this position requires regular in-person, on-site interaction with colleagues, both for purposes of relationship building and meaningful collaboration" - Then "Qualifications" heading with bullet list of qualifications. - Then "Education & Experience" heading with details. - Then "PHYSICAL DEMANDS" and "WORK ENVIRONMENT". - Then "Success In The First 12-months Will Look Like" with bullet list. - Then "Salary Range: $150,000 - $175,000" - Then "Join us and Create A Better Future For Yourself!" (maybe tagline) - Then "Flexible Benefits Available To Eligible Employees" list of benefits. - Then "Core Benefits Automatically Provided To Eligible Employees" list. - Then "Elective Benefits Available To Eligible Employees" list. - Then other boilerplate about discretionary annual incentive, verification, visa sponsorship, EEO. We need to remove boilerplate: EEO, visa, verification, discretionary annual incentive maybe considered not boilerplate? It's about compensation but could be considered part of benefits? Might keep as part of Benefits? But it's about incentive program; could be included under Benefits or Pay? Probably better to include under Benefits as "Discretionary annual incentive program". However the instruction: remove EEO/equal-opportunity/scam-warning boilerplate. The discretionary annual incentive is not EEO; it's a benefit. Might keep. But we need to avoid filler like "commensurate with experience", "not specified", etc. We have specific salary range, so we can include Pay section. Schedule: we have hybrid work environment: Tues-Thurs in office, flexibility remote Mon/Fri. That's schedule info. Benefits: we have detailed list. We need to avoid duplication: The "Flexible Benefits Available To Eligible Employees" and "Core Benefits" and "Elective Benefits" are all benefits; we can combine into a Benefits section with sublists? But we must use

• for any list of duties/requirements/benefits. So we can have a Benefits section with
  • items. Could categorize but not required. We need to preserve all substantive information: So we need to include all benefit items listed. Let's extract benefit items: Flexible Benefits Available To Eligible Employees: - Medical (including Vision) - Dental Core Benefits Automatically Provided To Eligible Employees: - Employer funded defined benefit pension plan (five year vesting) - Employee Life Insurance - Spouse and Dependent Life Insurance - Accidental Death and Dismemberment (AD&D) Insurance - Short-Term Disability (STD) coverage - Long-Term Disability (LTD) coverage (elected as either pre-tax or after-tax) - Business Travel Accident Insurance - Worker’s Compensation - Employee Assistance Program - Retiree health insurance (eligible after 10 years) - Retiree life insurance Elective Benefits Available To Eligible Employees: - 401(k) with matching contributions (immediate vesting) - Flexible Spending Accounts (FSAs) - Commuter Benefits - Educational Assistance Program available to eligible employees - Parental Leave available to eligible employees - Time Off available to eligible employees: Vacation, Sick, Personal and Holidays Also discretionary annual incentive program: "You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance." We'll include that as a benefit item. Now responsibilities: we need to list each duty as
  • . The duties are grouped under headings; we can either keep headings inside responsibilities? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have a section

    Responsibilities

    and then a
    • for each duty. We should not repeat the subheadings like "Rate making & Rate Indications" as headings inside? Could we keep them as part of the liability text? Probably we can include them as part of the
    • content, preserving the detail. So each
    • can contain the heading bold? But we cannot use markdown; we can just include plain text. Eg:
    • Rate making & Rate Indications: Produce overall and by-segment rate indications for personal and commercial lines, covering loss/premium trend, development, credibility, and expenses. Support classification ratemaking and develop rating factors using standard actuarial approaches. Prepare rate summary exhibits for communicating the proposed rate level need and findings to Company management. Be able to justify and defend proposed rate levels
    Similarly for others. We also have the line about effective performance requiring regular in-person interaction; that could be a responsibility as well. Now Requirements vs Qualifications vs Skills: The posting has "Qualifications" and "Education & Experience". We could map Qualifications section to Requirements? Or we could have both Requirements and Qualifications sections. But we need to avoid thin sections. Let's think: The posting includes a "Qualifications" bullet list (demonstrated production..., hands-on experience..., exposure..., Expert Excel..., Experience with BI/visualization tool..., P&C fundamentals..., Standard ratemaking..., U.S. state rate filing..., Reinsurance structures..., Capital frameworks..., Proactive..., Excellent communication..., Strong business acumen..., High integrity...). Then "Education & Experience": 10+ years..., Bachelor’s preferred... We could combine these into a single "Requirements" section (or "Qualifications") that includes both bullet lists. Or we could have separate sections: Requirements (maybe education & experience) and Qualifications (skills). But to avoid many thin sections, we can have one section "Requirements" containing all qualification and education details. Similarly "Skills" could be extracted from qualifications (expert Excel, BI tool, etc.) but we already have them in qualifications. Might not need separate Skills section. Thus we will have sections: About the role (overview), Responsibilities, Requirements, Benefits, Pay, Schedule. We need to ensure we don't create sections with filler. All have content. Now we need to write HTML fragment. Let's draft:

    About the role

    For more than 90 years, The Church Insurance Companies (CIC) has focused on providing The Episcopal Church with broad, cost-effective property and casualty coverage, as well as unique risk management strategies and tools. This team takes a disciplined, financially sustainable, and hands-on approach. We are seeking a proactive, business-minded Director of Data Analytics / Data Scientist to partner with management in turning policy, premium, and loss data into decisions on pricing, reserving, reinsurance, capital, and underwriting. The role owns the end-to-end workflow: mining data, building rate and reserve indications, supporting reinsurance renewals, evaluating capital adequacy, collaborating with consulting actuaries, and presenting to executives. This is a highly visible individual contributor role that is designed for a hands-on expert who wants to drive significant business impact.

    Then Responsibilities:

    Responsibilities

    • Rate making & Rate Indications: Produce overall and by-segment rate indications for personal and commercial lines, covering loss/premium trend, development, credibility, and expenses. Support classification ratemaking and develop rating factors using standard actuarial approaches. Prepare rate summary exhibits for communicating the proposed rate level need and findings to Company management. Be able to justify and defend proposed rate levels
    • Reserving & Reserve Indications: Maintain reserving triangles by line and accident year; produce quarterly and ad-hoc indications using chain-ladder, Bornhuetter-Ferguson, expected loss ratio, and frequency-severity methods. Analyze reserve adequacy and movement, explaining variances in business language. Partner with claims on case reserve philosophy, large losses, and claim-handling shifts.
    • Reinsurance Renewal & Structure: Own the data workstream for the annual renewal: in-force listings, premium/exposure, loss runs, large loss detail, and cat model output. Respond to reinsurer questions and data calls, working with brokers, underwriting, claims, and finance. Evaluate alternative structures (quota share, per-risk excess, aggregate, cat XOL) across attachments, limits, and cede percentages.
    • Cause of Loss & Trend Studies: Run cause-of-loss studies (water, theft, wind/hail, BI, auto physical damage) to identify frequency and severity drivers. Quantify effects of inflation, weather, legal environment, social inflation, and repair/medical costs. Translate findings into action on underwriting, coverage forms, deductibles, and rating plans.
    • Reporting & Ad-Hoc Analysis: Maintain recurring reports on loss/combined ratios, production, retention, rate change, and profitability by program, state, agent, and class. Respond to ad-hoc leadership requests with accurate, documented answers.
    • Communication & Implementation: Present findings in plain, business-focused language and translate them into concrete recommendations on rate, tier, underwriting, reinsurance, and product. Partner with IT, underwriting, and product to implement rating changes—writing requirements, testing, and validating production.
    • Effective performance of the essential functions of this position requires regular in-person, on-site interaction with colleagues, both for purposes of relationship building and meaningful collaboration.
    Now Requirements section: combine Qualifications and Education & Experience.

    Requirements

    • Demonstrated production of rate or reserve indications from raw data through executive-ready deliverables.
    • Hands-on experience with large policy, premium, and claims datasets.
    • Exposure to reinsurance renewals, capital adequacy, and outside consulting actuaries preferred.
    • Expert Excel (pivot tables, advanced formulas, exhibit workbooks for rate changes and reserving).
    • Experience with a BI/visualization tool (Power BI, Tableau, or similar).
    • P&C fundamentals: earned/written premium, loss development, IBNR, ALAE/ULAE, LDFs