Staff Engineer – Data & Insights Engineer

Job PurposeWhy This Role Exists T2 generates a rich stream of operational, quality, and behavioral data — every transformation produces content analysis results, quality scores with confidence bands, governance rule application traces, autonomy routing decisions, agent execution timelines, and user interaction signals (edits, acceptances, escalations). This data is the foundation for three things customers are actively asking for: Operational dashboards — “How is T2 performing? What quality levels am I getting? Where are my bottlenecks?” (Governor persona) Business outcome correlation — “How does my translation activity connect to revenue, support ticket deflection, or market engagement?” (This generated the strongest reaction from Dell — Eric said it was “the conversation we need to be having, not how many fuzzies.”) Self-improving intelligence — T2’s quality scoring recalibrates over time based on user edit patterns and acceptance signals. Someone needs to design how that behavioral data flows back into the system. The current team can build individual API endpoints that return data, but nobody owns the end-to-end thinking: what events to capture, how to structure them for temporal analysis, how to aggregate across transformations/languages/time periods, and how to surface this as compelling visual insights in the UI. This is a distinct discipline from building orchestration services or agent logic.About TransformAt 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 OverviewWhat This Person Owns Event schema and data collection architecture. Defining the canonical event model for transformation lifecycle events, quality assessment results, governance rule matches, user behavioral signals, and agent execution traces. Ensuring events flow from the Java services and Python agents into a consistent, queryable store. This isn’t a data warehouse — it’s MongoDB aggregation pipelines with thoughtful document design for the queries T2 needs to answer. The Reporting Service. This is an existing Java/Spring Boot service in the architecture. The Data & Insights Engineer owns its business logic — the aggregation queries, the time-series computations, the cross-dimension analytics (quality by language, by content type, by governance scope, over time). The service exposes APIs consumed by both T2’s own dashboards and (post-MVP) external BI tools. Dashboard data APIs and visualization components. Designing the API contracts that serve the Governor Dashboard (rule application stats, quality anomalies, ungoverned content, volume metrics) and the Business User Dashboard (transformation stats, quality trends, speed metrics). Building the React chart components — likely using Recharts or a similar library — that render this data. This is where the role overlaps with frontend: not building full pages, but building the data visualization layer that plugs into the UI. Metrics framework for the four metric categories. The PRD defines Speed Metrics (time to first output, time to all markets, speed vs. traditional), Quality Metrics (prediction accuracy, confidence accuracy, human edit rate, requirements coverage), User Engagement Metrics (task completion rate, return usage, autonomy distribution), and Business Impact Metrics (technology revenue growth, services offset value, net new revenue). This person designs how each metric is calculated, stored, and trended. Data export and external consumption readiness. Even for MVP, the architecture should allow customers to pull T2 data into their own BI tools. This means well-documented API endpoints, potentially webhook-based event streaming, and a clean data model that external systems can consume. Post-MVP, this extends to the semantic linking concept (tagging transformed content with business concepts and correlating with external CRM/support data). Behavioral feedback loops. Designing how user edits, acceptance patterns, and quality overrides flow back to recalibrate quality scoring. This is the “self-improving assessment framework” — not ML model training, but structured data collection that enables the Quality Evaluation Agent to get smarter over time. What This Person Is Not Not a BI analyst who builds reports in Tableau. Not a data warehouse architect designing star schemas. Not a front-end developer who happens to know D3. This is a backend-leaning engineer with a data mindset who can think about event modeling, aggregation patterns, and temporal data — and who has enough frontend capability to build clean chart componentsTechnical Profile
Java/Spring Boot — this person works primarily in the Reporting Service, which is Java

MongoDB aggregation framework — pipeline stages, $group, $bucket, time-series patterns, materialized views

Data modeling for analytics — event sourcing concepts, dimensional thinking, temporal data patterns

React + charting libraries — Recharts, D3, or similar; enough to build interactive dashboard components

API design — RESTful APIs optimized for dashboard consumption (pagination, filtering, date ranges, grouping)

Event-driven patterns — consuming RabbitMQ events to build aggregated views

Nice to have: experience with time-series data, exposure to BI tool integration (export APIs, data feeds), familiarity with business metrics/KPI design
Collaboration Pattern Works with the senior backend engineers (who emit events from the orchestration layer), the Python Agent Engineer (who emits events from agent execution), the UI developer (who consumes dashboard APIs), and directly with the architect on the data model and metrics framework. Post-MVP, collaborates with customers on reporting requirements and data integration. Life at RWSLife 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.

Apply Now