real interview stories, told over a cup of tea ♡
Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
3935 results
- ADCI - Karnataka Customer Success Engineer interview: AI topics and approachable codingADCI - Karnataka · Customer Success Engineer · Technical Screen · Jul 2026
The interview felt easy and straightforward. Questions focused mostly on general behavioral and AI-related topics, and the coding did not feel overwhelming. For coding, I was asked to find duplicates and solve longest common prefix. The rest of the discussion was about how I thought and explained my reasoning, rather than difficult algorithm tricks. I did not receive an offer, but the experience…
- ADCI - Karnataka Network Engineer interview: technical, program-manager and Bar Raiser roundsADCI - Karnataka · Network Engineer · Technical Screen · Jul 2026
The process took about a week, close to five business days. It moved briskly from technical interviews through a program-manager conversation and a Bar Raiser round. I felt they were assessing more than one kind of ability. The technical rounds followed familiar Amazon interview patterns. The Bar Raiser made the assessment feel more calibrated, as though they were checking whether my leadership a…
- ADCI - Karnataka Software Engineer assessment: DSA and AI debuggingADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026
The online assessment was the main part of my process. It had four pieces: a medium-to-hard DSA problem, a work-simulation task involving a website bug that I had to solve with AI, and two behavioral sections. The simulation changed the feel of the assessment. It was not only about writing correct code. I had to work out what the system was doing and use AI as part of the debugging process. The b…
- ADCI - Karnataka Software Engineer Interview Experience: a Java, React, SQL, and DevOps assignmentADCI - Karnataka · Software Engineer · Take-home Project · Jul 2026Rejected
My path began with an assignment that mixed Java depth, React, some SQL, and a smaller DevOps component. It was substantial and felt designed to test end-to-end reasoning rather than isolated coding. The next step was a paper-based written problem-solving round. I was rejected there, and I felt circumstances played a part alongside technical ability. I had traveled a long way for the interview an…
- ADCI - Karnataka Software Engineer interview experience: assessment through virtual onsiteADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026Offer
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…
- ADCI - Karnataka Software Engineer Interview Experience: easy-to-medium coding with intense LP drillingADCI - Karnataka · Software Engineer · Technical Screen · Jul 2026
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…
- ADCI - Karnataka Software Engineer interview experience: three one-hour conversationsADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026
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…
- ADCI - Karnataka Software Engineer interview: AI-usage and top-k promptADCI - Karnataka · Software Engineer · Technical Screen · Jul 2026
After the OA, I had two one-hour interviews. Both contained technical questions and leadership-principles discussion, and both included a question about using AI. In one hiring-manager-style round, I was given a prompt without an API that was framed as a variation on top-k elements. Another technical round used a more story-driven setting, including a restaurant-manager scenario involving groups…
- ADCI - Karnataka Software Engineer interview: Amazon-style loop and offerADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026Offer
My process followed a typical Amazon-style path: recruiter screening, then an OA with coding and work-style or behavioral components. After I cleared that stage, I had phone or video interviews that combined technical questions with leadership-principle behavioral questions. The main loop was multiple back-to-back rounds. I faced data structures and algorithms, plus system design or design discus…
- ADCI - Karnataka Software Engineer interview: coding and design loopADCI - Karnataka · Software Engineer · Jul 2026
I had a 30-minute recruiter phone screen about my background and resume, then a technical video interview with a senior engineer. That technical conversation lasted about an hour, beginning with introductions before a live coding challenge in a shared editor. After coding, I answered questions on system-design basics and how my projects related to their work. Later, the loop also included a syste…
- ADCI - Karnataka Software Engineer interview: coding and leadershipADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026
I began with an online coding assessment on data structures, algorithms, and general problem solving. The interviews that followed covered coding, system-design fundamentals, and Amazon Leadership Principles. Interviewers were professional and asked follow-ups for clarity and for my reasoning, not only the final answer. The coding work required careful reasoning and correctness. For Leadership Pr…
- ADCI - Karnataka Software Engineer interview: coding and repository bug fixADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026
The online assessment had two back-to-back coding tasks. The first was one coding question with a 45-minute limit. The second was a repository task where I fixed a bug in a project and spent about an hour getting it working. The coding question was long and detailed, almost like day-to-day work. The repository debugging made it harder because I had to make the system work end to end, not merely w…
- ADCI - Karnataka Software Engineer interview: coding assessment and a 45-minute behavioral callADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026
The online assessment had two coding problems, one algorithmic and one mathematical, plus a short work-style survey. After I passed it, I had one phone interview that was entirely behavioral. In the 45-minute call, I used STAR to discuss past situations, especially how I handled problems and collaborated. There was no coding, so I had to make my story and decisions carry the conversation. I felt…
- ADCI - Karnataka Software Engineer interview: five-round technical and behavioral loopADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026
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…
- ADCI - Karnataka Software Engineer interview: four difficult design, coding, and BQ roundsADCI - Karnataka · Software Engineer · Technical Screen · Jul 2026
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…
- ADCI - Karnataka Software Engineer interview: four in-person roundsADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026Offer
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…
- ADCI - Karnataka Software Engineer interview: four one-hour conversations and AI usageADCI - Karnataka · Software Engineer · Technical Screen · Jul 2026
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…
- ADCI - Karnataka Software Engineer interview: full leadership loopADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026Offer
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…
- ADCI - Karnataka Software Engineer interview: HackerRank and AI assistanceADCI - Karnataka · Software Engineer · Take-home Project · Jul 2026Rejected
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…
- ADCI - Karnataka Software Engineer interview: leadership principles and designADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026
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…
- ADCI - Karnataka Software Engineer interview: leadership principles and system designADCI - Karnataka · Software Engineer · Jul 2026
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…
- ADCI - Karnataka Software Engineer interview: leadership stories and timed codingADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026
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…
- ADCI - Karnataka Software Engineer interview: loop disrupted by screensharingADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026
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…
- ADCI - Karnataka Software Engineer interview: ML fundamentals and a second-round HR discussionADCI - Karnataka · Software Engineer · Technical Screen · Jul 2026
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…
- ADCI - Karnataka Software Engineer interview: OA and two technical interviewsADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026Offer
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…
- ADCI - Karnataka Software Engineer interview: real problem solving over pattern recallADCI - Karnataka · Software Engineer · Technical Screen · Jul 2026
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…
- ADCI - Karnataka Software Engineer interview: streaming system design and managerial roundsADCI - Karnataka · Software Engineer · Technical Screen · Jul 2026Rejected
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…
- ADCI - Karnataka Software Engineer interview: system design difficulty jumpADCI - Karnataka · Software Engineer · Technical Screen · Jul 2026Rejected
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…
- ADCI - Karnataka Software Engineer interview: take-home, coding, design, and behavioralADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026
After a recruiter screen, I received a take-home LeetCode-style coding assessment. I then had a live coding interview, a system design interview with two design questions, and a behavioral interview about communication, collaboration, and fit. Live coding and system design felt like the main technical checkpoints, while the behavioral round tested how I would work with others. The thorough struct…
- ADCI - Karnataka Software Engineer interview: three back-to-back interviewsADCI - Karnataka · Software Engineer · Jul 2026
I started with an online assessment and then moved quickly into three back-to-back interviews, with almost no downtime. One interview was fully behavioral and had a bar-raiser-style focus. The other two were technical, ranging from DSA to low-level system design. The loop tested more than memorized problem solving; it tested how I think under pressure. I did not get an offer. The back-to-back for…
