Robot Operator, Data Collection
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the content.
The posting text:
"About Mind Mind Robotics is building Physical AI for real-world industrial deployment, starting with the factory floor. We believe the hardest problems in AI are solved when researchers and engineers are hands-on with the physical world every day - and we're looking for people who are passionate about robotics, value ownership, and are excited to tackle difficult problems. About The Team And The Role The Data Collection team owns the raw material our foundation models are trained on. We pilot robots through real industrial manipulation work. The skills could be pick and place, sorting, fastening, seating connectors but then we turn those hours into the demonstration data our models learn from. With Rivian as our first manufacturing partner, we are emulating the live, high-variability work inside an active production facility. As a Robot Operator, you are the person actually showing the robot how the work is done. You'll spend your day on the floor running robots through tasks, some routine, some brand new, some that don't work yet and need figuring out. Along the way you will be developing judgment about what separates a good demonstration from a bad one. You'll be closer to the hardware than anyone at the company, which means you'll be the first to know what's awkward, what's unsafe, and what should change. We're early, so the process you learn this month may get rewritten next month, usually because someone on the team found a better one."
Then "Responsibilities" heading appears, then bullet list of responsibilities (some sentences separated by periods). We need to convert to
- items.
Then "Requirements" heading, then list of requirements.
We need to preserve all substantive info. Also note there is a line: "Expect to be on your feet and moving for roughly 5–6 hours of the day. Operating the rigs is sustained, full-body work: reaching, bending, crouching, twisting, holding position, and extended use of both arms and hands. Come ready for that.This is not a lifting role. There is no significant lift or carry requirement. The demand is sustained manipulation and posture, not strength.We can accommodate seated and wheelchair-based operators. Our control setups can be operated seated, and we're willing to adapt rigs, station height, and task assignment to make that work. If you use a wheelchair or have other accessibility needs, this role is open to you." This is part of responsibilities? It appears after responsibilities list but before Requirements. It's about physical demands and accommodations. Should be part of responsibilities or maybe a separate section like "Physical Demands" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could include it under Responsibilities as prose or list items. Since it's not a list but prose, we can put in
under Responsibilities after the list.
Similarly, there is a line: "Experience with humanoid or mobile robots, VR/AR systems, or motion capture is a plusExposure to how ML training data is produced is a plusLight scripting (Python or shell) is a plusTeaching or coaching experience is a plusShift work in a safety-sensitive setting is a plusTime in a manufacturing or production environment is a plus". This is under Requirements as "plus" items. Should be part of Requirements list.
We need to ensure we don't create sections with filler. We'll have sections: About the role (maybe combine About Mind and About The Team And The Role). Use
About the role
then with the prose.
Then
Responsibilities
then - items for each responsibility bullet. Then maybe a
for the physical demands paragraph.
Then
Requirements
then - items for each requirement bullet.
We must not include any boilerplate like EEO etc. There's none.
We need to preserve all substantive info. Let's extract.
First, combine About Mind and About The Team And The Role into one paragraph.
Original:
"About Mind Mind Robotics is building Physical AI for real-world industrial deployment, starting with the factory floor. We believe the hardest problems in AI are solved when researchers and engineers are hands-on with the physical world every day - and we're looking for people who are passionate about robotics, value ownership, and are excited to tackle difficult problems. About The Team And The Role The Data Collection team owns the raw material our foundation models are trained on. We pilot robots through real industrial manipulation work. The skills could be pick and place, sorting, fastening, seating connectors but then we turn those hours into the demonstration data our models learn from. With Rivian as our first manufacturing partner, we are emulating the live, high-variability work inside an active production facility. As a Robot Operator, you are the person actually showing the robot how the work is done. You'll spend your day on the floor running robots through tasks, some routine, some brand new, some that don't work yet and need figuring out. Along the way you will be developing judgment about what separates a good demonstration from a bad one. You'll be closer to the hardware than anyone at the company, which means you'll be the first to know what's awkward, what's unsafe, and what should change. We're early, so the process you learn this month may get rewritten next month, usually because someone on the team found a better one."
We'll output that as a single
.
Now Responsibilities bullet list: The text after "Responsibilities" heading:
"Pilot the robots. Operate leader/follower rigs and other control setups to run robots through industrial manipulation tasks: pick and place, bin sorting, fastener driving, connector seating, tool use.Produce data the models can learn from. Execute repeated demonstrations to a consistent standard — clean motion, consistent framing, sensible recovery when something goes wrong — and develop the eye to tell a usable episode from an unusable one.Own the quality of your own output. Review, label, and flag your own bad episodes rather than letting them through, and keep clear session logs another person can act on.Work safely, so we can work fast. Run pre-power-up safety checks, know where the stop is, follow lockout procedure, and raise concerns early. Careful people let us move quickly.Run new tasks from a cold start. Take an unproven task description, work out a repeatable approach on the hardware, and document what you found.Feed findings back into how the work is designed. Report rig ergonomics problems, ambiguous instructions, and task setups that don't survive contact with reality to the engineers and researchers who own them.Help the next person. Train new operators on tasks you've mastered and sharpen the written procedures as you go. There's a clear path toward owning task areas and training operators — that's the growth we expect, not a day-one expectation.Expect to be on your feet and moving for roughly 5–6 hours of the day. Operating the rigs is sustained, full-body work: reaching, bending, crouching, twisting, holding position, and extended use of both arms and hands. Come ready for that.This is not a lifting role. There is no significant lift or carry requirement. The demand is sustained manipulation and posture, not strength.We can accommodate seated and wheelchair-based operators. Our control setups can be operated seated, and we're willing to adapt rigs, station height, and task assignment to make that work. If you use a wheelchair or have other accessibility needs, this role is open to you."
We need to split into list items. Each sentence seems to be a responsibility. Let's identify:
1. Pilot the robots. Operate leader/follower rigs and other control setups to run robots through industrial manipulation tasks: pick and place, bin sorting, fastener driving, connector seating, tool use.
2. Produce data the models can learn from. Execute repeated demonstrations to a consistent standard — clean motion, consistent framing, sensible recovery when something goes wrong — and develop the eye to tell a usable episode from an unusable one.
3. Own the quality of your own output. Review, label, and flag your own bad episodes rather than letting them through, and keep clear session logs another person can act on.
4. Work safely, so we can work fast. Run pre-power-up safety checks, know where the stop is, follow lockout procedure, and raise concerns early. Careful people let us move quickly.
5. Run new tasks from a cold start. Take an unproven task description, work out a repeatable approach on the hardware, and document what you found.
6. Feed findings back into how the work is designed. Report rig ergonomics problems, ambiguous instructions, and task setups that don't survive contact with reality to the engineers and researchers who own them.
7. Help the next person. Train new operators on tasks you've mastered and sharpen the written procedures as you go. There's a clear path toward owning task areas and training operators — that's the growth we expect, not a day-one expectation.
8. Expect to be on your feet and moving for roughly 5–6 hours of the day. Operating the rigs is sustained, full-body work: reaching, bending, crouching, twisting, holding position, and extended use of both arms and hands. Come ready for that.
9. This is not a lifting role. There is no significant lift or carry requirement. The demand is sustained manipulation and posture, not strength.
10. We can accommodate seated and wheelchair-based operators. Our control setups can be operated seated, and we're willing to adapt rigs, station height, and task assignment to make that work. If you use a wheelchair or have other accessibility needs, this role is open to you.
We could combine some but it's okay.
Now Requirements section: after "Requirements" heading:
"Roughly one year or more of work history where you were accountable for your own output: showed up on time, held to a standard, dealt with the consequences when something went wrong. The industry doesn't matter; having been held to a bar does. No degree required — relevant hands-on experience or equivalent experience is what counts.Genuine interest in robots and AI. You don't need expertise. You do need to want to know how the thing works, and to get a little excited when it does something new.A demonstrated safety mindset. Steady around powered equipment, follows procedure without being watched, comfortable stopping work to raise a concern.Strong hand/eye coordination and spatial reasoning. You pick up physical skills quickly and can explain what makes one approach better than another.Tolerance for high-repetition work at a consistent quality bar across a full shift.Clear, plain written communication. Enough to log what happened in a session so someone else can understand and act on it.Comfort with direct feedback, both getting it and giving it.Tolerance for change. Early-stage means unfinished. If that sounds fun rather than stressful, that's a good sign.Authorization to work on-site in Palo Alto, CA for a role that cannot be performed remotely.Experience with humanoid or mobile robots, VR/AR systems, or motion capture is a plusExposure to how ML training data is produced is a plusLight scripting (Python or shell) is a plusTeaching or coaching experience is a plusShift work in a safety-sensitive setting is a plusTime in a manufacturing or production environment is a plus"
We need to split into list items. Let's identify each bullet:
1. Roughly one year or more of work history where you were accountable for your own output: showed up on time, held to a standard, dealt with the consequences when something went wrong. The industry doesn't matter; having been held to a bar does.
2. No degree required — relevant hands-on
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the content. The posting text: "About Mind Mind Robotics is building Physical AI for real-world industrial deployment, starting with the factory floor. We believe the hardest problems in AI are solved when researchers and engineers are hands-on with the physical world every day - and we're looking for people who are passionate about robotics, value ownership, and are excited to tackle difficult problems. About The Team And The Role The Data Collection team owns the raw material our foundation models are trained on. We pilot robots through real industrial manipulation work. The skills could be pick and place, sorting, fastening, seating connectors but then we turn those hours into the demonstration data our models learn from. With Rivian as our first manufacturing partner, we are emulating the live, high-variability work inside an active production facility. As a Robot Operator, you are the person actually showing the robot how the work is done. You'll spend your day on the floor running robots through tasks, some routine, some brand new, some that don't work yet and need figuring out. Along the way you will be developing judgment about what separates a good demonstration from a bad one. You'll be closer to the hardware than anyone at the company, which means you'll be the first to know what's awkward, what's unsafe, and what should change. We're early, so the process you learn this month may get rewritten next month, usually because someone on the team found a better one." Then "Responsibilities" heading appears, then bullet list of responsibilities (some sentences separated by periods). We need to convert to
- items.
Then "Requirements" heading, then list of requirements.
We need to preserve all substantive info. Also note there is a line: "Expect to be on your feet and moving for roughly 5–6 hours of the day. Operating the rigs is sustained, full-body work: reaching, bending, crouching, twisting, holding position, and extended use of both arms and hands. Come ready for that.This is not a lifting role. There is no significant lift or carry requirement. The demand is sustained manipulation and posture, not strength.We can accommodate seated and wheelchair-based operators. Our control setups can be operated seated, and we're willing to adapt rigs, station height, and task assignment to make that work. If you use a wheelchair or have other accessibility needs, this role is open to you." This is part of responsibilities? It appears after responsibilities list but before Requirements. It's about physical demands and accommodations. Should be part of responsibilities or maybe a separate section like "Physical Demands" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could include it under Responsibilities as prose or list items. Since it's not a list but prose, we can put in
under Responsibilities after the list. Similarly, there is a line: "Experience with humanoid or mobile robots, VR/AR systems, or motion capture is a plusExposure to how ML training data is produced is a plusLight scripting (Python or shell) is a plusTeaching or coaching experience is a plusShift work in a safety-sensitive setting is a plusTime in a manufacturing or production environment is a plus". This is under Requirements as "plus" items. Should be part of Requirements list. We need to ensure we don't create sections with filler. We'll have sections: About the role (maybe combine About Mind and About The Team And The Role). Use
About the role
thenwith the prose. Then
Responsibilities
then- items for each responsibility bullet. Then maybe a
for the physical demands paragraph. Then
Requirements
then- items for each requirement bullet.
We must not include any boilerplate like EEO etc. There's none.
We need to preserve all substantive info. Let's extract.
First, combine About Mind and About The Team And The Role into one paragraph.
Original:
"About Mind Mind Robotics is building Physical AI for real-world industrial deployment, starting with the factory floor. We believe the hardest problems in AI are solved when researchers and engineers are hands-on with the physical world every day - and we're looking for people who are passionate about robotics, value ownership, and are excited to tackle difficult problems. About The Team And The Role The Data Collection team owns the raw material our foundation models are trained on. We pilot robots through real industrial manipulation work. The skills could be pick and place, sorting, fastening, seating connectors but then we turn those hours into the demonstration data our models learn from. With Rivian as our first manufacturing partner, we are emulating the live, high-variability work inside an active production facility. As a Robot Operator, you are the person actually showing the robot how the work is done. You'll spend your day on the floor running robots through tasks, some routine, some brand new, some that don't work yet and need figuring out. Along the way you will be developing judgment about what separates a good demonstration from a bad one. You'll be closer to the hardware than anyone at the company, which means you'll be the first to know what's awkward, what's unsafe, and what should change. We're early, so the process you learn this month may get rewritten next month, usually because someone on the team found a better one."
We'll output that as a single
. Now Responsibilities bullet list: The text after "Responsibilities" heading: "Pilot the robots. Operate leader/follower rigs and other control setups to run robots through industrial manipulation tasks: pick and place, bin sorting, fastener driving, connector seating, tool use.Produce data the models can learn from. Execute repeated demonstrations to a consistent standard — clean motion, consistent framing, sensible recovery when something goes wrong — and develop the eye to tell a usable episode from an unusable one.Own the quality of your own output. Review, label, and flag your own bad episodes rather than letting them through, and keep clear session logs another person can act on.Work safely, so we can work fast. Run pre-power-up safety checks, know where the stop is, follow lockout procedure, and raise concerns early. Careful people let us move quickly.Run new tasks from a cold start. Take an unproven task description, work out a repeatable approach on the hardware, and document what you found.Feed findings back into how the work is designed. Report rig ergonomics problems, ambiguous instructions, and task setups that don't survive contact with reality to the engineers and researchers who own them.Help the next person. Train new operators on tasks you've mastered and sharpen the written procedures as you go. There's a clear path toward owning task areas and training operators — that's the growth we expect, not a day-one expectation.Expect to be on your feet and moving for roughly 5–6 hours of the day. Operating the rigs is sustained, full-body work: reaching, bending, crouching, twisting, holding position, and extended use of both arms and hands. Come ready for that.This is not a lifting role. There is no significant lift or carry requirement. The demand is sustained manipulation and posture, not strength.We can accommodate seated and wheelchair-based operators. Our control setups can be operated seated, and we're willing to adapt rigs, station height, and task assignment to make that work. If you use a wheelchair or have other accessibility needs, this role is open to you." We need to split into list items. Each sentence seems to be a responsibility. Let's identify: 1. Pilot the robots. Operate leader/follower rigs and other control setups to run robots through industrial manipulation tasks: pick and place, bin sorting, fastener driving, connector seating, tool use. 2. Produce data the models can learn from. Execute repeated demonstrations to a consistent standard — clean motion, consistent framing, sensible recovery when something goes wrong — and develop the eye to tell a usable episode from an unusable one. 3. Own the quality of your own output. Review, label, and flag your own bad episodes rather than letting them through, and keep clear session logs another person can act on. 4. Work safely, so we can work fast. Run pre-power-up safety checks, know where the stop is, follow lockout procedure, and raise concerns early. Careful people let us move quickly. 5. Run new tasks from a cold start. Take an unproven task description, work out a repeatable approach on the hardware, and document what you found. 6. Feed findings back into how the work is designed. Report rig ergonomics problems, ambiguous instructions, and task setups that don't survive contact with reality to the engineers and researchers who own them. 7. Help the next person. Train new operators on tasks you've mastered and sharpen the written procedures as you go. There's a clear path toward owning task areas and training operators — that's the growth we expect, not a day-one expectation. 8. Expect to be on your feet and moving for roughly 5–6 hours of the day. Operating the rigs is sustained, full-body work: reaching, bending, crouching, twisting, holding position, and extended use of both arms and hands. Come ready for that. 9. This is not a lifting role. There is no significant lift or carry requirement. The demand is sustained manipulation and posture, not strength. 10. We can accommodate seated and wheelchair-based operators. Our control setups can be operated seated, and we're willing to adapt rigs, station height, and task assignment to make that work. If you use a wheelchair or have other accessibility needs, this role is open to you. We could combine some but it's okay. Now Requirements section: after "Requirements" heading: "Roughly one year or more of work history where you were accountable for your own output: showed up on time, held to a standard, dealt with the consequences when something went wrong. The industry doesn't matter; having been held to a bar does. No degree required — relevant hands-on experience or equivalent experience is what counts.Genuine interest in robots and AI. You don't need expertise. You do need to want to know how the thing works, and to get a little excited when it does something new.A demonstrated safety mindset. Steady around powered equipment, follows procedure without being watched, comfortable stopping work to raise a concern.Strong hand/eye coordination and spatial reasoning. You pick up physical skills quickly and can explain what makes one approach better than another.Tolerance for high-repetition work at a consistent quality bar across a full shift.Clear, plain written communication. Enough to log what happened in a session so someone else can understand and act on it.Comfort with direct feedback, both getting it and giving it.Tolerance for change. Early-stage means unfinished. If that sounds fun rather than stressful, that's a good sign.Authorization to work on-site in Palo Alto, CA for a role that cannot be performed remotely.Experience with humanoid or mobile robots, VR/AR systems, or motion capture is a plusExposure to how ML training data is produced is a plusLight scripting (Python or shell) is a plusTeaching or coaching experience is a plusShift work in a safety-sensitive setting is a plusTime in a manufacturing or production environment is a plus" We need to split into list items. Let's identify each bullet: 1. Roughly one year or more of work history where you were accountable for your own output: showed up on time, held to a standard, dealt with the consequences when something went wrong. The industry doesn't matter; having been held to a bar does. 2. No degree required — relevant hands-on
- items for each requirement bullet.
We must not include any boilerplate like EEO etc. There's none.
We need to preserve all substantive info. Let's extract.
First, combine About Mind and About The Team And The Role into one paragraph.
Original:
"About Mind Mind Robotics is building Physical AI for real-world industrial deployment, starting with the factory floor. We believe the hardest problems in AI are solved when researchers and engineers are hands-on with the physical world every day - and we're looking for people who are passionate about robotics, value ownership, and are excited to tackle difficult problems. About The Team And The Role The Data Collection team owns the raw material our foundation models are trained on. We pilot robots through real industrial manipulation work. The skills could be pick and place, sorting, fastening, seating connectors but then we turn those hours into the demonstration data our models learn from. With Rivian as our first manufacturing partner, we are emulating the live, high-variability work inside an active production facility. As a Robot Operator, you are the person actually showing the robot how the work is done. You'll spend your day on the floor running robots through tasks, some routine, some brand new, some that don't work yet and need figuring out. Along the way you will be developing judgment about what separates a good demonstration from a bad one. You'll be closer to the hardware than anyone at the company, which means you'll be the first to know what's awkward, what's unsafe, and what should change. We're early, so the process you learn this month may get rewritten next month, usually because someone on the team found a better one."
We'll output that as a single
- items for each responsibility bullet. Then maybe a