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

Uber DriversSoftware Engineer
Reported Jun 2026

Uber Drivers Software Engineer interview: recursive strings and trees

I had two separate interviews built around DSA problems. The first was a recursion-based string-manipulation question. The second moved to trees and asked for a tree coding solution. Both interviews added follow-ups after the main question, so finishing the initial problem was not the end of it. Those extensions raised the difficulty and made the rounds feel more demanding than the opening prompt…

Technical Screen0
ZScalarAccount Executive
Reported Jun 2026

ZScalar Account Executive interview: mock cold-email exercise

I had a recruiter call and, about a week later, entered a structured process that moved quickly. It began with a hiring-manager conversation and a mock cold-email exercise. That first stage showed they were testing both how I thought about the role and how I would communicate in a realistic sales motion. If I had advanced, the later steps would have included another account-executive interview, p…

RejectedOther0
xAISoftware Engineer
Reported Jun 2026

xAI Software Engineer interview: language-model take-home

My process centered on a take-home assignment and a live follow-up. The topic was a Python language-model application. Before writing code, I had to explain at a high level how the language model worked and how that understanding applied to the specific context. In the live portion, I filled in a function based on what the application needed. They seemed to care about correctness and clarity in c…

Take-home Project0
MetaSoftware Engineer
Reported Jun 2026

Meta Software Engineer interview: 45-minute coding and leaderboard design

After I was scheduled, I had a coding round built around speed and follow-through. I worked through two LeetCode-style problems in 45 minutes and focused on optimization. At least one had a follow-up that required improving the solution instead of stopping once it worked. The onsite loop added coding, behavioral discussion, and system design. The design question involved a leaderboard-style compo…

Technical Screen0
GoogleSoftware Engineer
Reported Jun 2026

Google Software Engineer interview: language-library technical round

A recruiter first reached out, then I had a scheduled technical round. Early on, the interviewer focused on a very specific library connected to the language I had chosen. I could not fully remember the details on the spot, and that threw me off. The process then expanded into several technical rounds: DSA interviews, a high-level design discussion, and a Googliness-style behavioral interview. Th…

Technical Screen0
MicrosoftSoftware Engineer
Reported Jun 2026

Microsoft Software Engineer interview: passed OA then decline

My process started with an OA for a role that had the same title but a different job code. I fully passed both OA questions, but there were still more rounds afterward. The first interview was 45 minutes, followed by a loop with three separate 45-minute rounds on different days. Even though I felt prepared and thought I had done well, the process ended without an offer. I waited for several month…

RejectedOnline Assessment0
Applied MaterialsSoftware Engineer
Reported Jun 2026

Applied Materials Software Engineer interview: unexpected technical onsite

I did this interview partly for the experience, and it turned strange quickly. The first round was on Zoom. The interviewer had the wrong resume and accused me of lying about my experience before realizing the mix-up. He corrected it professionally, but the moment was tense. For the final onsite, I was told it would not be technical, which was fine because I was comfortable with LeetCode. When I…

In progressTechnical Screen0
Amazon Kuiper Commercial ServicesSoftware Engineer
Reported Jun 2026

Amazon Kuiper Commercial Services Software Engineer interview: long OA wait

My process began with an online assessment that took a long time before interviews started. After I submitted it, I moved into interviews built around coding patterns and Leadership Principles. The technical side leaned on LeetCode-style questions, while leadership themes stayed prominent. Based on what I had heard about common topics, I prepared stories around Customer Obsession, Ownership, and…

No responseOnline Assessment0
Amazon DSPSoftware Engineer
Reported Jun 2026

Amazon DSP Software Engineer interview: OA coding and leadership assessment

I received the online assessment about a week after applying, before any loop interviews. It took longer than I expected because it packed in a lot, including video material explaining the kind of reasoning and approach they wanted. The OA had standard coding challenges focused on algorithms and data structures, along with a leadership-assessment component. I had heard that leadership principles…

Online Assessment0
Amazon AdvertisingSoftware Engineer
Reported Jun 2026

Amazon Advertising Software Engineer interview: video-supported online test

I started with recruiter outreach and an initial online step. The assessment used video support and examples of the reasoning and approach they wanted, so it felt less about memorization than about how I structured my thinking. After I cleared it, I had short, focused technical interviews before the final round was scheduled. Later conversations explicitly covered networking, troubleshooting, aut…

Technical Screen0
Infosys FinacleSoftware Engineer
Reported Jun 2026

Infosys Finacle Software Engineer interview: Salesforce trigger exercise

I went through a short virtual interview that was still fairly technical and focused on Salesforce development. It moved from basic concepts into harder areas around Apex, LWC, and how the pieces fit together. I had to reason through integration scenarios, triggers, and related admin and runtime concerns instead of just defining terms. The session lasted about half an hour, and I had to write a t…

Technical Screen0
ADCI - KarnatakaSoftware Engineer
Reported Jun 2026

ADCI - Karnataka Software Engineer interview: four rounds in two days

I applied through Amazon Careers without a referral. A recruiter reached out, then I completed an OA. About a month later, I was scheduled for four rounds across two days. The pace was intense. Each interview included 30 minutes of behavioral discussion and 30 minutes of coding. Coding and system-design content were spread across the four interviews, while the overall format stayed consistent fro…

OfferOnline Assessment0
ADCI - KarnatakaSoftware Engineer
Reported Jun 2026

ADCI - Karnataka Software Engineer interview: four-round design loop

After I cleared the online assessment, I entered the Amazon loop. It had four rounds: two coding interviews, a behavioral interview focused heavily on Amazon Leadership Principles, and a final hiring-manager round that combined coding with high-level design. The first coding round had two LeetCode medium problems. The second moved to a hard problem, with the same expectation that I write clean co…

Online Assessment0
ADCI - KarnatakaSoftware Engineer
Reported Jun 2026

ADCI - Karnataka Software Engineer interview: OA and leadership principles

My process started with an online assessment, and it took a long time before I even reached the interview stages. After the OA, I had two interviews, each about 60 minutes. Across the process, I heard that both LeetCode-style problems and leadership principles were part of the evaluation. That meant my prep could not just be DSA. I also had to have specific stories ready for leadership-principle…

Online Assessment0
ADCI - KarnatakaSoftware Engineer
Reported Jun 2026

ADCI - Karnataka Software Engineer interview: architect-level questions

I applied through the Amazon job portal and got an HR call. After that, I went through five technical rounds in total: one described as a screening round and the rest scheduled as technical interviews. The early questions felt aimed at architect-level depth even though I was applying as a developer with four years of experience. The first two rounds were the hardest, and the questions pushed beyo…

Technical Screen0
Ernst & Young U.S. LLPConsultant
Reported Jun 2026

Ernst & Young U.S. LLP Consultant interview: delayed HR rejection

My first step was a brief phone call with HR, and it felt mechanical. The interviewer seemed to be reading from a list, without giving me much detail about the role or what the rest of the process would involve. After that call, I heard nothing for months. When I finally received an email, it was a generic rejection with no real feedback. The interview did not feel technically difficult, but the…

RejectedHR Screen0
Ernst & Young U.S. LLPConsultant
Reported Jun 2026

Ernst & Young U.S. LLP Consultant interview: virtual assessment process

My process felt long and somewhat unfocused. I went through several stages, including a video-based step and an assessment, but neither seemed to take me far. Each one felt more like a formality than a route to a final decision. Although everything was virtual and involved several moving parts, it did not feel efficient. I did not receive an offer, and I remember thinking it could have moved fast…

0
AmazonSoftware Engineer
Reported Jun 2026

Amazon Software Engineer interview: AI coding assessment

My Amazon process began with online tasks before the more traditional interviews. The DSA portion used something like a house-robber II problem, so it felt more focused on dynamic-programming trade-offs than a simple brute-force solution. The assessment also had an AI-based coding round. I was given a code repository and an AI model with guardrails, then had to work from failing test cases to und…

Online Assessment0
MeeshoSoftware Engineer
Reported Jun 2026

Meesho Software Engineer interview: SDE-1 problem solving

I interviewed for an SDE-1 full-stack role at Meesho after applying through the career portal and being shortlisted. The first round focused on problem solving and felt like a standard technical screen. One detail I kept being reminded about was logistics: I needed a backup internet connection for the interviews. It did not change the technical content, but it affected how I prepared and how I ma…

Technical Screen0
GoogleBackend Engineer
Reported Jun 2026

Google Backend Engineer interview: behavioral detail and impact

I went through Google's behavioral and HR round for a Backend Engineer role, and it put surprising weight on the details. The conversation followed the familiar behavioral format: how I would respond, how clearly I could explain my thinking, and how I connected my experience to the kind of work Google cares about. I found that precision mattered more than simply sounding confident. I kept checkin…

HR 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