Participants will be provided a prompted code-challenge. Work on it for 20 minutes! Your code challenge block will be used to go over any questions you may have. Every week you will screen record a single code-challenge in addition to your Yoodli core skills review. That’s two recordings each week! You will receive feedback at the beginning of the following week.
🎗️ Reminder: any stated challenges in your code problems should be after-thoughts - you can begin to apply the challenge once you’ve already solved the main challenge objective(s).
Lastly, for your core skills mock interviews, challenge yourself to not have scripted answers! Do NOT write your answers down and read them off. You can definitely go through the exercise of practicing answering questions, but then put those written answers away while you are interviewing. In most real world interviews, you won't always have the chance to write your answers out in advance of an interview. Challenge yourself to answer these questions in the moment so that you can really practice what it's like to organically collect your thoughts and think on the spot! That said, you can have your two employer questions written down. In fact, it is good practice to have a list of questions to ask the interviewer; you are thinking through which questions to ask, to develop your list!
Mondays will be used to review the feedback of your recorded session from the previous week. Consider and rework your answers to incorporate any actionable changes.
Review the lesson on how to address problem-solving technical questions. Practice in your own time with this code challenge.
Each Wednesday you will record your code challenge and core skills interviews, and add it into your “Growth Feedback” sheet. That’s two recordings each week! You will receive feedback at the beginning of the following week.
If you are using resources while on your recorded interview, be sure you are sharing your screen with the interviewer and including them in on your research - this is another part of including them in on your thought process.
In the coming weeks, you will focus on using less resources to problem solve, you won't always be able to use google or external resources when interviewing. If it is unclear to you at the time of interviewing, that is something that you should explicitly ask. A major part of these technical interviews, beyond knowing how to code and having methods memorized, is showing that you can communicate - so walk through your thought processes and share them with the interviewer.