Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

103 stories

Likes earn the author +10 XP for the first 3 likes each day

ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: hard DSA after the online assessment

The process started normally: I applied, a recruiter reached out for a brief HR-style introduction, and then I took a one-hour online assessment. The later rounds included two DSA coding interviews, one system-design interview, one behavioral or leadership-style question they called BQ, and several team-matching rounds. The DSA portion was much harder than I expected. The problems felt close to L…

HR Screen0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: timed recruiter, coding, and final-loop stages

I went through a three-round structure with clear time blocks: a recruiter screen, a one-hour technical screen, and a final loop made up of five interviews. The technical screen was tightly scheduled. It began with a short introduction, moved into behavioral questions, then a dedicated coding segment, and finished with a brief period for my questions. I did not receive an offer. What I remember m…

HR Screen0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

OfferTechnical Screen0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

HR Screen0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

Technical Screen0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: recruiter prep package and leadership examples

The experience was positive. The interviewers were genuinely nice, and the technical portion felt manageable because I had practiced the areas they emphasized, especially leadership principles. The recruiter gave me an interview prep package. Reading it and preparing strong examples mattered a great deal, and the interview did not try to catch me off guard. I received an offer. I connected the ou…

Offer0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

Online Assessment0
ADCI - KarnatakaSoftware EngineerNew Grad
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: graduate OA with a short first challenge

I was invited to an online assessment for graduates. What stood out was the time limit for the first programming challenge. The window to solve it felt absurdly short, so a large share of the time went to reading and understanding the prompt. The second test felt more reasonable by comparison. The content itself was not described as impossible, but the timing made the round stressful. I spent mos…

Online Assessment0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: rain fill, LRU, and delivery-service design

My interview focused on a couple of familiar technical questions. One was a straightforward "fill rain" problem. The design portion came afterward. One prompt felt close to an LRU cache, and the higher-level task was to design a delivery service similar to Uber or DoorDash. The conversation was practical. I reasoned through the core logic first, then moved into system-level thinking for the desig…

OfferTechnical Screen0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

Technical Screen0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: One round on VIM familiarity

The interview was essentially one round, and I did not get past it. It was unpleasant in the moment, and the feedback suggested that the decision was made quickly. The questions were specific. I realized I should have prepared more deeply for VIM because they asked me many questions about it and I did not handle that line of questioning well. The interviewer presented the process as fair, but I c…

Rejected0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

OfferOnline Assessment0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: Probability, estimation, and confidence

The process was heavily driven by an OA across three rounds, ranging from easy to medium. Then came an interview step that reviewed the code I had written in the OA, almost like a code-review session, for about 45 minutes. It felt very easy compared with typical interview loops. The questions leaned heavily on probability and statistics estimation. I had to solve them quickly, in roughly 30 minut…

OfferOnline Assessment0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: OA timing disrupted performance

I started with an online coding test and received an HR set of questions soon after submitting it. Then I had a face-to-face technical round that mixed coding and system design. That technical part included three coding questions and system-design discussion, followed by a manager round. The assessment phase threw me off more than the later stages. The OA questions did not seem impossible, but th…

RejectedOnline Assessment0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

Online Assessment0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: layered leadership-focused loop

My interviews involved several screening and loop conversations before the full evaluation. I began with a hiring-manager screening call, then spoke with an engineering director, a senior product owner, a senior software engineer, and a pair of Bar Raisers before a final hiring-manager round. The sequence was structured and layered. It was difficult overall, but each conversation seemed intended…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: promised phone interview that never happened

After the recruiter started arranging a phone interview, the company went quiet. The recruiter said they would set up the next step, but it never happened. The difficulty was described as very difficult, although the larger issue was not the technical bar. It was the lack of professional follow-through. I never reached a meaningful later stage because the process did not continue. I was not selec…

No response0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: GenAI coding to DSA and system design

My process began with an OA that included a hard LeetCode-style problem. The second round was a GenAI-related coding interview. After that came a technical screen with a high-level medium LeetCode question and leadership principles. The final loop was more DSA-heavy. It had three DSA questions followed by a system design round, so the last stage tested both algorithmic work and design thinking. I…

RejectedOnline Assessment0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: LeetCode rounds to large-scale design

My loop mixed technical work and design in a consistent flow. I had two technical rounds, then a system-design round, followed by a one-on-one conversation with a manager. The technical rounds were LeetCode-style problem solving. The system-design round was about designing large-scale systems and how I would structure the approach, rather than any one algorithm. The manager conversation stayed fo…

Offer0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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.…

0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP