Principal Software Engineer

Cotiviti•Remote,

5d•$130,000 - $176,000•Remote

About The Position

Cotiviti is consolidating several client-facing portals into one unified Client Performance Portal. This portal will span executive, analyst, and operations views, covering SLA reporting, benchmarking, case detail, enhancement requests, roadmap visibility, regulatory insights, and billing self-service. One module already exists in production (Support/ticketing, built on Blazor/.NET, Azure PaaS, Okta, and Jira) and will be folded in rather than rebuilt from scratch. We're looking for a hands-on, full-stack Principal Software Engineer to architect and help build this platform. This role involves assessing and integrating the existing Support module, designing how the portal connects to internal systems (claims, payment integrity, risk adjustment, billing, ITSM), and setting the patterns the rest of the team will build against. As the first hire on the program, expect real code alongside architecture decisions from day one.

Requirements

8+ years of software engineering experience, including 3+ years in a principal/staff-level or senior technical lead role, with hands-on full-stack delivery (not purely a design/architecture-only track record).
Strong C#/.NET experience, including exposure to Blazor or comparable component-based .NET web frameworks — enough depth to evaluate, integrate, or replatform an existing Blazor application, not just read about it.
Solid working knowledge of Microsoft Azure PaaS services: App Service/Web Apps, API Management, Logic Apps (or equivalent workflow/integration orchestration), Key Vault, and Azure-managed relational databases (Postgres or SQL).
Experience with enterprise identity platforms (Okta, Azure AD/Entra ID, or similar) — specifically SSO, MFA, and SCIM-based provisioning, not just "RBAC in general."
Experience integrating with third-party SaaS systems via REST APIs and webhooks (e.g., ticketing/ITSM platforms like Jira, ServiceNow, Zendesk) — bidirectional sync patterns specifically.
Track record of producing clear architecture documentation and driving technical decisions with cross-functional stakeholders (product, security, compliance, not just engineering).
Experience scoping and sequencing a multi-phase technical program, including making explicit build-vs-integrate-vs-replatform calls on existing systems.
Communicating with others to exchange information.
Problem-solving and thinking critically.
Completing tasks independently.
Interpreting data.
Making timely decisions in the context of a workflow.
Maintaining focus.
Assessing the accuracy, neatness and thoroughness of the work assigned.
Learning new tasks and completing tasks in situations that have a speed or productivity quota.
Remembering and adhering to processes and protocols.
Applying established protocols in a timely manner.
Must be able to provide high-speed internet access / connectivity and office setup and maintenance.
Remaining in a stationary position, often standing or sitting for prolonged periods.
Repeating motions that may include the wrists, hands, and/or fingers.
Must be able to provide a dedicated, secure work area.

Responsibilities

Assess the existing Support/ticketing module (Blazor, Azure PaaS, Okta, Jira) and make — and defend — the call on whether it's absorbed as-is, wrapped behind an API, or re-platformed to match the unified portal's target stack.
Lead technical discovery: inventory the systems behind each legacy client portal and assess what it takes to expose their data to a unified, client-facing layer.
Define and personally help build the overall architecture for the platform — API/aggregation layer, data pipelines, authentication/authorization model, and integration patterns with source-of-record systems.
Make and document build-vs-integrate calls for major components (e.g., enhancement-request workflow, document repository) with clear tradeoffs.
Design the role-based access control and data segmentation model so Executive/Analyst/Operations personas — and different client organizations — see only what they should, reconciling with the existing Okta/SCIM setup already in production.
Partner with Product, Security/Compliance, and Data teams to ensure the architecture supports regulatory and PHI/PII handling requirements from day one.
Write production code across the frontend and backend to establish the patterns (component structure, API conventions, integration approach) the rest of the engineering team will build against.
Produce architecture documentation and decision records for the engineering team that follows.
Advise on sequencing/phasing of the build given technical dependencies and risk.
Act as the primary technical point of contact through the discovery and early build phases.
Complete all responsibilities as outlined in the annual performance review and/or goal setting.
Complete all special projects and other duties as assigned.
Must be able to perform duties with or without reasonable accommodation.