What the work actually involves

You author engineering problems that a strong model should struggle with, then judge whether its answers hold up. A typical task starts from a realistic scenario — a mixed-model assembly line with an unbalanced takt, a distribution network choosing between cross-dock and direct ship, a control chart flagging a shift that turns out to be a measurement-system problem — and requires you to supply the correct solution path, the numeric answer where one exists, and the reasoning a grader can check against. The second half of the job is evaluation: reading model output, deciding whether it reached a defensible answer or a lucky one, and writing feedback specific enough that someone can act on it. "Wrong" is not useful; "applied EOQ without adjusting for the quantity discount break at 500 units" is.

Subject coverage spans the standard IE curriculum and its industrial practice: process optimization and linear/integer programming, production planning and MRP logic, facility layout and material handling, quality control and SPC, supply chain design, work measurement and time study, ergonomics, queueing, and discrete-event simulation. Most authors specialize in three or four of these rather than claiming all of them.

What the screen looks for

  • Real practice, not just coursework. Screeners probe for plants, projects, and numbers — what the line rate was, what the change saved, why the first attempt failed.
  • Calibration on difficulty. A question that a model answers correctly on the first pass wastes a task slot; a question that is ambiguous rather than hard is worse.
  • Defensible grading. You will be asked to justify a score when the model's answer differs from yours but is not obviously wrong — standard-time assumptions, rounding conventions, and modeling choices all produce legitimate disagreement.
  • Written precision. Feedback is the deliverable. Vague prose fails the screen even when the engineering behind it is sound.

Logistics

Fully remote and asynchronous — no standing meetings, no fixed hours. Contributors typically pick up batches and commit to a weekly hour range; consistent availability matters more than large blocks. Pay is hourly and has been observed between $75 and $115, varying with specialization depth, credentials, and task type; it is not guaranteed and rates are set per project. Expect calibration rounds early on, where your grading is compared against other reviewers before your volume increases.