Guidewire ClaimCenter Mentorship Support
Budget: $15 – $25 USD
I’m a full-time developer working directly in a live Guidewire ClaimCenter environment and I keep running into questions that slow me down. Most of my challenges revolve around writing efficient, optimized Gosu code that still respects ClaimCenter conventions and integrates cleanly with the existing services we already have in place. I have several code-quality and optimization tools running in the pipeline, so guidance will need to mesh with those rather than start from scratch.
What I need is an ongoing, hands-on mentorship: quick walkthroughs when a production incident pops up, deeper sessions where we dissect the current implementation, and regular checkpoints to review the efficiency of new logic before it reaches production. You’ll also help me confirm that documents generate correctly after assignment changes and explain why a particular integration behaves the way it does, but the core focus is always best-practice coding—especially performance tuning and resource optimization.
Deliverables
• 1-to-1 screen-share sessions (scheduled weekly, ad-hoc for urgent incidents)
• Code reviews highlighting performance bottlenecks, memory considerations, and stylistic issues
• Concise reference notes or snippets summarizing the fixes or patterns we discuss
• Optional mini-exercises I can run through between meetings for reinforcement
Acceptance Criteria
• Each session leaves me with a clear, reproducible solution or action plan.
• Reviewed code passes existing static-analysis tools with no new critical findings.
• Performance metrics in lower environments show measurable improvement when recommended changes are applied.
If deep ClaimCenter knowledge, a knack for teaching, and a passion for squeezing every millisecond out of Gosu sound like you, let’s get started.
What I need is an ongoing, hands-on mentorship: quick walkthroughs when a production incident pops up, deeper sessions where we dissect the current implementation, and regular checkpoints to review the efficiency of new logic before it reaches production. You’ll also help me confirm that documents generate correctly after assignment changes and explain why a particular integration behaves the way it does, but the core focus is always best-practice coding—especially performance tuning and resource optimization.
Deliverables
• 1-to-1 screen-share sessions (scheduled weekly, ad-hoc for urgent incidents)
• Code reviews highlighting performance bottlenecks, memory considerations, and stylistic issues
• Concise reference notes or snippets summarizing the fixes or patterns we discuss
• Optional mini-exercises I can run through between meetings for reinforcement
Acceptance Criteria
• Each session leaves me with a clear, reproducible solution or action plan.
• Reviewed code passes existing static-analysis tools with no new critical findings.
• Performance metrics in lower environments show measurable improvement when recommended changes are applied.
If deep ClaimCenter knowledge, a knack for teaching, and a passion for squeezing every millisecond out of Gosu sound like you, let’s get started.