The interview process was very long and much of it never made any sense. It just seemed like they kept asking questions from a list and see if you answer it weird. They never seemed to be expecting any sort of answer. A lot of the interviews had some awkward silences because the interviewer didn't know what to ask next. There was 3 steps to the interview process. The first two were video conference with shared code screen and the 3rd was a onsite with pair programming. The first interview was with one person and was a very typical computer science interview. Pick a language you are most comfortable with and be asked basic questions to prove you understand it. We then proceeded by doing a coding problem. The second interview was with 3 people with the same video conference format. They literally just asked me about my past positions and different behavior questions. They then did a coding problem (which was EXTREMELY easy). I don't think they really thought the problem out because when I started asking how they wanted the function to work, they didn't give an answer. The last interview was an all day thing. Here is a list of things I did that day: Welcome, Interview with manager, pair programming, lunch, more pair programming, and interview with CEO. The first interview was most behavior questions and talking about the company and their benefits. Prety much telling how of a company they were. The first pair programming was probably the best part of the day. It was a decent problem, but not too challenging. I think he gave me too much to do within one hour because he wanted me to write unit tests with the code I wrote. I wasn't able to finish in time. The second pair programming was a disaster. Thw whole time he was quiet and didn't say anything and when I would ask him for more details about the problem, he would shrug his shoulders and say "I don't know". At the beginning, he asked me some behavior questions and before he did, he said, "Before we start programming, they gave me some questions I have to ask you. I don't know why, but I have to ask them." I wrote the api on the white board and then started to code it. He spun up a basic web page (not angular or react...jquery). I'm not an ES2016 expert, but since he was the one doing the interview, I asked him how to create a class with ES2015. He said he didn't know. So he opens up the oldest version of Eclipse and says to write it in Java. Of course, I need a GUI for this app, and HTML would have been fine for that. Obviosuly, I didn't have time to complete that as well. The day ended with the interview with the CEO via video conference. He was slightly late which wasn't a big deal. I know he's probably really busy. The fact he took the time to talk to me was a neat experience. He really didn't have much to say. He mostly wanted to meet me and see if I had any questions. The day after the Faithlife recuiter said they weren't going to move further in the interview process. After I got this email, I was so confused. The fact I was there all day AND talked with the CEO made it seem like the job was in the bag. Faithlife, if you are reading this, do not make people go through this whole process to only reject them so quickly. That was a lot of time and energy for you and me. Overall, it never seemed like they really had a plan during the interviews. They just kept asking questions and seeing if I could solve some problems and waited til I did something wrong.