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

# Week 1

This session will walk through the Danish job market and what recruiters typically look for. Trainees are now in their specialisation round, so they're much stronger on the technical side than before. We'll also talk about how a solid CV and LinkedIn profile & Github together with those deeper tech skills help present them as mature, capable candidates that recruiters will actually notice.

## Learning Goals

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

* [ ] Understand the structure of a technical interview (e.g., intro, problem-solving, discussion)
* [ ] Know what interviewers are generally looking for (communication, problem-solving approach, etc.)
* [ ] Feel more comfortable with the idea of technical interviews.
* [ ] Learn how to approach a problem out loud and structure their thinking.

## Materials

* [Preparation](/course-content/shared-modules/specialist-career-training/week1/preparation.md)
* [Session Plan](/course-content/shared-modules/specialist-career-training/week1/session-plan.md) (for mentors)
* [Assignment](/course-content/shared-modules/specialist-career-training/week1/assignment.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://program.hackyourfuture.dk/course-content/shared-modules/specialist-career-training/week1.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.