Skip to main content

Push Developer - Claims Management

Posted yesterday

themesoftPhoenix (AZ)

SENIORITY

Mid

Apply (opens in a new tab)

About the role

Push Developer – Claims Management Fully REMOTE Push Developer with strong production support and application support experience across Guidewire ClaimCenter, Sonic integrations, EDW, MarkLogic, Claims Data Mart (CDM), and Snowflake. Responsible for monitoring and troubleshooting production integration failures, investigating Sonic and EDW validation errors, performing root-cause analysis, analyzing and remediating XML payloads, resolving data-quality issues, and validating successful downstream processing. Collaborates with business, application, integration, and data teams to restore impacted processing, resolve defects, support deployments, and maintain production stability.
Key Responsibilities: Provide production support for Claims Management applications and integrations, troubleshooting incidents involving ClaimCenter, Sonic, EDW, MarkLogic, CDM, and Snowflake. Investigate Sonic production failures, EDW validation errors, failed messages, and transaction-processing issues using SQL Server Management Studio (SSMS).Perform root-cause analysis (RCA) for production defects and data-processing failures by tracing transactions across source and downstream systems. Research ClaimCenter claim, payment, reserve, check, exposure, and contact data to identify source-data and integration issues. Analyze problematic XML payloads and XSLT transformations, identify validation or EBI-related issues, and perform payload corrections when remediation is required. Build, test, validate, and regenerate XML payloads using SoapUI to reproduce issues and confirm fixes. Use Beyond Compare and Notepad++ to compare payload versions, analyze XML/XSLT differences, and validate modifications. Review Guidewire and integration code using IntelliJ IDEA to assist with defect investigation and troubleshooting. Thank you Vinod

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this