I have worked here before, but these particular interviewers did not know me at all. This was for a quite senior engineer position, though the questions felt like they could/would be asked of anyone. Note that it was senior but not management.
Overall, I'd call it a tough interview that did not focus on annoying gotcha puzzles and more or less stayed on the topic of reasonably realistic design/coding/architecture matters. I appreciate this, as it won't weed out people who can't handle "brainy" questioning that's more fit for, I don't know what, but not actual engineers. There was also no "do this hard thing in 2 hours on your own" type of challenges, which I also appreciate.
Somewhat annoying was the lack of time to explore each question, as 45 minutes was not enough given the pace of discussion. This, of course, depends on the interviewee, but I was having healthy discussions, not hemming and hawing.
Architect elevator system.
Some tricky concurrency questions, answerable only with experience of relatively low-level details of various lock types and other considerations.
Implement a queue using only stacks.
Describe how to implement, essentially, Java's LinkedHashMap.
Discuss the pros and cons of a past project you worked on between 2005-2007 at the same company. Discuss design aspects of this project and how they might have been improved to make it more successful.
The following metrics were computed from 1 interview experience for the Akamai Technologies Senior Principal Software Engineer role in Santa Clara, California.
Akamai Technologies's interview process for their Senior Principal Software Engineer roles in Santa Clara, California is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Akamai Technologies's Senior Principal Software Engineer interview process in Santa Clara, California.