Why This Role Exists

T2's frontend is not a simple CRUD interface. It's a sophisticated, state-driven workspace that adapts based on transformation lifecycle (Draft → In Progress → Completed), surfaces real-time AI insights through a dynamic card system, provides a conversational AI assistant, renders complex governance rule editors, and presents quality assessment data through interactive visualizations. The current senior UI developer has the architectural skill to design these systems but is also expected to write Java backend code for the BFF and other services. That split attention will become the team's biggest throughput bottleneck once all backend services start producing data that the UI needs to render.

The UX engineer designs the experience. The senior UI developer architects the frontend and handles the technically hardest pieces. This role executes the volume of component implementation, page buildout, and interactive behavior that a platform of this complexity demands.

About Transform

At RWS, we enable the world’s largest enterprises to communicate with global audiences through cutting-edge language technology, AI-driven solutions, and expert services. Our RWS Transform division empowers organizations to accelerate digital transformation, scale global content, and unlock growth in every market.

What This Person could own (pairing with the existing senior UI)

The card system implementation. T2's primary UI building blocks are ContextCards — Terminology, Risks, Quality, Resources, Progress, Interaction cards — each with distinct data shapes, rendering logic, and interactive behaviors. The card system needs to handle dynamic addition/removal as AI agents produce insights, real-time updates during transformation execution, and contextual actions (e.g., "Fix with AI," "Get a specialist" on quality issue cards). This is a substantial component library.

The Transformation Detail View. The primary workspace, which adapts across three states: Draft (collecting requirements, AI suggesting, user steering), In Progress (monitoring execution, quality updates, intervention points), and Completed (review results, download/publish, iteration). Each state has different layouts, available actions, and data flows. Real-time progress updates via WebSocket/SSE from the Push Notification Service.

The Governance UI. Six distinct rule editor forms (Transformation Instructions, Resource Directives, Verification Directives, Human Involvement, Constraints & Guardrails, Adaptive Rules), each with different field sets and condition builders. The organizational tree view for scoping. The Quality Controls editor with threshold types and failure actions. Cross-reference visibility (rule ↔ concept, rule ↔ resource, tag ↔ rule). Conflict detection UI. This is the most complex form-based UI in the system.

The Content Lake browser. Browsable, searchable content repository showing assets with their quality × confidence tags, transformation lineage, and governance linkages. File/folder navigation with metadata panels.

The Assistant chat interface. Conversational UI integrated into the transformation workspace — rendering AI responses, suggestion cards, clarification requests, and user inputs. Handling streaming responses and maintaining conversation context across transformation states.

Dashboard page shells. The Business User Dashboard and Transformation Governor Dashboard layouts, wiring up the data visualization components built by the Data & Insights Engineer into full page experiences with filtering, date range selection, and drill-down navigation.

What This Person Is Not

Not the person who decides the UX patterns or information architecture (that's the UX engineer). Not the person who architects the frontend state management or WebSocket infrastructure (that's the senior UI developer). This is a strong implementer who can take design specs and architectural patterns and produce polished, tested, accessible components at pace.

Technical Profile

• React 18 + TypeScript — deep comfort with hooks, context, custom hooks, component composition patterns
• State management — experience with complex client-side state (React Query, Zustand, or similar) for managing real-time data flows
• WebSocket/SSE consumption — handling real-time updates from the Push Notification Service, optimistic UI updates
• Form building — complex, dynamic forms with validation, conditional fields, and nested structures (for the Governance editors)
• Data visualization — comfort with Recharts, D3, or Chart.js for rendering quality bars, progress indicators, distribution charts
• Component library development — building reusable, documented, testable components; understanding of design system principles
• Testing — Vitest + React Testing Library for component and integration tests
• i18n — the UI itself needs to be internationalized (ironic for a translation platform to have a monolingual UI)
• Nice to have: accessibility (WCAG) experience, animation/transition skills for card system dynamics, experience with Vite build tooling

Collaboration Pattern

Takes direction from the UX engineer (designs) and senior UI developer (architecture, patterns, code review). Works with the Data & Insights Engineer on dashboard components. Consumes APIs defined by the backend engineers via the UI BFF. Should be comfortable working from Figma/design specs and translating them into pixel-accurate implementations.