I applied online and received a call from their recruiter within a few days. She scheduled a phone screen, which happened a day or two afterward.

The phone screen started with him asking me to do a narration of my recent experience while he got his stuff together. He then asked me some questions about C++ keywords and how to determine integer bit size on any given machine.

I was then asked in for an onsite interview. They are in a temporary space right now, so it's just a bunch of folks all sitting at tables in the same room. They appear to have one conference room, in which the interview took place.

At first, the interview was going okay. He wrote a code snippet from a bug he had to fix earlier in the week and asked me to find the bug – a race condition – which was pretty easy. After that, he asked me to do some coding on the whiteboard. The coding question was really easy: write a sort algorithm for a singly linked list. However, at this point, I seemed to completely fall apart. Some stuff went on afterward, but I could read it in the interviewer's eyes that the interview was over.

There was one other interviewer who was a QA guy. He asked some questions about coding with testing in mind and asked how to detect if a linked list had a loop in it.

So, it was sort of a bad experience, but it was completely my fault. If you interview with these folks, I would suggest a review of your old data structures book before you show up.

There were no particularly difficult questions.