Akamai interview questions

1) OA questions: Time Complexity analysis (nested loops, log, log-log patterns) Operating Systems concepts (buffer overflow, epoll) C++ / OOP concepts (base class / inheritance behavior) Algorithm complexity of code snippets Binary Search behavior Process / Thread behavior with fork() CPU Scheduling calculation (time when process finishes) Hashing / Hash function computation Greedy / Scheduling coding problem (process size vs processor capacity) 2) Interview Rounds The interview process consisted of three rounds: 1) Technical Round This round focused on evaluating technical knowledge and problem-solving skills. Questions were asked from Data Structures and Algorithms (DSA) along with core computer science subjects such as Operating Systems (OS), Computer Networks (CN), Object-Oriented Programming (OOP), DBMS, and SQL queries. The interviewer also asked questions related to UML diagrams and basic system design concepts. In addition, several resume-based questions were asked, where the candidate had to explain their projects, technologies used, and the design decisions made during development. 2) Managerial Round This round mainly involved an in-depth discussion about the projects mentioned in the resume. The interviewer focused on understanding the candidate’s role in the project, the challenges faced, how those challenges were solved, and the reasoning behind the choice of technologies and design approaches. 3) HR / Behavioral Round This round focused on behavioral and situational questions to evaluate communication skills, attitude, teamwork ability, and cultural fit within the organization. Questions typically revolved around strengths, weaknesses, handling difficult situations, teamwork experiences, and career goals. 3) Interview Round Questions Technical Round In the technical round, questions were asked from Data Structures and Algorithms, system design, databases, and DevOps fundamentals. From DSA, multiple questions were asked including: One question on Binary Search Questions related to Binary Trees and Binary Search Trees One question on Bit Manipulation One problem based on the Fractional Knapsack (Greedy algorithm) Apart from DSA, the interviewer also asked questions related to UML diagrams, where the candidate was asked to design and explain the structure of a system. A backend system design and workflow was also discussed, where the candidate had to explain the architecture and how the system would function end-to-end. From the database side, complex SQL queries were asked, including queries involving joins, aggregations, and sorting. The interviewer also asked questions related to DevOps fundamentals, including basic Linux and Docker commands. In addition, several questions were asked about the projects mentioned in the resume, focusing on the implementation, challenges faced, and the candidate’s problem-solving approach. Managerial Round In the managerial round, the discussion was mainly focused on the projects mentioned in the resume. The interviewer asked detailed questions such as: Why a particular tech stack was chosen Why a specific database was used How the system could scale to support a large number of users Approximately how many users the system could handle This round mainly evaluated the candidate’s understanding of their project, system design thinking, and decision-making ability. HR / Behavioral Round The HR round consisted mainly of personal and situational questions. The interviewer asked questions about: The candidate’s background, such as where they are from and about their family Career goals, such as whether they plan to pursue government exams or continue in the engineering field The interviewer also asked situational questions related to teamwork and conflict management. For example: If a teammate suggests a solution that you believe is incorrect but the manager prefers that solution, how would you handle the situation? How would you deal with disagreements within a team? These questions were aimed at evaluating communication skills, teamwork, professionalism, and decision-making in collaborative environments.