Full Stack Dotnet Developerp

Job Role – Full Stack Dotnet Developer

Location – Draper, UT( Hybrid 3 days a week)

contract - till dec 31^st 2026

Pay rate - $50.00 per hour on W2

expr -7-12 yrs

Note - Final round will be in person in draper office

Try to look for local candidates .

Must have skills : .Net Core, AI-enabled Application Development, Cloud development (Strong), React (Strong)

Required experience :

· 7+ years building and reviewing production software.

· React 18+ and TypeScript in strict mode, with real experience building reusable component libraries or SDKs — not only application screens.

· You know the difference: public API design, peer dependencies, versioning, and not breaking your consumers.

· Solid CSS/SCSS, and an eye for building a component other teams will theme.
C# / .NET and Web API.

· AWS: Lambda, API Gateway, DynamoDB, and infrastructure-as-code (CDK, Terraform, or SAM).

· A testing discipline that holds up under a hard deadline — Vitest / React Testing Library and xUnit / NUnit, or close equivalents.

· We hold a high coverage bar and expect the tests to be worth the coverage.

· Shipping to a fixed external deadline on a live, user-facing application, including feature-flagged rollout and rollback.

· A track record of joining in-flight programs and being useful quickly. Scope and deliverables

· Embedded analytics integration in the host application, including authentication and row-level security pass-through.

· A versioned, documented React component library published to our internal registry, consumable by other product teams.

· Supporting .NET Web API and AWS serverless services, defined in infrastructure-as-code.

· Feature-flagged rollout with a tested rollback path, plus parity validation against the legacy platform.

· Handoff documentation sufficient for our engineers to own the work after the engagement ends. What will set you apart

· Embedding a third-party BI or analytics product in a host application — Logi Symphony, MicroStrategy Embedded, Power BI Embedded, Tableau Embedding API, Looker, Sisense. The specific product doesn't matter; working around an embedded SDK's limits transfers directly.

· Migrating users off a legacy platform, where "the numbers must match the old system” is the acceptance criterion.

· Publishing internal npm packages — semantic versioning, ESM packaging, type declarations, Artifactory or a similar private registry.

· OIDC / Okta / JWT validation, and token exchange between services.

· Data warehouse familiarity (Snowflake) and a working understanding of row-level security.

· AI-assisted development workflows (Claude Code or similar).