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

OracleAccount Executive
Reported Jul 2026

Oracle Account Executive interview: easy call, poor follow-through

One process began with a short recruiter conversation that felt easy and genuinely smooth. It lasted about 10 to 15 minutes, and I received positive feedback about the call, yet I was rejected afterward. A follow-up message after the call was never answered. In another run, the recruiter side broke down. The recruiter seemed careless and unprofessional, did not give useful detail about the role,…

RejectedHR Screen0
OracleSoftware Engineer
Reported Jul 2026

Oracle Software Engineer interview: LRU cache and course ordering

The technical rounds were more demanding than I expected. The questions did not seem unfair, but the interviewer energy and live problem-solving pace kept me switching gears. I implemented an LRU cache and then worked on a course-prerequisite ordering problem, which made me think about ordering constraints as well as code. The final round was the most stressful. I had to maximize the area trapped…

OfferOther0
National Debt ReliefAccount Executive
Reported Jul 2026

National Debt Relief Account Executive interview: virtual self-reflection

My virtual interviews took place in two steps, beginning with a recruiter-style conversation and continuing to a second round. The first part was standard: questions about me professionally, my strongest attributes, and how I handled failure or falling short. The second interview kept the same focus on my work history and how I reflected on mistakes. The second interview started about half an hou…

HR Screen0
SentinelOneSoftware Engineer
Reported Jul 2026

SentinelOne Software Engineer interview: fast online technical pair

After a recruiter reached out, I shared my availability and received invitations quickly. The process moved fast and felt straightforward. I first spoke with the recruiter, then completed the technical part online in English. There were two back-to-back video technical interviews. The first covered conventional programming, including coding fundamentals and problem solving. The second moved to sy…

Technical Screen0
Rockstar GamesSoftware Engineer
Reported Jul 2026

Rockstar Games Software Engineer interview: coding track and logistics

The process opened with a recruiter screen and moved directly into a technical track. In one version, the initial coding test covered basic Java, Spring Boot, SQL, and some problem solving. After that, I had a focused, practical screening or technical discussion with senior people. Later stages included a live CoderPad-style assessment with problems described as similar to LeetCode, followed by a…

RejectedOther0
RockstarSoftware Engineer
Reported Jul 2026

Rockstar Software Engineer interview: Java, Spring Boot, and SQL

I started with a coding test covering Java, Spring Boot, SQL, and some problem-solving prompts. It was a practical check across the stack, so I had to do the work rather than simply talk through what I might do. After that came a screening step and then a technical discussion with senior people. That conversation was more about how I approached problems and reasoned through solutions than about w…

Other0
RevolutProduct Manager
Reported Jul 2026

Revolut Product Manager interview: structured cases and bar raiser

After a recruiter call, I went through about four stages over roughly a month. The first substantive interview was a business problem-solving case. I clarified the situation, organized it in a MECE way, formed hypotheses to ask for data, and held off on solutions until I thought I had confirmed the root cause. The next case combined product thinking with technical system design, including the des…

RejectedOther0
RevolutOperations Manager
Reported Jul 2026

Revolut Operations Manager interview: two months of shifting logistics

The process felt chaotic from the start. A recruiter first contacted me on LinkedIn, then passed me to another recruiter whose availability was about three weeks away. That call was cancelled at the last minute, and the rescheduling options were extremely late, around 1 a.m. and similar times. After scheduling, I was ghosted until I chased a different recruiter through contact details I had found…

RejectedOnline Assessment0
SamsaraSoftware Engineer
Reported Jul 2026

Samsara Software Engineer interview: a thoughtful rerouting

I began with a recruiter conversation about my background. The recruiter did not think the role I applied for was the best fit, but instead of ending the process, he suggested another position in the Routing organization. I was unsure whether I had the right skills, though the problem domain interested me enough to continue. I did not reach the next stage, but the process felt thoughtful. The rec…

RejectedHR Screen0
SASSoftware Engineer
Reported Jul 2026

SAS Software Engineer interview: positive discussions, no offer

The process began with two back-to-back conversations: a 30-minute recruiter interview, then a 30-minute meeting with the hiring manager and team manager. After that, I spent almost three hours with the team and the team manager. The extended live discussion was the longest part, rather than any individual test. They asked extensively about projects on my resume and included behavioral questions.…

HR Screen0
Super Micro ComputerSoftware Engineer
Reported Jul 2026

Super Micro Computer Software Engineer interview: leadership in technical rounds

My loop blended leadership principles directly into technical interviews. The first technical conversation combined troubleshooting and GenAI fluency with prompts about Bias for Action. It was clear that behavior and engineering were not being treated as separate subjects. The next technical round focused on coding problems with leadership themes such as Deliver Results. A hiring-manager-style co…

Other0
Veeva SystemsConsultant
Reported Jul 2026

Veeva Systems Consultant interview: a 25 to 30 hour project

The experience was focused and brutal. I spent something like 25 to 30 hours on a project, and I believed the result was technically strong. I expected constructive next steps or at least a clear evaluation, but the team rejected the work coldly. The stated reason was essentially that my Zoom connection had been poor. That did not seem to match the effort I had invested or the quality I thought I…

RejectedTake-home Project0
Uber DriversAccount Executive
Reported Jul 2026

Uber Drivers Account Executive interview: aptitude and phone screen

I had a direct process that began with a recruiter-style check. The early screening asked about my client-facing work and how I had handled vendor relationships, including relationships with different alcohol vendors. An aptitude-style step followed, then a phone interview focused on my experience and gave me more information about what the role would involve. These early rounds felt average in d…

RejectedOnline Assessment0
UberAccount Executive
Reported Jul 2026

Uber Account Executive interview: vendor experience screen

After applying through the website, I was shortlisted and had an initial HR screen. The questions focused on my client-facing experience and how I worked with vendors, including different alcohol vendors and what that looked like in practice. The round was average in difficulty. It was not overly technical, but it did require me to explain real-world vendor and stakeholder work. I did not receive…

HR Screen0
SyntesSoftware Engineer
Reported Jul 2026

Syntes Software Engineer interview: friendly start, no follow-through

The first thing that stood out was the lack of clarity once I finally had a chance to interview. Recruiters were direct when they reached out, but they gave little information about the process length and I received no updates afterward. In a separate attempt, I was contacted after applying for an assessment path. There was a quick phone call about my background and fit, with the hiring manager c…

No responseHR Screen0
Susquehanna International GroupQuantitative Analyst
Reported Jul 2026

Susquehanna International Group Quantitative Analyst interview: CodeSignal, Bayes and expected value

I began with a structured math screen: a timed CodeSignal assessment with programming and algorithmic problems that also demanded test-style problem solving under pressure. The later interviews stayed focused on probability and clean reasoning. Interviewers wanted to hear how I thought, not only the answer. The math covered Bayes' rule, combinatorics, expected-value questions, and puzzle-like rea…

Online Assessment0
SupermicroSoftware Engineer
Reported Jul 2026

Supermicro Software Engineer interview: Bar Raiser depth

My loop started with a recruiter screen and a small set of structured technical rounds. The first technical round combined troubleshooting with Bias for Action and GenAI fluency. The next turned to coding problem solving, where I needed to solve a technical prompt and keep my output clear. Then came a hiring-manager-style round on Earn Trust, Learn and Be Curious, and Operational Excellence. The…

HR Screen0
ZscalerSoftware Engineer
Reported Jul 2026

Zscaler Software Engineer interview: networking to system design

After a recruiter touchpoint, I had a focused first technical round. It opened with networking questions, moved to two coding problems, and then shifted to an open-ended system-design prompt. The system-design part was the hardest to get my head around. The interviewer did not feel encouraging or helpful while I was trying to organize an approach. Compared with that, the coding portion was manage…

Technical Screen0
Zoom Video CommunicationsSoftware Engineer
Reported Jul 2026

Zoom Video Communications Software Engineer interview: delays after a VP call

I was drawn into a long hiring loop that took most of three months. After the recruiter stage, I prepared a presentation and then had a VP interview, with long delays between steps. I kept getting positive signals and being told I was advancing, but I also had to chase updates, and the recruiter and hiring manager were hard to reach when I needed clarity. The VP call gave me the most confidence.…

No responseHR Screen0
AccentureConsultant
Reported Jul 2026

Accenture Consultant interview: cases, routing, and SAP FICO

One path moved quickly through three interviews: two case-focused rounds and a less formal fit conversation with someone from a prospecting team. It was easy to follow and did not feel overly formal. In a different experience, I was told the first interviewer had not reviewed my CV and thought I might fit another team better. They still gave me a case, but the way my application was being routed…

WithdrewOther0

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