I applied through university. I interviewed at Hillcrest Labs (Pittsburgh, PA) in Sept 2015
Interview
It was on job fair in my school. We first talked about my resume and then they inform me to take an interview. The interview is divided into 2 part. First part is behavioral questions, like leadership, what are your interests and strength. The second part is technique questions.
Interview questions [2]
Question 1
Brain twister: 8 ball problem, one ball is heavier than others, use a scale to find it with smallest number of time
The on-site interview process was a full day long, starting at 8:00 am and culminating in a dinner at a bowling alley ending at 10:00 pm. This was part of a college recruiting event, so I was one of five or six interviewees from several colleges. I had first spoken to Hillcrest at a career fair at my university, and they followed up with an on-campus interview. The on-site interview was a few weeks later.
There were several interviews, which mixed behavioral and technical questions. There was a "survey" which was formatted like a school exam, asking technical questions about various fields related to what the company does (electrical engineering, signal processing, geometry, programming), which we were given ample time to complete, though I spent far too much time on the geometry question. It was stressed that it is okay if we couldn't answer all of the questions, so I assume that the role of this survey was to determine what departments the candidates would best fit in, given their expertise.
Interview questions [1]
Question 1
The most difficult question asked about the best data structure to store temporal data that is constantly being acquired and consumed. Unless you had encountered this before, you might gravitate towards a naive linked-list solution, or else try to use some kind of tree. We were asked to consider the running times for the storage and retrieval operations, and I was able to keep the conversation going as I was thinking about my answer by rattling off my pre-existing knowledge of data structures and their running times.
