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
- Accenture Software Engineer interview: three virtual and office roundsAccenture · Software Engineer · Technical Screen · Jun 2026Offer
My journey included three interviews, with a format change near the office stage. The first two were virtual, and the third took place in an Accenture office after scheduling adjustments. Before the technical conversations, I had a recruiter screen that lasted about 30 to 45 minutes. Then I spoke with someone from a developer background for another 30 to 45 minutes. The final step was behavioral…
- ADCI - Karnataka Network Engineer Interview Experience: online tasks and video promptsADCI - Karnataka · Network Engineer · Online Assessment · Jun 2026
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…
- ADCI - Karnataka Software Engineer four-hour loop and shadow-deployment designADCI - Karnataka · Software Engineer · HR Screen · Jun 2026Offer
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…
- ADCI - Karnataka Software Engineer four-interview leadership and GenAI loopADCI - Karnataka · Software Engineer · Technical Screen · Jun 2026
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…
- ADCI - Karnataka Software Engineer interview experienceADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026
The process began with online recruitment quizzes full of brain-teaser-style questions that felt irrelevant to the Software Engineer job. I was frustrated because I was not applying to solve riddles. Even at that early stage, the tone affected how I saw everything afterward. It felt disrespectful to my time and did not give me confidence in the evaluation. I did not receive an offer. The difficul…
- ADCI - Karnataka Software Engineer Interview Experience: about three months from assessment to decisionADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026
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…
- ADCI - Karnataka Software Engineer Interview Experience: DSA, design, and bar raiserADCI - Karnataka · Software Engineer · Technical Screen · Jun 2026
The loop began with demanding technical rounds. I had to work through two LeetCode DSA problems, one medium and one hard. Getting the solution to work was only part of it: I had to explain my thinking, analyze time and space complexity, cover edge cases and optimizations, and discuss alternative approaches and trade offs. Next came system design for a scalable, distributed Amazon style service. W…
- ADCI - Karnataka Software Engineer Interview Experience: four back-to-back onsite roundsADCI - Karnataka · Software Engineer · Onsite · Jun 2026
After the initial recruiter interactions, I had an onsite loop with four back-to-back rounds in one day. It was intense but clearly structured: two coding-heavy rounds with senior engineers, one hiring-manager round, and one behavioral round with a bar raiser. Leadership principles and data-structures topics appeared repeatedly through the day, so I could not really separate the behavioral piece…
- ADCI - Karnataka Software Engineer Interview Experience: Guided online testADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026Rejected
Someone from the hiring side contacted me through LinkedIn, and after I applied, the process began with an online test. The questions resembled HackerRank problems, but they came with a few videos that explained the reasoning and approach the company expected. The difficulty felt average. This stage seemed to be testing how I reasoned rather than brute-force coding. I did not receive an offer, th…
- ADCI - Karnataka Software Engineer Interview Experience: Recruiter call and codingADCI - Karnataka · Software Engineer · HR Screen · Jun 2026
My first substantive conversation was a phone interview over Chime with a recruiter. It began casually enough that I thought it might remain a relaxed chat. Instead, it quickly shifted into behavioral questions about how I had handled situations, along with one easy LeetCode coding problem. The difficulty was average, but the timing and change in tone caught me off guard. I did not receive an off…
- ADCI - Karnataka Software Engineer interview: architect-level questionsADCI - Karnataka · Software Engineer · Technical Screen · Jun 2026
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…
- ADCI - Karnataka Software Engineer interview: four rounds in two daysADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026Offer
I applied through Amazon Careers without a referral. A recruiter reached out, then I completed an OA. About a month later, I was scheduled for four rounds across two days. The pace was intense. Each interview included 30 minutes of behavioral discussion and 30 minutes of coding. Coding and system-design content were spread across the four interviews, while the overall format stayed consistent fro…
- ADCI - Karnataka Software Engineer interview: four-round design loopADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026
After I cleared the online assessment, I entered the Amazon loop. It had four rounds: two coding interviews, a behavioral interview focused heavily on Amazon Leadership Principles, and a final hiring-manager round that combined coding with high-level design. The first coding round had two LeetCode medium problems. The second moved to a hard problem, with the same expectation that I write clean co…
- ADCI - Karnataka Software Engineer interview: OA and leadership principlesADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026
My process started with an online assessment, and it took a long time before I even reached the interview stages. After the OA, I had two interviews, each about 60 minutes. Across the process, I heard that both LeetCode-style problems and leadership principles were part of the evaluation. That meant my prep could not just be DSA. I also had to have specific stories ready for leadership-principle…
- ADCI - Karnataka Software Engineer silicon-team domain, design, and C roundsADCI - Karnataka · Software Engineer · Technical Screen · Jun 2026
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…
- ADCI - Karnataka Software Engineer technical phone screen before loopADCI - Karnataka · Software Engineer · Technical Screen · Jun 2026
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.…
- Addepar Software Engineer Interview Experience: Positive feedback followed by silenceA A Addepar · Software Engineer · Technical Screen · Jun 2026Rejected
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…
- ADP Account Executive interview experience: VP conversation and field shadowingADP · Account Executive · Jun 2026
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…
- ADP Software Engineer interview: project depth, Java ecosystem questions, and a final HR checkADP · Software Engineer · Technical Screen · Jun 2026
The interview process felt organized and quick, beginning with a large pool. Roughly fifty students were shortlisted, then the process moved through three stages. In the first technical round, I leaned heavily on my resume because the discussion focused on projects, including architecture choices and implementation details. Near the end, the interviewer moved to core DSA, especially searching and…
- AI-Assisted ML Round, Rejected on Level CalibrationMicrosoft · Data Scientist · Senior+ · Onsite · Jun 2026Rejected
Background: about 4 years of YOE, full-stack DS at a startup. Timeline: Cold apply → recruiter reach out: 9 weeks Reach out → phone screen: 3 weeks Phone screen → onsite: 4 weeks (got the notice in the third week) Onsite → result: 5 weeks (I heard some people waited even longer) I'd long heard that Microsoft interviews move slowly, and now I've experienced it myself. Phone screen: resume walkthro…
- Air Liquide Home Healthcare Software Engineer electronics experience online interviewAir Liquide Home Healthcare · Software Engineer · Technical Screen · Jun 2026Offer
My first step was an online interview that felt comfortable and smooth. The interviewer asked about my technical knowledge and my experience in electronics. It was not confrontational or excessively technical. It felt like a conversation about how I thought and what I had done. The interviewer also helped me understand the role and how my background could translate into contributions at the compa…
- AKUNA CAPITAL Quantitative Analyst interview experience: math video and coding screenAKUNA CAPITAL · Quantitative Analyst · Online Assessment · Jun 2026Rejected
My run began with an online assessment and video interview, then moved into a more interactive technical round. During the video step, I answered math and probability questions and had to explain how I reached each solution. It was not enough to give an answer. I needed to make my reasoning clear. The technical round included coding-related questions and a couple that connected to my resume. The…
- AKUNA CAPITAL Quantitative Analyst interview with quant-style math testingAKUNA CAPITAL · Quantitative Analyst · Online Assessment · Jun 2026
My process started with the usual screening and assessments, then moved into online testing that leaned heavily on quant style math. I reached the later stages, including a final technical evaluation. The last question was the one that tripped me up. I couldn't land the final step cleanly, and I couldn't tell whether that meant I was done entirely or whether there was any behavioral wrap-up after…
- AKUNA CAPITAL Quantitative Analyst interview with two hour-long probability roundsAKUNA CAPITAL · Quantitative Analyst · Online Assessment · Jun 2026
I went through an assessment-heavy process in which the later rounds shifted from coding toward deeper probability. After passing the earlier online steps, I reached a technical screen focused on probability and statistics. It was genuinely hard and reminded me of the tougher Greenbook-style questions people mention for quant research. As I progressed, the final interviews focused almost entirely…
- AkunaCapital Quantitative Analyst interview experience: probability screen after timed assessmentsAkunaCapital · Quantitative Analyst · Online Assessment · Jun 2026Rejected
My process had several online stages before I spoke with anyone live. The assessment setup combined coding with a video interview, where I worked through math and probability questions while explaining my reasoning. The timing was tight enough that I had to be deliberate, though it felt relevant to the work expected of a quantitative researcher. After those assessments, I had a technical screen c…
- ALTEN Belgium Software Engineer army-mission mismatch and no follow-upALTEN Belgium · Software Engineer · Jun 2026Withdrew
I did not get far at first because my context did not match what was available. After I applied, the only missions offered were related to the army, and I chose not to continue beyond that initial stage. Later, I did have a phone interview about my professional project and goals, so there was an effort to understand where I was coming from. Afterward, I was told they would get back to me when a s…
- Amazon Account Executive interview experience: unannounced Excel taskAmazon · Account Executive · Jun 2026
A recruiter contacted me about a different account-management role. The email said the interview would be competency based and focused on Amazon Leadership Principles. There was not supposed to be an HR prescreen, and the confirmation did not suggest a complicated set of materials. On the day, the format changed in a frustrating way. I was suddenly given an Excel-sheet task without advance notice…
- Amazon Advertising Software Engineer Interview Experience: four demanding loop roundsAmazon Advertising · Software Engineer · Online Assessment · Jun 2026
The process started with an online assessment and moved into four rounds: coding, deeper technical design, Leadership Principles, and another design round. The coding interview had two DSA problems, one medium and one hard. I had to solve them optimally, explain my approach, cover time and space complexity, edge cases, optimizations, alternatives, and trade offs. The design work covered an Amazon…
- Amazon Advertising Software Engineer interview: video-supported online testAmazon Advertising · Software Engineer · Technical Screen · Jun 2026
I started with recruiter outreach and an initial online step. The assessment used video support and examples of the reasoning and approach they wanted, so it felt less about memorization than about how I structured my thinking. After I cleared it, I had short, focused technical interviews before the final round was scheduled. Later conversations explicitly covered networking, troubleshooting, aut…
- Amazon Business Analyst interview experience: expected SQL that never cameAmazon · Business Analyst · Jun 2026Rejected
The process initially sounded as if it would cover SQL and behavioral topics. Once the interview started, however, it stayed entirely behavioral and scenario based. I expected a live SQL assessment, but it never materialized. Communication afterward was poor. The recruiter did not reply to my follow-up emails, and an automated rejection notice arrived a couple of days later. The interview itself…
