{ The Rithm Blog }

Rithm School Interview FAQs August 01, 2018

Last updated 09/27/2022

Welcome to Rithm School, prospective students! This post details Frequently Asked Questions we get about the Rithm School interview process as well as key information about the interview itself. If you are looking to get into Rithm in the near future, hopefully this gives you more insight as to how best to prepare and what exactly to expect on your interview date.


 

Prior to the Interview

How do I start the interview process?

Reach out to [email protected] for an initial chat with our Admissions Coordinator. Then, take our mandatory 30-minute timed coding challenge. To prepare for this timed coding challenge, we'd like you to go through our JavaScript Fundamentals Course, and while not mandatory, we highly recommend using our practice problems. If you can get through 100% of the practice problems, you will be ready for the assessment!  After you've passed the coding challenge, you can schedule your interview!

When can I interview?

After you've completed the 30-minute timed coding challenge, we will send you a link to schedule your technical interview. Interviews are typically scheduled Monday through Friday at 9:45 am or 1:45 pm Pacific. If you are unavailable at those times, we will work with you to find a time that works for both you and your interviewer.

Generally, you will be allowed to interview for any upcoming cohort up until 4 weeks prior to the start date, depending on available seats (classes are capped at 18 seats). Interviews will not grant admission to a cohort that begins less than 4 weeks away from the interview date. However, you can interview as early as you want for future cohorts.

What pre-requisite knowledge do I have to have before the interview?

Basic to intermediate JavaScript syntax as covered by our online courses. This includes different types of loops, logical conditions, and common Array/String methods such as .split, .join, .includes, .indexOf, etc.

We DO NOT expect any prior knowledge of algorithms or data structures, but you should be comfortable with all the essential types within JavaScript including Objects, Arrays, Strings, Numbers, Booleans, and Null/Undefined/Falsy values.

We do not test web development knowledge during the interview, but the pre-work following the interview will require you to be comfortable with JavaScript in the DOM, HTML, and CSS.

What can I do to prepare for the interview?

Assuming you've completed our 30-minute timed coding challenge

  • Go through our free curriculum for Introduction to JavaScript and complete Part 1 and Part 2 of our practice problems. You can watch a video walkthrough on how to download and test these practice problems here!
  • Sign up and do practice JavaScript problems on Codewars at the 8th, 7th, and 6th kyu levels.
  • Apply to join our free Private Prep course, where you will learn live from our instructors and work with other students who are preparing for the technical interview.
  • And perhaps most importantly, practice whiteboarding or writing out problems by hand. ✍️ It will make a big difference in your speed / comfort-level during the interview. You can find some tips on whiteboarding here.

 


The Interview Itself

How long is the interview?

The technical part of the interview usually lasts for about 90 minutes. Time is allotted for non-technical questions or follow-up discussions at the end of the interview.

What is the format of the interview?

Interviews are held one-on-one via Zoom, with your camera on and screen shared. They ypically consist of 2-4 technical coding problems to be completed in the code editor of your choice. We ask that interviewees write syntactically-correct JavaScript to the best of their ability. In addition to the JavaScript, writing pseudocode or diagramming out problems is highly encouraged.

Why do you do whiteboard interviews? I've heard bad things about whiteboarding!

Whiteboarding is extremely common in the software industry as an interview technique. It is certainly not always the best measure of a person's professional competence or qualifications for a role. However, as a coding school preparing developers to enter the tech industry, we want to make sure our prospective students are ready to handle this interview format from the get-go, because at the end of the cohort, students will inevitably have to whiteboard again for a number of job interviews.

Additionally, we find the format helpful for measuring an interviewee's familiarity with JavaScript (since they will have to recall most of the methods and syntax they use from memory), as well as their ability to solve moderately-challenging problems without relying on other people's work or a text editor / IDE.

Rithm Student Whiteboarding

Who will interview me?

Every interview is conducted by a member of our instructional team. All of our interviewers have experience not only interviewing prospective coding school students, but also as professional engineers as well.

How difficult is the interview?

We might give an easy/warm-up problem, and then a couple moderate to difficult problems. On Codewars, they would probably be 7th or 6th kyu, on LeetCode they would be considered "Easy", although this is a vague approximation, and everybody has a difference frame of reference for what is considered easy or hard.

What are you looking for in the interview?

There are a handful of criteria we use to evaluate candidates in an interview. The most important criteria are:

  • Problem solving ability: Can you think abstractly, ask critical questions, understand the problem statement, and come up with a viable solution?
  • Technical knowledge: Are you able to write syntactically-correct JavaScript to solve the problem, can you remember essential JS methods / operators?
  • Behavior and communication: Do you exhibit professionalism, do you communicate your thought process effectively, can you articulate what the code should do, can we tell that you understand the problem?

As instructors, we are also looking for coachability, which means a willingness to accept input and feedback from your interviewer and possibly adapt your strategy to hints or suggestions from us. This is a really important one, because we don't expect everyone to walk in and instantly ace the interview problems. Since we are interviewing prospective students, we just want to see if interviewees are fast learners and will be able to vastly improve their skills throughout the cohort.

What if I get stuck?

No worries, everybody gets stuck sometimes! Simply let your interviewer know where you're at. Make sure you tell him/her what you understand already and what you think you need to learn to get unstuck. We don't consider getting stuck a big problem unless you just sit there and don't say anything. However, getting stuck more than a few times can be an indication that you may need more preparation.

Also, we are always willing to help out if you forget how some methods work or make a few syntax mistakes. As long as we can see you are doing your best, we won't hold it against you if you forget, for example, that the .splice() Array method returns an array of the removed elements.

 


After the Interview

When do I find out if I passed?

We typically get back to candidates within 1-2 business days of interviewing.

I didn't pass the interview. What do I do now?

No worries, not everyone passes the interview on the first go! We will usually recommend interviewing again between 2-6 weeks after the initial attempt.

We may also give you additional problems to work on, or we occasionally offer special events to prepare prospective students (check the newsletter or contact [email protected] directly for more information).

How many times can I attempt the interview?

We will try to limit candidates to three attempts for an upcoming cohort. After that, it's not impossible to attend Rithm at a later date, but we would recommend that you wait at least 3-6 months before looping back around.

I passed the interview! What's next?

Congratulations! We will send you an offer of admission as well as an invoice for your tuition deposit. We will also send you our pre-work, which consists of ~80 hours of self-study problem-solving and web development projects that are required to be completed before the start of the cohort.

Once all the prework is completed and the deposit is paid, you are officially in. Welcome to Rithm School!

🎉🎉🎉 Here's to you becoming a developer!!! 🎉🎉🎉

Written by Anna

Back to all posts

Get Started with Rithm School