Difficulty
Average
Candidate-reported interview insights
Explore commonly reported questions, interview rounds, difficulty, duration, and candidate experiences at Akamai.
Difficulty
Average
Average rounds
3.3
It was a 4-round process, all technical. They asked complete DS and algo questions. Design patterns, puzzles, and architecture designs are a must if you are going through this. They asked everything about my previous projects and told me to explain the complete architecture of that.
I went through a lot of interview rounds for this Director role with the hiring manager and other stakeholders. It involved both phone and in-person interviews. After what felt like forever, over 3-4 months of interviews and waiting, they told me they weren't hiring me. Then, about 6 months later, they mentioned there was a chance they might rehire and I was still in consideration. I got interested again and wanted to talk to them. But when I asked about when I could speak with them again, they never replied, leaving me hanging. Super unprofessional for a senior role.
Recruiter reached out via an online job board. A phone interview was set up for the next day. The interviewer asked about release engineering processes. I answered most of them correctly regarding the RE process. However, on the question about the benefits of CI and implementing it in legacy systems, I detailed the benefits and implementation, but it felt like the interviewer was expecting a different answer. For Perl, the interviewer only asked how a Perl script is interpreted. There were no questions to test logical or analytical skills in Perl. It's hard to gauge someone's Perl skills with just one question.
A focused selection of the most detailed candidate-submitted questions.
Practice technical, system design, and behavioral questions with Zitlee.
Interview information is based on candidate reports and may not represent the current official hiring process of Akamai.