What the work actually involves
You receive a design brief and build it in FreeCAD — Part Design, Sketcher, TechDraw, assemblies, STEP/IGES export — inside a remote Ubuntu desktop reached through noVNC or a similar VNC client. The session is a reference demonstration, so the trajectory matters as much as the finished body: clicks, sketch constraint choices, dimension entries, parameter inputs and the order you applied them. Expect roughly 60 minutes of average handling time per task, with pay assessed per task.
The second half of the job is adversarial. You flag briefs that are ambiguous, sketches that are under-constrained, library parts that don't exist in the environment, and FreeCAD crashes or regressions that make a task unsolvable as written. Then you deliberately solve the same part a different way — pad versus revolve, a different sketch plane, a different constraint scheme — to check whether the automated grading script accepts a technically correct alternative or wrongly rejects it. Written feedback on solvability is a deliverable, not an afterthought.
What the screen looks for
- Real FreeCAD hours, not general CAD familiarity — the workbench names, the topological naming problem, how you rescue an over-constrained sketch
- Habits of fully constrained, parametrically robust models rather than whatever geometry happens to look right
- Judgment about when a brief is genuinely under-specified versus when you're expected to make a reasonable engineering assumption and log it
- Comfort working in a laggy remote Linux desktop without losing precision
Logistics
Fully remote and asynchronous, per-task pay, initial duration around five weeks with possible extension and an immediate start. You need your own reliable machine and connection good enough for a usable VNC session. Selection is an interest form followed by profile review, so the details you enter — FreeCAD versions used, workbenches, kinds of parts modeled — are what gets read.