Guidewire PolicyCenter Configuration Developer

We need to output HTML fragment only, with headings

for 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 as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove "Employment Eligibility" etc? That might be considered boilerplate? It's about eligibility, location restrictions, remote role, etc. That is substantive? It's about eligibility and location; maybe we should keep as part of Requirements? But we need to follow instructions: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Employment eligibility is not exactly those but might be considered boilerplate? It's about work authorization and location restrictions. Might be considered relevant to requirements. However the instruction says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Employment eligibility is not EEO. It's about eligibility to work. Could be considered part of requirements. But we also have "Why Join FormativGroup" etc which is fluff; maybe we can keep as part of About the role? But we need to preserve all substantive information; not invent or summarize away detail. However we can condense into sections but must preserve all substantive info. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine some. We need sections: About the role (already present). Responsibilities (What You'll Work On). Requirements/Qualifications/Skills (maybe combine). Benefits, Pay, Schedule only if present. Pay is present: Estimated Compensation Range: $115,000—$165,000 USD. Also mention discretionary bonuses, commissions, comprehensive benefits package. Benefits: medical, dental, vision, 401(k), paid time off, etc. So we can have Benefits and Pay sections. Schedule: not mentioned (remote role, travel on need basis). Travel is mentioned but not schedule. No explicit schedule like full-time, hours. So we should not create Schedule section. We need to avoid placeholder text like "commensurate with experience", "not specified", etc. We have actual pay range, so okay. We need to preserve all substantive info: role description, responsibilities, requirements (experience, certifications, technical skills, etc.), qualifications (education), skills (maybe same), benefits, pay. We need to use

for each section heading. Use

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

  for prose. We must not include markdown code fences. Output only HTML fragment. Let's extract content. About the role: The paragraph after "About the role": "The Guidewire PolicyCenter Configuration Developer role is focused on supporting the configuration, development, integration, and delivery of Guidewire PolicyCenter solutions for Property & Casualty insurance clients. We're anticipating future openings and are connecting with great talent who'd like to be considered when the time comes. This role sits within FormativGroup's Guidewire practice and supports implementation and enhancement work across Personal Lines and Commercial Lines environments." We can keep that as prose. Responsibilities: The bullet list under "What You'll Work On". Each bullet starts with a verb. We'll make

  • for each. List items: - Configure, enhance, and support Guidewire PolicyCenter solutions across implementation and modernization projects. - Work across PolicyCenter configuration, product model updates, business rules, workflows, integrations, and platform extensions. - Support Property & Casualty insurance solutions across Personal Lines or Commercial Lines products. - Collaborate with onsite coordinators, project teams, and client stakeholders to understand requirements, clarify technical needs, and support delivery activities. - Contribute to project deliverables, technical documentation, configuration updates, testing support, and issue resolution. - Support enterprise system integrations using Java, XML, web services, SQL, messaging platforms, and related integration technologies. - Troubleshoot configuration, integration, and environment issues across Guidewire implementation workstreams. - Apply software development best practices to ensure quality, maintainability, performance, and platform stability. - Support Guidewire Cloud implementation activities and Advanced Product Designer-related configuration when applicable. - Participate in project status discussions, delivery coordination, and client-facing working sessions as needed. - Travel to client locations on a need basis. We should keep all. Requirements/Qualifications/Skills: The "What You'll Bring" section lists many items. We can split into Requirements (experience, certifications), Qualifications (education), Skills (technical). But we can combine into one section maybe "Requirements". However instruction says prefer few substantive sections over many thin ones. Could have one section "Requirements" that includes experience, certifications, technical skills, education. But we also have "Bonus Points If You Have" which is optional; we could include as part of Requirements or separate? It's bonus, not required. Could be included as a subsection maybe under Requirements as a list. But we need to avoid filler. We'll include them as part of Requirements. Let's parse "What You'll Bring": - 6-8+ years of relevant industry experience, including hands-on Guidewire PolicyCenter configuration experience. - Strong experience with Property & Casualty insurance, including Personal Lines, Commercial Lines, or both. - Valid, active Guidewire certifications highly preferred - Experience with Personal Lines products such as Personal Auto, Property, Homeowners, Personal Umbrella, or related products. - Experience with Commercial Lines products such as Commercial Auto, Commercial Property, Workers' Compensation, Farm, Commercial Umbrella, Farm Umbrella, Business Owners, or related products. - Strong technical experience with Java, JEE, XML, Web Services, SQL, ANT, and enterprise integration concepts. - Experience with PL/SQL, Spring, Hibernate, Castor, or enterprise messaging systems. - Knowledge of application servers such as Tomcat, WebSphere, or WebLogic. - Real-world experience supporting enterprise system integrations, preferably within the insurance domain. - Understanding of software development best practices, configuration standards, testing support, and release delivery. - Strong business communication skills with the ability to work effectively with technical teams, business stakeholders, and client-facing project teams. - BE, BTech, MCA, or equivalent experience in a related technical field. Bonus Points If You Have: - Experience with Guidewire Cloud implementation engagements. - Experience with Guidewire Advanced Product Designer, including conceptualizing, visualizing, and finalizing product models. - Experience using Xmind, creating mind maps, working with mind map elements, and applying markers within Advanced Product Designer workflows. - Client-facing delivery experience within Guidewire or insurance technology consulting environments. - Experience supporting both Personal Lines and Commercial Lines PolicyCenter implementations. We also have "How You Work" and "What Success Looks Like" and "Why Join FormativGroup". Those are more fluff but contain substantive info about work style, success criteria, company description. Might be worth including as part of About the role or separate sections? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info too. However we must avoid boilerplate like EEO etc. "How You Work", "What Success Looks Like", "Why Join FormativGroup" are substantive but could be considered fluff. Yet they contain info about expected behavior, success metrics, company culture. We should keep them maybe as part of About the role or as separate sections like "Work Style" and "Success Criteria". But we only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot add other headings. So we must fit that extra info into those allowed sections. We can incorporate "How You Work" into Requirements or Skills? It's about work style, could be part of Requirements (soft skills). "What Success Looks Like" could be part of Responsibilities? Or maybe we can add a section "Expectations"? Not allowed. So we need to embed within allowed sections. We could add a subsection under Requirements for "Work Style" as a list. Or we could add a paragraph under About the role describing success criteria. But we must not invent headings. Thus we will have sections: About the role (includes role description and maybe success criteria?), Responsibilities, Requirements (includes experience, certifications, technical skills, education, work style, success criteria?), Benefits, Pay. We need to ensure we don't create thin sections. We'll have About the role, Responsibilities, Requirements, Benefits, Pay. Now we need to extract Benefits: "In addition to base pay, employees may be eligible for discretionary bonuses, commissions, or other incentive programs, as well as a comprehensive benefits package that includes medical, dental, vision, 401(k), paid time off, etc." Also earlier: "We are committed to pay equity and transparency. The compensation range for this position represents our good faith estimate of the range we reasonably expect to pay for this role at the time of posting. The actual compensation offered will be determined based on factors such as the candidate's experience, skills, education, work location, and internal equity." That's about pay. Thus Benefits: medical, dental, vision, 401(k), paid time off, etc. Also discretionary bonuses, commissions, other incentive programs. Pay: Estimated Compensation Range: $115,000—$165,000 USD. Now we need to remove boilerplate: "Employment Eligibility Applicants must be authorized to work for ANY employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa currently.This role is a remote role.To be considered for this position, candidates must reside in one of the following U.S. states: AR, AZ, CA, CO, CT, DE, FL, GA, IA, ID, IL, IN, KS, KY, MA, MD, MI, MN, MO, NC, NH, NJ, NV, NY, OH, OK, OR, PA, TN, TX, VA, WI, or Washington, DC.Candidates residing outside these states are not currently eligible for consideration.This role is not open to 3rd party/C2C." Is that substantive? It's about eligibility and location restrictions. Could be considered part of Requirements (location). But it's quite detailed. We could include it as a paragraph under Requirements. However it's not exactly EEO; it's about work authorization and location. The instruction didn't say to remove that. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those, but it's about eligibility. Might be considered legal? It's about employment eligibility. Could be considered legal boilerplate. But it's substantive for candidates. I'd keep it as part of Requirements. Also "We are committed to pay equity and transparency..." is part of Pay section. Also "#formativgroupcareers #WorkWithUs Click here to view our Privacy Policy" is boilerplate; remove. Also "ADA Specifications: Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions of this position." That's legal/EEO; remove. Also "FormativGroup operates within the critical middle layer..." etc is fluff but maybe part of About the role? Could keep as part of About the role. We need to preserve all substantive info; we can include that description of FormativGroup in About the role. Now let's craft HTML. We'll start with

    About the role

    then

    ... combine role description and company description.

    Then

    Responsibilities

    • ... each bullet.
    Then

    Requirements

    • ... list of requirements, qualifications, skills, work style, success criteria, eligibility, location.
    But we need to separate maybe into sublists? Could just have one big list; it's okay. We need to ensure we don't lose any detail. Let's compile