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

Super Micro ComputerSoftware Engineer
Reported Jul 2026

Super Micro Computer Software Engineer interview: streaming design and manager rounds

The process was simple in structure but hard in content. After initial setup, I had three rounds: a system-design interview followed by two managerial rounds. For system design, I was asked to design a streaming application like a major video platform. I had to explain how the system would work at scale and discuss architectural trade-offs. The later managerial discussions focused on how I work a…

RejectedTechnical Screen0
VeeamSoftware Engineer
Reported Jul 2026

Veeam Software Engineer interview: five rounds halted after hiring pause

I went through a longer process that was mostly standard in structure even as it dragged on. After a recruiter touchpoint, there were about five rounds: a coding-pad-style test, a hiring-manager conversation, technical interviews, and a system-design round. It seemed to be progressing in a controlled way, and I was told I had cleared every stage and could advance my candidacy. Then the momentum s…

Technical Screen0
U.S. BankFinancial Analyst
Reported Jul 2026

U.S. Bank Financial Analyst interview: simple rounds with unclear timing

The process started normally, but its pacing soon felt off. The interviews themselves were straightforward, yet I received little communication afterward. Things on their side felt rushed and not well organized, and I was left waiting even when I thought an interview had gone well. Another part of the journey became a longer sequence: phone screen, hiring-manager round, then a final conversation…

0
U.S. BancorpFinancial Analyst
Reported Jul 2026

U.S. Bancorp Financial Analyst interview: welcoming questions on finance and fit

I went through a straightforward, mostly people-focused sequence. The recruiter call covered what I wanted, my interests and their fit with the role, my real-estate and Excel experience, and the office I was targeting. Interviews with managers or team members remained welcoming. They asked about my background, teamwork, leadership, why I wanted the bank, and how I thought about the future. I also…

0
UCBResearch Scientist
Reported Jul 2026

UCB Research Scientist interview: long panel and late technology feedback

I went through several steps that ended with a long final panel. After two earlier rounds, I was invited to a face-to-face stage lasting roughly 3 to 4 hours. It began with a presentation, moved into Q&A, and involved discussions with about 10 interviewers. I was eager to meet the team and understand how the group worked, but the day took substantial time and preparation. The feedback afterward t…

Onsite0
UberSoftware Engineer
Reported Jul 2026

Uber Software Engineer interview: recursion, tree questions, and full onsite loop

After a recruiter conversation, I moved quickly into coding interviews. Across two interviews, I had two DSA problems: a recursion-based string-manipulation task and a tree question. Both came with follow-up extensions, so each session became a continuing problem-solving stretch rather than one fixed prompt. Later, I had a loop-style onsite day with all interviews on the same day. The interviewer…

Technical Screen0
TuringSoftware Engineer
Reported Jul 2026

Turing Software Engineer interview: HR conversation and escalating coding test

I started with an HR conversation centered on motivation, personality, and general questions about how I think and work. I then moved to the technical stage and completed coding exercises. The technical part was an online coding interview lasting about an hour. I received three questions and could choose among programming languages. The difficulty rose as the session continued, and the final ques…

HR Screen0
SupermicroSoftware Engineer
Reported Jul 2026

Supermicro Software Engineer interview: medium coding questions under pressure

My interview opened with a basic introduction and then went directly to two medium-level LeetCode questions. One was a balloon-bursting-style problem, and the other involved tree path sum. The difficulty felt easy, but I still choked during the session. There was little beyond the usual expectation that I reason through the approach and implement it. The larger problem was performing under pressu…

Technical Screen0
StrykerSoftware Engineer
Reported Jul 2026

Stryker Software Engineer interview: administrative talent call then manager video

My first step was a talent-acquisition phone call. It was not really technical. We covered administrative and logistical points such as role details, salary range, and similar practical checks. After that, I had a video technical interview with the manager. The tone did not work for me from the beginning. The early talent-scout call never explored my overall background or motivation; it stayed na…

Technical Screen0
YochanaSoftware Engineer
Reported Jul 2026

Yochana Software Engineer interview: late Teams interviewer and tense tone

My interview call was on Teams, and the tone felt off from the start. The interviewer joined late and then asked questions in an abrupt, almost machine-like way. I felt they were more interested in showing their own knowledge than evaluating how I solved the problem. When I could not answer one question immediately, the impatience was obvious. The interaction became colder, with an arrogant respo…

0
WorldQuantQuantitative Analyst
Reported Jul 2026

WorldQuant Quantitative Analyst interview: probability, math, and light coding

After recruiter outreach, I entered a straightforward early loop. I discussed previous work and what I would do in scenarios. The technical prompt was a live-coding-style question that felt fairly easy compared with what came later. Soon afterward, I completed an online round with math-focused, probability-style questions and some light coding. It was clearly about math and probability, but it di…

RejectedOnline Assessment0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: pressured DSA and leadership-principles loop

After the initial online assessment, I entered several technical interviews with a consistent structure: coding first, then strong pressure to connect my answers to Amazon Leadership Principles. The most intense round combined leadership-aligned evaluation with multiple DSA problems, turning it into a test of time and completeness rather than one neat solution. I also had a couple of medium codin…

Online Assessment0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: streaming-system design in a four-round loop

My interview journey was straightforward in how the rounds were organized. After the early steps, I entered a loop with four interviews, each about an hour. It began with a system-design conversation, and later rounds included manager-style discussion plus bar-raiser and behavioral evaluation. The design prompt was to build a streaming application like Netflix or Amazon Prime Video, so the discus…

Technical Screen0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: four-interview loop and leadership principles

I took an online assessment and, about a week later, had four interviews in a single day. The recruiter stayed responsive throughout, which helped me understand what each round would look like. The onsite loop ran back to back and followed the Amazon loop format closely. I had coding-and-judgment moments mixed with Leadership Principles. One round was more team or hiring-manager focused, while an…

OfferOnline Assessment0
TDSoftware Engineer
Reported Jul 2026

TD Software Engineer interview: in-person L1 and L2 process

I interviewed in person, which made the process feel more immediate than a remote screen. The timeline described L1 and L2 followed by a managerial or HR round. In L1, I had a Python coding question, discussed my current project in detail, and answered questions about AWS Cloud knowledge. The prompts tested both execution and context: code alongside how I had applied it. Managing timing was a lit…

Technical Screen0
ResmedSoftware Engineer
Reported Jul 2026

Resmed Software Engineer interview: unexpected Java and full-stack questions

My first technical round was supposed to be focused on data structures and algorithms, but it did not match that expectation once it began. Instead, the questions leaned strongly toward Java and full-stack topics. I was asked how to create scope in Java, what proxies are, and how to explain a multiton pattern with an example. The interviewer came across as rude, which made the round more stressfu…

Technical Screen0
NIKESoftware Engineer
Reported Jul 2026

NIKE Software Engineer interview: repeated follow-ups and hostile response

The process felt odd and frustrating from the start. I received a virtual interview call only after several follow-ups with HR, even though I had not been invited to an ongoing face-to-face hiring drive. After the interview, I contacted HR for an update and expected a normal status message. Instead, the response was essentially a demand that I stop texting. There was no clear closure, and that ho…

0
CiscoSoftware Engineer
Reported Jul 2026

Cisco Software Engineer interview: fair questions and disputed cheating concern

I entered the interviews confident because the questions matched my strengths: backend concepts, Java, system design, and coding. The interaction felt positive, and I believed I answered clearly. After the rejection, I spoke with HR to understand what happened. I learned that the interviewer thought I was looking at answers during the interview. That surprised me because I was not using anything…

RejectedTechnical Screen0
CiscoSoftware Engineer
Reported Jul 2026

Cisco Software Engineer interview: assessment followed by weeks of silence

My process began with a Hackerrank-style exam. It included several easy-to-medium LeetCode-style problems and a simple SQL question, so it felt manageable compared with harder online assessments I had heard about. After I finished, I heard nothing for weeks. The silence eventually ended without further progress, so the outcome felt less like the result of an interview conversation and more like a…

Online Assessment0
BrillioSoftware Engineer
Reported Jul 2026

Brillio Software Engineer interview: machine coding with immediate feedback

My first round was a machine-coding interview with a panel. The interviewers were polite and gave feedback immediately while I worked through the problems. They also asked a few theoretical questions alongside the coding. I explained fundamentals such as event-loop behavior and closures. The panel guided me through the discussion instead of simply throwing questions at me. It felt like an interac…

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