> For the complete documentation index, see [llms.txt](https://docs.scholars.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scholars.net/info/assessments.md).

# Assessments

Learn more about assessments on Scholars.

To qualify for jobs on Scholars, we need to know you possess certain skills. To verify that you have the skills we need, jobs require you to take and pass certain assessments.

## What are assessments?

Assessments are quizzes you take online directly from the Scholars website. When you're done, you'll get a score. To be able to apply to certain jobs, you will need to have passed certain assessments with certain scores.

Questions you leave unanswered still count toward the assessment's total possible score and receive zero points. Skipping a question therefore does not increase your final percentage.

## What can I see before starting?

Open an assessment from the *Assessments* list or a job page to see its details. You can review:

* The title and description.
* The number of questions and time limit.
* Any guidelines and proctoring requirements.
* Whether retakes are allowed.
* Related jobs that are available to you, when shown.

Click *Start Assessment* when you are ready to begin setup. Opening the details page does not start your attempt.

Once you start the attempt, keep the assessment page open until you finish. Leaving, refreshing, or closing it marks the attempt as *Abandoned*, and it cannot be continued. Whether you can start again depends on the assessment's retake settings or a retake allowed by the team.

## How do I take an assessment?

Please check out the dedicated page on taking assessments for information on taking or retaking assessments:

{% content-ref url="/pages/WT0Nde8FvexbYqIsriFc" %}
[Take an assessment](/how-to/take-an-assessment.md)
{% endcontent-ref %}

## How can I see which assessments I have taken?

From the home page, enter the *Assessments* tab:

<figure><img src="https://620615177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcMVr1tcqZLg9WCEj5GgZ%2Fuploads%2Fgit-blob-50db9d33c9e7fcada76e1eeb38b7bc15b8bb35be%2Floreshot-20260113-100456%402x.png?alt=media" alt=""><figcaption></figcaption></figure>

Assessments are listed from newest to oldest. Each assessment appears once with the status of your latest attempt. A completed assessment can show your assessment score and the dates when you started and completed it.

### Check your latest attempt

Open the assessment to see the status of your latest attempt. Once scoring is complete, the details page shows your assessment score, start and end times, and duration. While scoring or manual review is still in progress, the page explains that your results are pending. Proctoring results are reviewed by the team and are not displayed to you.

If another attempt is allowed, the details page shows *Retake Assessment*.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scholars.net/info/assessments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
