Real, anonymous reports from people who interviewed for QA Automation Engineer at Akamai, newest first and distilled into what to expect across the loop.
Get your personalized Akamai QA Automation Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After applying, I ended up with a set of interview rounds that felt pretty friendly and well paced. I had an initial conversation with the recruiter, and then the process moved into three technical conversations. The panel approach stood out to me—each person I spoke with was engaging and supportive, and I never felt like the tone was adversarial.
Across the technical rounds, the format was consistent: short coding questions paired with domain-focused questions based on what the team works on. Each round ran about 45 minutes on a coding platform. I remember having to switch between solving and then talking through the reasoning behind my approach, and the interviewers stayed interactive rather than just grilling me.
9 months ago
Average Negative Bengaluru
I went through a process that stretched out way longer than it needed to, and the silence at the end was what stuck with me most. After a recruiter contact, I had a 1-hour technical screen on HackerRank where things went smoothly, and I was told there would be three technical rounds plus an HR round. Soon after, I was invited for an in-person interview with the hiring manager at the Bengaluru office, and I was surprised to find I was the only person being brought in physically.
That conversation felt productive, and I even left with the sense that I was moving forward and would be able to prepare for the next round. Then the timing got frustrating: it took weeks of follow-ups—calls and emails to HR, TA, and the recruiter—with no real response. Eventually I received a rejection email, which was disappointing and confusing because I’d believed I was progressing based on the early signals.
> 1 year
Difficult Negative Israel, TX
My process started with a short phone screen where I was asked a very unusual question: how I would test a large language model. It was only about fif…
> 1 year
Easy Positive Sat home
My interview path felt like it was built around practical testing and fundamentals, moving from a mix of coding and systems topics into deeper technic…
> 1 year
Average Positive Toronto, ON
My process felt unusually structured for a QA-type role, with clear time blocks and multiple people involved. I started with a 30-minute video call wi…
Unlock every QA Automation Engineer interview experience
