> For the complete documentation index, see [llms.txt](https://program.hackyourfuture.dk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://program.hackyourfuture.dk/course-content/shared-modules/specialist-career-training/week1/preparation.md).

# Preparation

## Something to think about before the session!

* [ ] Come ready to engage and ask questions.
* [ ] Reflect on any previous interview experience (if any) - what felt challenging or unclear?
* [ ] What is your biggest worry regarding technical interviews? Or interviews in general?
* [ ] Bring a notebook or document for taking notes.
* [ ] Write down 2 or 3 things that surprised you and be ready to bring them to the session.

## Do

Please check at least on of this Webpages and do the Test so you familiarise yourself with it.

Behavioral tests help companies see past your resume by understanding how you're likely to think, act, and react in real work situations.

* [ ] [www.16personalities.com](http://www.16personalities.com)
* [ ] [www.truity.com/test/big-five-personality-test](http://www.truity.com/test/big-five-personality-test)
* [ ] [www.discusonline.com/free-disc-test.php](http://www.discusonline.com/free-disc-test.php)


---

# 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://program.hackyourfuture.dk/course-content/shared-modules/specialist-career-training/week1/preparation.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.