Jobs · New Jersey

Primary Casualty Claims Manager

AXIS (AXIS Capital) · Short Hills, NJ · 1 mo ago
Hybrid$145k–$160k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Team", "How Does This Role Contribute to Our Collective Success?", "What Will You Do in This Role?" (which contains subsections: People Leadership..., Technical Claim Oversight..., Litigation..., Portfolio..., Business Partnership...), "About You", "What We're Looking For", "Role Factors", "What We Offer". Also "About AXIS Capital" intro maybe not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - Intro about AXIS Capital (mission, culture). Could be "About the company" but not listed as allowed heading? Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However they say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings, but we can also use other headings? Probably they expect to map content to those generic headings. But the posting has its own headings like "About The Team", "How Does This Role Contribute to Our Collective Success?", "What Will You Do in This Role?", "About You", "What We're Looking For", "Role Factors", "What We Offer". We need to decide which to keep. The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests we should use those standard headings. However they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to decide which sections have real content. We have content for: - About the role / team: "About The Team" and intro about AXIS. Could map to "About the role". Provide description. - Responsibilities: "What Will You Do in This Role?" with subpoints. Could map to Responsibilities. - Requirements / Qualifications: "What We're Looking For" and "About You" (skills, experience). Could map to Requirements and Qualifications. - Skills: maybe part of Requirements. - Benefits: "What We Offer" includes salary range, incentive, benefits package. So we can have Benefits section. - Pay: The posting includes salary range $145,000 to $160,000. That's pay info. Could be separate Pay section, but they said prefer few substantive sections over many thin ones. Could combine Pay into Benefits? But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay range, so we could have Pay section. However Benefits also includes compensation and benefits. Might be okay to have both Pay and Benefits, but they'd be thin. Perhaps combine into Benefits (including pay). But they said "Prefer a few substantive sections over many thin ones." So maybe we combine Pay and Benefits into one Benefits section that includes salary and benefits. However they also said "never create Pay/Schedule/Benefits sections unless the posting actually states them." If we combine, we still have a Benefits section (which is allowed). We'll not create separate Pay section. - Schedule: "Hybrid role requiring office attendance three days per week". That's schedule info. So we could have Schedule section. Thus we could have sections: About the role, Responsibilities, Requirements, Benefits, Schedule. We need to use

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

      for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include details from each section. We must remove boilerplate: EEO statements, duplicated lines, application instructions, cookie/navigation/legal etc. The posting includes EEO statement about qualified applicants will receive consideration... That's boilerplate; remove. Also "This posting is for an existing vacancy." maybe minor metadata; could drop or fold into short p. We'll drop. Also "United States position classified as Exempt for FLSA purposes." appears twice; we can keep once maybe under Schedule or Role Factors? It's not schedule but maybe part of role factors. Could be included in About the role? Might be considered metadata; we could keep as short p under About the role. We need to preserve all substantive information: details about role contributions, duties, requirements, benefits, schedule. Let's extract content. Intro: "This is your opportunity to join AXIS Capital – a trusted global provider of specialty lines insurance and reinsurance. We stand apart for our outstanding client service, intelligent risk taking and superior risk adjusted returns for our shareholders. We also proudly maintain an entrepreneurial, disciplined and ethical corporate culture. As a member of AXIS, you join a team that is among the best in the industry. At AXIS, we believe that we are only as strong as our people. We strive to create an inclusive and welcoming culture where employees of all backgrounds and from all walks of life feel comfortable and empowered to be themselves. This means that we bring our whole selves to work." That's about company culture; could be part of About the role. About The Team: "AXIS is seeking a Primary Casualty Claims Manager to join the North America Claims team. The role leads a team responsible for primary casualty claims and supports disciplined, consistent claim outcomes across a complex portfolio. The manager will combine people leadership, technical claim oversight, portfolio management, and strong partnership with underwriting, actuarial, legal, finance, brokers, insureds, reinsurers, auditors, and external service providers." How Does This Role Contribute to Our Collective Success?: details about accountability, strategy, reserve adequacy, expense discipline, litigation/vendor management, develops talent, provides portfolio insight. What Will You Do in This Role?: broken into subsections: People Leadership and Team Management: bullet points (actually sentences separated by periods). We'll need to make list items. Technical Claim Oversight: bullet points. Litigation, Counsel, and Vendor Management: bullet points. Portfolio, Governance, and Operational Excellence: bullet points. Business Partnership and Communication: bullet points. About You: "We encourage candidates to bring their own experience and perspective. The successful candidate will demonstrate strong technical casualty judgment, credible people leadership, sound financial discipline, and the ability to make and communicate decisions in a complex, fast-moving environment." What We're Looking For: list of requirements: - Typically 8 or more years of progressively responsible casualty claims experience, including significant experience with complex litigated claims; prior people-management or team-lead experience strongly preferred. - Demonstrated experience handling primary general liability claims. - Experience with construction, premises liability, products liability, serious bodily injury, wrongful death, or other high-severity casualty matters is advantageous. - Advanced knowledge of coverage analysis, liability and damages evaluation, reserving, negotiation, litigation, mediation, arbitration, and trial processes. - Proven ability to provide technical direction, apply authority controls, evaluate reserve adequacy, and make sound decisions under pressure. - Ability to lead and develop others, manage competing priorities, and hold internal and external partners accountable for results. - Strong analytical skills and comfort using claims data, metrics, and trend analysis to support portfolio management and decision-making. - Excellent written, verbal, presentation, negotiation, and stakeholder-management skills, including the ability to communicate effectively with senior executives and parties with differing viewpoints. - Demonstrated ability to collaborate and influence across organizational levels and functions while maintaining independent judgment. - Bachelor’s degree required. Juris Doctor or other relevant advanced degree is preferred, or an equivalent combination of education and directly relevant experience. - Active adjuster licenses, or the ability to obtain and maintain required licenses, in accordance with AXIS and state requirements. - Ability to travel for team leadership, court proceedings, mediations, settlement activity, broker or insured engagement, and other business needs. Role Factors: "Hybrid role requiring office attendance three days per week, subject to applicable local arrangements and business needs.Role requires adherence to AXIS licensing, authority, compliance, confidentiality, data-protection, and claims-handling requirements.United States position classified as Exempt for FLSA purposes.Compensation range and target incentive opportunity to be inserted based on approved grade, work location, and Talent Acquisition guidance." What We Offer: "For this position, we currently expect to offer a base salary in the range of $145,000 to $160,000. Your salary offer will be based on an assessment of a variety of factors including your specific experience and work location. In addition, you will be offered competitive target incentive compensation, with awards based on overall corporate and individual performance. On top of this, you will be eligible for a comprehensive and competitive benefits package which includes medical plans for you and your family, health and wellness programs, retirement plans, tuition reimbursement, paid vacation, and much more. Where this role is based in the United States of America, this role is Exempt for FLSA purposes. This posting is for an existing vacancy." We need to remove duplicated lines like "United States position classified as Exempt for FLSA purposes." appears twice; we can keep once. We need to remove boilerplate like EEO statement (not present? Actually there is a line: "All qualified applicants will receive consideration for employment without regard to any protected characteristic, including age, color, disability, ethnicity, gender identity, marital status, national origin, pregnancy, race, religion, sex, sexual orientation, veteran status, or any basis prohibited by the laws that govern its operations." That's EEO; remove. Also "This posting is for an existing vacancy." maybe minor metadata; we can drop. Now we need to decide sections. Option: About the role (h3) containing intro + About The Team + How Does This Role Contribute? Could be combined. Responsibilities (h3) containing What Will You Do in This Role? (with subpoints maybe as lists). Requirements (h3) containing About You + What We're Looking For (maybe combine). Benefits (h3) containing What We Offer (salary, incentive, benefits). Schedule (h3) containing Role Factors (hybrid schedule, FLSA exempt, licensing adherence). We must not create Pay section separately; we included salary in Benefits. We must not create Schedule section unless posting actually states them; yes it does. We must use

      • for any list of duties/requirements/benefits. So for Responsibilities we need to turn the bullet points into
        • . For Requirements we need list. For Benefits we need list (salary range, incentive, benefits). For Schedule maybe just prose. We need to preserve all substantive information; we must not lose any detail. Let's craft. First, About the role section:

          About the role

          This is your opportunity to join AXIS Capital – a trusted global provider of specialty lines insurance and reinsurance

Similar jobs