Senior UI/UX Developer (SPA & .NET Integration)

Location: 100% Remote (Work from Home)

Employment Type: Full time

Experience: 8+ YearsSenior UI Engineer (Blazor/C#)

Senior UI Engineers to build and jointly own our shared Blazor/Telerik component library — the single, shared foundation consumed by all roughly 15 cross-functional product pods. This is senior, architecture-level work: component contracts, Figma Code Connect mappings, and CI enforcement that keeps every pod's usage consistent, not a junior build-out role.

About the role

You and your counterpart will be the two technical drivers of this library's architecture. Your closest working relationship is with our UX Design Leads: you'll be in Figma Dev Mode daily, translating their design intent into correct, accessible, enforceable code.

This role is AI-first by design. You'll use Claude Code as a core part of how you author components day to day, and you'll design every component and Code Connect mapping so AI coding agents, not just humans, can consume it correctly — that's a first-class requirement, not an afterthought. As the component framework matures, manual coding on new component instances shrinks. But building the framework itself, the contracts, the Code Connect templates, the CI enforcement rules, the underlying architecture, stays fully hands-on and senior. AI doesn't design a contract; you do, and you're the one who can tell whether AI-generated output actually honors it, not just looks plausible.

What you'll do

- Build and jointly own our single, shared Blazor/Telerik component library, consumed by all roughly 15 product pods — not a pod-by-pod split
- Author and maintain Figma Code Connect mappings,



working in Dev Mode with our UX Design Leads to keep code and design intent in sync
- Design components and mappings so both humans and AI coding agents can consume them correctly; own the content and schema of our planned MCP component catalog (the Principal AI Platform Engineer owns the reusable MCP server infrastructure it runs on)
- Set up and maintain Roslyn analyzers and CI build checks that hard-block raw HTML, hardcoded styles, and deprecated components — enforcement happens in CI, not as a personal veto over another engineer's PR
- Review PRs across pods, distinguishing additive changes from contract-breaking ones
- Own accessibility: WCAG 2.2 AA compliance and ARIA patterns across every component, including field-clinician and offline/tablet usage scenarios
- Document component usage, variant naming, and migration paths so the library stays usable without you in the room

What you'll need

- Experience building or maintaining a shared component library used by more than one team or product
- Comfortable in Figma: Dev Mode, component variants, and reading a design system file well enough to spot when code and design have drifted
- Working knowledge of semantic versioning and the discipline of shipping breaking changes safely, including deprecation windows and migration notes
- Experience with automated testing, including visual regression or snapshot testing




- Strong written communication. A meaningful part of this job is writing documentation and PR feedback that both designers and engineers can follow
- Experience working with AI coding assistants such as Claude Code or GitHub Copilot in a production codebase, especially structuring rules or context files that keep an agent's output consistent

Nice to have

- Experience with Figma Code Connect, or any tool that maps design components to real code
- Experience with Telerik UI for Blazor specifically
- Exposure to healthcare, HIPAA-regulated, or other compliance-heavy software environments
- Experience working inside a cross-functional, pod-based or value-stream-aligned engineering org, rather than a siloed front-end team

What success looks like

Given this is a new, two-person function with no existing internal backstop, we're rolling this out in phases rather than targeting a flat 90-day bar:

- Phase 1 — Audit: inventory existing Blazor/Telerik usage across pods and document where contracts are already being broken informally
- Phase 2 — Small release: ship the first version of the shared library and Code Connect mappings into one pod
- Phase 3 — Prove it: validate component-contract CI enforcement and the Code Connect to component workflow end-to-end in that one pod before expanding further
- Phase 4 — Expand: roll the proven pattern out to the remaining pods

As the framework and its pod adoption mature, the day-to-day work shifts from building the system to maintaining and extending it across the pods that use it

Pay: ₹2,000,000.00 - ₹3,500,000.00 per year

Benefits:

- Provident Fund

Work Location: Remote

📌 Sr.UI engineer (Blazor/C#) (India)
🏢 NSR information systems
📍 India