After applying online, I heard back from an EA recruiter within a few days, letting me know that the Technical Director wasn't currently out of town but would have my resume to review as soon as he got back.

About two weeks later, I was asked to come in for an interview. They were able to work with my availability and scheduled an interview time that worked for both of us. A week later, the day of the interview came. The recruiter gave me a tour of the studio, giving me some info on the company and the industry as a whole. It was an excellent icebreaker and calmed my nerves. When it was time for the interview, the recruiter told me that the Technical Director would be running a little late, so instead, he introduced me to one of the producers. We went for coffee and chatted about the project that I would be working on.

When the Technical Director arrived, that's when the real interview started. The interview consisted of only a few typical quiz-like questions. These questions were what I would consider the "dummy test." If you couldn't answer these first few questions, there was no point in going any farther because I obviously lied about my experience with the technologies on my resume. The rest of the interview consisted of me explaining my previous experience and projects. This is where natural enthusiasm and interest play a big part.

The recruiter came back and, as he was escorting me, asked if I would mind hanging around so that I could meet the Executive Producer. Twenty minutes later, my second interview began. He asked about my education background, my work experience, why I was interested in the job/EA, etc., followed by answering any questions I had.

The week following the interview involved a lot of back and forth with the recruiter, sending them my university transcripts, current compensation, etc.

Explain to me how you use technology <abc> in your current job.

What are the ABCs of WCF?