Principal UI Developer

About the Role

The Appointment Scheduling platform at Engageware is the front door to some of the most important moments in a customer's day — booking time with their banker, checking in at the branch, waiting in queue, or meeting virtually with a specialist. Behind those experiences sits a suite of purpose-built applications: a multi-tenant admin console, customer-facing scheduling interfaces, in-branch self-check-in kiosks, queue management and concierge tools for branch staff, and virtual channel integrations — all running at enterprise scale for leading banks, credit unions, and healthcare organizations.

We're looking for a Principal UI Developer who can own this surface end-to-end. That means leading the migration of our Angular application estate to React, setting the front-end architecture and design system, owning features all the way through the API layer when needed, and bringing strong design sensibility to interfaces that have had limited dedicated design attention. This is a high-leverage role, and we expect AI tooling to be a meaningful part of how you operate — scaffolding components, generating tests, assisting with Angular-to-React migration, exploring design directions quickly — so the scope is real but so is the support.

What You'll Do

React Migration & Front-End Architecture

• Own the migration strategy for the Appointment Scheduling front-end estate — defining how and in what sequence we move existing Angular applications (admin console, scheduling flows, kiosk, queue management, concierge) to a modern React foundation.

• Establish the shared component library, design tokens, state management patterns (React Query, Zustand, or Redux Toolkit), and routing architecture that all new and migrated applications are built on.

• Make pragmatic migration decisions — incremental strangler-fig patterns vs. targeted rebuilds — balancing speed, risk, and continuity for live enterprise customers.

• Define the module boundaries and shared abstractions that allow Angular and React to coexist safely during the transition.

Design System & Interface Quality

• Own the visual and interaction language for the Appointment Scheduling platform: component library, spacing system, color tokens, typography, and interaction patterns — maintained in Storybook and connected to Figma where design work happens.

• Bring design sensibility to every interface you ship. In the absence of dedicated design resources, you are the person who catches the awkward empty state, the unclear confirmation flow, the button that doesn't belong. You use AI design tools (Figma AI, v0, Claude) to explore and prototype directions quickly rather than waiting for a design brief.

• Ensure all applications meet WCAG 2.1 AA accessibility standards — a non-negotiable for banking and healthcare customers with regulatory obligations.

• Optimize for the full deployment surface: responsive web, touch-screen kiosks (constrained sizes, high-contrast, minimal input complexity), and staff-facing branch tablets in fast-paced environments.

API Layer & End-to-End Feature Ownership

• Own features end-to-end when the critical path runs through the front end: design and build the BFF (Backend for Frontend) endpoints, lightweight Spring Boot routes, and data-shaping layers the UI requires — without waiting on someone else to unblock you.

• Design clean REST API contracts between front-end applications and the scheduling platform services, with clear error-handling conventions and versioning.

• Collaborate with backend engineers on deeper service-layer work, contributing meaningfully to API design reviews and surfacing front-end integration requirements early.

• Handle the full stack of front-end reliability concerns: caching strategies, optimistic UI, graceful degradation, and real-time event handling (WebSockets, SSE) where the scheduling experience demands it.

Test-Driven Development & Quality

• Champion test-driven development across all front-end work: unit tests, component tests, and end-to-end tests written alongside code, not after.

• Establish and enforce testing standards using Vitest or Jest, React Testing Library, and Playwright or Cypress — so the team can migrate, refactor, and ship with confidence.

• Use AI-assisted test generation as an accelerant, not a shortcut: AI scaffolds the coverage, you ensure it's meaningful and deterministic.

• Lead front-end code reviews focused on testability, maintainability, and architectural consistency.

AI-Augmented Development

• Operate with AI as a core part of your workflow: use coding agents (built on Claude) for component scaffolding, Angular-to-React migration assistance, test generation, accessibility audits, and design exploration via v0 or Figma AI.

• Help the team adopt AI-augmented development confidently — setting the guardrails (review standards, coverage requirements) that keep quality high when AI is doing real work.

• Stay current on agentic development patterns (including MCP-based tooling) as the ecosystem evolves rapidly.

Technical Leadership

• Set the front-end technical direction for the Appointment Scheduling team, documenting architectural decisions so the team builds consistently.

• Mentor front-end engineers on React, TypeScript, testing, accessibility, and API integration.

• Partner directly with the Principal PM and Team Lead on new features — shaping what is buildable, raising UX and implementation concerns early, and influencing decisions before specs are locked.

What We're Looking For

Must-have qualifications:

• 8+ years in front-end or full-stack web development, with 3+ years at a senior or principal IC level owning front-end architecture for a production application suite.

• Expert-level React and TypeScript — hooks, concurrent features, performance optimization, and common state management patterns.

• Real experience migrating Angular applications to React in production, with the judgment to choose incremental migration over rewrites where appropriate.

• Strong Angular fluency (multiple versions) — you need to read, reason about, and migrate existing codebases confidently.

• Ability and willingness to own the API layer for front-end features: BFF patterns, REST endpoint design, and working in Spring Boot (Java) for UI-adjacent services.

• Genuine design sensibility — you can look at an interface and know what's wrong with it, and you're comfortable making design decisions in the absence of a dedicated designer.

• Rigorous test-driven development discipline — tests come with the code, not after.

• Proficiency with React Testing Library, Jest or Vitest, and Playwright or Cypress.

• Solid WCAG 2.1 AA accessibility knowledge — designed and built in from the start.

• Hands-on experience with AI coding and design tools as a genuine productivity multiplier, not a curiosity.

• Based in the United States, with willingness to travel occasionally for team and customer meetings.

Nice to Have

• Experience building scheduling, calendar, or real-time availability interfaces.

• Background in financial services, banking, credit unions, healthcare, or retail technology.

• Figma proficiency — able to create and maintain a component library and design tokens, not just consume them.

• Experience with Storybook for component documentation and testing.

• Micro Frontend architecture or module federation experience for managing multi-app front-end ecosystems.

• Depth in kiosk or large-format touch UX — the constraints are different from a browser tab and most candidates haven't been there.

Our Stack

Knowing our stack is not a requirement, but this is what you'll be working with:

• Frontend (current): Angular (multiple versions) — the estate you'll be migrating from

• Frontend (target): React with TypeScript — the standard for all new and migrated applications

• Design: Figma, Storybook; AI design tooling (v0, Figma AI)

• API layer: Spring Boot (Java 17) and Scala/Akka services over REST

• Testing: React Testing Library, Jest / Vitest, Playwright / Cypress

• Data: SQL Server and PostgreSQL

• Infrastructure: Kubernetes on AWS

• AI: Claude models (Anthropic), with MCP-based agent tooling

Originally posted on Himalayas