Akamai logo
AkamaiSolutions Engineer
Updated Feb 3, 2026

Akamai Solutions Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Solutions Engineer at Akamai, newest first and distilled into what to expect across the loop.

Get your personalized Akamai Solutions Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
7 months ago
Average Neutral San Diego, CA

I went through a multi-stage process that felt more like a product-knowledge gauntlet than a balanced evaluation. The role was positioned as solutions engineering / pre-sales work, where translating business needs into technical solutions is supposed to be central—but the hiring loop appeared to push deep, product-specific technical knowledge very early, before there was much room to show how I think, communicate, and influence.

What made it hard was not just the technical content, but the structure and time investment: the process felt like a large number of stages, including multiple technical screens and even a panel presentation. It created a kind of high-theater cycle that was demanding and slow enough to add friction, especially given the role’s customer-facing emphasis. By the time it ended, the biggest reflection I had was that the technical depth could be taught, but the interpersonal and stakeholder-clarifying ability is harder to demonstrate when the process is overly weighted toward memorization and early technical filters. I didn’t get an offer.
> 1 year
Average Negative United States

My interview journey felt elimination-style from the start. I remember that each round mattered a lot—if I didn’t qualify, the process stopped. The first step was a problem-solving round where I got a prompt shared in an online IDE via a HackerRank link and had to work through it live. After that, I moved into a round that focused more on system design and coding standards.

The last technical/behavioral combination round was more general but still engineering-shaped. I was asked broader questions like what traits an ideal team should have, and how I handle things like code reviews. There was also a sense that the questions stitched together the earlier problem-solving and standards work, so it wasn’t only behavioral polish.

Unlock every Solutions Engineer interview experience

Real Solutions Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.