The Quicken technical process starts with a tough phone interview. This is followed by a request for a code example. If you pass this, you are invited to a departmental panel interview where the entire department turns out to meet you and grill you. This turns out to be about 12 to 15 people. Questions for both interviews range from the highly technical to personality/maturity questions.

After the interview, I heard from the recruiter that his feedback on candidates lately had raised the issue of money as a consideration from within Quicken. The recruiter complained that his past 5 candidates had been bounced because one of the team members was making less than the candidates' asking price.

How do you treat a name in the request object safely for return to the client?

What do you do to prevent SQL injection on the server side?

Their teams use the Agile programming method. Be prepared to talk about various flavors of Agile and how things go wrong with it.