Akosha Interview Experience
Interview Experience
I recently got a call from Akosha Bangalore for on-site interview. This Interview had three round, two technical and one manager round.
Round 1 Written Test : 30 Min*20 M...
Full Details
I recently got a call from Akosha Bangalore for on-site interview. This Interview had three round, two technical and one manager round.
Round 1 Written Test : 30 Min 20 MCQ Two programming questions : only one need to attend Find Maximum area in Boolean matrix (0/1).
Solution: https://www.geeksforgeeks.org/dsa/largest-rectangular-area-in-a-histogram-using-stack/ I forget second one, but it was on List of List ( very lame question, I did not like the question so I did not solve it)
Round 2
Technical Interview 1 hour 30 Min This round totally focused on technical knowledge including data structure, algorithms, web services, Protocols etc. Discussion on recent project in detail Role and responsibility in recent project *Linked list random pointer problem: https://www.geeksforgeeks.org/dsa/a-linked-list-with-next-and-arbit-pointer/ * Restful apis discussion, design etc. * HTTP protocol discussion * GET/POST/PUT/DELETE methods discussion * Difference between POST/GET and POST/PUT when to use what * (interesting question) You have a rest api for Post method, Suppose you embedded this api in your application and this api usually takes 2 hour to respond back . How will you handle this situation? -- Lots of discussion were done on timeout, sync call, aysnc call etc But I was not able to give what he was seeking to.
Round 3
Manager Round 1 hour 30 Min * General behavioral questions * Why you want to leave ur current company so early * What you liked so far in development etc I got the offer from company but they were paying sameas what I’m getting currently. More over HR is very bad, she has no sense of talking. After few days I reject the offer (due to their bad behavior, they call me 2’s in a day(7-8 days) from different sources just to say resign asap) I would to say thanks to Geeksforgeek for such a wonderful platform for tech guys.
About This Question
This is a candidate experience report from a akosha interview for a swe role during the phone screen round reported in 2025.
It covers the following topics: Linked List, System Design, Behavioral, Matrix, Stack .
About Akosha Interview Reports
This question was reported by a candidate who interviewed at Akosha. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Akosha are the higher-signal extractions to take from this report.
For broader preparation context, the Akosha interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Akosha reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Akosha Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Akosha reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.