(Side note: I have a bachelor's in Comp Sci, so I don't know how interview difficulty scales if you're coming out of a bootcamp that didn't stress OOP and/or SQL.) The interview process was broken down into 3 parts: the "phone interview" (which wasn't an interview, but rather a general screening to see if you understand what you applied for), the online assessments (which were broken down into 2 parts themselves), and the "Final Assessment Day" (which was broken into 3 parts, and were over Zoom), Going into more detail of the latter two screenings, the online assessment had a technical and behavioral component. The technical was over basic SQL, Boolean Logic, "Problem Solving", Data structures, OOP and basic Unix commands. Cursory preparations on Khan Academy helped me greatly in the SQL category. Problem solving was a matter of being able to walk through code and understand what it was doing. (There were some questions about the use of the words "static" and "final", which would be one of two appearances this question made an appearance during the interview process, so make note of this.) With Data Structures it was a matter of having a general understanding of the structure, as opposed to any intimate coding knowledge of how they work. Frankly, I have the most robust experience with Unix, but I was able to guess my way to passing that section. The behavioral was more difficult for me. You had to record your responses to questions prompted to you by a short video clip. The video would play, and then you would get 90 seconds to collect your thoughts before you were recorded for another 90 seconds (I think? Could have been shorter), and keep in mind, you could NOT start over once the recording started. I was stuttering quite a bit, but managed to state my points, and was sufficient, apparently. After this, I was called by the recruiter who talked me through my results, and set up my final interview date. The "Final Interview" was over Zoom with 3 different people. One was a presenter who gave a quick company overview with a group of other people. The second was a behavioral interviewer who asked questions of similar nature to the previous behavioral interview. The third was the technical interviewer, which I think was the most difficult part of the whole process. They essentially look at your resume and ask you questions about the technologies and concepts--not the projects-- on it. This is where that "final"/"static" question came up again, and I flubbed it. Overall kind of rough, but I managed. The takeaway here is that, if Java and/or SQL are on your resume, and are not your primary languages, you may have a hard time at this point. Though that's not to say they won't ask you about another language; it's just, if you have those listed, they'd prefer to ask about those, seeing as they're the most relevant. After all that, I got my offer same-day.