I met the Director of Software Engineering, Paul Pavlik, at my school's career fair where I talked with him and conveyed my interest and enthusiasm towards different aspects of software engineering such as Agile development. After we had talked, I gave him a resume and a week later, I was given an interview. The interview process was fairly standard and consisted of two senior programmers and myself in a spacious and well-lit room. I was first asked to give a brief description about myself and why I decided to pursue a career in software engineering. I was later told that this question was asked to relax and get rid of any nervousness felt by the interviewee (which I appreciated). After the introductions, I was given two brain teasers. After a small hint, I was able to solve the first one and I easily solved the second brain teaser by using that same hint. I later learned that this is what the interviewers were looking for - identifying similarities between problems and using the same approach that worked on one problem, on a different problem. I was then asked a programming question ("write a program that reverses a c-style string") which I did fairly well in. Initially, I had several errors in my code but luckily, I was given a chance to look over my code to catch these errors without any help. Finally, I was asked to talk about one of my school projects and some of the design choices I had made.

Interviewed for a QA testing position. Interviewed with on person for roughly 30 minutes to an hour. Standard technical black box testing questions, linux terminal questions, simple coding questions, networking technical questions, and behavioural questions. The experience was good overall, the interviewer was more than happy to answer some of my questions, as well as drop hints on simple errors made during white board coding.