What the work involves

This is applied-software work, not writing about software. You will be asked to carry out realistic MATLAB tasks on your own Windows machine — building and debugging scripts, working with matrices and data imports, running Simulink or toolbox workflows, plotting and tuning figures, processing signals or images, profiling slow code — while capturing the screen so that a model can learn what competent use of the application actually looks like. Expect a mix of task execution, step-by-step documentation of what you did and why, and judgment calls about whether a recorded workflow is a good example or a sloppy one.

Because the capture is the deliverable, mechanical details matter as much as domain skill. Screenshots must exceed 2.5 megapixels, which in practice means a single display at QHD or above (4:3 at 1826×1370, 16:9 at 2109×1186, 16:10 at 2000×1250, 3:2 at 1937×1291, 21:9 at 2416×1036 or better), or two side-by-side 1080p-plus monitors captured as one spanning image. A lone 1080p screen does not qualify, even if it is half of a dual setup.

What the platform screens for

  • Genuine, current access. You are expected to be able to open MATLAB on Windows today, under your own licence or an institutional one you legitimately hold.
  • Depth of real use. Screens probe for the kind of detail that only comes from having shipped work: which toolboxes, what versions, what you did when a solver would not converge or a script ran out of memory.
  • Domain context. Most strong candidates come from electrical, mechanical, control-systems, aerospace, or signal/image processing backgrounds and can tie MATLAB use to an engineering problem.
  • Evaluation judgment. Can you tell a correct-but-unidiomatic solution from a genuinely good one, and explain the difference concretely.

Logistics

Fully remote and asynchronous, contractor basis, paid hourly in the $45–55/hr band observed on this listing — rates vary by task type and are not guaranteed. Work arrives in batches; contributors typically pick up somewhere between a few hours and twenty hours a week depending on availability and how much is queued. There is no fixed schedule, but tasks often carry turnaround windows measured in days, so intermittent availability should be flagged honestly up front.