Manager, Business Rules Platform

We need to output HTML fragment with sections: About the role, Responsibilities (What You’ll Do), Requirements (What You’ll Need), maybe Benefits? There's a line: "The base salary for this role can range from $95,000 to $115,000 based on a full-time work schedule." That's pay info, so we need a Pay section. Also schedule? Not given. Benefits? Not given explicitly. There's a link to benefits but not details. So we should not create Benefits section unless posting actually states them. It doesn't list benefits, just link. So omit Benefits. Also schedule not given. So only sections: About the role, Responsibilities, Requirements, Pay. Also maybe Qualifications? The "What You’ll Need" includes qualifications; we can treat as Requirements. Could also have Skills but not separate. We'll follow headings: About the role, Responsibilities, Requirements, Pay. We need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. The posting includes some fluff like "What We Do", "Who We Are", "Who You Are". Those are substantive? They describe company culture, values. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep those sections if they contain substantive info. However they might be considered boilerplate? They are descriptive of company. Might be considered substantive. But we need to decide. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "What We Do", "Who We Are", "Who You Are" sections are not boilerplate; they describe company culture and expectations. Could be included as separate sections? But we only have headings for specific list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when we have content. It doesn't forbid other headings, but says "use

for section headings (e.g. ...)" meaning those are examples. Likely we should stick to those headings. The "What We Do", "Who We Are", "Who You Are" could be placed under About the role? But About the role already has content. Could we add a subsection? Not allowed. Better to incorporate that info into About the role paragraph? But that would change meaning. However we could create additional sections like "About the Company" but not in allowed list. The instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but the examples are those. Safer to stick to those headings and put any extra info under About the role as prose. Thus we will create:

About the role

... (combined from About The Role paragraph plus maybe What We Do etc? We'll include the About The Role paragraph only; but we need to preserve all substantive info. The "What We Do", "Who We Are", "Who You Are" are substantive. If we omit them, we lose info. So we need to include them somewhere. Could we add a

About the company

? Not in list but maybe acceptable as it's not prohibited. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, just gives examples. So we could add About the company. However they said "Prefer a few substantive sections over many thin ones." Adding many sections may be thin. But we could combine company info into About the role section as extra paragraphs. Thus About the role section will have multiple paragraphs: first the role description, then company description, then expectations. Let's extract: About The Role paragraph: "PURE is in the process of externalizing its underwriting business rules into Sapiens Decision, and we are looking for someone to own that platform on behalf of the business. The Business Rules Manager represents the interests of business users across Underwriting at every stage of rule development: deciding which rule sets to build next and why, drafting rules with subject matter experts, managing UAT, and analyzing how rules perform once they are live. You will be accountable for the success of the rollout and for how the platform is adopted and experienced across the business. This role requires operating at two altitudes. At the strategic level, you will think about rule logic, messaging, and when and why rules should fire, as well as how rules across states and lines of business build on and interact with one another. At a more granular level, you will make sure every rule is worded so that end users know exactly what to do when it fires and what is being asked of them. Over time, you will shape how Sapiens Decision grows from a rules engine into a true decision support tool that Underwriting, Product, and other cross-functional partners can leverage and rely on." What We Do: "We're a member-owned property and casualty insurer designed exclusively for financially successful families and driven by a purpose of doing what is right for our members. We provide exceptional service, hospitality and care, we partner with our members to help prevent losses and we create smart insurance solutions at fair prices. We aim for our members to love their insurance. It is our mission is to create a membership experience so compelling that our members never want to leave." Who We Are: "We want to be transparent about what we expect from each other. From PURE, you can expect: Opportunities to stretch and grow: your professional and personal development matters to us. We’re committed to providing experiences through on-the-job learning and professional development that increase your impact and rewards. Clarity and kindness: you can rely on us to be open, honest and supportive, offering clarity on what success looks like. Support in good times and bad: we believe in showing up for each other consistently, not only when it’s easy. You can expect a thoughtful partner, even when we disagree. A community that cares: we are committed to sustaining a community in which each person feels cared for as an individual. We lift each other up, celebrate wins together and support one another through challenges in work and life." Who You Are: "All of the strongest relationships are a partnership- a two way street. So here’s what we ask of you: Aim to bring your best every day: you’re here because you want to be part of a team that makes a real impact and aims high. Be a student and a teacher: share your knowledge and talents and be willing to listen and learn from those around you. Get comfortable being uncomfortable: we face tough moments and obstacles with a “courage over comfort” approach and a positive, solutions-oriented mindset. Be a culture builder: building a positive culture is everyone's responsibility, based on care, respect and openness to diverse perspectives." We'll combine these into About the role section as multiple

elements. Responsibilities: from "What You’ll Do." list of bullet points (each sentence starting with a verb). We'll turn each into

. Requirements: from "What You’ll Need." list of bullet points. Pay: from "The base salary for this role can range from $95,000 to $115,000 based on a full-time work schedule. An individual’s ultimate compensation will vary depending on job-related skills and experience, geographic location, alignment with market data, and equity among other team members with comparable experience." We'll put that in a

under Pay section. We must not include metadata like Time Type, Desired Office Location, Reports to. Those are minor metadata; we should fold into a short

or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short paragraph at top maybe under About the role? But better to drop them as they are not substantive? They are location and time type. Could be considered substantive but minor. We could include a short

after the heading maybe. But they said "fold minor metadata into a short

or drop it." So we can include a short

with that info. Let's include a

after the opening maybe before About the role? But we need to output only HTML fragment; we can have a

containing that metadata then sections. Thus structure:

Time Type: Full-Time; Hybrid In-Office 3 days/Remote 2 days. Desired Office Location: Charleston, Scottsdale, Chicago, White Plains, Warren – any office is acceptable. Reports to: Head of Underwriting Execution.

Then

About the role

with paragraphs. Then

Responsibilities

with

. Then

Requirements

with
. Then

Pay

with

. Make sure no extra sections. Now extract bullet points. Responsibilities list (from "What You’ll Do."): - Own the Sapiens Decision business rules platform on behalf of the business, and hold yourself accountable for the success of its rollout, adoption, and ongoing use. - Work directly with underwriting, product, and other business subject matter experts to draft rules, ensuring rule language is consistent, clear, and produces the intended outcome for both internal and external policy system platform users. - Think strategically about when, why, and in what form a rule should fire, and connect the dots across rules in different states and lines of business to understand how they build upon and interact with one another. - Set the roadmap for which rule sets PURE develops next and articulate the rationale, balancing immediate underwriting needs against the platform’s longer-term potential as a decision support tool. - Partner with the Analytics team to monitor rule performance: identify rules firing more or less often than anticipated, diagnose why, and quantify the impact rules are having on the underwriting process. - Manage the UAT process for new and changed rules so that we know rules are firing correctly and business sign-off is grounded in evidence before go-live. - Serve as the primary business liaison to IT throughout design, build, and release, resolving requirements and design questions and driving timely decisions. - Build relationships with underwriters to understand how they use and experience the rules engine, gather feedback as rules roll out, and feed what you learn back into rule design. - Manage a portfolio of concurrent rule initiatives, including intake, prioritization, dependencies, and deadlines, and keep stakeholders and leadership informed on progress and risk. - Identify and develop new use cases for the platform across Underwriting, Product, Risk Management, etc., and champion its evolution into a decision support tool for the business. - Establish and maintain standards for rule authoring, naming, and governance so the rule library stays coherent and understandable as it grows. - Provide stakeholders and leadership with timely, actionable reporting on rule performance, emerging insights, and recommended changes. Requirements list (from "What You’ll Need."): - 5 years of experience in P&C insurance underwriting, underwriting operations, product, or a closely related function. - Demonstrated ability to work at both altitudes: thinking strategically about the underwriting process and portfolio while getting into the nitty-gritty of how individual rules are constructed and behave. - Incredible attention to detail. Rule language must be precise, consistent, and correct every time. - Exceptional written and verbal communication skills. You are articulate and thoughtful, and write in language that is clear and easy to understand. - Outstanding organization and time management. You are comfortable with many balls in the air, and you consistently hit deadlines. - An analytical mindset and comfort working with data and analytics partners to interpret rule performance, quantify impact, and communicate and respond to insights. - Strong relationship-building skills and a track record of working effectively across IT, analytics, and business stakeholders. - A genuine ownership mentality