READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 6 of 153
Interview experiences · Verkada
Account Executive interview at Verkada
The recruiter was responsive and the interviews were polite and enjoyable. After LinkedIn outreach, I went through what seemed like a typical four-stage process. They contacted my professional references and told me there was an intent for a verbal offer, which surprised me. Then they asked for another interview round. After I completed it, I was rejected with a generic explanation of insufficien…
Interview experiences · ACI Worldwide
ACI Worldwide Software Engineer Interview Experience: OOP, DBMS, and motivation
I began with an introduction conversation about what the company does and what the role involves. It felt more like a fit check than an interrogation because they asked about my interests and details from my personal background. The next step was a technical round on fundamentals. I was asked theory about OOP and DBMS, implementation questions about interfaces, and some data-structures topics. Th…
Interview experiences · Act Digital
Act Digital Data Analyst interviews across six client processes in 2026
I took part in six hiring processes with the company during 2026, each tied to different clients and projects, including automotive, insurance, and vacuum-machine manufacturing. In almost every cycle, I felt the interviews went well. One final client even gave positive feedback on my participation. In the end, though, I never moved to an offer. On five occasions, I received the same explanation:…
Interview experiences · Acturis
Acturis Business Analyst Interview Experience: GMAT test and case studies
After I applied, I received a short GMAT-style test with 20 questions and about 30 minutes to complete it. A recruiter followed up, and I went through three interviews. Each round paired case study analysis with more personal questions. The schedule felt intense but structured: two interviews on the same day, followed by a final round on another day. The first Teams interview began with getting t…
Interview experiences · Acturis
Acturis Business Analyst online quiz and case interview experience
The process began with an online quiz and quickly moved to online interviews. I had two sessions on the same day, one in the morning and one in the afternoon. The rounds built on the earlier assessment: reviewing quiz answers, working through a case study, and answering standard questions about the job and my CV. The compressed virtual schedule meant switching between logic and GMAT-style questio…
Interview experiences · Acuvate Software
Acuvate Software Software Engineer five-round interview
My process had five rounds. It began with an aptitude and reasoning assessment, followed by a group discussion and two technical rounds on programming fundamentals and problem-solving. Project thinking and core programming concepts came up. I was struck by how much the technical work still overlapped with reasoning and how I think, not only what I know. The final round was HR. We discussed commun…
Interview experiences · Acuvate Software
Acuvate Software Software Engineer Interview Experience: Aptitude-heavy process
I began with a recruiter-style interaction. About a week later, I took a test that leaned heavily on aptitude and felt tricky. It seemed to judge more than experience. Even with a background, there was a clear emphasis on reasoning and aptitude questions. The sequence felt structured and demanding from the start. After the aptitude round came a group discussion, where communication and confidence…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Customer Success Engineer interview: AI topics and approachable coding
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Network Engineer Interview Experience: online tasks and video prompts
This did not feel like a normal series of recruiter calls and technical interviews. I applied online, and the later steps were mainly online tasks: watching videos, answering questions, and completing work prompts rather than participating in live interviews. I was surprised by how little in person style interviewing there was. After I finished the tasks, I received an email a few days later sayi…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Network Engineer interview: technical, program-manager and Bar Raiser rounds
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer assessment: DSA and AI debugging
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer four-hour loop and shadow-deployment design
The process began with an HR screening that included two LeetCode questions, then an HR manager screening. After that came four hour-long loop interviews, so it felt like a full interview day rather than a brief conversation. The loop included three medium LeetCode questions and one system-design interview. The design topic was shadow-deploying test software to millions of users. It made me think…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer four-interview leadership and GenAI loop
After an initial recruiter touchpoint, I went through a four-interview loop built around Amazon-style leadership principles. Three interviews were with people from the team I might have joined, and the last was with a bar raiser from another organization. Two interviews were coding-focused. One was LeetCode style and another leaned into system design. I also had a general GenAI round, so it was n…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: AI-usage and top-k prompt
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: Amazon-style loop and offer
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: architect-level questions
I applied through the Amazon job portal and got an HR call. After that, I went through five technical rounds in total: one described as a screening round and the rest scheduled as technical interviews. The early questions felt aimed at architect-level depth even though I was applying as a developer with four years of experience. The first two rounds were the hardest, and the questions pushed beyo…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: coding and design loop
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: coding and leadership
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: coding and repository bug fix
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: coding assessment and a 45-minute behavioral call
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: a Java, React, SQL, and DevOps assignment
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: A year of waiting
This was frustrating mostly because it dragged on. The technical and personality parts were not the main problem. I had been interviewing for more than a year and did not feel that anyone kept me updated or consistently looped me in. The sequence was a home technical exam, then a home technical and personality set, followed by a Zoom technical exam. I kept waiting for clarity about timing and wha…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: about three months from assessment to decision
My path began with an online assessment, followed by a recruiter call that set up an onsite loop. The onsite had three consecutive stages: a bar raiser loop, a DSA focused loop, and an LLD focused loop. The full timeline, from the assessment to the final decision, was about three months, far longer than I expected. The interviews felt as though they covered the usual breadth: leadership judgment…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer Interview Experience: AI-assisted debugging and leadership principles
The process began with an online assessment that had one DSA coding task and an AI-assisted debugging exercise. For the debugging part, I was given a coding database and had to use an assistant through prompts to work out why something failed. The stage ended with leadership-principles style questions. After that, I had three technical rounds. Each combined a DSA question with leadership-principl…