I had a couple of telephonic conversations about my resume, interests, and to improve my understanding of the position, reporting structure, and the company. Questions about my resume and interests were pretty standard, such as:

• What different technologies have I used?
• Why did I want to move?
• What am I looking forward to working on?
• What is my dream job in the next 5 years?
• What are my educational interests?

On-site interviews were all 1:1 with 4 senior engineers, 2 dev managers, 1 QA manager, and finally a Senior Director. The interview was quite technical and grilling. The people were really nice. They were looking at my approach rather than the exactness of my answers. Their questions were highly adaptive and deeply conceptual.

I gave a high-level model of packet-forwarding and then asked:

What design changes would you suggest to improve the routing speed?

After I provided an answer, I asked:

What other alternative ways exist to achieve this? Consider both good and bad approaches, and outline their major pros and cons.

This was followed by an analytical problem related to data structures:

Something like: A mouse and a tortoise started running in opposite directions on a 100-mile highway. The mouse made stops for various reasons, with specific times provided. These times were also presented relative to the tortoise's movements. The final question was how many times the mouse would have run each way before the tortoise completed one round.