This was the most efficient interview process I've ever seen.

The HR phone screen was a standard 45-minute conversation with the recruiter. They made the decision to move forward within just a few hours.

The technical phone screen was with the Senior Engineer, hiring manager, and manager's boss. Each had their own technical questions: the Senior Engineer asked challenging questions about the Java language, the manager asked about schedules and project decisions, and the manager's boss asked about interpersonal skills and experiences. It was grueling, and I thought I had failed. They made the decision to move forward within one hour.

The on-site interview was most impressive. The hiring manager brought his entire team into a conference room and asked, "Tell us about yourself." That allowed everyone to hear about me, and we didn't need to go over my experience six times. Then, all except two engineers left, and they asked hard Java questions for a while. Afterward, two others relieved them and asked more hard technical questions. Finally, the hiring manager came back, asked if I had any questions for him, and then it was all over. It only took two hours, and they had a pretty good sense of what I could do. The downside was that I didn't get as much of a chance to learn about them as I would have liked. The best part? They made their decision and contacted me with an offer within two hours.

Here's an obscure piece of code. What will be printed at line 27? (Although I've seen this question multiple times, thankfully they didn't use "messed-up" variable names.) They also asked about infrequently used language features: Transient, Volatile, Finalize, etc.