The robotics engineer
OpenWrites robot methods for hard assembly steps, as task records not tied to one robot maker, and helps define the missing interface between humanoids and production systems.
An open invitation, not a vacancy: several people can take it at once, and it carries no number until you commit to something specific. This page says what Moduloa hopes for and where a first contribution could start.
Why Moduloa needs this
In the factory OS a robot task is a record: skill, tool, success rate, safety limits and expected cycle time, which is what would make a humanoid a schedulable resource rather than a demo. The Journal found that the interface between a humanoid and the system holding the order has no name, no standard and no owner, and recommends writing a humanoid profile of an existing interface such as VDA 5050 rather than a new one. Humanoid assembly is the design target, but the execution page is plain that the cells are proven and the humanoid layer is not.
What you would bring
- Robot applications you have taken to a real line: insertion, screwdriving, cable routing or other force-controlled assembly.
- Measured reliability rather than demos: task success rate, mean time between interventions, cycle time, safe failure behavior.
- ROS 2, MoveIt or vendor controller APIs, and the fleet and orchestration interfaces above them, such as VDA 5050, OPC UA and MQTT.
- A grounded view of learned policies (vision-language-action models such as NVIDIA's GR00T, and open toolkits such as LeRobot) and of where a scripted fixed cell still wins.
- Experience writing specifications that other teams actually implement.
Tasks that suit you
Each has a plain test for done. Ask to commit to one: name what you will deliver and a date no more than three months after it is accepted. Several people can work on the same task, each with its own deliverable.
- J-04 Robot task interface · Three to four weeks · Ask to commit to J-04 →
- F-01 Factory OS data model v0.1 · Six to twelve weeks · Ask to commit to F-01 →
Other first deliverables
Each is specific enough that by its date anyone can tell whether it was delivered. Some are a task above in a smaller form. Name one, or a better one.
- The first entry in the robot task library, an open Stage 0 task: one EX-100 step, such as fitting the seal and lid at 0.6 N·m, written as a task record with tool, fixture, tolerance, success criterion, safety limits and the result it reports back.
- A gap map of VDA 5050 v3.0 against manipulation work: which messages and factsheet fields carry over and which are missing, as the outline of the humanoid profile the 29 August note recommends.
- A reasoned challenge to the cells-versus-humanoid split the execution page shows for the five EX-100 steps: which belong in a fixed cell, which need a flexible robot, and what measured evidence would move a step across.
What this is, and is not
Not a request to build a humanoid or a foundation model: the Journal argues Moduloa should do neither, and there is no robot floor yet. On its own a seat carries no pay, no equity and no supplier position, and any paid work is agreed separately.
When your commitment is accepted, it shows on the task and on your seat card, and a first commitment takes the next permanent number on the register, with your name, a link and your date. When the work is delivered in the open you are aboard and a certificate is issued. Nothing is paid for a seat and none is for sale: on its own a seat carries no equity and no supplier position, and any paid work is agreed separately, on its own terms. The entry stays either way: a commitment not delivered by its date is marked lapsed and dated, never removed.
Pick a task that suits you and ask to commit to it, or name your own first deliverable: what you will deliver and a date no more than three months after it is accepted. Write to shk@moduloa.com, or use the link on any task, which opens the contact page with the subject filled in. It does not have to be large. It has to be specific enough that anyone can tell by its date whether it was delivered.
Read these first
- moduloa.com/journal/2026-08-29-the-interface-is-being-written-now
- moduloa.com/manufacturing/os
- moduloa.com/manufacturing/execution
- moduloa.com/humanoid-race
Also needed in JACQUARD · Assembly floor: The toolmaker · The test and flashing engineer · The intralogistics engineer · The robot safety engineer · The hub partner · The pilot partner