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

AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: technical and leadership rounds

My process had multiple technical rounds and a couple of structured behavioral rounds. One technical conversation mixed troubleshooting with leadership themes such as Bias for Action and GenAI fluency, so it was not solely about writing code. Another technical round focused more directly on coding problems. The hiring-manager round covered leadership principles including Earn Trust, Learn and Be…

Other0
AmazonTechnical Program Manager
Reported Jul 2026

Amazon Technical Program Manager interview: scheduling fell apart

The process began smoothly but ended inconsistently. I had a recruiter phone screen to check cultural fit and whether the role matched my background. The planned next step was a loop of four or five interviewers using cases connected to Amazon Leadership Principles. In practice, communication was where it broke down. After recruiter contact, I did not hear about scheduling for some time and event…

RejectedHR Screen0
Zoom CommunicationsSoftware Engineer
Reported Jul 2026

Zoom Communications Software Engineer interview: three months without closure

The process lasted roughly three months and began to feel inconsiderate of my time. After the recruiter touchpoint, I went through several steps that kept being moved ahead, including a presentation that required real preparation and a VP interview. The conversations felt positive, but the gaps grew harder to tolerate and recruiters became difficult to reach. I had a strong VP call. They told me…

No responseHR Screen0
ABBSoftware Engineer
Reported Jul 2026

ABB Software Engineer interview: fundamentals and a difficult final round

The process started with a familiar technical sequence but became a test of both fundamentals and performance under pressure. I faced medium-level data-structures and algorithms questions, plus computer-networks and operating-systems topics with a clear cybersecurity-basics tilt. There was also a group discussion, which made it feel less like a one-shot evaluation and more like an assessment of h…

RejectedOther0
ABBSoftware Engineer
Reported Jul 2026

ABB Software Engineer interview: one quick behavioral conversation

I had one behavioral interview that lasted about half an hour, followed by a short wait while they followed up. Things moved quickly once the interview ended: an offer arrived roughly 15 minutes later. There was plenty of time for questions during the conversation, and I appreciated being able to ask and clarify things. It was a very good experience. The quick, conversational format made it easie…

OfferOther0
YASH TechnologiesConsultant
Reported Jul 2026

YASH Technologies Consultant interview: SAP MM process flow

The interview was calm, and the main thing I remember was one significant technical question about business processes and the SAP MM module. The interviewer wanted me to explain the business process first, then connect that understanding to the relevant T-codes. It was a focused conversation rather than a broad grilling. The structure of the question made me feel that they were checking whether I…

OfferOther0
WSPSoftware Engineer
Reported Jul 2026

WSP Software Engineer interview: timed video assessments

My process began with a video interview and quickly moved to assessments. In a HireVue-style format, I recorded webcam responses to prerecorded questions. Each prompt allowed a short preparation window before a timed answer. The questions covered behavioral experience, motivation for the role, and interest in the energy sector. There was also a test-like cognitive component with timed numerical,…

Online Assessment0
Oracle HealthAccount Executive
Reported Jul 2026

Oracle Health Account Executive interview: brief and unresolved

I began with a short HR interview of about 10 to 15 minutes, and it went smoothly. The recruiter gave me positive feedback, so I was surprised to be rejected later. A follow-up email also received no response. It was a brief experience with a friendly tone at the start, but the later silence left it feeling incomplete. The biggest surprise was how quickly it ended despite the initial positivity.…

RejectedHR Screen0
Oracle HealthSoftware Engineer
Reported Jul 2026

Oracle Health Software Engineer interview: LRU cache under pressure

My interview loop was tougher than I expected, although the overall tone was engaging. Across several technical rounds, I implemented an LRU cache and solved a course-prerequisite-ordering problem. The pace kept me on my toes and made it hard to relax into the problems. The last round became more intense with an optimization-style challenge: maximizing the container area between vertical lines. I…

OfferTechnical Screen0
Tata Consultancy Services (North America)Software Engineer
Reported Jul 2026

Tata Consultancy Services (North America) Software Engineer interview: NQT fundamentals

After clearing the online NQT, I was invited to a combined technical, managerial, and HR interview. The NQT included aptitude, logical reasoning, verbal ability, and coding. In the interview, the panel checked what I had put on my resume and connected it to core computer-science fundamentals. The technical discussion covered data structures and algorithms, DBMS, OOPs, and operating systems. I als…

OfferOnline Assessment0
RipplingSoftware Engineer
Reported Jul 2026

Rippling Software Engineer interview: a dismissive phone screen

I applied online, and a recruiter contacted me a couple of weeks later to arrange a technical phone screen. The process went badly quickly because the interviewer seemed disengaged from the start. I was interrupted almost immediately during my introduction and could not finish it. The interviewer moved to the coding question and kept their camera off for most of the session. I still solved the pr…

RejectedTechnical Screen0
Micro1Software Engineer
Reported Jul 2026

Micro1 Software Engineer interview: AI assessment instability

My interview opened with an AI-driven conversational segment before moving into technical tasks. It felt more like an assessment than a human conversation. The sections tested whether I could reason clearly, explain tradeoffs, write code, and debug under time pressure. I worked through live coding and debugging, code-optimization tasks, and API questions. The questions were not vague in the way s…

Other0
MD Anderson Cancer CenterResearch Analyst
Reported Jul 2026

MD Anderson Cancer Center Research Analyst interview: team presentation

I started with a recruiter-style call that covered basic background questions. Then I had a technical-light Zoom interview with the whole team. The format was simple: everyone joined the call, I gave a presentation of about ten minutes, and they asked follow-up questions about my experience instead of pushing into deep technical problem solving. I was surprised by how few technical questions ther…

HR Screen0
LyftData Scientist
Reported Jul 2026

Lyft Data Scientist interview: probability to causal modeling

I began with a recruiter screen of about 30 minutes. It was structured: they checked the basic boxes and explained what would happen next. The process then moved through a general data-science screen on probability, A/B testing, and business sense, followed by four deeper technical rounds. Those covered coding and algorithms, optimization, causal modeling, and business acumen tied back to product…

HR Screen0
Lockheed MartinSoftware Engineer
Reported Jul 2026

Lockheed Martin Software Engineer interview: conversational STAR format

The interview felt more like an extended conversation than a strict test. It was virtual and conversational throughout, with technical leaders asking about my experience and following with situational behavioral questions. They also asked object-oriented-programming questions, and I used STAR to organize my answers. It began with the usual "tell me about yourself," then they described the role to…

Other0
Lockheed MartinSoftware Engineer
Reported Jul 2026

Lockheed Martin Software Engineer interview: STAR and LQR

After applying, I followed a familiar structured path: a recruiter-style step and then a standard virtual interview with several behavioral questions and one technical prompt. The process was tightly schedule-driven through email invitations, and the interview questions closely matched what had been described publicly. I answered a full set of STAR-based behavioral questions and one technical que…

OfferHR Screen0
InstacartData Scientist
Reported Jul 2026

Instacart Data Scientist interview: case study and SQL screen

One part of my process felt light technically for how long it took. After a recruiter-style step, I completed a live case study that lasted 1.5 hours. I used Python, or another tool of my choice, for the main technical task. The case study took up most of the time; I also gave a presentation and answered questions from people presented as stakeholders. In a separate recruiter-to-tech-screen path,…

Technical Screen0
CapgeminiConsultant
Reported Jul 2026

Capgemini Consultant interview: pharmaceutical validation scenarios

I had a demanding, consulting-style process with two face-to-face rounds. Both interviewers were professional and interactive. They concentrated on technical expertise, problem solving, and my real project experience, going deep into the role instead of staying theoretical. The part I remember most was the scenario discussion around pharmaceutical validation and digital quality systems. They aske…

OfferOther0
AstraZenecaResearch Scientist
Reported Jul 2026

AstraZeneca Research Scientist interview: five rounds in China

I went through a structured five-round process. It started with a recruiter screen with HR, conducted in Chinese because the role was based in China. About a week later, I had an informal 30-minute conversation with the hiring manager that felt more like a chat than an interrogation. The next panel round had me present a past project and answer questions from people who seemed to represent my pot…

OfferHR Screen0
AppleMachine Learning Engineer
Reported Jul 2026

Apple Machine Learning Engineer interview: smooth and rushed flows

My smoother interviews began with a technical phone screen, then a comfortable, practical DSA-style round. It included a regression-model critique and a subset-sum-style problem. I had recently worked through similar problems, so those patterns were already familiar. I then had a codebase-style evaluation around PDF evaluation logic. The structure felt familiar because I had previously reviewed t…

OfferTechnical 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