What the work actually involves

You are not teaching and you are not supporting end users. You are constructing test fixtures inside Moodle so an AI agent can be measured on whether it can do LMS administration correctly. A typical task starts with realistic academic material you author yourself — a syllabus, a grading policy, a question bank, a student cohort — and ends with a machine-checkable definition of success.

  • Map Moodle capabilities into discrete task units: course creation, enrollment methods, role and capability overrides, gradebook aggregation, quiz settings, competency frameworks, SCORM packages.
  • Execute the workflow yourself in Moodle and record a reference trace of every step and setting.
  • Define verification checks — often SQL against `mdl_course`, `mdl_grade_items`, `mdl_quiz`, or file-level inspection of `.mbz` backup archives and their XML.
  • Review other contributors' task instructions for accuracy, solvability, and whether the stated answer is genuinely the only correct one.
  • Write short technical explanations of why a permission structure resolves the way it does, or why a Natural versus Weighted Mean aggregation produces a given course total.

What the screen is looking for

The hiring filter is depth of hands-on Moodle administration, not breadth of edtech exposure. Expect follow-up questions on specifics that only an administrator would know: how capability overrides interact across context levels, what happens to a grade item's weight when extra credit is toggled under Natural aggregation, how hidden and excluded grades affect aggregation, where cohort sync sits relative to manual enrollment. Vague familiarity — "I've used Moodle at my institution" — does not survive two follow-ups. Clear written English matters because task instructions are a deliverable, not a side effect.

Logistics

Fully remote, hourly, asynchronous. Stated duration is five weeks with possible extension based on project needs, and the start date is as soon as possible. Pay band is undisclosed in this listing; Turing typically sets hourly rates per project and per expert during onboarding. Expect to need your own Moodle instance or sandbox access to reproduce workflows, and comfort with at least basic SQL querying against a Moodle database.