Mercor
- Current roles
- 33
- With pay shown
- 31
- Latest listing check
- Sep 27, 2026
Professions/Research and academia
Browse all profession guidesProfession guide
Research AI work is a fit for people who can judge evidence, spot unsupported claims, and communicate uncertainty without padding.
Research AI evaluation roles fit applicants who can judge evidence, citations, and uncertainty clearly. They are usually selective project opportunities, not guaranteed academic employment.
Provider counts are based on current reviewed listings in this professional category. Empty providers are omitted; use the role details to confirm credentials, tasks, location rules, screening, and project availability.
Based on the current reviewed inventory. Counts describe listings shown here, not platform-wide availability or guaranteed work.
Fit for this field
Not sure this field matches your background? Find my matches
These reviewed roles currently match this professional category. Check each role's requirements and current availability before applying.
Pay
$50–$100/hr
Location
Remote
Pay
$80–$110/hr
Location
Remote
Pay
$80–$110/hr
Location
Remote
Scientific AI projects can ask you to review a claim, check a derivation, create a reference problem or evaluate a computational result. Start with the deliverable: reviewing an explanation is different from writing scientific software, and both differ from running a reproducible test.
Match the actual subfield and methods, not just the degree title. A chemistry or physics doctorate does not establish experience with every simulation, numerical method or software environment. Strong scientific judgment and the coding skills requested by a particular project are separate requirements.
| Task | Evidence to prepare | Important distinction |
|---|---|---|
| Review scientific reasoning | Explain the assumptions, method and limits of a conclusion. | A plausible explanation is not the same as experimental confirmation. |
| Develop a reference problem or answer | Prepare an original or authorized example with a checkable solution. | Do not reuse confidential laboratory work or protected assessment material. |
| Review scientific code | Identify the relevant language, library, units and numerical checks. | Reading code does not establish that you executed it. |
| Run computational tests | Record the environment, inputs, checks and output actually observed. | An unrun test has no result, and one result need not generalize. |
A report says a simulation completed at one parameter setting. A generated answer claims that this proves stability at every setting. Identify the unsupported generalization, explain what the existing result establishes, and list the extra runs or evidence needed to assess the broader claim. Completion alone is not a stability test.
This is an original preparation exercise, not a provider assessment or a prediction of acceptance. In an application, distinguish methods you used from methods you only studied. Use public or otherwise authorized examples rather than unpublished research, client records or confidential code.
Read the role's subfield, deliverable, tool rules, location eligibility, time commitment and payment unit. Research-oriented contract work is not an academic appointment or a research grant. A search result can remain visible after applications close; use the reviewed role details and the provider's current instructions to decide whether to proceed.
Use a fit-first application path and avoid unsupported claims about credentials or availability.
See how research and academia fits alongside other professional backgrounds.
See current counts, platform snapshots, language roles, and role context.
Compare remote employment, contract, freelance, and specialist AI work arrangements.
Often yes, especially when listings ask for subject expertise rather than a specific license.