View job listing
.Net developer health care claims
Remote.
contract role.
Job Description:
Hands-on developer to go job-by-job and procedure-by-procedure through a healthcare payer's Claims batch environment (jobs, stored procedures, Tidal-orchestrated) and turn it into an evidence-backed performance baseline and remediation roadmap. Heavy SQL Server + .NET reading, AI-accelerated review, real production impact in 90 days.
Must-Haves
· 5+ years production .NET / C# and SQL Server, including stored-procedure-heavy codebases
· Hands-on with a batch job scheduler — Tidal, Control-M, Autosys, or similar
· Can read SQL Server Query Store / DMVs / execution plans to diagnose a slow or failing procedure, not just write new ones
· Has actually used AI/LLM tools (Copilot, Claude, ChatGPT) in a real engineering workflow — code review, refactor, or analysis at scale — and knows where to trust it and where not to
· Comfortable in ambiguous legacy code: business logic buried in stored procedures, sparse documentation, hundreds of jobs
Nice-to-Haves
· Healthcare payer or other regulated, high-volume transactional domain (claims, billing, banking core)
· Splunk or equivalent log-based observability tooling
· Exposure to config-driven rules engines or event-driven processing patterns
· Azure familiarity (not a migration mandate for this role)
Apply to .Net developer (health care claims exp MUST) | Remote | W2 Only.
Note: Please ensure your resume includes a valid LinkedIn profile link. Applications without a LinkedIn profile will not be considered.
.Net developer health care claims
Remote.
contract role.
Job Description:
Hands-on developer to go job-by-job and procedure-by-procedure through a healthcare payer's Claims batch environment (jobs, stored procedures, Tidal-orchestrated) and turn it into an evidence-backed performance baseline and remediation roadmap. Heavy SQL Server + .NET reading, AI-accelerated review, real production impact in 90 days.
Must-Haves
· 5+ years production .NET / C# and SQL Server, including stored-procedure-heavy codebases
· Hands-on with a batch job scheduler — Tidal, Control-M, Autosys, or similar
· Can read SQL Server Query Store / DMVs / execution plans to diagnose a slow or failing procedure, not just write new ones
· Has actually used AI/LLM tools (Copilot, Claude, ChatGPT) in a real engineering workflow — code review, refactor, or analysis at scale — and knows where to trust it and where not to
· Comfortable in ambiguous legacy code: business logic buried in stored procedures, sparse documentation, hundreds of jobs
Nice-to-Haves
· Healthcare payer or other regulated, high-volume transactional domain (claims, billing, banking core)
· Splunk or equivalent log-based observability tooling
· Exposure to config-driven rules engines or event-driven processing patterns
· Azure familiarity (not a migration mandate for this role)