READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 7 of 153
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: arrays by hand and bidding design
My loop began with an in-person first round that the interviewer said would take about an hour. We started with my resume and past experience, then moved into HR-related questions tied to that background. The technical portion was a medium arrays problem that I had to solve by hand. The second round was online and focused on backend design for bidding at an advertising agency. Moving from a hand-…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview experience: assessment through virtual onsite
I started with an online assessment and then moved into a virtual onsite. The onsite mixed coding, system design, and behavioral questions, along with discussion of my past experience and projects. Each round had a clear purpose even where the topics overlapped. Coding required the most active problem-solving. In system design, I had to explain tradeoffs and work through how I would tackle a larg…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: behavioral focus with easier coding
My interview loop was more straightforward than I had heard. There were two rounds, both combining behavioral questions with easier LeetCode-style questions. The first was with a manager and the second with a team member. The difficulty felt manageable, and the behavioral conversation was not harsh. Leadership principles clearly mattered, but the discussion did not feel adversarial. It felt like…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: behavioral panel on Microsoft Teams
My interview was a roughly forty-five-minute Microsoft Teams call with a two-person panel. It was mostly behavioral, focused on my background and resume, with fewer technical questions than I expected. The pace felt more like a conversation than a coding session. The panel wanted me to explain my experience instead of pushing deeply into algorithms. I did not receive an offer. In hindsight, the f…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: binary search, BFS, and AI questions
I went through two interview rounds. The first had two DSA problems. One used binary search on the answer, and the other was BFS. During that same round, they also asked about AI and hallucinations. The second round was a crypto number style question. The topics were varied, and the AI portion in the first round surprised me because it moved the conversation away from pure coding. I did not get a…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: binary tree serialization and complexity
The first round had two DSA problems, with about 30 minutes for each. One was about serializing and deserializing a binary tree, followed by questions on time and space complexity. I handled both concepts in that round and moved forward, but things did not work out after that. The process stayed focused on fundamentals. They wanted me to implement a solution and explain its efficiency. When I did…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: Bug finding and a relaxed culture fit
The process was compact and low-stress. I first had an online assessment to find bugs in code, followed by another online assessment with two medium LeetCode-style problems. Then I had an in-person conversation about my experience and a LeetCode problem. The last stage was a culture-fit test that also had an online-assessment component. Everyone I spoke with was relaxed and easy to talk to. The t…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview experience
The process began with online recruitment quizzes full of brain-teaser-style questions that felt irrelevant to the Software Engineer job. I was frustrated because I was not applying to solve riddles. Even at that early stage, the tone affected how I saw everything afterward. It felt disrespectful to my time and did not give me confidence in the evaluation. I did not receive an offer. The difficul…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: Clarify before coding
The interviewer was friendly, and their questioning style made me feel less rushed. They would ask a question, wait for my answer, listen carefully, and then ask follow-ups. What stood out was the importance they placed on clarity before coding. They repeatedly appreciated it when I clarified the requirements and intended approach instead of jumping straight into writing code. That made the inter…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: CodeSignal AI round
Communication was smooth from the start. I flew out to meet the team and had a few interviews with clear coordination and good back-and-forth. The assessment was the one part that initially threw me. CodeSignal was confusing at first because they said there was now an AI round. Once I understood what they wanted, it became easier to follow, although the early uncertainty added some mental overhea…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: coding, projects, and leadership principles
The process followed a typical new-grad pattern: an initial coding round followed by three more rounds. Across them, I saw behavioral questions, project discussion, low-level system design, and more coding. Many questions tied directly to leadership principles, so the behavioral part was more specific than a standard tell-me-about-yourself conversation. I had to shape my answers around those them…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: CV discussion and STAR-style stories
The process began with a phone interview that was mostly about my CV. I then had one technical interview and two behavioral interviews with different managers. The behavioral interviews required a lot of stories. It became clear that they wanted answers in a structured format, so I used STAR-style framing to avoid rambling when they asked for specifics. The technical and CV discussions felt strai…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: difficult first-stage coding gate
I expected the process to be hard, but it was harder than I thought, and I did not reach the second stage. The first stage had three parts: two chunks of coding and technical work, followed by a short survey. I understood the structure but still could not get through all of it. The difficulty was high enough that I could not recover as the stage went on. I was not selected. What disappointed me w…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: DSA, design, and bar raiser
The loop began with demanding technical rounds. I had to work through two LeetCode DSA problems, one medium and one hard. Getting the solution to work was only part of it: I had to explain my thinking, analyze time and space complexity, cover edge cases and optimizations, and discuss alternative approaches and trade offs. Next came system design for a scalable, distributed Amazon style service. W…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: DSA, design, and resume probing
My process felt technical and tough. It combined DSA, low-level design, and a resume discussion that went deeper into my background than I expected. They wanted solid fundamentals in trees, graphs, hash maps, and arrays. I felt challenged throughout, instead of in only one hard round, and I came away thinking I needed to be extremely comfortable with those core areas. I was surprised by how much…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: DSA follow-ups and behavioral principles
My interviews followed a three-round sequence. I started with an online assessment, then had a technical interview on basic DSA coding questions with follow-ups, including time-complexity questions. The final round was behavioral and tied directly to Amazon-style behavior principles. Although the DSA questions were described as basic, they still required careful reasoning and clear explanations.…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: DSA followed by system design
I went through two technical rounds. The first was classic LeetCode-style DSA work with two medium problems, including binary search. The second moved away from pure coding and toward larger systems and products. It covered system design and product discussion, along with design patterns and database questions. It felt like an engineer's interview rather than trivia. The difficulty was average fo…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: DSA, LLD, GenAI, and leadership principles
I had four rounds that stayed consistent from start to finish: a DSA-focused round, two LLD rounds, and a final leadership-principles and behavioral round. Leadership-principles questions also appeared throughout the technical discussions. One LLD round covered GenAI best practices, while the remaining LLD discussion focused on design tradeoffs. Across the process, the interviewers cared more abo…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: easy DSA and RAG project discussion
After I applied, I moved to an online assessment and then a technical interview. The assessment covered DSA and aptitude. In the live round, I solved easy DSA-style questions before the discussion shifted to my resume, especially a project where I had used a RAG model. The interview felt straightforward. I explained what I had built and how I approached it, and the DSA portion was more manageable…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: easy-to-medium coding with intense LP drilling
The interview began with LeetCode-style problems that were easy to medium, then became more intense through Leadership Principle drilling. About half the time went to LP follow-ups, while the other half went to coding-style questions in the usual LeetCode rhythm. That pattern repeated across two rounds. I was not answering leadership questions once and moving on. I had to explain how I would thin…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: Familiar technical loop
The experience felt dated and generic. I went through technical rounds on systems and databases, along with the usual LeetCode-style questions available online. The behavioral rounds used stressful prompts to evaluate my social skills. It never felt tailored, and by the end it was not engaging enough to match the effort I had put in. I ended without an offer. What stayed with me was how standard…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: Fifty-minute DSA and behavioral round
I started with an assessment and then moved to a first technical round, but failed after that. The round included a DSA question, a behavioral question, and a situational prompt. The whole interview lasted around fifty minutes. It was compact, with different types of questions coming back to back in a short window. The process was not long, but it clearly tested both coding fundamentals and how I…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: first-round DSA gate
My process had three rounds, and getting past the first one depended on solving both DSA questions. The second round had no clear right answer. They wanted to see whether I could follow the prompt and explain my reasoning. The third round was managerial. That structure made the stakes clear from the beginning. I could not treat the first round as a warm-up. The manager round shifted toward leader…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: four back-to-back onsite rounds
After the initial recruiter interactions, I had an onsite loop with four back-to-back rounds in one day. It was intense but clearly structured: two coding-heavy rounds with senior engineers, one hiring-manager round, and one behavioral round with a bar raiser. Leadership principles and data-structures topics appeared repeatedly through the day, so I could not really separate the behavioral piece…