The test and flashing engineer
OpenDesigns the stations that flash firmware and test a board or finished product, so every unit's result, firmware version included, lands in its own record.
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
On the industrialization page, testing is derived from assembly, never invented: each test traces to a machine-checkable acceptance criterion written at intake and runs at the last moment its feature is still reachable, which is why the EX-100 needs an in-process jig before step 4 seals the test pads. The intake standard already asks for the firmware version and hash of a flashed part, but how firmware would be loaded and verified on the line is not yet written down. That step, and the record it leaves, is what this invitation is for.
What you would bring
- Production test for PCBAs and finished products: in-circuit, flying probe, boundary scan (IEEE 1149.1), functional and end-of-line test.
- Firmware programming in production over JTAG or SWD, with image verification and serial or key provisioning.
- Test fixtures you have built: bed-of-nails, connector cradles, leak test adapters.
- Test software that writes per-serial results, limits and station identity to a database, not a spreadsheet.
- Measurement system analysis (gauge R&R), so a pass at one station means the same as a pass at another.
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-02 Tooling standard v0.1 and the EX-100 jig set · Four to six weeks · Ask to commit to J-02 →
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.
- A proposed flashing step for the EX-100's main PCBA: whether it belongs at the supplier or on the line, where it would sit in the build sequence (before step 4 seals the test pads, or after), what the station verifies (the image hash against the released revision), and the fields it writes to the unit record.
- A per-serial test record schema for jigs TJ-120 and TJ-140, mapped to the OS's quality record object, as JSON Schema with one filled example, offered to the Factory OS data model sketch.
- A design note for TJ-120, the bed-of-nails on a standard frame: which parts of the frame are shared across products and which are made per product.
What this is, and is not
Not a purchase of test equipment and not a role: there is no line to test on 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/manufacturing/industrialization
- moduloa.com/manufacturing/intake
- moduloa.com/manufacturing/quality
- moduloa.com/manufacturing/marking
Also needed in JACQUARD · Assembly floor: The toolmaker · The robotics engineer · The intralogistics engineer · The robot safety engineer · The hub partner · The pilot partner