Remote Staff Engineer – UI Developer @ RWS Group

Job Purpose

 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.

Job Overview

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 

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. 

Life at RWS

Life at RWS  If you like the idea of working with smart people who are passionate about growing the value of ideas, data and content by making sure organizations are understood, then you’ll love life at RWS. 

Our purpose is to unlock global understanding. This means our work fundamentally recognizes the value of every language and culture. So, we celebrate difference, we are inclusive and believe that diversity makes us strong. We want every employee to grow as an individual and excel in their career. 

In return, we expect all our people to live by the values that unite us: to partner, putting clients fist and winning together, to pioneer, innovating fearlessly and leading with vision and courage, to progress, aiming high and growing through actions and to deliver, owning the outcome and building trust with our colleagues and clients.

RWS embraces DEI and promotes equal opportunity, we are an Equal Opportunity Employer and prohibit discrimination and harassment of any kind. RWS is committed to the principle of equal employment opportunity for all employees and to providing employees with a work environment free of discrimination and harassment. All employment decisions at RWS are based on business needs, job requirements and individual qualifications, without regard to race, religion, nationality, ethnicity, sex, age, disability, or sexual orientation. RWS will not tolerate discrimination based on any of these characteristics. 

RWS Values 

Get the 3Ps right – Partner, Pioneer, Progress – and we´ll Deliver together as RWS.

Recruitment Agencies: RWS Holdings PLC does not accept agency resumes. Please do not forward any unsolicited resumes to any RWS employees. Any unsolicited resume received will be treated as the property of RWS and Terms & Conditions associated with the use of such resume will be considered null and void.