> 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/assignment.md).

# Assignment

## Prepare for technical mock interview

* [ ] Go through your Event app and do your last small changes.
* [ ] Build your portfolio, or if you already have one, polish it using what you learned.

### If you not already started with these changes from Foundation this is the last chance to take a look at these docs and fix your profiles.

1. Read the [HYF CV Guide](/course-content/foundation/career-training/week1/session-materials/cv-guide.md)​
2. Add your current email address, LinkedIn profile and **GitHub** profile to your Slack profile
3. Polish and update your LinkedIn ([example 1](https://www.linkedin.com/in/alex-sudar/), [example 2](https://www.linkedin.com/in/remyamm/), [example 3](https://www.linkedin.com/in/saloumehsarabi/), [example 4](https://www.linkedin.com/in/anna-louise-jensen-559a89177/))
4. Write a short profile text about yourself - about 400-500 characters and add it to your CV.
5. Update your current CV fully - all professional experience as well as soft and hard skills.


---

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