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: graph and monotonic stack problems

After I was shortlisted from an online assessment, I was called for an interview that felt friendly and focused on solving. The interviewer gave me two medium-level DSA problems, one on graphs and one involving a monotonic stack. I was comfortable enough to talk through my approach while working, and the problems covered a useful mix of techniques rather than one narrow topic. I did not get an of…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: Standard systems and LeetCode rounds

I went through technical rounds on systems and database knowledge, along with the usual LeetCode problems you see online. There were also behavioral rounds with stressful questions meant to evaluate social and communication skills. It felt boring and outdated to me, and I did not get an offer. I was disappointed by more than the outcome. The process did not bring anything new even though I had pu…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: rising coding difficulty under time pressure

My first assessment round involved difficult coding with limited time. I remember occasional helpful hints, but it was still very hard to finish under the clock. The questions grew harder as the round went on, which made the final part the most stressful. I was also frustrated that there was not more real-time guidance from an interviewer while I worked. I did not complete the full coding portion…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

Offer0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

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…

Offer0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: metrics monitoring design

After the recruiter screen, the rest of my loop took almost a month, which felt longer than I expected. After the initial phone conversation, I had two technical interviews centered on data structures and algorithms. One covered merging overlapping intervals, and the other asked for the minimum number of meeting rooms. The final interview was system design. I had to design a scalable metrics moni…

OfferHR Screen0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: streaming system design and managerial rounds

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…

RejectedTechnical Screen0
ADCI - KarnatakaCustomer Success Engineer
Reported Jul 2026

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…

Technical Screen0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: four difficult design, coding, and BQ rounds

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…

Technical Screen0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: real problem solving over pattern recall

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…

Technical Screen0
ADCI - KarnatakaNetwork Engineer
Reported Jul 2026

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…

Technical Screen0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: leadership stories and timed coding

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…

Online Assessment0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

Software Engineer interview at ADCI - Karnataka: networking depth

A phone screen began with my ongoing work and projects, but every answer led to deeper follow-up. I used STAR-style stories to keep the conversation structured as the interviewer drilled into my experience. The technical part covered TCP/IP and routing topics including OSPF and BGP. The interview assessed both how I described impact and ownership and whether I could reason through practical netwo…

0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

Software Engineer interview at ADCI - Karnataka: difficult DSA and GenAI

The process moved from an OA-style round to DSA and then a GenAI-focused round, but late stages still included LeetCode-style DSA work. One problem used graph algorithms and another required more ad-hoc reasoning; both felt genuinely hard. Amazon Leadership Principles shaped the behavioral framing throughout, linking impact and ownership to problem solving. The difficulty kept rising, especially…

0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

Software Engineer interview at ADCI - Karnataka: DSA and GenAI

The process had two compact rounds. In the first, I solved two medium LeetCode-style DSA problems and discussed a project. The second combined one DSA question with basic GenAI questions and more project discussion about both individual and team work. The difficulty felt reasonable, but I had to explain my answers clearly and connect technical decisions to leadership-principle ideas such as trade…

0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: system design difficulty jump

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…

RejectedTechnical Screen0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: loop disrupted by screensharing

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…

Online Assessment0

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