READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 10 of 153
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: take-home, coding, design, and behavioral
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: three back-to-back interviews
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…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: three technical rounds and a behavioral final
I started with an online assessment and then spoke with a recruiter. Next came four rounds over two days, each about an hour. Three were technical, and the fourth was behavioral and based on leadership principles. The behavioral round had no coding. It was entirely about how I had handled past situations. Taking two days made the process drag somewhat, but the questions were not overly punishing.…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: timed code and debugging home test
I received a home test with two hands-on parts. First, I had a HackerRank or LeetCode-style question in a fixed 40-minute window. Then I had 60 minutes to debug a full-stack-app repository where one API call was not behaving as expected. The task was to find the bug and make changes until every test passed. It felt hard because a real-project workflow contains moving context, and I needed to trac…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: Two Sum and longest substring questions
The online assessment had two DSA questions and behavioral questions. After that, I had an interview with two more DSA questions at an easy-to-medium level. They were Two Sum at the easy level and Longest Substring Without Repeating Characters at the medium level. The process was smooth and the decision came quickly. I was selected and accepted an offer. The criteria were clear: DSA came first, w…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview: waitlisted after DSA
After being shortlisted, I took an online assessment with coding and behavioral-style questions. The coding portion covered data structures and algorithms, including an explanation of brute force versus optimal approaches and time and space complexity. I then had a coding-heavy online DSA round with two questions. I felt reasonably confident in my approach, but it moved quickly and did not turn i…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer interview with book system design
I had a face-to-face loop with four rounds. It began with two DSA questions, one on binary search and one on binary trees. Next came an LLD round where I designed a book management system, followed by a hiring-manager round and a leadership round. The leadership questions were closely tied to leadership principles, and those themes also came up in the technical rounds. I received an offer. My ove…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer silicon-team domain, design, and C rounds
I interviewed for the silicon team. The loop was clear about what each round covered, and each interview lasted about 50 minutes. The first round focused on domain-specific knowledge. The second moved to system design, and the third covered C coding. The overall difficulty was average, and I did not receive an offer. What I remember is how deliberately the responsibilities were separated: domain…
Interview experiences · Amazon India (ADCI)
ADCI - Karnataka Software Engineer technical phone screen before loop
The process began with a phone screen that lasted about an hour or more. It was mostly technical questions. After I cleared that step, I moved into the loop interview. The loop was the next stage after the initial screen. Difficulty was average, and I did not receive an offer. The first call set the tone because it tested technical thinking right away rather than serving as a casual introduction.…
Interview experiences · Addepar
Addepar Software Engineer Interview Experience: Positive feedback followed by silence
My journey went through several rounds before stalling in a way that did not match the conversations. I had an introductory call with a director or hiring manager, LeetCode-style medium coding questions, a system design round, a manager behavioral round, and an additional HR touchpoint. The technical discussions felt fair and generally solid while I was in them. The problem appeared after the fin…
Interview experiences · Addepar
Addepar Software Engineer Interview Experience — Table Transactions with Commit and Rollback
Coding / OOD + Data Structure The interview used a simplified table: I needed to implement: The inputs for the basic operations were simply the parameters in each method signature. showTable() printed the current table. There were no especially complicated return-value requirements. The table could be modified only after a transaction had begun. The transaction behavior was similar to a database:…
Interview experiences · Addepar
Addepar Software Engineer Interview Experience — Ticketmaster Reservations Across Regions and Planets
Addepar Interview - System Design Question: Design Ticketmaster. Functional requirements: Users should be able to view events. Users should be able to search for events. Users should be able to book tickets to events. The same event has multiple sections at the same venue, and different sections have different prices. Checkout has a 10-minute time limit. After the time expires, the ticket must be…
Interview experiences · Adobe
Adobe Account Executive Interview Experience: prospecting task and no closure
The process lasted about four rounds and felt more demanding than a standard recruiter-to-manager path. It began with a discovery-style conversation and a peer interview. I was also asked to prospect for a meeting with the hiring manager. That task was awkward because the hiring manager did not answer calls and had a private LinkedIn profile, so outreach was not straightforward even though the pr…
Interview experiences · Adobe
Adobe Account Executive interview: supportive first round followed by radio silence
The process felt normal and contained, with about three rounds. It began with a recruiter conversation, then a task, and finally a meeting with the hiring manager. Communication ran smoothly at first, and the recruiter was especially supportive. I received helpful, actionable feedback instead of vague notes. After the first round, the experience did not continue that way. I got nothing back. Ther…
Interview experiences · Adobe
Adobe Research Analyst Interview Experience: One-hour research conversation
After a recruiter touchpoint, I had one technical conversation with a team member. It lasted an hour and stayed mainly focused on the research I had already done and where I wanted to take it during the internship. The process moved quickly. I had the interview and received a decision about two weeks later. There was not much jumping between steps. It was essentially a discussion about my work an…
Interview experiences · Adobe
Adobe Software Engineer Interview Experience — Five Relaxed Rounds Built Around OOP and API Design
This one felt pretty comfortable to interview with — slow pace, none of that being-chased-the-whole-time feeling. Each round was an hour, and in some rounds close to half the time was just chatting. The problems were medium-to-easy, but they really like steering things toward object-oriented design and code design — the questions here are different from what other companies ask. A quick note: I'm…
Interview experiences · Adobe
Adobe Software Engineer Interview Experience — Four Rounds on the AEP Team, Recruiter Wanted More System Design Experience
This was for the AEP team — a pit that a friend referred me into. Four rounds total, overall not too hard. Round 1 was billed as tech/coding, but after we finished going over my resume, the interviewer just started asking about request latency analysis, plus some front-end/back-end fundamentals-style questions. I initially expected coding or system design, but it ended up basically being a conver…
Interview experiences · Adobe
Adobe Software Engineer Interview Experience — Four Rounds, Team Shutdown, and a Month-Long Wait for Rejection
I finished interviewing right before they shut down the team at the end of last month. Then the HM took a two-week vacation, and after waiting almost a month, I got the classic "they were touched but rejected me anyway" treatment — moved to another candidate. It was for the AEP team, a referral pit from a friend. Four rounds total, overall not too hard. The first round was billed as tech/coding,…
Interview experiences · Adobe
Adobe Software Engineer Interview Experience — Scala Trivia, Then a Surprise LeetCode Classic
This is one of the many applications I scattered around blindly. I applied to GenStudio on the DX team (people on the forum say DX is a "poison team," same as AEP?). When I applied, it happened to line up with Adobe's legendary summer break, so by the time HR came back from vacation and finally reached out to me, I'd already piled up several rejection letters from other places, hah, wry laugh. Th…
Interview experiences · ADP
ADP Account Executive interview: behavioral sales questions and missing follow-up
After a recruiter conversation about the role, I met sales leadership over Zoom. The flow felt organized and reasonable on timing, with each round checking a different part of my background and fit. I got standard why-sales and why-ADP questions, but the focus stayed on my work, how I handle situations, and whether I had the drive to close. The process was behavior-focused. My answers needed stru…
Interview experiences · ADP
ADP Account Executive Interview Experience: Two efficient Zoom fit conversations
My interview moved quickly and had a clear structure. After a short recruiter call, I had a brief Zoom conversation that began with an overview of the role and moved into a prepared set of questions. It lasted about half an hour, so there was not much room to drift, and I appreciated that clarity. The next step was another efficient Zoom conversation with leadership. It stayed on basic fit and my…
Interview experiences · ADP
ADP Account Executive interview experience: VP conversation and field shadowing
A recruiter contacted me first by phone, and the process then moved to a Zoom conversation led by a VP. After that, I went in person for a ride-along or field-style segment intended to show what the job was like outside an office. I was left waiting for a while before the in-person part got started, which disrupted the momentum. The field reality was central to the process. They made it clear tha…
Interview experiences · ADP
ADP Consultant interview: a month-long wait and stalled application status
What stayed with me was the duration and lack of clarity. I started with a video interview that let me record answers more than once, followed by a skills assessment. I was then scheduled to meet a manager and hiring manager and was told I would hear back by the end of that week. Instead, the email came a full month later and said they had moved forward with someone else. In a separate part of th…
Interview experiences · ADP
ADP Software Engineer interview: campus internship drive
I attended ADP's campus software-internship drive at DYPCOE Akurdi in Pune. It began with an online assessment, followed by two technical interviews and an HR interview. The structure was clear as it moved from coding into deeper technical discussion and then HR. The technical rounds emphasized fundamentals and connecting my background to the work they were evaluating. By HR, the conversation was…