Ashby integration, example

An Ashby customer's jobs on RobotTraining.jobs

This is the integration running on the test account Ashby gave us. The postings below are Ashby's sample data, not real openings, and they appear on this page only. A customer who switches the integration on gets exactly this, with its robot roles on the board.

How to switch it on

How it works

From Ashby to an application in Ashby

1
You switch it on in Ashby
An Ashby admin enables the RobotTraining.jobs tile under Admin, Integrations. Nothing is set per job, and no API key is used.
2
Ashby shares your published jobs
Your published postings appear in Ashby's partner job feed for us. We read it every day, together with your public Ashby job board, and we write nothing to Ashby.
3
We list the robot roles
Each posting is screened by its title and its own description. Hands-on robot work gets a page on the board; everything else is left out.
4
Applicants apply in Ashby
The role's Apply button opens your posting's Ashby application form, so the applicant and the application live in your Ashby pipeline. We collect no application.

Step 2

What Ashby shares

Ashby's feed lists 10 published postings for the test organization “RobotTraining.jobs” (job board demo.robottraining.com), as built by Ashby on Nov 12, 2026, 11:21 UTC. For each posting it gives the title, team, location, employment type, pay, description and the address of the posting on the customer's Ashby job board.

Steps 3 and 4

The role we list

Hands-on robot work: operating or teleoperating robots, collecting data for robot learning, test driving, drone and fleet work. This is what a listed role carries, and where its Apply button goes.

Ashby test account · Robot Teleoperation

Robot Teleoperator (Demo posting)

Remote · Full time · Posted Nov 10, 2026

DEMO POSTING for the RobotTraining.jobs integration review. This is not a real opening. You will teleoperate a robot arm with a VR headset and hand controllers to perform household manipulation tasks, recording demonstrations that are used as training data for the robot's AI model. You will reset the scene between episodes, mark each recorded episode as a success or a failure, and report hardware issues to the robotics team. No engineering degree is needed; training is provided.

Apply on Ashby

Opens this posting's Ashby application form. On the board the button names the employer.

Step 3

Shared with us, not listed

Engineering, research, office and sales roles reach us through the same feed and stay off the board. Nothing needs to be excluded by hand.

RecruiterRecruiting · not hands-on robot work
Product ManagerProduct · not hands-on robot work
Infrastructure EngineerInfrastructure Engineering · not hands-on robot work
Engineering ManagerProduct Engineering · not hands-on robot work
Backend EngineerProduct Engineering · not hands-on robot work
Head of RecruitingRecruiting · not hands-on robot work
Account ExecutiveSales · not hands-on robot work
Director of Platform EngineeringInfrastructure Engineering · not hands-on robot work
Frontend EngineerProduct Engineering · not hands-on robot work

Good to know

Limits and edge cases

We read the feed every day, so a role you publish shows after the next read, and one you close or unpublish drops off at the next read.
A customer with no hands-on robot roles is not listed, and nothing of it is shown.
We list only postings that are in Ashby's feed for us. A posting Ashby does not share with us stays off the board, even when it is on your own job board.
The same job posted for several locations is shown as one job with each location, each with its own Apply link.
We read two things, both public and read-only: Ashby's partner job feed, and each listed posting on your Ashby job board (its application questions, and whether it is still open). We hold no API key and never write to Ashby.
Disabling the tile in Ashby takes the roles listed through the integration off the board at the next read.