> For the complete documentation index, see [llms.txt](https://hub.fruitsalad.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.fruitsalad.ai/rooms/interview.md).

# Interview

The "Interview" room is an innovative space designed for conducting interviews with a twist. Here, candidates can be assessed not only through traditional questioning but also by engaging in specially designed games. These games are crafted to evaluate skills like problem-solving, critical thinking, and adaptability in a more interactive and revealing manner. For example, a puzzle game might assess logical thinking, while a strategy game could reveal decision-making skills. This approach provides a deeper insight into the candidate's abilities and fit for the role, making the interview process more comprehensive and engaging.

This is a collaborative space, allowing multiple interviewers and observers to join in real-time. This setup fosters a team-based evaluation process, where different perspectives can be shared and discussed seamlessly. The collaborative nature of the room also allows for dynamic interaction with the candidate, providing a more holistic view of their interpersonal and communication skills in a group setting. This enhances the decision-making process, ensuring a well-rounded assessment of each candidate's potential.

See also: [Interview AI](https://hub.fruitsalad.ai/rooms/ai-interviewer.md)


---

# 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://hub.fruitsalad.ai/rooms/interview.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.
