READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 9 of 153
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: two 60 minute in person rounds
I started with HR questions soon after applying, then moved into tightly scheduled in person sessions. The loop had two back to back rounds: one with a hiring manager and one with an engineer. Each lasted about 60 minutes. The first 15 minutes of each were behavioral, and the remaining time was for DSA. The DSA portion carried the usual expectation to explain my thinking clearly. The format place…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: Two coding questions per round
I started with an online assessment containing two coding questions. Within a few days I was selected for the next round, a computer-fundamentals MCQ with about nine sections. After clearing it, I received an interview invitation for two technical rounds. Each technical round had two questions. The topics ranged from basic math to graphs, trees, and HashMap-related problems. The format was very f…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: uneven onsite question difficulty
I think my loop followed a classic coding-and-design structure, but the outcome went against me. I went through an assessment and several later stages. By the final onsite setup, it felt as though I was competing against other interviewers' question sets. At the onsite stage, I had the impression that some candidates got standard LeetCode questions while others got harder, less familiar variants.…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: Virtual DSA OA and timed Zoom round
I was invited to a virtual OA with multiple DSA problems that went from easy to harder at the end. After that, the process had two timed parts: a Zoom session with a LeetCode-medium block followed by behavioral questions. The coding portion lasted about 30 minutes, and the behavioral portion took another 30. The behavioral questions were a real shift in pace immediately after the technical sectio…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: Word Search II, House Robber, and OOP design
My interview ran across two days, with two rounds each day and about an hour per round. Because the content varied by interviewer, it did not feel completely scripted. Round one had two leadership-principle questions and Word Search II. I started with a fixed grid size, then had to explain how I would handle a grid whose size was no longer fixed. Round two was only leadership-principle questions.…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: workday simulation and three final interviews
My loop began with an OA HackerRank round. Within two days, I had a second round that became a workday simulation. I pretended to be an Amazon SDE and talked through decisions about issues that come up in that job. It was less about producing a lot of untested code and more about how I would handle real-world tradeoffs and choices. The final stage was three back-to-back one-hour interviews, each…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: five-round technical and behavioral loop
I went through five rounds in total: an initial OA, a quick recruiter call, and then four back-to-back rounds. The technical questions covered topological graph sorting, detecting a cycle in a linked list, and an LRU cache. The behavioral round was tied to leadership principles. The back-to-back format tested my stamina and whether I could stay consistent across different question types. The roun…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: four difficult design, coding, and BQ rounds
I went through four tight rounds, each about an hour, with a steady level of pressure across design and coding. The first combined object-oriented design with BQ. The second used LeetCode medium plus BQ, the third was BQ only, and the final round returned to LeetCode medium with BQ. I did not receive an offer, and the overall difficulty felt hard. What stayed with me was how consistently the loop…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: four in-person rounds
About a month after the online assessment, I entered an in-person loop with four rounds and a lunch break. Everyone was professional and friendly, and the tight schedule felt organized rather than stressful. One round was fully behavioral; the other three combined behavioral and technical questions. The technical side emphasized fundamentals, especially digital design, while Python knowledge and…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: four one-hour conversations and AI usage
After an early recruiter stage, I had an Amazon-style loop over two days: four one-hour conversations in total. It was long, but the questions were not impossibly hard. The rounds mixed system design, LeetCode-style coding, and behavioral questions tied to Amazon's style and principles. I was also asked how I think about using AI in real work, rather than only in theory. Communication mattered th…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: four-round design loop
After I cleared the online assessment, I entered the Amazon loop. It had four rounds: two coding interviews, a behavioral interview focused heavily on Amazon Leadership Principles, and a final hiring-manager round that combined coding with high-level design. The first coding round had two LeetCode medium problems. The second moved to a hard problem, with the same expectation that I write clean co…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: four rounds in two days
I applied through Amazon Careers without a referral. A recruiter reached out, then I completed an OA. About a month later, I was scheduled for four rounds across two days. The pace was intense. Each interview included 30 minutes of behavioral discussion and 30 minutes of coding. Coding and system-design content were spread across the four interviews, while the overall format stayed consistent fro…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: full leadership loop
After a recruiter call, I completed a 90-minute online coding assessment with two problems and behavioral questions at the end. The full loop followed with four back-to-back rounds of about an hour each. The loop included a coding interview with a hard and a medium LeetCode-style question, system design, behavioral discussion, and a Bar Raiser round that mixed coding with behavioral questions. Th…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: HackerRank and AI assistance
I was given a HackerRank take-home exam and did not do well on it. I did not fully solve everything. After that, I faced another problem involving "AI assistance," but the help felt intentionally unhelpful. My impression was that I was better off ignoring it and solving the task directly. I still reached the next interview stage, where I answered LeetCode-style questions and explained my experien…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: leadership principles and design
I began with an online assessment that combined Amazon leadership-principles behavioral questions with coding. After I passed it, I went to in-person interviews. The first was with the hiring manager and was mostly behavioral, with many leadership-principles questions plus discussion of my past experience and projects. Near the end of that sequence, I had a system-design coding problem. Then I me…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: leadership principles and system design
My process began with an online assessment on data structures and algorithms, followed by a technical phone screen. The final stage was a loop of several consecutive rounds. Those rounds emphasized Amazon-style leadership principles alongside system design. I expected technical evaluation, but I was surprised by how much leadership framing appeared while I worked through design questions. It made…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: leadership stories and timed coding
I passed an online assessment with coding and behavioral questions tied to Amazon Leadership Principles, then moved to in-person interviews. The hiring-manager interview was mostly behavioral, covering leadership principles and my previous experience and projects. Near the end, I received a system-design coding problem. It surprised me by combining implementation with design decisions. I then met…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: loop disrupted by screensharing
After a recruiter call, I took a 90-minute online coding assessment with two problems and some behavioral discussion at the end. A week later I joined a four-round loop, with each round about an hour. The panel included a potential hiring manager, team members, a senior leader, and a Bar Raiser, and each interviewer evaluated specific Amazon Leadership Principles. The loop included LeetCode-style…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: ML fundamentals and a second-round HR discussion
The process was compressed into two rounds: a technical assessment followed by HR. The technical stage covered ML concepts and core computer-science fundamentals, and I was told the difficulty was medium to hard. HR mixed discussion of my resume and projects with questions about how I work and communicate. Across both rounds, they checked whether I could back up what I had written, especially on…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: OA and leadership principles
My process started with an online assessment, and it took a long time before I even reached the interview stages. After the OA, I had two interviews, each about 60 minutes. Across the process, I heard that both LeetCode-style problems and leadership principles were part of the evaluation. That meant my prep could not just be DSA. I also had to have specific stories ready for leadership-principle…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: OA and two technical interviews
After applying, I completed an online assessment with LeetCode-style problems, prompts about emails, and fit questions. I then had two technical interviews, each combining behavioral questions and LeetCode coding. One coding question was medium and another hard. The ones I remember most involved BFS and strings. I received an offer. What stood out was that behavioral and technical evaluation were…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: real problem solving over pattern recall
The recruiter and interview process were unusually clear about what they expected, which gave the experience a positive tone. It did not feel like a vague fit check. The process had defined goals. The technical work emphasized actually solving the problem instead of relying only on memorized LeetCode patterns. I focused on understanding the prompt and working through it end to end. I did not rece…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: streaming system design and managerial rounds
I had three rounds: system design first, followed by two managerial rounds. The process felt difficult. I cleared the system-design portion but did not make it through to an offer. The system-design prompt was to create a streaming application like Netflix or Amazon Prime Video. It required broader thinking than coding: service components, handling streaming workloads, and organizing the design a…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: system design difficulty jump
The process began with a quick DSA screen that felt easy. Once it moved into system design, the difficulty rose sharply because the conversation needed more structure and deeper reasoning than coding alone. Later technical rounds returned to LeetCode-style problems, including DP, graphs, and shorter easy checks such as minimum sliding window. Behavioral questions appeared too, but technical reaso…