READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 8 of 153
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: GenAI coding to DSA and system design
My process began with an OA that included a hard LeetCode-style problem. The second round was a GenAI-related coding interview. After that came a technical screen with a high-level medium LeetCode question and leadership principles. The final loop was more DSA-heavy. It had three DSA questions followed by a system design round, so the last stage tested both algorithmic work and design thinking. I…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: graduate OA with a short first challenge
I was invited to an online assessment for graduates. What stood out was the time limit for the first programming challenge. The window to solve it felt absurdly short, so a large share of the time went to reading and understanding the prompt. The second test felt more reasonable by comparison. The content itself was not described as impossible, but the timing made the round stressful. I spent mos…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: graph and monotonic stack problems
After I was shortlisted from an online assessment, I was called for an interview that felt friendly and focused on solving. The interviewer gave me two medium-level DSA problems, one on graphs and one involving a monotonic stack. I was comfortable enough to talk through my approach while working, and the problems covered a useful mix of techniques rather than one narrow topic. I did not get an of…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: Guided online test
Someone from the hiring side contacted me through LinkedIn, and after I applied, the process began with an online test. The questions resembled HackerRank problems, but they came with a few videos that explained the reasoning and approach the company expected. The difficulty felt average. This stage seemed to be testing how I reasoned rather than brute-force coding. I did not receive an offer, th…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: hard DSA after the online assessment
The process started normally: I applied, a recruiter reached out for a brief HR-style introduction, and then I took a one-hour online assessment. The later rounds included two DSA coding interviews, one system-design interview, one behavioral or leadership-style question they called BQ, and several team-matching rounds. The DSA portion was much harder than I expected. The problems felt close to L…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: House Robber and leadership principles
I started through an on-campus opportunity with an OA that mixed fundamentals and personality fit. It included two DSA questions and behavioral questions, followed by two interview rounds. The first interview began with a project discussion and moved to one low-level design question. The second was more coding-heavy: two DSA problems, House Robber 1 and House Robber 3, followed by questions tied…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: layered leadership-focused loop
My interviews involved several screening and loop conversations before the full evaluation. I began with a hiring-manager screening call, then spoke with an engineering director, a senior product owner, a senior software engineer, and a pair of Bar Raisers before a final hiring-manager round. The sequence was structured and layered. It was difficult overall, but each conversation seemed intended…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: LeetCode rounds to large-scale design
My loop mixed technical work and design in a consistent flow. I had two technical rounds, then a system-design round, followed by a one-on-one conversation with a manager. The technical rounds were LeetCode-style problem solving. The system-design round was about designing large-scale systems and how I would structure the approach, rather than any one algorithm. The manager conversation stayed fo…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: metrics monitoring design
After the recruiter screen, the rest of my loop took almost a month, which felt longer than I expected. After the initial phone conversation, I had two technical interviews centered on data structures and algorithms. One covered merging overlapping intervals, and the other asked for the minimum number of meeting rooms. The final interview was system design. I had to design a scalable metrics moni…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: OA timing disrupted performance
I started with an online coding test and received an HR set of questions soon after submitting it. Then I had a face-to-face technical round that mixed coding and system design. That technical part included three coding questions and system-design discussion, followed by a manager round. The assessment phase threw me off more than the later stages. The OA questions did not seem impossible, but th…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: One round on VIM familiarity
The interview was essentially one round, and I did not get past it. It was unpleasant in the moment, and the feedback suggested that the decision was made quickly. The questions were specific. I realized I should have prepared more deeply for VIM because they asked me many questions about it and I did not handle that line of questioning well. The interviewer presented the process as fair, but I c…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: onsite coding and Bar Raiser gap
I began with a straightforward OA and then moved to onsite interviews. The coding rounds were easier than I expected, with LeetCode medium or medium-hard style problems. The Bar Raiser round was different. It felt more complicated and demanded much more preparation than the coding rounds. I could not turn my onsite coding performance into enough strength in the Bar Raiser evaluation. I did not re…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: Probability, estimation, and confidence
The process was heavily driven by an OA across three rounds, ranging from easy to medium. Then came an interview step that reviewed the code I had written in the OA, almost like a code-review session, for about 45 minutes. It felt very easy compared with typical interview loops. The questions leaned heavily on probability and statistics estimation. I had to solve them quickly, in roughly 30 minut…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: promised phone interview that never happened
After the recruiter started arranging a phone interview, the company went quiet. The recruiter said they would set up the next step, but it never happened. The difficulty was described as very difficult, although the larger issue was not the technical bar. It was the lack of professional follow-through. I never reached a meaningful later stage because the process did not continue. I was not selec…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: quick move from assessment to virtual onsite
My process started with an online assessment that I completed in about three days. The HR contact asked when I could finish it, so timing mattered from the start. After that, I had a phone screen with behavioral questions and LeetCode. A couple of days later, I had the virtual onsite. It included more LeetCode, OOD, and system design. When I reported the experience, I had just completed the phone…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: rain fill, LRU, and delivery-service design
My interview focused on a couple of familiar technical questions. One was a straightforward "fill rain" problem. The design portion came afterward. One prompt felt close to an LRU cache, and the higher-level task was to design a delivery service similar to Uber or DoorDash. The conversation was practical. I reasoned through the core logic first, then moved into system-level thinking for the desig…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: Recruiter call and coding
My first substantive conversation was a phone interview over Chime with a recruiter. It began casually enough that I thought it might remain a relaxed chat. Instead, it quickly shifted into behavioral questions about how I had handled situations, along with one easy LeetCode coding problem. The difficulty was average, but the timing and change in tone caught me off guard. I did not receive an off…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: recruiter prep package and leadership examples
The experience was positive. The interviewers were genuinely nice, and the technical portion felt manageable because I had practiced the areas they emphasized, especially leadership principles. The recruiter gave me an interview prep package. Reading it and preparing strong examples mattered a great deal, and the interview did not try to catch me off guard. I received an offer. I connected the ou…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: repeated rescheduling around standard questions
The questions themselves were mostly normal interview questions. What wore me down was the process: my interviews were rescheduled three times, and the changing schedule was stressful. Even with that disruption, the content was not out of line. I got LeetCode-medium-level coding questions and behavioral questions, with nothing especially novel or unfair for an SDE role. I did not get the offer. T…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: rescheduled campus loop
This started as an on-campus opportunity. The online assessment had two DSA questions and behavioral questions. After that, I had two interview rounds. The first was a project discussion plus an LLD question. The second had two DSA questions and leadership-principles questions. The questions themselves sounded fairly standard, but my interviews were rescheduled several times. That made the loop f…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: rising coding difficulty under time pressure
My first assessment round involved difficult coding with limited time. I remember occasional helpful hints, but it was still very hard to finish under the clock. The questions grew harder as the round went on, which made the final part the most stressful. I was also frustrated that there was not more real-time guidance from an interviewer while I worked. I did not complete the full coding portion…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: Standard systems and LeetCode rounds
I went through technical rounds on systems and database knowledge, along with the usual LeetCode problems you see online. There were also behavioral rounds with stressful questions meant to evaluate social and communication skills. It felt boring and outdated to me, and I did not get an offer. I was disappointed by more than the outcome. The process did not bring anything new even though I had pu…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview experience: three one-hour conversations
After an initial coding assessment, I had three one-hour interviews with different team members. The first was entirely coding. It moved quickly enough that I had to explain my reasoning as I went, though it never became chaotic. The second split its time between coding and behavioral questions, so I had to change gears while still working on a technical problem. The last was entirely behavioral…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: timed recruiter, coding, and final-loop stages
I went through a three-round structure with clear time blocks: a recruiter screen, a one-hour technical screen, and a final loop made up of five interviews. The technical screen was tightly scheduled. It began with a short introduction, moved into behavioral questions, then a dedicated coding segment, and finished with a brief period for my questions. I did not receive an offer. What I remember m…