Job Description
Job Description \n
Job Role – Full Stack Dotnet Developer
\n\n
Location – Draper, UT( Hybrid 3 days a week)
\n\n
contract - till dec 31st 2026
\n\n
Pay rate - $50.00 per hour on W2
\n\n
expr -7-12 yrs
\n\n
\n\n
Note - Final round will be in person in draper office
\n\n
\n\n
Try to look for local candidates .
\n\n
\n\n
Must have skills : .Net Core, AI-enabled Application Development, Cloud development (Strong), React (Strong)
\n\n
\n\n
Required experience :
\n\n
· 7 years building and reviewing production software.
\n\n
· React 18 and TypeScript in strict mode, with real experience building reusable component libraries or SDKs — not only application screens.
\n\n
· You know the difference: public API design, peer dependencies, versioning, and not breaking your consumers.
\n\n
· Solid CSS/SCSS, and an eye for building a component other teams will theme.
\nC# / .NET and Web API.
\n\n
· AWS: Lambda, API Gateway, DynamoDB, and infrastructure-as-code (CDK, Terraform, or SAM).
\n\n
· A testing discipline that holds up under a hard deadline — Vitest / React Testing Library and xUnit / NUnit, or close equivalents.
\n\n
· We hold a high coverage bar and expect the tests to be worth the coverage.
\n\n
· Shipping to a fixed external deadline on a live, user-facing application, including feature-flagged rollout and rollback.
\n\n
· A track record of joining in-flight programs and being useful quickly. Scope and deliverables
\n\n
· Embedded analytics integration in the host application, including authentication and row-level security pass-through.
\n\n
· A versioned, documented React component library published to our internal registry, consumable by other product teams.
\n\n
· Supporting .NET Web API and AWS serverless services, defined in infrastructure-as-code.
\n\n
· Feature-flagged rollout with a tested rollback path, plus parity validation against the legacy platform.
\n\n
· Handoff documentation sufficient for our engineers to own the work after the engagement ends. What will set you apart
\n\n
· 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.
\n\n
· Migrating users off a legacy platform, where "the numbers must match the old system” is the acceptance criterion.
\n\n
· Publishing internal npm packages — semantic versioning, ESM packaging, type declarations, Artifactory or a similar private registry.
\n\n
· OIDC / Okta / JWT validation, and token exchange between services.
\n\n
· Data warehouse familiarity (Snowflake) and a working understanding of row-level security.
\n\n
· AI-assisted development workflows (Claude Code or similar).
\n
