PolicyCenter Configuration Developer
Most RequestedBuilds and maintains screens, entities, typelists, validation and policy transaction behaviour inside PolicyCenter.
- Gosu
- PCF
- Studio
- Data model
Hire configuration, product model, rating and integration specialists for Guidewire PolicyCenter — on-premise or Guidewire Cloud. Every profile we send has shipped PolicyCenter work on a live insurance programme, not adjacent Java experience with a Guidewire course attached.
For insurers, MGAs and Guidewire delivery partners. Contract, contract-to-hire and dedicated pods.
A CV that says “Guidewire” can mean four very different engineers. Someone who has written rate routines and versioned a product model is not interchangeable with someone who has only touched ClaimCenter workflow, or who has read the Gosu documentation.
We screen on the specific work: how the product model was structured, what happened during the last rate revision, how policy transactions and out-of-sequence endorsements were handled, what broke during the cloud upgrade. That conversation takes a specialist recruiter and a platform reviewer, which is how our screening is set up.
All Guidewire TalentMix and match into a squad, or add one specialist to a team you already have.
Builds and maintains screens, entities, typelists, validation and policy transaction behaviour inside PolicyCenter.
Owns product definition, coverage structure, rate tables and rate routines through revision cycles and new lines of business.
Connects PolicyCenter to rating engines, document systems, print, payment, bureau and downstream data platforms.
Sets configuration standards, reviews code, sizes change, and keeps the build inside Guidewire’s upgrade-safe boundaries.
Translates underwriting and product rules into configurable requirements the developers can actually build against.
Regression and functional coverage across policy lifecycle transactions, rating outcomes and integration points.
Supports version upgrades and moves to Guidewire Cloud — configuration remediation, retrofit and regression.
Agent and customer-facing quote and bind journeys built on top of PolicyCenter data and services.
Requirements get mapped against this grid before we send anyone, so you can see depth by area instead of reading it out of a CV.
Named specialists for a defined period — a release, a rate revision, a peak.
DetailsWork together first, convert to permanent once the fit is proven on your codebase.
DetailsA standing pod — developers, BA, QA, lead — that stays with your platform roadmap.
DetailsA scoped outcome — new line of business, upgrade wave, integration workstream.
DetailsFour steps, and you hear from us at each one.
Module, version, on-prem or cloud, product lines in scope, and what the team already covers.
A Guidewire-experienced reviewer probes actual work: product model decisions, rating logic, defects owned.
Profiles arrive with a written view on depth by area, notice period, rate and known gaps.
We coordinate panels, handle paperwork and stay involved through the first weeks on your codebase.
Representative profile structures for the three most common briefs.
Personal lines · on-premise and cloud
Commercial lines · new LOB and rate revisions
Guidewire Cloud · multi-system estate
These are representative profile structures, not live availability. Current availability, notice periods and rates are shared against a specific requirement.
Yes. Most programmes need more than one module, and we staff across the Guidewire InsuranceSuite — see ClaimCenter, BillingCenter and integration talent.
Both. Partners typically come to us when a client programme ramps faster than their bench allows, and need people who can work inside an existing configuration standard from day one.
It does, and we screen for it. Cloud programmes constrain what can be customised, so engineers used to unrestricted on-premise customisation need evidence of working inside cloud guardrails. We flag this on the shortlist rather than letting it surface in interview.
Yes — a single specialist is a common starting point. If the scope grows, the same engagement can extend into a dedicated team without re-contracting from scratch.
A JD if you have one. If not: module, Guidewire version, cloud or on-prem, the product lines in scope, seniority, engagement type and location expectations. That is enough to begin screening.
We coordinate panels around your team’s availability, run the contracting and compliance paperwork, and stay in contact through the first weeks so ramp-up issues get raised early.
Send a JD or a two-line outline. We come back with the roles that fit, what the market looks like for them, and a shortlist against your requirement.
Two minutes now, a shortlist conversation next.