Phone screen with HR, Take home coding exercise, 2nd take home exercise with Senior Software Engineer, 3rd is an onsite interview that lasts half a day. The interview process is relatively easy. This is coming from a guy who failed numerous whiteboarding exercises and at times couldn't get past the phone screen. I won't disclose the questions since I signed an NDA but if you've done coding exercises on hackerrank or leetcode, the questions given would rank easy or even below easy. I was given two coding exercises (One during phone screen, and one as a pairing exercise) and neither of them required data structures or algorithm knowledge. Couple red flags went off when I first talked to the Phone Interviewer who was a Senior Engineer at Enova. The question he posed was "Could I optimize this code by sorting it?" I answered no since the best run time of sorting is O(n log n) a merge sort to which he responded "Yeah but ruby has a method to sort." During the onsite, you get meet a lot of people which is really cool. First was a set of behavior questions. The standard: "what was an obstacle and how did you overcome it" kind. The second was a pairing exercise. The coding exercise is really simple. No tricks, no critical thinking, just write the code for blank methods and test it and they'll casually ask you about what can be improved. Next came a break/snack with two senior engineers who you have a casual conversation with. You have a lot of time to ask questions (Every interviewer gives you time to ask questions which is awesome). What the company culture is like, how rigorous coding review is, etc.. Next up was a case study and there were 3 interviewers total. It was a case study question, something that resembles your day-to-day tasks. This is probably my biggest gripe in the entire interview process. The interviewer asked what the difference between a POST and a GET was and I answered that GET requests have the params in the URL as opposed to the POST where it is in the body. He said I didn't understand the difference and I got blank stares from the other interviewers.

4 stage process: 1. Recruiter phone screen 2. Homework(Sort of a problem you would usually solve live in coderpad, but without live pressure here) 3. Homework phone interview(Going over your code and thought process) 4. On site interviews(Some coding, some whiteboarding, some behavior and some culture interviews) Overall, I found the process to be very clear, with expectations laid out very clearly at each step. I never felt on the spot or under pressure. Everyone I talked to was very nice and courteous. It was probably the best interview experience I've had.