The interview consisted of two primary steps. The first was on my campus, and the second was in Denver. On campus, the interview was a 2 on 1 interview with 2 parts. The first part took 30 minutes and was filling out an IQ test with multiple choice, fill in the blank, and 2 easy coding standard coding examples from an elementary coding class. The second part of the interview was also about 30 minutes and was spent figuring out how you would react in certain situations mainly. Of course, they also asked me what I knew about the company, which was pretty limited to a few facts from the website at that time. They are pretty forgiving if you do not know if you want to be on the Tech Team or Implementation Consultant prior to the interview, so if you are unsure which you would like better, be sure to ask about it. The second interview was in their headquarters in Denver (as an aside, an awesome building). This varies from candidate to candidate based on which employee at FAST interviews you. For me, there was 2 main people: a PR rep, and a software engineer that I was pretty sure was on the Tech Team. The PR rep mainly tried to clear up any concerns you had or any non-technical questions, while the other person varies a lot from other interviewees I talked to. The software engineer I talked to went about the interview in a unique way, where he wanted me to ask him most of the questions for a long period of time and then answer a few thought examples with him. He did a basic coding question that I was intimately familiar with, an easy mathematical question that requires eliminating possibilities, and an example that relied on your ability to visualize objects to get a solution. As some tips, I highly suggest having a lot of questions that are not the boring ones found on google's results for interview questions. Many of my questions that they never heard asked before got really great responses so you can dig into specifics behind both recent failures/events and also what might be common to spend large amounts of time on day-to-day. I also suggest talking to other interviewees and anyone you meet along the way. I found out a bunch of things by talking to random people. One guy made me aware that I should not mention any graduate school aspirations I have (I hope to eventually retire and become a professor, and so planning to go to graduate school in the next 20 years is not likely with FAST). A driver made me learn that if they take you to lunch/dinner after the second interview, you apparently did pretty well and are likely to get an offer. Another interviewee told me about some company specifics he found out that greatly helped me understand FAST a lot better. Hell, I even talked to some employees of FAST and found out really amazing secret details they cannot tell you much about until you accept a job. In summary, the main thing I suggest is to prepare a lot of unique questions and make sure to talk to people (even if you are very shy like me).