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

AmazonSoftware EngineerIntern
Reported Jul 2026

Amazon Software Engineer internship interview: leadership principles and FBA pitch

For this internship role, I had two one-hour interviews focused on Amazon’s Leadership Principles. Questions covered delivering results, earning trust, diving deep, and ownership. The interviews also reflected that the position was sales-oriented. There was a simulated customer pitch about adopting Amazon FBA. The difficulty felt easy, and the process was driven by the principles, with the sales…

Offer0
ZalandoSoftware Engineer
Reported Jul 2026

Zalando Software Engineer interview: technical depth, system design, and manager debrief

After a recruiter screen, I had an HR call about my experience, salary expectations, and a detailed explanation of the process and interviewers. I then had several technical rounds in a structured but flexible sequence: general technical depth, system design, and behavioral or managerial evaluation. Each technical round lasted about an hour. The questions tied closely to work I had described, inc…

0
ISS STOXXData Analyst
Reported Jul 2026

ISS STOXX Data Analyst interview: Excel assessment through final on-site discussion

After applying, I went through a structured process starting with an Excel-skills assessment. Passing it led to an online HR interview, business interviews, and a final on-site discussion. HR emailed clear next steps and deadlines. Before the interviews, there was a hands-on technical exam on data handling and report-output case scenarios, including data visualization and manipulation. The instru…

0
EPAM IndiaSoftware Engineer
Reported Jul 2026

EPAM India Software Engineer interview: LRU cache, technical rounds, and canceled follow-up

My EPAM process was assessment-heavy. It started with an OA covering aptitude, OS, computer networks, and coding. Next came a pen-and-paper coding test in an auditorium, where I worked on an LRU cache problem. Then there was a group discussion where the evaluator let us choose the topic. After that came technical interviews on DSA, DBMS, OS, CN, and more coding, followed by HR. It was not one con…

No response0
Oracle HealthSoftware Engineer
Reported Jul 2026

Oracle Health Software Engineer interview: trade reconciliation and low-level design

My loop began with a detailed low-level design round where I designed a trade reconciliation service. The interviewer was knowledgeable and helpful, but the bar for clarity and completeness felt strict. I left realizing that my preparation had gaps. Later rounds were more focused. One was described as basic DSA. Another drilled into my projects, asking me to defend design decisions rather than ju…

0
SalesforceSoftware Engineer
Reported Jul 2026

Salesforce Software Engineer interview: DFS and scalable-system design

My process began with a recruiter screen and then a technical round built around a hard LeetCode-style DSA problem that leaned heavily on DFS. I spent the session working through the approach and tradeoffs while trying to keep my reasoning clear. After that, I had a high-level design interview about scalability and reliability. It pushed me beyond an immediate coding solution toward how a system…

0
IBMSoftware Engineer
Reported Jul 2026

IBM Software Engineer interview: coffee chat, pitch, and technical-behavioral session

I started with a more casual conversation than expected: a coffee chat about my background, resume projects, and prior work. There was no real coding pressure, just friendly questions and a sense of getting to know the role and team. The next step was more structured. I received an email with questions about my location and background, then had one 30-minute technical and behavioral session. It s…

Offer0
AtlassianAccount Executive
Reported Jul 2026

Atlassian Account Executive interview: five-week plan stretched to eight weeks

A recruiter told me the process would be structured, about five weeks long, with at least four or five interviews and a required presentation. Scheduling was the part that threw me off. My interview times kept being rescheduled, and while I understood that things change, it kept pushing the calendar. End to end, the process took about eight weeks instead of the original expectation. The loop soun…

0
NVIDIAEmbedded Engineer
Reported Jul 2026

NVIDIA Embedded Engineer interview: firmware protocol system design

My process started with an OA that immediately felt demanding. It covered LeetCode-style questions from easy through medium, plus C++ data-structure properties. After the OA, I had a technical interview with a team member. The difficult part was a firmware system-design-style problem framed around a firmware protocol, with computer-networking concepts as well. The scope felt broad, not purely alg…

0
OpenAISoftware Engineer
Reported Jul 2026

OpenAI Software Engineer interview: two days of coding interviews

The process was straightforward and fast-paced. I had two days of back-to-back interviews, mostly coding problems, plus a hiring-manager interview. It felt practical, more about showing I could solve problems than getting lost in theory. The topics matched standard preparation: LeetCode-style practice covered the coding well, and I also prepared for the behavioral round. The turnaround after the…

0
MicrosoftSoftware Engineer
Reported Jul 2026

Microsoft Software Engineer interview: quick take-home follow-up and manager interviews

I heard back quickly after applying and again after the take-home step. Then I went straight into three interviews, all with managers. The overall vibe was professional and easy to talk to. The conversations felt thoughtful instead of stressful. It seemed they wanted to understand my work and how I communicated, and I left each session feeling that I had covered the points they were listening for…

0
Amazon AdvertisingSoftware Engineer
Reported Jul 2026

Amazon Advertising Software Engineer interview: ambiguous practical programming task

The questions were practical programming prompts rather than textbook-only coding. The first was fairly trivial math. The second was interactive: I had to work out what the interviewer wanted, then implement several functions to make it work. That second task stretched me because it required clarification and interpretation. I had to check my understanding early and keep iterating until the imple…

0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: leadership principles and system design

My process began with an online assessment on data structures and algorithms, followed by a technical phone screen. The final stage was a loop of several consecutive rounds. Those rounds emphasized Amazon-style leadership principles alongside system design. I expected technical evaluation, but I was surprised by how much leadership framing appeared while I worked through design questions. It made…

0
Accenture in IndiaSoftware Engineer
Reported Jul 2026

Accenture in India Software Engineer interview: HR, programming, SQL, and Git

I had a two-part process: an HR call followed by a technical round. The HR conversation covered introductions and context. The technical section covered core programming concepts, SQL, and Git. There was also problem solving and a brief practical exercise, so they could see how I approached a task rather than only how I described it. The format stayed straightforward and focused on fundamentals t…

Offer0
ADCI - KarnatakaSoftware Engineer
Reported Jul 2026

ADCI - Karnataka Software Engineer interview: three back-to-back interviews

I started with an online assessment and then moved quickly into three back-to-back interviews, with almost no downtime. One interview was fully behavioral and had a bar-raiser-style focus. The other two were technical, ranging from DSA to low-level system design. The loop tested more than memorized problem solving; it tested how I think under pressure. I did not get an offer. The back-to-back for…

0
QuantiphiMachine Learning Engineer
Reported Jul 2026

Quantiphi Machine Learning Engineer interview: unexpected computer-vision focus

My first interaction focused heavily on computer vision, even though the role description had seemed more about text and agentic work. After introductions and questions about my projects, the interviewer moved into vision situations, including how to improve a model’s accuracy, plus a coding-style question involving decorators and dictionary use. The vision focus continued through questions about…

0
Prime VideoSoftware Engineer
Reported Jul 2026

Prime Video Software Engineer interview: coding and leadership-principles screen

After recruiter outreach, I went through a focused phone interview process with one coding round and two leadership-principles-style questions. Coding and the principles felt like two parts of the same test: I needed to show general engineering ability and communicate how I was thinking. I did not need deep knowledge of the exact team. The recruiter presented it as a general-skill screen about ho…

0
Prime VideoSoftware Engineer
Reported Jul 2026

Prime Video Software Engineer interview: online assignment and medium coding question

My process began with a straightforward online assignment. After a wait, I was invited to one additional round. That round combined a LeetCode-style medium coding question with a short behavioral section. It felt balanced: I had to solve the problem and talk through my experience and behavioral instincts in the same session. Location: Culver City, CA. Overall feedback: positive. Offer status: got…

Offer0
Quest GlobalSoftware Engineer
Reported Jul 2026

Quest Global Software Engineer interview: recruiter call through HR round

I started with a recruiter call and, about a week later, had a technical screen. The early conversations were mostly technical, followed by an HR round by phone. Everything was professionally organized, and updates were communicated clearly instead of leaving me guessing. The difficulty felt average: serious enough to matter, but not chaotic. I left feeling that my answers had been understood and…

Offer0
PinterestSoftware Engineer
Reported Jul 2026

Pinterest Software Engineer interview: interrupted virtual technical questions

The interviewer sent the wrong virtual-meeting link and arrived about five minutes late, which set the tone. During a warmup that was basically a Boyer-Moore Voting Algorithm variation, they kept interrupting as I tried a brute-force implementation to understand the problem. I could not finish my thought. That happened again on a graph-traversal question. The interviewer seemed disengaged from th…

0

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