NOTE: The process changes on a per-job basis. Some interviews follow the below format, and some follow the experimental format. Currently they are exploring a take-home assignment, and then will ask you questions about your code during the interview. They'll ask why you made specific decisions, why you didn't choose another approach (they are NOT blaming you, only probing your brain) I think this type of interview can waste a candidate's time. Below you'll find what I experienced. --- I applied to the C&J division while I was still in college. First was a phone screen with HR who asked standard HR questions, along with some basic technical questions that any computer science graduate *should* be able to answer. After that I met in-person for an hour-long interview. Or maybe it was a two hours. First was behavior, second was technical (the order can swap). Both took place in the same room, with a small break between them. Both had two people on the other side of a table, with a whiteboard behind me. --- 1. The interviewers were managers of teams, one of which I ended up working with. Behavior questions were standard, but they probed deeper into my resume. Questions about favorite class, projects, why Tyler, etc. Nothing was too challenging. The most important part is to express passion when talking about items on your resume and being charismatic and friendly. 2. The interviewers were senior and lead software engineers, one of which I ended up working with. The technical part asked standard technical questions, half "trivia" questions and half was a coding exercise on a whiteboard. The "trivia" questions were stuff like the 4 principles of OOP, types of SQL joins, when to use types of loops, how to handle exceptions, etc. No concrete design questions. They also asked about the technical details of my resume, so always be prepared to explain both at a surface-level and in-depth about your work. Whiteboard question was LeetCode easy. Variations could be medium.