> 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/the-impossible-bench/selection-process.md).

# Selection Process

1. Kickoff, with JB, Head of DevRel\
   Check motivation, 6+ month scope, and 10 to 15 h/week. Review the contract. \
   If fit, book the tech interview.
2. Before the tech interview\
   Have at least 10 to 15 hours of code started. Send a short project brief, roadmap, and key challenges 24 hours ahead. Share GitHub access. 
3. Technical interview, with Antho or Olivier (both senior back end engineers)\
   Evaluate complexity, potential, and code quality. \
   Written feedback and a go or no-go within 24 hours.
4. Admin validation\
   If accepted, you get a confirmation email and the contract.  
5. One-month review after contract signature\
   Committee checks progress and quality. \
   Decision based on delivery, effort, and rule compliance. 
6. Payment and legal\
   On approval, finance pays the first quarterly €7,500.  


---

# 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/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.