Policy Configuration Developer
Most RequestedAuthors product, screens and policy transaction behaviour, working with the inheritance model rather than against it.
- Author
- Manuscripts
- Extensions
- Policy lifecycle
Duck Creek Suite
Duck Creek Talent Who Configure With the Inheritance Model, Not Around It
Hire policy, rating, billing, claims and integration specialists for the Duck Creek suite. The engineers worth hiring know why an override that works today makes the next upgrade expensive — and configure accordingly.
For insurers, MGAs and Duck Creek delivery partners. Contract, contract-to-hire and dedicated pods.
What a Duck Creek Brief Usually Looks Like
Live demand- Roles
- Policy configuration developer, rating specialist, billing or claims configurator, integration developer, tech lead
- Core stack
- Author and manuscripts, inheritance and extension model, rating tables, .NET and SQL Server, APIs
- Typical trigger
- A new line of business, a rate revision, an OnDemand upgrade, or a partner ramping a squad
- Engagement
- Contract · Contract-to-hire · Dedicated team · Project pod
- Working models
- Onsite, hybrid, offshore, or blended with your existing squad
Send us a JD or a rough outline —start a requirement.
Suite coverage
- Policy
- Rating
- Billing
- Claims
- Distribution
- Digital & portals
Why This Role Is Hard to Fill
Duck Creek Draws a Different Engineer From the Rest of Core Insurance
Configuration is authored rather than coded in the usual sense, sits on a .NET and SQL Server foundation, and depends on an inheritance model that rewards extending and punishes overriding. None of that maps neatly onto a Guidewire or in-house background, which is why cross-platform substitutions rarely work as well as a brief assumes.
So we screen on the model, not the logo. Where did you extend versus override, and why? What did the last upgrade cost you in remediation, and which decisions caused it? How was the product structured for a new line of business? On OnDemand, what could you not do that you would have done on-premise? Engineers who have lived it answer immediately.
All Expertise- Generic .NET Offered as Duck CreekThe platform runs on a Microsoft stack, so strong .NET profiles get submitted with no real configuration or manuscript depth behind them.
- Override HabitsEngineers who solve problems by overriding rather than extending leave a remediation bill that lands at the next upgrade.
- Guidewire Experience Assumed to TransferBoth are core insurance platforms; the configuration model, tooling and stack are not the same discipline.
- OnDemand Versus On-Premise MismatchHosted estates constrain what can be changed and how releases happen. We check which the experience came from.
- Rating Depth OverstatedRating is its own discipline. Plenty of configurators have touched it; fewer have owned a rate revision cycle end to end.
Roles We Staff
The Duck Creek Roles Insurers Ask Us For
Mix and match into a squad, or add one specialist to a team you already have.
Rating Specialist
Owns rating logic, tables and rate revision cycles, including the testing that proves premium is right.
- Rating
- Rate tables
- Revision cycles
Billing Configuration Developer
Billing and payment plans, invoicing, delinquency behaviour and the finance handoff.
- Billing plans
- Invoicing
- Payments
Claims Configuration Developer
Claim intake, lifecycle, reserves and payments, plus the workflow the adjusters actually use.
- Claim lifecycle
- Financials
- Workflow
Integration Developer
APIs, managed integrations, document and payment systems, bureau data and downstream reporting.
- APIs
- .NET
- SQL Server
- Managed integrations
Distribution & Producer Specialist
Producer onboarding, licensing, hierarchy and compensation configuration.
- Producer data
- Licensing
- Compensation
Tech Lead / Solution Architect
Sets configuration standards, reviews extension design and keeps the build upgrade-safe.
- Design authority
- Code review
- Upgrade strategy
Upgrade & OnDemand Engineer
Version upgrades and hosted migration — impact analysis, remediation and regression.
- Upgrades
- Remediation
- Regression
What We Screen For
The Capability Grid Behind Every Shortlist
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.
Authoring & ConfigurationHow change is actually made
- Author
- Manuscripts
- Inheritance model
- Extensions versus overrides
- Screens & data capture
- Validation
- Policy transactions
Product & RatingWhere most policy programmes get stuck
- Product structure
- Coverages & forms
- Rating logic
- Rate tables
- Rate revision cycles
- New line of business build
- Premium testing
Billing & ClaimsThe rest of the suite
- Billing & payment plans
- Invoicing
- Delinquency
- Claim intake & lifecycle
- Reserves & payments
- Recoveries
Platform & IntegrationThe Microsoft foundation
- .NET & C#
- SQL Server
- REST APIs
- Managed integrations
- Document generation
- Payment gateways
- Bureau & third-party data
- Data extracts & reporting
OnDemand, Upgrade & ReleaseVersion currency on a hosted estate
- OnDemand constraints
- Version upgrades
- Upgrade impact analysis
- Configuration remediation
- Environment management
- Release & deployment
Digital, Distribution & QualityEverything around the core
- Producer & consumer portals
- Distribution management
- Analytics & reporting
- Test automation
- Rating regression packs
- Defect triage
Engagement
Compare all modelsFour Ways to Bring Duck Creek People On
Contract Staffing
Named specialists for a defined period — a release, a rate revision, an upgrade wave.
DetailsContract-to-Hire
Work together first, convert to permanent once the fit on your configuration is proven.
DetailsDedicated Technology Teams
A standing pod — developers, BA, QA, lead — that stays with your product roadmap.
DetailsProject Team Staffing
A scoped outcome — a new line of business, an upgrade, an integration workstream.
DetailsHow We Get to a Shortlist
Screening, in the Order It Happens
Four steps, and you hear from us at each one.
- 1
Requirement Intake
Which suite components, version, OnDemand or on-premise, product lines in scope, and what the team already covers.
- 2
Platform Screening
A reviewer with core insurance background probes configuration decisions: extension design, rating owned, upgrade remediation.
- 3
Shortlist With Notes
Profiles arrive with a written view on depth by component, notice period, rate and known gaps.
- 4
Interview and Onboard
We coordinate panels, handle paperwork and stay involved through the first weeks on your codebase.
Profile Shapes
What a Duck Creek Shortlist Tends to Contain
Representative profile structures for the three most common briefs.
Senior Policy Configuration Developer
Personal or commercial lines · OnDemand and on-premise
- Multiple releases authored and delivered end to end
- Works with the inheritance model deliberately
- Can explain an override they chose not to make
- Has worked under a delivery partner’s configuration standards
Rating Specialist
New lines of business and rate revisions
- Owned rating for a new line of business end to end
- Rate tables and revision cycles in production
- Worked directly with product and actuarial teams
- Maintains premium regression through each revision
Integration Developer
Microsoft stack · multi-system estate
- API and managed integration work in production
- Strong .NET and SQL Server foundations
- Document, payment and bureau integrations
- Data extracts for reporting and downstream systems
These are representative profile structures, not live availability. Current availability, notice periods and rates are shared against a specific requirement.
Before You Send a Brief
Questions We Get Asked
Would a Guidewire developer work on a Duck Creek programme?
Sometimes, for the insurance domain knowledge, but not as a like-for-like substitution. The configuration model, tooling and technology stack are different enough that the ramp-up is real. If you are open to a cross-platform hire we will say what that ramp-up costs rather than presenting it as an even swap.
The pool looks thin in our market. Is that right?
It is smaller than the Guidewire pool in most markets, and we would rather say so on the intake call than after three weeks. Where dedicated depth is genuinely scarce, we will tell you what a realistic near match looks like and what it would need to succeed.
Does OnDemand change the profile we should hire?
It does. Hosted estates constrain what can be changed and how releases work, so engineers used to unrestricted on-premise configuration need evidence of working within those limits. We flag it on the shortlist rather than letting it surface in interview.
Can you staff more than one suite component at once?
Yes, and most briefs need it. We screen for depth per component rather than treating suite experience as one undifferentiated skill.
Can we start with one developer and scale later?
Yes. If the scope grows, the same engagement can extend into a dedicated team without re-contracting from scratch.
What do you need from us to start?
A JD if you have one. If not: suite components, version, OnDemand or on-premise, product lines in scope, seniority, engagement type and location expectations.
Request Talent
Tell Us What Your Duck Creek Team Is Missing
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.
Send Your Requirement
Two minutes now, a shortlist conversation next.