The process started my schools (Clemson) career fair. After Talking to the two representatives they took my resume and invited me to an on campus interview the next day. Most of the questions were based off my resume with few technical questions. A few weeks later I received an email inviting me to their "career day" where they brought in about 15 other interviewees. They split us into two groups and interviewed the first group and gave the second group a tour and had them fill out some paper work. Then the two groups switched. We were fed lunch then it was over around 2pm. The technical questions asked were along the lines of Question: What happens when you try to free a null pointer Question: What is the difference between a process and a thread Question: What is the difference between the stack and the heap Question: What is "yoda conditions" Answer: this is an obscure question so i'll provide an answer. Normally you'd write an if conditional like this: if( ch1 == '_' ); however, if you use yoda conditions "if('_' == ch1) { ... }" it allows the compiler to catch the occasional typo "if('_' = ch1) { ..}" i.e. the compiler will say you cannot assign a value to a constant thus catching your error (not typing if('_' == ch1)). Also they gave us a print out of a program with several errors and we had to identify them all and give suggestions on how to correct them. Make you know what a unit8 is and how using that could be bad for processing a string.

I sat in with a group of four other engineers for about an hour and a half. The team all took turns asking questions about the experiences I listed in my resume and my knowledge on abstract data structures such as the heap and the stack. They also asked me about my knowledge in C, including evaluating a macro. Following that, they gave me some sample code written in C and asked me to see what was wrong with the code. There was one whiteboarding problem at the end.