The interview process starts out with a phone interview that is a pop quiz/verbal skills test. Interviewer will typically introduce himself/herself, then immediately jump into technology questions. Some of these questions (and answers) can be easily googled. For example, if you are interviewing for a ASP.NET developer, google "ASP.NET interview questions" first. 50% of the questions will be there.
As the phone interview progresses, the questions become harder. If they think you know too much, they have a few zingers and gotcha questions ready for you. Like, a question about Globalization differences between .NET 1.1 and 2.0, that 95% of developers would know off the top of their head. Mind you, you will never actually use these technologies on the job, but if a boost to the ego of the interviewer that he knows this (from googleing beforehand) and you don't. Overall, the goal of the interviewer is to break you, to demoralize you, and if he/she somehow fails, then they will invite you to an in person interview (although not right away, they tell you they'll get back to you then the recuiter notifies you like a week later).
The in-person interview consists of a couple managers, maybe a director, and some technical people from other areas (i.e. DBA). Its a more personable interview this time. They'll still try to break you, but in a more more friendlier way. But they will grill you. Prepare to whiteboard your answers. Luckily, if you've made it this far you are usually in good shape.
Overall I've noticed that many candidates never get past the phone interview, and other get put off by their hardened style of interviewing. If you are ex-military you may feel more comfortable with it since these are the folks that usually get hired.
