> For the complete documentation index, see [llms.txt](https://help.prentus.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.prentus.co/how-to-play/leaderboard-and-rankings.md).

# Leaderboard & Rankings

<figure><img src="/files/MVRlUrOsyLAt1ecC30BJ" alt=""><figcaption><p>Your ranking will always be shown on your Dashboard.</p></figcaption></figure>

### How Rankings Work

Each Monday, you will get a Weekly Summary Email covering all the points you earned the previous week along with your new ranking. You only get a ranking email if you logged in the week before. After 30 days of inactivity, you don't get a ranking at all.

While job searching, you are ranked among all active job seekers in Prentus. This gives you a good indication of where you are in progress on your job search so far. After you mark yourself as hired, your ranking will be among non-jobseekers instead.

### After You Get Hired

When you get hired, you "win" your job search. Your final ranking will be stored on your Job Search Summary in the Placement tab of your profile for you to remember.

You don't have to stop competing though. Yes, the job search goals won't be around anymore but there's a separate leaderboard for non-jobseekers on Prentus.

Now that you are hired, you have a ton of knowledge you can share with the community. Create a post, answer questions, and share jobs on the community board. That will earn you CP and help you compete against a different pool of people in the community.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.prentus.co/how-to-play/leaderboard-and-rankings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.