Making Technical Project Reviews More Inclusive

A project review should explain what is being assessed. Publish the task, the expected output and the constraints before reviewing the result, so applicants can prepare relevant evidence.

Ask for the contribution

Invite the applicant to distinguish their own work from a group's work. Coursework, independent study and a personal project can be discussed on their actual merits. Avoid guessing skill from a polished title or the familiarity of an institution's name.

Offer a clear demonstration format

Explain whether the review requires a written explanation, a live demonstration or a recording. Give instructions that can be followed without access to private systems. A sample task should use synthetic information rather than asking for material from another workplace.

Make questions possible

Provide a route for clarifying the task and the submission format. Record the same relevant criteria across reviews, and document the reason for a decision rather than relying on a vague impression.

Applicants can use these questions when reading a current role listing. Ask how the review criteria will be explained and how an applicant can clarify a submission.