The Technical Check-in is an important step in the Immersive interview process we use to evaluate students’ readiness for the Immersive based on their technical and interpersonal skills. However, you should consider the check-ins to be more like coaching sessions that, while evaluating you, also help train you to be a better coder and strengthen your JavaScript fundamentals. You can also take the Technical Check-in multiple times (more details on this down below). Don’t worry, everyone is nervous at these check-ins but you quickly get comfortable once you start coding.
The Technical Check-in evaluates your:
The Technical Check-in covers only JavaScript. You do NOT need to know any other programming languages for the Technical Check-in. The check-in will go over these topics and more:
The Technical Check-in will be conducted online through Google Meet with one of our Technical Interviewers in a pair programming style, meaning you will tell the interviewer what code to write. You do not touch the keyboard during the check-in because you will only be speaking the code (navigating). The Technical Interviewer will have their screen shared so you can see what they type (driver). This adds an extra level of challenge that helps us assess whether you have internalized the fundamentals required for the Immersive.
The Technical Check-in is open note and open internet. During the check-in, you may use handwritten notes or organize your thoughts on pen and paper. If you need to Google something, you simply need to tell the Technical Interviewer and they will Google what you tell them with their screen shared and you direct the search by telling them where to click, what to type, etc.
Yes, after each Technical Check-in, you will receive feedback about your check-in via email and what you should work on to prepare for the next one. You will NOT receive feedback during the Technical Check-in. Included in the email will also be the amount of time you must wait to have your next check-in.
The Technical Check-in will have two types of questions:
Along with these list of topics referenced above:
These are topics you should be familiar with for the Technical Check-in:
These are topics you should be familiar with by Immersive Day 1, but NOT required for the Technical Check-in:
You can take the Technical Check-in multiple times. At Code Chrysalis, we believe that a strict admissions process leads to better outcomes. It’s no coincidence that the most selective programs tend to produce the most successful graduates.
In order to cultivate the best class experience, we reserve the right to deny admission to our course at any point. However, this shouldn’t scare you away from applying – we typically encourage promising candidates to retake our Technical Check-in multiple times, or to reapply again at a future date.
We offer two introductory JavaScript courses that will teach you most of the topics covered in the Technical Check-in:
We also recommend these other online resources for concept learning:
We hope this guide was helpful and should you have any questions not addressed in this guide, email our Admissions Team at admission@codechrysalis.io. You can also schedule an online video consultation with our Admissions Team here.
Good luck and we hope to see your application with us soon!
お問い合わせ
サービスご利用についてのご相談や資料請求は
お問い合わせフォームよりご連絡ください。