> For the complete documentation index, see [llms.txt](https://docs.onlydust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onlydust.com/~/revisions/hDyFLjt7yK9TBrWfEAXo/the-impossible-bench/selection-process.md).

# Selection Process

#### 1. Initial Meeting

* Assess motivation, project potential (6+ months), and time commitment (10–15 h/week).
* Review contract terms and confirm understanding.
* If suitable, schedule the technical interview.

<sub>*With JB - head of devRel*</sub>

***

#### 2. Before the Technical Interview

* The candidate must have already started coding (about 10–15 hours).
* Submit a short project description, roadmap, and key technical challenges 24 hours in advance.
* Share GitHub access and follow coding rules (clear PRs, tests, no AI use).

***

#### 3. Technical Interview

* Evaluate project complexity, technical potential, and code quality.
* Reviewers provide written feedback and a recommendation within 24 hours.

<sub>*With either Antho or Olivier - both senior back end engineers*</sub>&#x20;

***

#### 4. Administrative Validation

* Accepted candidates receive a confirmation email and a contract to sign.
* Reminder of the one-month review and €7,500 payment conditions.

***

#### 5. One-Month Review

* The committee reviews progress and code quality.
* Decisions are based on delivery quality, effort, and compliance with the rules.

***

#### 6. Payment and Legal Setup

* Upon approval, the finance team processes the €7,500 payment.
* Candidates may need to create a micro-enterprise for legal compliance.
* Legal terms (IP rights, licensing, non-compete) can be reviewed with counsel.


---

# 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://docs.onlydust.com/~/revisions/hDyFLjt7yK9TBrWfEAXo/the-impossible-bench/selection-process.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.