> 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/week2/preparation.md). # Preparation ## How to Prepare for Presenting Your Project in a Mock Technical Interview * [ ] There will be a code freeze on Wednesday so make sure your project is ready before that( No more future or any other big changes, you are only allowed to fix bugs). * [ ] Know your project (Events Startup Project) inside out. Be ready to explain why you made every technical decision, what trade-offs you considered, and what limitations your project still has. Structure your presentation into four parts: a quick overview of the problem you solved, a live demo showing 2-3 key features, a technical deep dive on one interesting challenge, and your key learnings. Practice your demo at least three times, have a backup (screenshots or video), and prepare answers for common questions like "What was the hardest bug?" or "How would you scale this?" * [ ] During the presentation, speak clearly and don't rush. If you don't know something, say "I don't know, but here is how I would find out" instead of guessing.\ Interviewers are evaluating your technical competence, problem-solving, communication, and self-awareness — not whether your project is perfect.\ Be honest, be prepared, and remember, they want to see how you think, not catch you failing.\\ * [ ] Practice solving simple problems out loud.\\ * [ ] Frontend trainees: use the [React interview preparation path from FrontendAtlas](https://frontendatlas.com/guides/framework-prep/react-prep-path) to choose a 7-, 14-, or 30-day plan and rehearse hooks, state, rendering, testing, and performance trade-offs before the mock interview. * [ ] Review your elevator pitch and be ready to confidently present yourself at the beginning of the interview * [ ] Come ready to engage and ask questions. This interview will be 10% soft skills and 90% technical. That means, that while the main focus is on the technical aspects, attention will also be on how well you manage to communicate your technical knowledge. You should start with a brief introduction of yourself as well as your interest in the position. A technical interview serves as a practical evaluation of a candidate’s problem-solving abilities, coding skills, and technical understanding relevant to the role. It allows interviewers to assess how candidates approach challenges, structure their thinking, and apply core concepts in real-time. Beyond arriving at a correct solution, this stage emphasizes clarity of communication, logical reasoning, and the ability to collaborate through problems. This process helps identify candidates who can effectively translate their knowledge into practice while demonstrating the technical competence required for the role. --- # 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/week2/preparation.md?ask=&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.