> 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/foundation/career-training/week2.md).

# Week 2

This session is for practicing for a screening interview and receiving feedback from peers and volunteers.

You've made a lot of progress on your CVs and LinkedIn profiles so far, and now you get the opportunity to practice a screening interview. Watch out in your teams' slack channel, where you will receive a case to prepare for.

We will also bring a camera so that you can get updated photos for your LinkedIn and CV - so wear the clothing you would like to have on your professional profile!

## Learning Goals

By the end of this session, you will be able to:

* [ ] Give a personal elevator pitch clearly and confidently
* [ ] Learn how to perform well in a screening interview
* [ ] Understand and practice asking your own questions during the interview
* [ ] Practice receiving constructive feedback
* [ ] How to handle job rejection and job anxiety
* [ ] Feel prepared and ready to take on a real interview

## Materials

* [Preparation](https://program.hackyourfuture.dk/course-content/foundation/career-training/week2/preparation.md)
* [Session Plan](https://program.hackyourfuture.dk/course-content/foundation/career-training/week2/session-plan.md) (for mentors)
* There is no assignment for this session


---

# 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/foundation/career-training/week2.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.
