Interview Experiences

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

Share yours, earn XP

4433 stories

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

ShopeeData Analyst
Reported Jul 2026

Shopee Data Analyst interview: delayed and cancelled process

My experience began badly with inconsistent communication. I completed the first stage in early July and was told I would hear back in two days, but the response did not arrive until the end of the month. An automated WhatsApp message said I had advanced and asked whether I wanted to continue. I confirmed, waited another two days for a form, and then heard nothing for a week. When they eventually…

0
VisaSoftware Engineer
Reported Jul 2026

Visa Software Engineer interview: short Java and algorithms round

My Visa interview lasted about 30 minutes and moved quickly. I began with a coding question and had around five minutes to produce a solution. That was followed by a logical puzzle. The interviewer then tested object-oriented programming and Java fundamentals, including implementing inheritance. The last part was a binary-search problem: I started with a brute-force approach, explained how I woul…

Other0
Amazon Web ServicesSoftware Engineer
Reported Jul 2026

Amazon Web Services Software Engineer interview: LLD and GenAI onsite loop

After the OA, I reached four onsite rounds. The first focused on LLD, and later technical rounds combined coding with Leadership Principle questions. One later round added a GenAI component alongside another LeetCode-style coding question. The demanding part was switching among lower-level design, coding, and leadership discussion. The LeetCode questions felt medium overall, but the range of desi…

Online Assessment0
AirbusSoftware Engineer
Reported Jul 2026

Airbus Software Engineer interview: CV-led technical process

The early interviews were tied closely to my CV. The first technical conversation covered my background and fundamentals. A follow-up included Python and algorithms before going deeper into projects I had listed, and the last HR discussion asked about strengths and weaknesses. I was not asked to code live, but I had to explain my background in detail. The panel divided the questions so that each…

HR Screen0
XylemSoftware Engineer
Reported Jul 2026

Xylem Software Engineer interview: fundamentals under pressure

The interview was hard and highly conceptual. I had to think deeply instead of reciting facts, and vague answers were not enough. They wanted precise answers grounded in fundamentals. I do not remember a long, step-by-step sequence of stages. What I do remember is that the difficulty stayed consistent: conceptual depth mattered more than quick problem-solving tricks. I did not receive an offer. L…

0
University College LondonResearch Analyst
Reported Jul 2026

University College London Research Analyst interview: research presentation panel

This interview felt heavier than the others because it added a short presentation to a formal panel. Before the main discussion, I prepared and gave a 5 to 10 minute talk on my previous research, then proposed a protocol or approach for a technique used in the lab. The panel moved straight from that presentation into probing questions. Each panel member asked background and competency questions,…

Other0
ScotiabankFinancial Analyst
Reported Jul 2026

Scotiabank Financial Analyst interview: Superday valuation questions

The process felt more like interview school than a casual screen. The first round combined behavioral and technical questions, and the Superday was a series of short back-to-back conversations. Some interviewers wanted role-specific technical knowledge while others stayed behavioral, but all of it tested whether I understood the market instead of just definitions. I was pushed on a stock pitch, i…

Other0
SAPConsultant
Reported Jul 2026

SAP Consultant interview: Teams lag during video interview

The recruiter call went well, then I moved to a video interview on MS Teams. That conversation was frustrating because it lagged noticeably. I had not experienced that kind of Teams lag in interviews before, and it threw me off because my camera and connection worked fine in another meeting shortly afterward. The only explanation I could think of was that the HR interviewer and I were in differen…

HR Screen0
DoorDashData Scientist
Reported Jul 2026

DoorDash Data Scientist interview: take-home after manager screen

I had a quick phone screen and then a Zoom meeting with the hiring manager that lasted about 30 minutes. After that, I completed a take-home assignment and submitted it within 72 hours. That was the end of the process for me. My submission did not move forward, and I did not get another live round. The path looked straightforward on paper, but it was still frustrating because all of my momentum r…

RejectedHR Screen0
CiscoSoftware Engineer
Reported Jul 2026

Cisco Software Engineer interview: networking OA cutoff

The process began with an online assessment, and the later interview path depended on that result. For me, the OA was the gate. I solved some questions, but my overall performance was not strong enough to continue. There was no detailed technical follow-up afterward, only the sense that the feedback did not support moving forward. The assessment covered networking and C fundamentals: subnetting,…

Online Assessment0
AppleSoftware Engineer
Reported Jul 2026

Apple Software Engineer interview: technical depth and uncomfortable tone

The overall cycle was technically heavy and thorough. I had multiple rounds with mostly professional, fair questions about heat transfer, fluid mechanics, and thermodynamics. I was expected to show understanding even when the questions became specific. Two rounds felt different. Those interviewers kept adding follow-ups until they found something I could not answer, and some questions required de…

Other0
MicrosoftSoftware Engineer
Reported Jul 2026

Microsoft Software Engineer interview: story-based medium-hard rounds

After clearing the OA, I had three technical rounds. The questions were story-based and ranged from medium to hard. Not every interviewer required me to fully execute code; some were more interested in whether I could explain an approach clearly. The interviews were demanding because I had to stay precise about both the algorithm and my reasoning while the conversation moved quickly. I was trying…

Online Assessment0
Airbus AmericasSoftware Engineer
Reported Jul 2026

Airbus Americas Software Engineer interview: bilingual fit discussion

One session combined HR and a developer in the same block. The questions were general, with no technical assessment, and the conversation switched languages: French first, then English. The wait afterward stretched for a long time, which I assumed was connected to security and background checks. Earlier in the process, I had another interview that was more relaxed and discussion-based. It did not…

HR Screen0
Airbus Americas Customer ServicesSoftware Engineer
Reported Jul 2026

Airbus Americas Customer Services Software Engineer interview: motivation and wait

The process began with a quick initial call about the company and my motivation. It also covered why I wanted to work in Spain, so the location question was specific rather than generic. Then I met with a manager and HR in a fairly classic format: discussion of my profile and CV, motivations, and a mix of technical and personal-fit themes depending on what they wanted to explore. From the early v…

HR Screen0
Airbus Americas Customer ServicesSoftware Engineer
Reported Jul 2026

Airbus Americas Customer Services Software Engineer interview: CV and structures

The interviews leaned heavily on my CV. Two panelists divided the questions between them, and most of the conversation stayed close to my resume. They also tested basic fundamentals rather than advanced or unfamiliar material. A substantial part used scenarios involving aircraft structural concepts. It felt as though they wanted to know whether I understood the principles well enough to apply the…

Other0
Airbus GroupSoftware Engineer
Reported Jul 2026

Airbus Group Software Engineer interview: resume-based fundamentals

The panels worked closely from my resume. I spoke with two interviewers, each responsible for a defined set of questions. Some checked basic knowledge, while others probed the strength of my general engineering understanding. It was not a broad technical coding interview. Instead, the conversation was mostly about walking through my projects and discussing relevant fundamentals to confirm that my…

Other0
ASTEKSoftware Engineer
Reported Jul 2026

ASTEK Software Engineer interview: short, flexible, and responsive

The process felt very smooth and fairly short. Once I had been contacted and scheduled, I moved through the steps without waiting for weeks. I felt the team concentrated on the substance: getting to know me and seeing whether my profile fit the role. Their willingness to work around scheduling constraints also stood out. I did not feel there were an excessive number of stages. Communication was r…

Offer0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview: timed first stage

The process had three stages and moved quickly from the first assessment into a work-style component. The opening stage had two parts: a couple of timed coding questions and then a workstyle assessment. I did not finish that first stage, so the process stopped there. I had to solve two coding problems within their time windows. I felt I was managing my time, but still could not make enough progre…

RejectedOnline Assessment0
Bain &Consultant
Reported Jul 2026

Bain & Consultant interview: remote cases and in-person day

Once the earlier steps were over, the scheduling moved quickly. I had two case interviews remotely on the same day, which left little time to recover between them. Each case required me to stay structured while adapting to the interviewer's direction. Later I went in person for the next stage. That day included a case interview, a presentation, and a behavioral interview. The mix felt consistent…

Onsite0
Varroc GroupSoftware Engineer
Reported Jul 2026

Varroc Group Software Engineer interview: automotive fundamentals

After an assessment, I moved to a technical round and then an HR round. The technical discussion began with my resume and past work before moving into automotive fundamentals. I was asked about automotive protocols and the electronics concepts behind them, and the difficulty matched the average level they seemed to want. The HR conversation lasted around 15 minutes and acted as a short check-in a…

Technical Screen0

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