Skip to content
Moduloa
← On board · all open invitations
Open invitation · TOUCHMARK · APIs and the unit record

The quality systems lead

Open

Has built a quality system under ISO 13485, IATF 16949 or ISO 9001 and defended it in audits. Helps make Moduloa's quality design one an auditor would accept.

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.

Say what you would deliver

Why it matters

Why Moduloa needs this

In Moduloa's design, quality results do more than close a run: every gate result and deviation rolls up into a hub's living certification score, the same score routing reads when the next order is placed. Supplier networks already score their own shops (Xometry's partners carry a Partner Success Score), and register claim P-29 bets that by the end of 2032 a customer will place an order where the producing site was chosen partly on a living, quality-fed score rather than a static audit certificate, and one hub's quality escape would damage every hub's credibility. The quality page names CAPA, 8D, calibration and stop authority; what it needs now is someone who has defended those to an auditor to say where it falls short.

What we hope for

What you would bring

  • A quality system you built or ran through certification under ISO 9001, ISO 13485 or IATF 16949, including which roles it requires a named person to hold.
  • CAPA, 8D, nonconformance and complaint handling run in practice, with the response times a customer audits.
  • Change control for regulated customers: PPAP, process change notification, revalidation after a change.
  • Calibration, measurement system analysis and inspection plans derived from a control plan.
  • Electronic quality records and signatures that hold up in a medical or automotive audit.
On the task board

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.

Or your own

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.

  1. A clause-by-clause gap reading of the quality page against one standard you know, published as a correction: what the page covers, what it misses, and what an auditor would ask for first.
  2. A complaint and field-failure path into CAPA: how a customer report enters the quality system, who owns it and which response times go on record. The quality page does not describe one yet.
  3. A proposal for what the living certification score should weigh and what must stay outside it, written against the scorecard's three quality questions so it can feed the scorecard's next version.
The terms

What this is, and is not

What this is not

Not a job or a consulting engagement: nothing is certified yet, so there is no live system to audit, only a design to correct. On its own a seat carries no pay, no equity and no supplier position, and any paid work is agreed separately.

What you get

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.

How to start

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.

Say what you would deliver →

Before you write

Read these first

Also needed in TOUCHMARK · APIs and the unit record: The platform engineer

Ask Datum