My loop was short and mostly technical. I started with a DSA round that included finding the intersection of two linked lists, followed by writing a function to validate an IPv6 address. That part felt like the typical “solve it cleanly” coding expectation, and I worked through the logic with the usual attention to edge cases.
A second round was more technical and product-adjacent. I was asked about Kubernetes and microservices, with questions tailored to how Akamai’s systems and offerings relate to those concepts. I also noticed the way the discussion went: it wasn’t just theory, it was tied back to practical architecture.
2 months ago
Average Positive Bengaluru
After an initial recruiter touchpoint, I went through a fairly structured sequence of interviews that felt professional and organized. The overall loop landed with the usual combination of technical and role-aligned discussion, with an emphasis on core problem-solving rather than anything overly exotic. Timing varied, but the experience didn’t feel dragged out.
I had an online assessment first, focused on coding and problem-solving. Then I moved into two technical interviews: the first leaned heavily into data structures and algorithms, and the next shifted toward system design and situational problem-solving. In both rounds, the interviewers were friendly and supportive—when I got stuck, they provided helpful hints, and the conversation stayed constructive.
2 months ago
I applied via referral, and things moved pretty quickly after HR got in touch. I got the call and had my interview scheduled for the same Friday, roug…
3 months ago
Difficult Positive United States
My process had two main stages. I started with a short recruiter call with no technical questions, just context on the role and the next steps. Then I…
6 months ago
Average Neutral San Diego, CA
After going through the full process, my overall impression was that the role’s framing didn’t match the way the hiring loop worked. I expected someth…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process is generally organized and follows a clear sequence, starting with a recruiter call, followed by technical assessments and behavioral interviews. Candidates noted that the timeline felt efficient, with no prolonged waiting periods between stages.
StructuredEfficientTimeline
Technical Rounds Focus
Candidates can expect a strong emphasis on technical skills, particularly in data structures, algorithms, and system design. Questions often reflect practical applications, such as API design and big data concepts, with a mix of theoretical and hands-on problem-solving.
Data StructuresSystem DesignPractical Applications
Behavioral & Managerial Interviews
There is typically a managerial round that includes behavioral questions, assessing both technical and situational responses. Candidates should be prepared to discuss their past experiences and how they relate to the role's requirements.
BehavioralSituationalManagerial
Communication & Follow-Up
Many candidates reported issues with communication, particularly a lack of follow-up after interviews. Some experienced ghosting or inadequate feedback, which left them feeling uncertain about their performance and the hiring process.
CommunicationFeedbackFollow-Up
Interview Atmosphere & Tone
The tone of interviews can vary significantly; while some candidates found the environment supportive and friendly, others experienced unprofessional behavior or a lack of engagement from interviewers, impacting their overall impression.
AtmosphereProfessionalismEngagement
Assessment of Practical Knowledge
Candidates noted that interviewers often seek a deep understanding of practical concepts rather than just theoretical knowledge. Expect to explain your reasoning and connect concepts in a comprehensive manner during technical discussions.