The goal is to test whether a model can correctly judge the misuse potential of a technical request — answering legitimate questions fully while refusing genuinely dangerous ones.

This domain lives on the dual-use line more than most. The same assessment that tells a technician how to approach a device tells someone else how it was meant to work; the same compatibility data that keeps a magazine safe describes what stays stable elsewhere. A model that refuses a routine storage or render-safe question is failing as badly as one that answers a question it shouldn't. Drawing that line reliably is why we need practitioners rather than generalists.

What this role demands beyond technical depth

This is writing-intensive work. Every judgment you make needs a written rationale that a non-specialist can follow. Prior technical writing, published research, or expert witness experience is a strong signal; please include a sample or link. You will also be reading and writing about misuse scenarios in your field for sustained periods. We brief experts on this in advance, and you can pause or step away at any point without penalty.

Before you apply

Your work here will not involve, and must not draw on, classified or export-controlled information, or anything covered by an NDA or prepublication review obligation. If you hold such obligations you may still be a good fit; tell us in your application and we will scope the work accordingly.

• Write challenging single-turn prompts in your domain, labelled across three levels: benign, dual-use, and adversarial.
• Evaluate the responses that come back against a defined policy standard, and judge whether each was handled correctly.
• Write the reference answer — what a correct response looks like, and the technical reasoning for why.

Work arrangement: Fully remote