Akamai Software Engineer candidates reported an online assessment or multiple technical conversations centered on programming fundamentals, SQL, project decisions, and explaining solutions clearly.
$136K
Avg. Base Comp
$180K
Avg. Total Comp
Not reported
Typical Rounds
2-4 weeks
Process Length
Akamai Software Engineer interview reports point to an assessment-and-technical-discussion process that rewards clear engineering explanations alongside coding fundamentals. One Software Development Engineer candidate reported resume screening followed by a HackerRank MCQ test spanning data structures and algorithms, Linux, networking, operating systems, and databases. A subsequent technical interview included an easy-to-medium array problem, a SQL query, and questions about projects, Python, and Linux.
A separate Software Engineer candidate described multiple technical rounds covering Java, Spring Boot, SQL, REST APIs, and data structures. That candidate was asked about Java OOP, collections, multithreading, exception handling, JVM basics, dependency injection, and transaction annotations; they also faced joins, aggregations, indexing, and an array/hash-map coding problem with complexity and edge-case follow-ups. Prepare to explain both your solution and your design choices, not simply produce an answer.
Project discussion appears across the available engineering accounts. Be ready to describe architecture choices, implementation challenges, and production issues, and to explain how your own decisions affected the result. Other candidates also reported live Python exercises, system-design prompts, Linux and networking questions, and resume-based managerial conversations. The available evidence spans several related engineering roles, so the exact sequence and technical emphasis may vary by team and hiring path.
Synthesized from 7 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Akamai process.
The interview process consisted of multiple technical rounds covering Java, Spring Boot, SQL, REST APIs, and data structures. The interviewers focused more on problem solving and explaining design decisions than memorized answers. I was comfortable with the Java and Spring Boot discussions but needed more time on one DSA problem involving graphs.
Questions asked: The technical questions covered Java OOP concepts, Collections, multithreading, exception handling, JVM basics, and Spring Boot annotations such as @Transactional, dependency injection, and REST APIs. I was asked to write SQL queries involving joins and aggregations, explain indexing, and solve a coding problem using arrays and hash maps. There were also follow-up questions on time and space complexity, edge cases, and how I would optimize my solution. The interviewer also discussed a previous project from my resume and asked about my design decisions, challenges faced, and how I handled production issues.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Akamai
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Target Indices | |
| Portfolio Platform Architecture | |
| Skyscanner Partner ETL | |
| Seller Type Modeling | |
| Three Indexes Adding Zero | |
| Blob Indexing | |
| Text Editor With OOP | |
| LRU Cache 1 | |
| Weighted Keys | |
| Longest Increasing Subsequence | |
| Flatten N-Dimensional Array to 1D Array | |
| Complete Addresses | |
| Centralized Event Ingestion | |
| Common Prefix | |
| Count Transactions | |
| Second Longest Flight | |
| Stranded Capacity | |
| Client Solution Pushback | |
| Decreasing Payments | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| String Shift |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reported a short presentation followed by MCQs on machine learning, operating systems, computer networks, and DBMS, plus a vector-addition OOP design task and two SQL queries. That candidate received a shortlist the same day.
One Software Engineer candidate described multiple technical conversations on Java, Spring Boot, REST APIs, SQL, and data structures, including an array/hash-map problem with complexity and edge-case follow-ups. Another reported practical systems and OOP fundamentals.
Both Software Engineer reports included discussion of past work. Candidates may be asked to explain design decisions, implementation challenges, and production issues; one report specifically described questions on MongoDB and authentication versus authorization.
