Real, anonymous reports from people who interviewed for QA Engineer at Akamai, newest first and distilled into what to expect across the loop.
I had a process that centered heavily on HackerRank and longer timed evaluations. It started with a recruiter conversation, and then about a week later I was scheduled for a HackerRank technical screen that lasted roughly an hour. The questions pulled from a lot of areas at once—my projects, Linux and shortcuts, software engineering principles, object-oriented programming, computer networks, and then coding questions. Even though I could tell what topics they were aiming at, the breadth made it intense to stay focused the entire time.
My process kicked off after HR reached out following a Glassdoor application and profile shortlist. In the screening stage I was asked screening questions that centered on Linux and Python, which quickly set the tone for how technical the next rounds would be. Because of the COVID-19 lockdown, the process ran as two technical rounds instead of anything purely onsite.
The interview process typically starts with an HR conversation followed by multiple technical rounds, often including a HackerRank assessment. Candidates noted that the timeline can vary significantly, with some experiencing delays in communication after initial positive interactions.
Technical interviews often cover a wide range of topics, including coding, SQL, Linux, and system fundamentals, with a mix of practical and theoretical questions. Candidates reported that questions were generally aligned with core engineering concepts rather than abstract challenges.
Candidates experienced behavioral interviews that focused on motivations, past experiences, and situational responses, often conducted by hiring managers. These discussions were noted to be more in-depth and personal compared to technical evaluations.
Overall, candidates described the interview environment as friendly and supportive, though some reported negative experiences due to perceived personal questioning or a lack of respect during technical evaluations. The tone varied significantly across different interviewers.
Interviews often included a mix of coding challenges and discussions where candidates were expected to articulate their thought processes. The format was generally interactive, allowing candidates to showcase their reasoning and problem-solving skills.
Candidates frequently expressed frustration over delayed feedback and unclear outcomes, with some feeling that their efforts were not matched by timely communication. Many left interviews without a clear understanding of their performance or next steps.