1. Take-home project. Implement it as if it were a production app. I took two days to fully implement it with all the bells and whistles, test code, architecture, etc., a fully-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) Whiteboard architecture questions c) Behavioral 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 interviewer's full OK. 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 we 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 software engineers, versus most companies that want you to whiteboard what I feel are stupid problems totally irrelevant to what your job would be.

How do you deal with difficult situations or people?

Give examples.

What is the most memorable production bug you've caused, and how did you prevent it from happening again?

Have you ever been given good or bad feedback?

Have you ever given someone else good or bad feedback?

Discuss various design patterns and their uses.

How do you feel about diversity?