Back to jobs

[TrainAI] Robot Application and Data Engineer

Pay
Pay not listed
Work setting
Not stated
Employment
Full-time — employment source
Employment type in the employer’s posting: FULL_TIME
From the employer’s posting

What you’ll work on

Full posting

You own two things: the software a person experiences from our humanoid, and the data that comes out of it.

The software is the speech pipeline that hears people in their language, the dialogue that answers from the venue’s knowledge, the skills that turn an answer into a greeting, a direction or a hand-off, and the operator console that lets one person keep the robot good on day one.

  • Run the server-side pipeline: ingestion, quality control, and dataset export for robot data

  • Build a LAN-hosted speech, dialogue, and speech synthesis pipeline for the robot

  • Build the task-level skill library as behavior trees or state machines

  • Build the knowledge pipeline feeding venue information into a retrieval layer

  • Build the Wizard-of-Oz operator console for live robot control and correction

From the employer’s posting
You own two things: the software a person experiences from our humanoid, and the data that comes out of it.
The software is the speech pipeline that hears people in their language, the dialogue that answers from the venue’s knowledge, the skills that turn an answer into a greeting, a direction or a hand-off, and the operator console that lets one person keep the robot good on day one. You build these to the specifications of our HRI scientist, who designs the interaction and owns the content.
Own the server side of our robot data collection to the technical lead’s specification
build the alternative if it does not meet the bar: a LAN-hosted pipeline of streaming speech recognition, language identification and switching, an LLM dialogue layer grounded in the venue knowledge base, and multilingual speech synthesis
Build the task-level skill library (greet, answer, direct, recommend, hand off) as behavior trees or state machines
Build the knowledge pipeline: the venue’s floor plans, points of interest, scripts and FAQs
Build the Wizard-of-Oz console to the HRI scientist’s workflow

Before you apply

Work authorization
Must already have the right to workeligible to work in China

About RWS Group

RWS TrainAI is the AI data and evaluation business of RWS Group, working with leading AI developers worldwide.

In the employer’s words · Read in context

Apply at RWS Group

Posting record

Report an error

Actively hiringFirst seen by us 2 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 19, 20262 days ago
Recorded sightings
3
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 2

Early. Similar jobs usually come down between day 6 and day 56.

At RWS Group, jobs usually come down by about day 27.

From 14,766 similar postings that came down, and 13 of RWS Group’s. Coming down is not always a hire.

RWS Group is hiring

38 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Hiring is picking up
  • Takes jobs down at a usual pace
Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • C++
  • Python
  • TypeScript
  • Docker
  • Go
Where the posting names them
- Hands-on experience with speech and language pipelines: streaming speech recognition, text-to-speech, and LLM integration with retrieval over a knowledge base, in at least one system that ran with real users. - Strong Python and one of TypeScript, C++ or Go; comfortable with Linux, Docker, GPU inference serving and local-network deployment. - Experience building operator or internal tools with a web front end, and integrating with a hardware API (ROS 2, a robot SDK or a device SDK) as a client.

Your next step

Complete your application on careers-rws.icims.com. The employer’s form will show what is required.

Applying through iCIMS

  • You start with your email. New applicants then create a login, and returning ones sign in.
  • Upload your resume before you fill anything in: iCIMS fills some profile fields from it.
  • Check your status on the employer’s iCIMS Dashboard, under Past Job Submittals.

Already applied? Track this application

Job description

View original posting ↗

Job Purpose

About the Role

 

You own two things: the software a person experiences from our humanoid, and the data that comes out of it.

The software is the speech pipeline that hears people in their language, the dialogue that answers from the venue’s knowledge, the skills that turn an answer into a greeting, a direction or a hand-off, and the operator console that lets one person keep the robot good on day one. You build these to the specifications of our HRI scientist, who designs the interaction and owns the content.

The data is every interaction the robot has and every demonstration we record with the robot and our capture devices. You run the pipeline that turns it into training-ready datasets: ingestion, quality control, annotation export and delivery in the formats robot-learning teams use, to the data specification our technical lead defines.

You are the upper layer of a small engineering team. A systems integration engineer owns the robot and exposes it to you as behavior primitives and sensor events; you do not decide what the robot should do, you make it do what the interaction designer specified, reliably and fast, and you make sure everything it does becomes data.

 

About Train AI

 

RWS TrainAI is the AI data and evaluation business of RWS Group, working with leading AI developers worldwide. We are building a physical AI practice: multilingual, culturally localized interaction for service robots, human evaluation of how robots behave around people, and the data pipelines behind both. Our advantage is a global, multilingual human network and a focus on behavior that is culturally appropriate, measured and auditable.

 

Job Overview

Key Responsibilities

 

Run the data pipeline

  • Own the server side of our robot data collection to the technical lead’s specification: ingestion from the robot and from capture devices, submission-time checks and batch quality control, episode segmentation and annotation export, and delivery in the formats clients use (LeRobotDataset, RLDS, MCAP).
  • Log every interaction (what the person said, what the robot heard, what it did, what the operator corrected) against the failure taxonomy the HRI scientist defines, with the consent and notice hooks our data team specifies, and report autonomy rate and operator calls per hour from day one.
  • Operate the observability and QC stack against live collection, keep data inside China where contracts require it, and keep the stack reproducible so a second robot in another location comes up from your documentation.

Build the voice and dialogue pipeline

  • Test the platform’s own speech stack in venue noise for turn latency and recognition accuracy per language, and build the alternative if it does not meet the bar: a LAN-hosted pipeline of streaming speech recognition, language identification and switching, an LLM dialogue layer grounded in the venue knowledge base, and multilingual speech synthesis, with the robot as a client and no internet dependency.
  • Keep the whole turn fast enough for a face-to-face conversation; measure and report latency per stage and hold it inside the budget.

Build the skill library and the knowledge base

  • Build the task-level skill library (greet, answer, direct, recommend, hand off) as behavior trees or state machines on the robot’s behavior primitives, to the HRI scientist’s specification of what the robot does and when, including the timing of speech, gesture and gaze.
  • Build the knowledge pipeline: the venue’s floor plans, points of interest, scripts and FAQs, and a tagged map of the venue, into a retrieval layer the dialogue answers from, maintained by the content owners without engineering help. Behavior and language are configuration, so a new venue or language is content, not code.

Build the operator console

  • Build the Wizard-of-Oz console to the HRI scientist’s workflow: live view of what the robot hears, sees and intends; approve, correct or trigger skills within the time a person will tolerate; runs on a laptop or tablet.

 

Skills & Experience

Required

  • 3+ years building production software, including data pipelines that ran against live data: ingestion, validation and quality control, format conversion, and the operations behind them.
  • Experience with multimodal or time-series sensor data (video, audio, IMU, robot joint states): synchronization, storage formats (Parquet, HDF5, MCAP or similar) and dataset versioning.
  • Hands-on experience with speech and language pipelines: streaming speech recognition, text-to-speech, and LLM integration with retrieval over a knowledge base, in at least one system that ran with real users.
  • Strong Python and one of TypeScript, C++ or Go; comfortable with Linux, Docker, GPU inference serving and local-network deployment.
  • Experience building operator or internal tools with a web front end, and integrating with a hardware API (ROS 2, a robot SDK or a device SDK) as a client.
  • Native-level Mandarin and professional working English; eligible to work in China.

 

Preferred

  • Voice-agent frameworks (Pipecat, LiveKit Agents, TEN or similar) and self-hosted open models (Qwen-class LLMs, Whisper-class speech recognition).
  • Multilingual language identification and switching, or conversational AI for a second language.
  • Robot behavior scripting with behavior trees or state machines, or real-time interactive systems such as games or animation.
  • Robot learning data conventions (LeRobot, RLDS) and an understanding of how imitation-learning or VLA models consume data; multimodal annotation or observability platforms.
  • Teleoperation or Wizard-of-Oz tooling and turning operator corrections into training data.
  • Robots or kiosks that interact with the public, and privacy and consent requirements for recorded interactions (PIPL, GDPR).
  • SLAM, navigation, or real-to-sim and simulation work. Venue maps, reconstructed scenes and simulated evaluation runs all flow through the data pipeline you own.

 

What success looks like
  • First 3 months: a live, multilingual interaction demo on the real robot in front of an audience. Not polished: scripted interactions plus open Q&A on a venue knowledge base, in two languages with automatic switching, with one operator on your console; every interaction logged and exportable for annotation from that first demo; speech-stack decision made from measured data.
  • By 6 months: capture-device and robot recordings ingested, QC’d and delivered in LeRobotDataset / RLDS / MCAP against the technical lead’s quality metrics; autonomy rate and operator calls per hour reported weekly; skill library and knowledge base maintained by the content owners without you.
  • By 12 months: observability and QC stack running against live collection without engineering intervention; a new language added as configuration in under a week; the stack deployed on a second robot in another location from your documentation.

 

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.

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 845, the most 1,344, and the latest week had 1,007.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Shanghai

Working pattern and location restrictions need checking in the full posting.

Work authorization
- Experience building operator or internal tools with a web front end, and integrating with a hardware API (ROS 2, a robot SDK or a device SDK) as a client. - Native-level Mandarin and professional working English; eligible to work in China. Preferred

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.