Senior Guidewire Developer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Job Title: Senior Guidewire Developer (already shown, not to repeat as heading). Location: 100% Remote (U.S.) Position Type: Full-time, Direct W2 Salary Range: $100,000–$160,000 Annually Experience Required: 8+ years Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position. Job Summary: paragraph. Key Responsibilities: list bullet points. Required Qualifications: list bullet points. Preferred Qualifications: list bullet points. How to Apply: application instructions - we must remove application instructions. EEO etc: remove. We need to decide sections. We have: - About the role: could be job summary paragraph. - Responsibilities: Key Responsibilities list. - Requirements: maybe combine Required Qualifications? Or separate Requirements and Qualifications? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have content for: - About the role: job summary paragraph. - Responsibilities: list. - Requirements: maybe "Experience Required: 8+ years" plus sponsorship? But also "Required Qualifications" list. Could treat Requirements as the experience and sponsorship details, and Qualifications as the bullet list of required qualifications. Or we could combine. - Qualifications: maybe Preferred Qualifications. - Skills: maybe not explicitly listed; but we could extract skills from responsibilities and qualifications (Gosu, etc). However we should not invent content; we need real specific content. There's no explicit "Skills" section. So we should not create Skills unless posting has real specific content. The posting does not have a separate Skills heading. So we skip Skills. - Benefits: not mentioned. No benefits content. So skip. - Pay: Salary Range given: $100,000–$160,000 Annually. That's specific. So we should include Pay section. - Schedule: Position Type: Full-time, Direct W2. Also location remote. Could be schedule? The posting mentions "Full-time, Direct W2". That's schedule type. So we can include Schedule section with that. We also have location info; but location is not a heading per list; we could fold into a short p maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Location is minor metadata; we could include a short p after About the role maybe. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all substantive info: job summary, responsibilities list, required qualifications list, preferred qualifications list, salary range, experience required, sponsorship, position type full-time, remote, etc. We must not repeat job title as heading. We must not include application instructions, EEO, etc. We need to output only HTML fragment. Let's structure:

About the role

Job summary paragraph.

Location: 100% Remote (U.S.)

Position Type: Full-time, Direct W2

Experience Required: 8+ years

Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position.

Then Responsibilities:

Responsibilities

• ...
...

Then Requirements: We could put "Experience Required" etc but we already placed them in About the role. However the instruction says we can have a Requirements section. If we already placed experience etc in About the role, we might duplicate. Better to keep About the role as just job summary paragraph, and put experience, sponsorship, position type, location in a Requirements section? But Requirements heading is for requirements like experience, education, etc. However we also have Required Qualifications list (education, years of Guidewire experience, etc). So we could split: Requirements section for experience required, sponsorship, position type, location. Qualifications section for Required Qualifications bullet list. Skills maybe not needed. Preferred Qualifications as another section maybe Qualifications? But we have two qualification lists: Required and Preferred. Could combine under Qualifications with subheadings? But instruction says use headings for sections; we could have Qualifications section containing both required and preferred? Might be messy. Better: Use Requirements for the experience, sponsorship, position type, location. Use Qualifications for Required Qualifications bullet list. Use Skills for Preferred Qualifications? Not ideal. Alternatively, we could have Requirements for Required Qualifications bullet list, and Qualifications for Preferred Qualifications bullet list. Then we need a separate section for experience etc maybe under About the role? But About the role is for job summary; we could add a short p for location etc inside About the role. Let's think: The instruction says "Prefer a few substantive sections over many thin ones." So we should not create many sections with little content. We have: - About the role: job summary paragraph (substantive) - Responsibilities: list (substantive) - Requirements: could include experience required, sponsorship, position type, location (some content) - Qualifications: Required Qualifications list (substantive) - Preferred Qualifications: maybe we could add as part of Qualifications? But we could also add a separate section "Preferred Qualifications" if we want, but that may be thin? It has several bullets; it's substantive. - Pay: salary range (substantive) - Schedule: position type full-time (but we already used position type in Requirements). Could combine schedule with requirements? But schedule heading expects schedule details like full-time/part-time, shift, etc. We have full-time. Could include schedule section with "Full-time". But we already used position type in Requirements; maybe better to move position type to Schedule section, and keep Requirements for experience required and sponsorship. Location could be in About the role. Let's design: About the role: job summary paragraph + location (remote) maybe as a p. Responsibilities: list. Requirements: experience required 8+ years, sponsorship details. Qualifications: Required Qualifications bullet list. Preferred Qualifications: Preferred Qualifications bullet list. Pay: salary range. Schedule: position type Full-time, Direct W2. We need to ensure we don't repeat info. Let's extract exact text. Job Summary paragraph: "We are seeking a Guidewire Developer to deliver configuration, integration, and customization across the Guidewire InsuranceSuite — PolicyCenter, BillingCenter, and ClaimCenter — and Guidewire Cloud. The role focuses on hands-on Gosu development, integration design, product model configuration, and Guidewire Cloud upgrades, working closely with business analysts and SMEs to ship reliable insurance-platform features. The ideal candidate has shipped meaningful Guidewire work in production for insurance carriers and understands the trade-offs that come with deep platform customization. In this role you will work closely with cross-functional partners — product, design, engineering, operations, and business stakeholders — to translate ambiguous requirements into well-engineered solutions, and will be expected to raise the bar through code review, design review, and mentorship of more junior engineers. The successful candidate brings strong engineering discipline, a clear communication style, and a track record of shipping meaningful work that holds up well in production." That's the job summary. Location: "100% Remote (U.S.)" Position Type: "Full-time, Direct W2" Experience Required: "8+ years" Sponsorship: "U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position." Now Responsibilities bullet list (as given). Need to preserve each bullet exactly. Let's copy them: - Develop configuration and customizations across PolicyCenter, BillingCenter, and ClaimCenter using Gosu - Implement product model changes including coverages, conditions, and term-level logic - Build and maintain Guidewire integrations using messaging, batch, plugins, and Guidewire Integration Gateway - Develop integrations with policy, claims, billing, document generation, payment, and reinsurance systems - Implement rules using GX Model, business rules, and validation rules - Support Guidewire Cloud Platform upgrades, configuration refactoring, and adoption of cloud-native patterns - Develop and maintain unit tests, regression suites, and automated testing for Guidewire components - Build PCF (Page Configuration File) customizations following Guidewire best practices - Implement Guidewire entity model extensions, augmentations, and data model changes following platform-supported patterns that remain compatible with future Cloud Platform upgrades - Profile and optimize performance of complex Gosu logic and database queries, applying systematic measurement, targeted improvements, and data-driven validation to deliver quantifiable gains in throughput, latency, or resource efficiency - Participate in code reviews, contribute to standards, and document technical decisions - Troubleshoot production issues across the InsuranceSuite footprint — PolicyCenter, BillingCenter, and ClaimCenter — applying systematic diagnostics and partnering with insurance SMEs to drive durable resolutions - Collaborate with business analysts, product owners, and SMEs on requirements clarification - Stay current with Guidewire releases, Cloud Platform evolution, and insurance domain trends Now Required Qualifications bullet list: - Bachelor’s degree in Computer Science or a related field - Five or more years of Guidewire development experience - Deep expertise in Gosu programming and Guidewire data model - Hands-on experience with PolicyCenter, BillingCenter, or ClaimCenter customization - Strong understanding of product model and rule design - Experience building Guidewire integrations (messaging, batch, plugin) - Familiarity with Guidewire Cloud Platform - Strong SQL skills and understanding of Guidewire database schema - Strong troubleshooting and analytical skills - Excellent communication and stakeholder management skills Preferred Qualifications bullet list: - Guidewire ACE certifications - Experience with Guidewire Cloud upgrades - Familiarity with Guidewire Digital portals or DataHub/InfoCenter - Insurance domain expertise across P&C lines - Experience with reinsurance, policy administration, or claims modernization programs Now Pay: "$100,000–$160,000 Annually" Schedule: "Full-time, Direct W2" (but we already used that; maybe we can put schedule as "Full-time". However the posting says "Full-time, Direct W2". We'll put that in Schedule. Now we need to avoid duplication: we already have Position Type in Schedule; we should not also put it elsewhere. So we will not include Position Type in About the role or Requirements. We'll keep location in About the role maybe as a short p. Requirements section: experience required and sponsorship. Now we need to ensure we don't include any boilerplate like EEO, application instructions, etc. Now produce HTML. We'll wrap sections in appropriate tags. We'll not include or . We'll output:

About the role

Job summary paragraph.

Location: 100% Remote (U.S.)

Responsibilities

...

Requirements

Experience Required: 8+ years

Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position.

Qualifications