The interview process was as follows: - Screening interview: Parse data from a JSON API Construct a UI to render a list of items Populate the UI from the content - Onsite - 4 interviews - Manager - behavioral - Bug fixes in a given app - Building an app from scratch (2 parts, architecture + coding)

1) Take home project. Implement it as if it were a production app. I took 2 days to fully implement it with all the bells, whistles, test code, architecture, etc. a full fledged app would have. 2) If that passes a phone screen about various aspects of your code. 3) If that passes an on-site where you a) Add a feature to your code b) White board architecture questions c) Behavior interview d) Hands-on debugging e) Manager lunch When I was asked to do (a) I quickly realized there was not enough time to do it "correctly" in 45 minutes. So I sort of hacked it in, with the full OK from the interviewer. Something didn't work at the end and the debugger was giving me problems trying to examine why. I clearly demonstrated I was quite capable of solving the problem, and it seemed the interviewer thought so, but ran out of time. When I was rejected for the job the next day the recruiter said it was because I failed this test. I don't think this was the real reason but it left them an "out." Until this bogus reason for not getting an offer I thought they were one of the few companies that knew how to interview seasoned SW engineers vs most companies that want you to white board what I feel are stupid problems that are totally irrelevant to what your job would be.