Interview Experiences

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

Share yours, earn XP

4514 stories

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

Advanced Micro DevicesSoftware Engineer
Reported Jul 2026

Advanced Micro Devices Software Engineer interview: technical panels and C++ STL

The first conversation was a quick discussion with the hiring manager about my day-to-day experience and previous work. From there, I moved into technical panels with several interviewers evaluating me at once. They asked about both problem solving and technical depth, and seemed interested in how I reasoned through a question. The panels included medium LeetCode-style problems and more logic-hea…

Technical Screen0
Amazon DSPSoftware Engineer
Reported Jul 2026

Amazon DSP Software Engineer interview

The process started with an online assessment containing two coding problems and multiple test cases. I passed some cases right away and did better on the second problem. Then I had two coding rounds: graphs and arrays in one, linked lists and binary search trees in the other. There was also a behavioral section on situations and workplace fit, spread across multiple rounds over a couple of days.…

Online Assessment0
AMD Construction GroupSoftware Engineer
Reported Jul 2026

AMD Construction Group Software Engineer interview

I first spoke with the hiring manager about the team and my day-to-day work in earlier roles. The rest of the process was several technical panels, with scenario-based questions that tested both problem solving and technical range. The panels covered computer architecture, UART, SPI, I2C, AXI, APB, AHB, coverage, assertions, UVM fundamentals, debugging, and verification strategy. One round also t…

Technical Screen0
LTMSoftware Engineer
Reported Jul 2026

LTM Software Engineer interview

After a recruiter call, I had a technical screen built around a coding and design prompt. I needed to create an API that returned a transaction identifier, then explain API versioning and exception handling. The follow-ups covered real microservice implementation and the tradeoffs among batch processing, messaging queues, and event-driven approaches. They also asked about Google Cloud Storage, Bi…

Technical Screen0
ALSTOMSoftware Engineer
Reported Jul 2026

ALSTOM Software Engineer interview

After I cleared the first technical screening, things moved quickly. The test produced a very large shortlist, and I was invited to an in-person group discussion on online versus traditional education. In that setting, they seemed to be watching how I reasoned and communicated. The technical interview lasted about half an hour. I began with my projects, then answered basic questions tied to what…

OfferTechnical Screen0
IntelSoftware Engineer
Reported Jul 2026

Intel Software Engineer interview

My interview focused on digital electronics. We covered Verilog and CMOS fundamentals, then moved to RTL design and questions meant to test how I reasoned through engineering tradeoffs. The interviewers were professional and mixed conceptual questions with coding and circuit-design problems. They were looking beyond recall: whether I could reason from fundamentals into an implementation and conti…

Technical Screen0
Stellantis Financial Services UsSoftware Engineer
Reported Jul 2026

Stellantis Financial Services Us Software Engineer interview

I began with a short phone call about why Stellantis and why the role suited me. It was the usual walk-me-through-yourself and fit discussion. About a week later, I had a Teams interview. It was one behavioral session with a couple of targeted questions, followed mostly by a normal conversation. I used STAR to organize my examples, and the tone stayed easygoing and low-stress. There were no surpr…

Technical Screen0
StellantisSoftware Engineer
Reported Jul 2026

Stellantis Software Engineer interview

The recruiter first called to ask why I wanted Stellantis and why I thought I fit. Soon after, I had a Teams interview. It was mostly behavioral, and I used STAR to keep my answers organized, but the exchange did not feel like an interrogation. The 30-minute virtual interview was a small panel of engineers, with no HR present. They asked a few pointed questions and talked through examples from my…

Technical Screen0
Super Micro ComputerSoftware Engineer
Reported Jul 2026

Super Micro Computer Software Engineer interview: a large project with about an hour to work

After the early screening and assessment, the process became a run of back-to-back rounds that mixed behavioral and technical questions. It felt harsher than the interviews I was used to. They gave about an hour for a large project, which felt more like a stress test than a normal interview. I had to work through DSA problems while also talking about design. System design became important late in…

Online Assessment0
TeslaSoftware Engineer
Reported Jul 2026

Tesla Software Engineer interview

Two technical managers interviewed me, and the conversation became intense right away. They asked about my motivation as well as technical and behavioral topics. One technical question concerned a motor module and required more rigor than I expected. The behavioral questions asked how I would handle production-engineering difficulties, when problems stack up and work still has to ship. I found th…

Technical Screen0
SupermicroSoftware Engineer
Reported Jul 2026

Supermicro Software Engineer interview: strings, priority queues and object-oriented design

This was a multi-round loop with an Amazon-style level of intensity. Behavioral and technical questions were mixed together, and the bar felt high. One round probed leadership, while another used more conventional interview topics. I saw strings, priority queues, and object-oriented design, plus a round that was entirely behavioral. The time pressure made the whole thing feel like a test of wheth…

Technical Screen0
Walmart LabsSoftware Engineer
Reported Jul 2026

Walmart Labs Software Engineer interview: compact technical rounds and backend stack discussion

After recruiter-style contact, I entered a compact technical process that felt straightforward and clearly structured. The setup was about 30 minutes for a sequence of technical rounds, with a LeetCode-style problem as the main expectation. Between questions, I was also asked about my work history, resume, and how it mapped to my tech stack, including Kafka, Kubernetes, and Java Spring Boot. The…

0
Walmart de México y CentroaméricaSoftware Engineer
Reported Jul 2026

Walmart de México y Centroamérica Software Engineer interview: conversational live coding

I started with a recruiter screen and then, about a week later, had a structured, recruiter-friendly technical interview. The technical session was divided into a few rounds, and each interviewer explained the plan upfront. I completed LeetCode-style coding and also talked through my background, resume, and the tech stack I had used in past work. Kafka and Kubernetes came up naturally while we di…

0
AdobeAccount Executive
Reported Jul 2026

Adobe Account Executive interview: supportive first round followed by radio silence

The process felt normal and contained, with about three rounds. It began with a recruiter conversation, then a task, and finally a meeting with the hiring manager. Communication ran smoothly at first, and the recruiter was especially supportive. I received helpful, actionable feedback instead of vague notes. After the first round, the experience did not continue that way. I got nothing back. Ther…

No response0
WatersSoftware Engineer
Reported Jul 2026

Waters Software Engineer interview: selective full-stack and SQL assessment pipeline

I went through the more intense, high-volume track. It began with an online assessment containing 20 multiple-choice questions on full-stack topics and SQL. After that came a group discussion, and the numbers made the process feel very competitive. After the applications and screening, 30 people were shortlisted for the next step. From there, 12 reached a stage where the process continued far eno…

Online Assessment0
Walmart Supply ChainSoftware Engineer
Reported Jul 2026

Walmart Supply Chain Software Engineer interview: coding rounds and backend stack discussion

The process felt structured and efficient. After the initial tech-focused intake, I had a roughly 30-minute technical assessment spread across three rounds. Each round was essentially a LeetCode-style coding challenge, and the interviewers were attentive and clear. I also talked through my background, resume, and the tech stack listed there. Kafka and Kubernetes came up along with Java and Spring…

0
Zensar TechnologiesSoftware Engineer
Reported Jul 2026

Zensar Technologies Software Engineer interview: campus assessment, interview, and HR

The process began on campus and had two parts: an online assessment, followed by an interview and an HR round. It felt straightforward to moderately challenging. Nothing was especially punishing, but it was not completely trivial either. The interview followed the assessment, and the HR conversation was the final step. My impression was that the process was structured and kept moving. I did not f…

OfferOnline Assessment0
WixSoftware Engineer
Reported Jul 2026

Wix Software Engineer interview: timed LeetCode exam and system design follow-up

I went through a tight technical process that began with an onsite LeetCode-style exam. It lasted about two hours and included a warmup plus easy, medium, and hard questions. The structure matched what I had been told to prepare for. I did not feel rushed when I finished, but the main challenge was getting the medium and hard questions right under the clock. After the exam, I interviewed with dev…

Onsite0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: a high-pressure technical and behavioral process

The interview process felt intentionally intense and streamlined, but still brutal. It mixed behavioral and technical questions with artificial time pressure, like being given something massive to complete in about an hour as a deliberate stress test. It seemed designed to see whether I would break under constraints, and it matched what I had heard about high-attrition hiring models at companies…

0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: four-round onsite loop with bar raiser

I went through a four-round loop spread across two onsite rounds. Each interview mixed behavioral questions with a technical segment, except for one that was behavioral-only. The technical topics included strings, priority queues, and object-oriented design. A bar-raiser-style round was part of the loop and felt notably harder than the others. Even with the mix of topics, the structure was consis…

Onsite0

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