What the work involves

The core loop is data generation and adjudication. You are given a design intent — a dimensioned sketch, a written spec, a screenshot of a legacy part — and asked to produce a clean, parametric FreeCAD model that matches it, usually with a documented feature tree and named constraints so the model can be regenerated or perturbed programmatically. The other half of the work runs the opposite direction: a model comes out of an AI system, sometimes as a FreeCAD Python script, sometimes as a STEP or STL export, and you have to decide whether it is correct. That means checking whether the sketch is fully constrained, whether the fillets and drafts actually resolve, whether the solid is watertight, whether wall thicknesses and hole positions match the spec, and whether the feature order would survive a parameter change.

Your written rationale is the deliverable as much as the verdict. A rejection that says "geometry is wrong" is not usable; one that says "the pocket is dimensioned from the wrong datum face, so the 12 mm wall becomes 8 mm when the plate thickness parameter is driven to 20 mm" is. Expect to write these in volume, and expect to be spot-checked against other reviewers.

What the platform screens for

  • Real FreeCAD fluency, not general CAD familiarity — the sketcher and constraint solver, PartDesign versus Part workbench, topological naming problems, why a model breaks on rebuild.
  • Scripting: comfort with FreeCAD's Python console and the `App`/`Part` API, enough to generate variants, batch-export, or assert geometric properties in code.
  • Interoperability judgement: STEP, IGES, mesh formats, and what is lost or corrupted in each direction.
  • Engineering grounding: tolerances, GD&T basics, manufacturability, and the ability to say when a model is geometrically valid but would never be made.
  • Calibration under disagreement — whether you can hold a position on a borderline model and also change it when shown a better argument.

Logistics

Fully remote and asynchronous. Tasks are claimed from a queue; there are no fixed shifts, though some projects come with a turnaround window measured in hours rather than days. Most contributors run 10–25 hours a week alongside other work, and volume fluctuates with project cycles — this is contract work, invoiced hourly or per task, not salaried. You need your own machine capable of running FreeCAD comfortably, and a working setup of a recent stable release.