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

ZomatoSoftware Engineer
Reported Jul 2026

Zomato Software Engineer interview with paper coding

The Zomato process began with resume shortlisting and moved straight to technical interviews. The first technical round mixed DSA, CS fundamentals, puzzle-style questions, resume details, and basic web development. That combination initially threw me because it was not a pure coding interview. The next technical round made the DSA work more intense, and I had to write code on paper rather than on…

Technical Screen0
XebiaSoftware Engineer
Reported Jul 2026

Xebia Software Engineer interview on DSA, Java, and Kafka

The process was straightforward and not especially stressful. I had about three to four rounds, with early conversations on my background, fit, and core engineering fundamentals. Technical rounds covered arrays, algorithms and DSA, including a medium-level live coding problem. There was also a Java discussion and a higher-level Kafka conversation about system design and data flow. I gave a quick…

Technical Screen0
Wise. EnergySoftware Engineer
Reported Jul 2026

Wise. Energy Software Engineer interview with pair programming

I went through a standard multi-stage loop. It started with a recruiter conversation, then a 30-minute coding interview, followed by a longer technical session with system design and another coding segment with two engineers. After that came a product interview and a final conversation with managers and a lead. The exercises felt practical rather than contrived. In the pair-programming portion, c…

Technical Screen0
AmazonBusiness Analyst
Reported Jul 2026

Amazon Business Analyst interview with SQL and business case

After the assessment, I was invited to an initial screening. The interviewer asked three SQL questions, then moved into a deep-dive behavioral segment with about two or three questions on the same theme. A business case study was also part of the flow, so it was neither pure coding nor only storytelling. The process felt structured and relevant to the role. The SQL questions were the most concret…

Technical Screen0
ZoomInfoSoftware Engineer
Reported Jul 2026

ZoomInfo Software Engineer interview on projects, debugging, and coding

After a recruiter call involving the hiring manager, I had a technical screen that mostly covered my projects, the role, and resume alignment. A couple more technical conversations followed, mixing coding-style problem-solving and debugging with JavaScript, Java, and SQL. The feeling was practical: they were testing reasoning, not memorization. My background stayed central throughout. I repeatedl…

Technical Screen0
ThoughtWorksFull Stack Engineer
Reported Jul 2026

ThoughtWorks Full Stack Engineer interview cancelled before it began

I applied and had an interview scheduled about a week ahead, which made it feel like a real opportunity. I was surprised by how quickly it moved. Then, the day before the interview, I received a generic rejection saying I was not a good fit. That did not feel consistent with the criteria they stated publicly. I had compared my resume with the job description using an ATS match and received a stro…

Rejected0
Hudson River TradingSoftware Engineer
Reported Jul 2026

Hudson River Trading Software Engineer interview on OS and C++

The process was low-level from the start. After an initial online assessment or coding step, I entered live rounds that demanded deep knowledge rather than surface familiarity. I was asked how things work under the hood, down to memory and kernel operation, with an emphasis on the kind of understanding that gives a developer full control. One screen focused on OS topics at an implementation level…

Online Assessment0
Tata Consultancy Services (North America)Business Analyst
Reported Jul 2026

Tata Consultancy Services (North America) Business Analyst capital-markets interview

The interview felt moderate overall. Most questions concerned SQL and the domain side of my background, followed by why I wanted to switch. My domain was capital markets, so the discussion covered the trade lifecycle and compared equity with derivatives. It went into futures and options and how the products relate in practice. Although it was not described as an especially deep technical intervie…

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

Tata Consultancy Services (North America) Systems Engineer rushed round

One interview round was rough. The interviewer arrived late, and with time already tight, I was not given a real chance to discuss or explain my reasoning. Questions came quickly and felt more like rapid checking than conversation. Near the end, they wrapped up by asking only a few more questions and telling me I was not a fit for the role. The difficulty felt high largely because I did not get t…

Rejected0
DatadogSoftware Engineer
Reported Jul 2026

Datadog Software Engineer HackerRank and final technical interview

The process felt smooth and standard. It began with a HackerRank-style online test containing two LeetCode-like questions. Next came a roughly half-hour recruiter call focused on fit and the usual recruiter topics. The final technical stage lasted about an hour. It included more medium-hard LeetCode-style questions and a separate behavioral and HR block within the overall stage. The recruiter and…

RejectedOnline Assessment0
Arista NetworksSoftware Engineer
Reported Jul 2026

Arista Networks Software Engineer live coding interview

The process felt simple and organized. After a short recruiter-style beginning, I entered live technical rounds. A few people took turns asking questions while I worked in real time. The session lasted about an hour and combined behavioral questions grounded in my resume with one LeetCode-style problem. I also went through a similar three-step process in which every stage involved live coding. Th…

Technical Screen0
AutodeskSoftware Engineer
Reported Jul 2026

Autodesk Software Engineer interview with shifting expectations

The process began reasonably but became confusing when it mattered. In a coding round, I solved a straightforward problem, yet the expectations kept changing. After I had a working solution, the interviewer shifted the problem and pushed toward more abstract architecture improvements without explaining the criteria. It felt as if a particular end state was expected instead of an open engineering…

Technical Screen0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview with four final-loop sessions

My first step was a relaxed recruiter conversation of about half an hour. We discussed my background, school or earlier experience, and what was ahead. Then I completed a 45-minute technical screening coding challenge where how I organized and explained my reasoning mattered as much as reaching an answer. The final loop had four 45-minute interviews, usually spread across one or two days so it wo…

Technical Screen0
Airbus AmericasSoftware Engineer
Reported Jul 2026

Airbus Americas Software Engineer HireVue and manager discussions

I started with the fully automated HireVue video stage. I recorded answers to preset questions with limited preparation time, enough to plan wording but not fully compose it. I could rerecord for each question in at least part of the process, so it felt more like iterating on delivery than brainstorming live. After HR validated me, I had a manager interview about my background, fit, and situation…

0
Accenture EspañaSoftware Engineer
Reported Jul 2026

Accenture España Software Engineer interview with programming and SQL test

After applying, I entered a friendly, structured process. The early conversation covered me and my background, including volunteer work and an internship, my programming languages and tools, how the company is organized, and its benefits. I then completed an online test in my own time. It covered basic programming, object-oriented programming, SQL fundamentals, and logical reasoning rather than p…

RejectedOnline Assessment0
Airbus Americas Customer ServicesSoftware Engineer
Reported Jul 2026

Airbus Americas Customer Services Software Engineer HireVue process

I began with a HireVue interview and answered questions through prerecorded video responses. If HR validated my application, I moved to a manager interview. The early manager involvement depended on clearing that HR gate. The manager conversation was a direct discussion of the role and how I would fit. It did not have heavy technical depth in my experience, but it still seemed to evaluate whether…

0
AIRBUS U.S. Space & DefenseSoftware Engineer
Reported Jul 2026

AIRBUS U.S. Space & Defense Software Engineer HireVue interview

My first step was an automated HireVue stage. I recorded answers to preset prompts with a short preparation window before the camera started. With only a prompt and timer instead of a person, it was unnerving. Some responses allowed retakes, which made the exercise feel focused on wording and structure. After getting through the video interview, I had a traditional conversation with the hiring ma…

0
Airbus HelicoptersSoftware Engineer
Reported Jul 2026

Airbus Helicopters Software Engineer HireVue screening experience

Soon after applying, I completed an automated HireVue-style video interview. I answered predefined questions without a real interviewer in the room. The short preparation window before each recording felt destabilizing, although I had multiple takes for at least some responses, which made it a little less rigid. Once HR validated the video screen, I moved into live conversations with the hiring s…

0
Airbus GroupSoftware Engineer
Reported Jul 2026

Airbus Group Software Engineer HireVue and manager interview

The process started with a HireVue interview, which was unfamiliar to me. I recorded responses to questions with only a short preparation window before the camera started. It was fully automated, with no conversation partner, and that lack of interaction felt destabilizing. After I completed it, the next step was a manager interview if HR validated me. The flow was simple: recorded screening, HR…

0
Cadence Design SystemsSoftware Engineer
Reported Jul 2026

Cadence Design Systems Software Engineer onsite technical rounds

I went through an onsite process that was almost entirely technical. Two deep rounds covered core data structures and system design fundamentals. Each pushed me through complex algorithmic questions where the code needed to be clean, efficient, and well structured. The difficulty was clearly high. It was not enough to make something work; I had to present an organized and efficient solution from…

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