|
| 1 | +# Session Plan |
| 2 | + |
| 3 | +This session is focused on realistic Technical interviews, peer feedback, and volunteer involvement. Trainees present themselves with an elevator pitch, and give answers based on a case that they’ve been preparing. |
| 4 | + |
| 5 | +## Session Goal |
| 6 | + |
| 7 | +Equip trainees with a realistic understanding of the job search process and what is expected beyond technical proficiency. Clarify how HYF can support them, and where its boundaries lie. Set the foundation for professional self-presentation and awareness of the Danish job market structure.\ |
| 8 | +It’s an opportunity to explore both the practical and personal sides of the interview process, and to better understand what to expect when applying for roles in tech. |
| 9 | + |
| 10 | +Guide trainees to understand how their CV and LinkedIn & Github profile should work in harmony to present a complete and professional image to recruiters. Provide tools, examples, and hands-on practice in critiquing and improving their online presence. |
| 11 | + |
| 12 | +## Session Plan  |
| 13 | + |
| 14 | +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 the trainee manages to communicate their technical knowledge and present themselves professionally. They should start with a brief introduction of yourself as well as your interest in the company and the position and from there, move into the technical interview.  |
| 15 | + |
| 16 | +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. |
| 17 | + |
| 18 | +## For mentors (Interviewers) |
| 19 | + |
| 20 | +Review the provided interview guides and prepare to facilitate mock interviews |
| 21 | +Be ready to give constructive, actionable feedback |
| 22 | +If it’s possible , review the trainee's project beforehand. You can find their last Pr’s if they have not deployed it yet in the Assignment sheet [BK](https://docs.google.com/spreadsheets/u/0/d/1z6__6d-nt89IOtkgZ1F_lbEdQoLYVXiCVQ34dAHRQvs/edit),[FE](https://docs.google.com/spreadsheets/u/0/d/1hKIJhRQhTw5tQDJslHBrR2OppdcF-mGEH9lkuAKjSlY/edit).\ |
| 23 | + Go through their code, test the functionality, and compare their work against the expected tasks outlined in the Events Startup Project brief ([FE](https://program.hackyourfuture.dk/course-content/backend/events-startup-project), [BK](https://program.hackyourfuture.dk/course-content/frontend/events-startup-project)). Take notes on what they completed successfully, what is missing or partially done, and any areas where their approach differs from what was expected. This will allow you to assess whether the trainee understood the requirements and how well they succeeded in executing everything as requested. |
| 24 | + |
| 25 | +## During the Interview |
| 26 | + |
| 27 | +1. Start by asking the trainee to give a brief overview and demo of their project (5-7 minutes). |
| 28 | +2. Observe how clearly the candidate explains their technical thinking and problem-solving approach |
| 29 | +3. Note whether solutions are structured, logical, and appropriately detailed for the problem at hand |
| 30 | +4. Assess how the candidate breaks down problems and communicates their reasoning step by step |
| 31 | +5. Evaluate their ability to ask clarifying questions before and during the task |
| 32 | +6. Consider how well they balance speed with accuracy and code quality |
| 33 | +7. Observe how they handle being stuck—do they communicate, explore options, and respond to hints? |
| 34 | +8. Assess familiarity with core concepts relevant to their chosen track (front-end or back-end) |
| 35 | +9. Evaluate code readability, naming conventions, and overall organization (if coding is involved) |
| 36 | +10. Consider their adaptability when requirements or constraints are adjusted |
| 37 | + |
| 38 | +### Examples of General Technical Questions (for all candidates) |
| 39 | + |
| 40 | +1. Can you walk me through how you would approach solving this problem before you start coding? |
| 41 | +2. How do you ensure your code is readable and maintainable? |
| 42 | +3. What do you do when you get stuck on a technical problem? |
| 43 | +4. How do you test and verify that your solution works as expected? |
| 44 | +5. Can you explain a technical concept you’ve recently learned in simple terms? |
| 45 | +6. How do you approach debugging when something isn’t working? |
| 46 | +7. What trade-offs do you consider when choosing between different solutions? |
| 47 | +8. How do you handle feedback during code reviews? |
| 48 | +9. Can you describe a recent project and the technical decisions you made? |
| 49 | +10. How do you prioritize what to learn next in your development journey? |
| 50 | + |
| 51 | +### Backend-Focused Questions |
| 52 | + |
| 53 | +1. How would you design a simple API for this feature? What endpoints would you include? |
| 54 | +2. Can you explain how data flows through your system from request to response? |
| 55 | +3. How do you handle error handling and edge cases in your backend logic? |
| 56 | +4. What considerations do you take into account when working with databases (e.g., performance, structure)? |
| 57 | +5. How would you structure your code to keep it modular and scalable? |
| 58 | +6. Can you explain the difference between synchronous and asynchronous operations? |
| 59 | +7. How would you optimize a slow-performing endpoint? |
| 60 | +8. What steps would you take to ensure data integrity and security? |
| 61 | + |
| 62 | +### Frontend-Focused Questions |
| 63 | + |
| 64 | +1. How would you structure a component for this feature? |
| 65 | +2. Can you explain how you manage state in your application? |
| 66 | +3. How do you ensure a good user experience when handling loading or error states? |
| 67 | +4. What considerations do you take into account for responsive design? |
| 68 | +5. How do you approach performance optimization in the browser? |
| 69 | +6. Can you explain how the browser renders a page (at a high level)? |
| 70 | +7. How do you organize and reuse code across components? |
| 71 | +8. How do you handle user input validation and feedback? |
| 72 | + |
| 73 | +--- |
| 74 | + |
| 75 | +## Agent Instructions: Querying This Documentation |
| 76 | + |
| 77 | +If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. |
| 78 | + |
| 79 | +Perform an HTTP GET request on the current page URL with the `ask` query parameter: |
| 80 | + |
| 81 | +```Text |
| 82 | +GET https://program.hackyourfuture.dk/course-content/shared-modules/specialist-career-training/week-2/session-plan.md?ask=<question> |
| 83 | +``` |
| 84 | + |
| 85 | +The question should be specific, self-contained, and written in natural language. |
| 86 | +The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. |
| 87 | + |
| 88 | +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. |
0 commit comments