Sr Catastrophe Research Analyst

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About The Role: paragraph describing role. - What You’ll Do: list of duties. - What We’re Looking For: list of requirements/qualifications/skills. - What’s In It For You: includes benefits, compensation, etc. Also there is description of company at start (mission, vision, locations). That could be part of About the role? Actually "About The Role" heading is present. The earlier paragraph about Orion180 is company overview; maybe we can include as part of About the role? But instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. The posting includes "About The Role". So we should have an

About the role

and include the paragraph(s) that describe the role (the paragraph after "About The Role Join Our Team as Senior Catastrophe Research Analyst ..."). Then responsibilities: "What You’ll Do" list. Then requirements/qualifications/skills: "What We’re Looking For" includes advanced degree, experience, etc. Could split into Requirements (experience, degree), Qualifications (maybe same), Skills (programming, GIS). But we can combine into one section if content is substantive. However instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits. Possibly also Skills if distinct. But we have Pay mentioned: "Compensation: Competitive base pay and performance bonuses." That's specific enough to create Pay section. Schedule: mention "An employee must be willing and able to work their regularly assigned work schedule onsite, and in times of need, be able to work an extended schedule depending on company or departmental needs, project requirements, or customer demands." That's schedule info. Benefits: "Benefits: Medical, dental, vision, 401k, paid holidays, PTO and more!" plus maybe other benefits like dynamic environment, career growth, mentorship. Thus we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We must not include empty sections. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. Let's extract: Company overview paragraph (mission, vision, locations) maybe not needed as it's not under a heading. But we could include it as part of About the role? The instruction: "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." The company overview is not a heading; it's just descriptive text. Should we keep it? It's substantive info about the company. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it, but where? It appears before "About The Role". Since we don't have a heading for company overview, we could just include it as a

before the first heading. That's allowed: output only HTML fragment, we can have

paragraphs and headings. Thus we will output:

At Orion180, we don’t just stand out for what we do; we shine because of how we do it. Our mission is to deliver an exceptional insurance experience through innovative technology, unparalleled customer service, and a comprehensive suite of products. Our vision is to be the premier global provider of insurance solutions and redefine the insurance industry. Orion180 is proud to call three vibrant cities home. Our headquarters on Florida’s stunning Space Coast in Melbourne offers an exceptional quality of life, with affordable housing, excellent transportation, and close proximity to major cities like Orlando, Tampa, and Miami. Our Irving, Texas, office places us in a dynamic center of culture, business, and entertainment, keeping us closely connected to innovation and growth. Our Draper, Utah, location, nestled in the heart of the Salt Lake Valley, connects us to a rapidly growing tech ecosystem and provides access to the outdoor lifestyle and natural beauty the region is known for.

Then

About the role

with the paragraph(s) describing role. Let's extract that paragraph: "Join Our Team as Senior Catastrophe Research Analyst At Orion180, we believe the future of insurance belongs to organizations that can transform data into a deeper understanding of risk. Modeling and analytics are not a support function—they are core strategic capability dictates how we grow, price risk, optimize our portfolio, and maintain a sustainable competitive advantage. The Senior Catastrophe Risk Research Analyst is responsible for delivering Catastrophe (Cat) risk analytics across all lines at Orion180. This critical position acts as a thought Cat modeler and research & development partner to customize, establish, and implement Orion180's "view of risk", ensuring world-class approaches to Cat exposure management, Cat models validation, calibration and adjustments, and helps build portfolio management framework that is aligned with underwriting, product, actuaries and enterprise risk management strategies. The ideal candidate has deep expertise in catastrophe modeling, a strong analytical mindset, exceptional communication skills, and proven project management experience. Positioned as a key member of Enterprise Risk Management, you will drive initiatives that support our expansion into new markets and products. This role offers a unique opportunity to join a growing organization where your work has direct executive visibility and measurable business impact." We need to keep that as prose (

). Possibly split into multiple paragraphs but one is fine. Now Responsibilities: "What You’ll Do" list items: - Customize, establish, and implement Orion180 view of risk - Collaborate with underwriting, product, claims, actuarial, finance, and IT functions to deliver robust catastrophe risk insights that inform technical pricing, portfolio optimization, accumulation control, and capital management. - Support group wide efforts to aggregate catastrophe risk, and deliver associated analytics that support development and execution of underwriting strategy - Inspire and mentor a team of analytics professionals, promoting collaboration, technical excellence, and innovation. - Evaluate emerging risks, trends, and technologies in catastrophe modeling and analytics, recommending adoption where appropriate. - Partner internal teams and external vendors, data providers, and internal technology partners to develop and deploy optimized Catastrophe modeling workflows and toolset for production of risk analytics. - Provide analytical support during live catastrophe events We'll put each as

inside

. Now Requirements/Qualifications/Skills: "What We’re Looking For" includes: - Advanced degree in relevant fields. - A minimum of 5+ years’ experience in catastrophe risk analytics, with significant exposure to property catastrophe insurance business models. - Demonstrated experience in embedding advanced analytics and automation in catastrophe risk management processes. - Deep understanding of global reinsurance markets, regulatory environments, and commercial vendor models (e.g., RMS, AIR Worldwide, KatRisk). - Excellent interpersonal and communication skills; able to translate complex analytics into actionable business insights for both technical and non-technical audiences - Hands-on experience with advanced analytics, statistical modeling, data governance, big data platforms and visualization tools. - Up-to-date knowledge of regulatory environments affecting catastrophe risk. - Strong programming and data science skills (e.g., Python, R, SQL). - Proficiency with GIS software for exposure and spatial risk analysis We could split into Requirements (education, experience), Skills (technical). But we can also just have one section "Requirements" containing all. However instruction: prefer a few substantive sections over many thin ones. Having one big section is fine. But we also have separate "Benefits", "Pay", "Schedule". So we will have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We need to ensure we don't include filler like "commensurate with experience". Not present. Now Benefits section: from "What’s In It For You" includes: - Dynamic Environment: On-site role with a fast-paced and collaborative team culture. - Results-driven office where your contributions make a real impact. - Compensation: Competitive base pay and performance bonuses. (but we will move compensation to Pay section) - Career Growth: Mentorship, growth tracks, and professional development. - Benefits: Medical, dental, vision, 401k, paid holidays, PTO and more! - The office environment is fast-paced and collaborative. (duplicate) - An employee must be willing and able to work their regularly assigned work schedule onsite, and in times of need, be able to work an extended schedule depending on company or departmental needs, project requirements, or customer demands. (schedule) - While performing general duties for this position, the employee is regularly required to sit, stand, and/or walk around (including the use of stairs). Other demands include the ability to openly communicate with others by talking, listening, comprehending, and reading; being able to lift light objects ( or drop it. This is physical demands; maybe we can drop as minor metadata? But it's substantive. However we have no heading for physical demands; we could include as a

under Requirements or Benefits? Probably better to drop as minor metadata? The instruction: "fold minor metadata into a short

or drop it." This is not metadata about job ID; it's job demands. Might be considered minor? Not sure. Safer to keep as a

under Requirements? But it's not a requirement. Could be under "Requirements" as additional note. However we already have Requirements section with list; we could add a paragraph after list about physical demands. That would preserve info. Similarly, the duplicate "The office environment is fast-paced and collaborative." appears earlier; we can keep one. Thus Benefits section content: Dynamic Environment, Results-driven office, Career Growth, Benefits (medical, dental, vision, 401k, paid holidays, PTO and more!). Also maybe mention "On-site role". We'll keep. Pay section: "Compensation: Competitive base pay and performance bonuses." Schedule section: "An employee must be willing and able to work their regularly assigned work schedule onsite, and in times of need, be able to work an extended schedule depending on company or departmental needs, project requirements, or customer demands." Now we need to ensure we don't include boilerplate like EEO etc. Remove that. Now produce HTML fragment. We'll start with company overview

. Then

About the role

...

. Then

Responsibilities

...
. Then

Requirements

...
maybe also include physical demands paragraph after list? Could add

Physical demands: ...

. But we need to decide. Better to keep Requirements as list only, and add a separate

Physical Demands

? Not allowed headings list; but we could fold into Requirements as a paragraph after list. That's okay. Thus after the
for requirements, add a

describing physical demands. Then

Benefits

...
. Then

Pay

Competitive base pay and performance bonuses.

Then

Schedule

An employee