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

SupermicroSoftware Engineer
Reported Jul 2026

Supermicro Software Engineer interview: delayed OA-to-onsite process

After my initial OA, I waited a long time before hearing about an in-person onsite. Once the onsite finally happened, the later stages were a short back-to-back sequence with SWE rounds and a managerial discussion. The application kept moving slowly, and HR was not consistently responsive. Even when I followed up, replies arrived late. That uneven communication affected my confidence more than th…

RejectedOnline Assessment0
VoleonSoftware Engineer
Reported Jul 2026

Voleon Software Engineer interview: four-part virtual onsite pressure

After a recruiter screen, I had a technical screen about a week later and then a four-part virtual onsite. The pace was fast for such a heavy process. The most intense piece was a two-hour coding session with several parts, framed as real-world problems rather than one tidy exercise. The loop focused on hard LeetCode-style coding. Even the system-design portion felt algorithmic and exercise-like.…

RejectedTechnical Screen0
TripadvisorSoftware Engineer
Reported Jul 2026

Tripadvisor Software Engineer interview: coding, design, and culture rounds

The Tripadvisor loop began with HR covering my background and fit, with a few quick basic technical checks. The next technical screen included an easy LeetCode-style question, OOP and data-structure discussion, and an open-ended technical problem. Later coding rounds had two LeetCode questions and discussion of time and space complexity. The last technical round combined another LeetCode problem…

Technical Screen0
Walmart de México y CentroaméricaAccount Executive
Reported Jul 2026

Walmart de México y Centroamérica Account Executive interview: store conversations and customer scenarios

Things usually moved quickly after I applied online. A recruiter or HR call would arrange an interview, which was brief and conversational. I spoke with someone from the store or hiring team about why I wanted to work there, how I'd handle customer-service situations, my availability and whether I could do the required tasks. The usual format was a phone or virtual screen followed by an in-person…

Other0
AMDProject Manager
Reported Jul 2026

AMD Project Manager interview: Agile and team-dynamics discussion

After a recruiter conversation, I met with two team leads and then had a second round with a senior manager. The tone was friendly and easygoing, so the process felt more like a conversation than a test. Most questions concerned my past experience and behavioral situations, especially how I would handle team dynamics when things were not working smoothly. Agile and Scrum terminology came up repea…

Other0
AccentureSoftware Engineer
Reported Jul 2026

Accenture Software Engineer interview: Python, HTTP, and compensation tradeoff

Accenture sent me an online coding task, followed by a technical interview with two people and then HR. After the HR conversation, I received an offer. The technical round was polite and calm. We discussed my current project, general software engineering, Python, and HTTP concepts, then did a short live-coding segment. The interviewers were helpful while I worked, and the questions felt relevant…

OfferOnline Assessment0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: four friendly interviews over two days

I completed four friendly Amazon interviews, each about an hour, over two days. The questions covered system design, LeetCode-style coding, behavioral topics, and my use of AI. The loop was long but not especially difficult. Because the tone stayed approachable, I could focus on explaining my thought process instead of only racing to write code. I left with a clearer sense of the balance they wan…

Technical Screen0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: technical assessment and team rounds

I applied online, completed a technical assessment, and then had a couple of interviews with people from the team I would work with. The process was simple and team aligned rather than chaotic. It had multiple rounds but did not feel like a prolonged gauntlet. The difficulty was easy, and it felt more like a check of fit and baseline skills than a difficult hiring process. Location: South Africa.…

OfferOnline Assessment0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: Two Sum and substring offer

I received an OA with two DSA questions and behavioral questions. I then had one interview with two more DSA questions at easy to easy-medium difficulty: Two Sum and longest substring without repeating characters. The interview followed the same basic DSA pattern as the assessment, and the two questions were the kind of fundamentals I could work through directly. The process moved quickly and fel…

OfferOnline Assessment0
Western DigitalSoftware Engineer
Reported Jul 2026

Western Digital Software Engineer interview: staff-level leadership assessment

After a recruiter call, I spoke with a hiring manager or tech-lead-style interviewer about past projects and a high-level architecture scenario. The questions pressed on what I had built, the tradeoffs behind my decisions, and how I reasoned about technical direction. Later rounds focused on staff-level scope: quantifiable outcomes, ambiguity, communication, and cross-functional influence without…

OfferTechnical Screen0
ScotiabankSoftware Engineer
Reported Jul 2026

Scotiabank Software Engineer interview: late start and unclear Python exercise

I joined the Scotiabank interview five minutes early, but the main interviewer arrived about 20 minutes late. Once it began, I gave detailed answers and explained the business reasons behind choices in my past projects. I felt some answers were judged through assumptions that did not match the context I was trying to clarify. I was also frustrated by the implication that I relied on AI tools, bec…

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

Tata Consultancy Services (North America) Software Engineer interview: basics to HR

The technical portion was manageable and covered string manipulation, arrays, and regex. It felt focused on practical fundamentals rather than obscure material. The second round was HR, including salary discussion. We reached agreement and I was selected. In another part of the process, I saw the same practical approach: OOP, DBMS, JavaScript, a couple of SQL queries, DSA exercises such as Fibona…

OfferTechnical Screen0
ShopifyData Scientist
Reported Jul 2026

Shopify Data Scientist interview: guided SQL and Python screening

About a week after I applied, HR contacted me. The first interview lasted 30 minutes and covered behavior, background, experience, and fit. Soon after, I had a one-hour technical screen with a team member split between SQL and Python. Before each round, Shopify sent a detailed PDF guide. That made preparation feel less like guessing because I knew what they were measuring. The recruiter also expl…

Technical Screen0
Micro1Software Engineer
Reported Jul 2026

Micro1 Software Engineer interview: backend and database depth

The Micro1 interview began with React and Node.js fundamentals, then quickly moved into practical backend topics: worker threads, task processing, queues and message services, and using idempotency to make operations safe and repeatable. The discussion continued into distributed systems and PostgreSQL internals, including transactions, isolation levels, concurrency control, query optimization, an…

Technical Screen0
IBMSoftware Engineer
Reported Jul 2026

IBM Software Engineer interview: campus shortlists and interrupted interview

My IBM process began with an on-campus assessment that combined multiple-choice questions and coding. Only a limited number of students were shortlisted. The technical interview took a fixed hour block and went well enough that the interviewer gave positive feedback. Afterward, HR announced names for the next stage in waves. When my name was not in the first list, I assumed I had been rejected. I…

RejectedOnline Assessment0
Hewlett Packard Enterprise | HPESoftware Engineer
Reported Jul 2026

Hewlett Packard Enterprise | HPE Software Engineer interview: rounds then hold

A recruiter called to schedule an open position, and the Hewlett Packard Enterprise process expanded into around four virtual rounds plus an onsite at an office. Each stage emphasized deep technical work. The questions were mostly DSA coding, with operating systems and computer networking mixed in. Later interviews pushed further into technical depth and topics tied to the job description. After…

Onsite0
CapgeminiConsultant
Reported Jul 2026

Capgemini Consultant interview: SAP TRM and HR practicalities

After a recruiter stage, I had a technical screen followed by HR. The technical discussion focused on SAP TRM, its related business process, and questions about payments and repayments. The interviewer wanted to know whether my prior experience mapped to that module. The next conversation was resume driven and calmer. It included aptitude and logical-reasoning work with many memory-style question…

Technical Screen0
NVIDIASoftware Engineer
Reported Jul 2026

NVIDIA Software Engineer interview: practical problems and delayed rejection

After an online assessment, I had interactive technical interviews where I was expected to explain my approach, not only reach an answer. One session began with a review of my resume projects and a couple of behavioral questions, then moved to a problem that felt like a realistic day-to-day task for the role. The interviewers were generally straightforward, and I appreciated their focus on fit ra…

RejectedOnline Assessment0
NVIDIASolutions Architect
Reported Jul 2026

NVIDIA Solutions Architect interview: EVPN shifted to DevOps

The NVIDIA interview opened with EVPN questions, which I answered confidently. It then shifted almost entirely to DevOps, a direction I did not expect for a Solutions Architect position. Nothing in the rest of the conversation connected to my AI or HPC background. By the end of the call, I felt that much of the questioning did not match the advertised role. I did not receive an offer. My main tak…

Technical Screen0
AutodeskSoftware Engineer
Reported Jul 2026

Autodesk Software Engineer interview: full-stack development and agentic AI deep dives

The hardest round for me involved designing a full-stack web application in React and Node.js. I had to write frontend and backend code and cover API design in about two hours. Everything felt tightly timed. Coordinating the architecture from end to end added to the pressure of writing the code. Another technical session lasted three hours. The first half was technical and the second was behavior…

RejectedTechnical 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