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

ServiceTitanAccount Executive
Reported Jul 2026

ServiceTitan Account Executive interview: repeated communication failures

The first recruiter screen went smoothly. The recruiter seemed engaged and said next steps with the hiring manager would be scheduled. Then I heard nothing for about two weeks. I emailed twice, and only after I included the hiring manager did I receive a rejection. It was especially frustrating because this was not my first experience with the company, and I felt my time was not being respected.…

RejectedHR Screen0
ScaleProduct Manager
Reported Jul 2026

Scale Product Manager interview: AI product cases and fit

After a recruiter call, I entered a product-focused process that lasted several weeks. It combined behavioral questions with product-sense work. The work was AI-focused, and the cases asked for broad thinking with room to shape an approach. The live interviews involved several people and tested different aspects of my thinking. Some conversations were about product sense and design, while others…

Technical Screen0
The University of PennsylvaniaResearch Analyst
Reported Jul 2026

The University of Pennsylvania Research Analyst interview: presentation day

After recruiter-style outreach, I had a full-day interview with people from the department and institute. Before the day, I had a prep call that let me meet people in advance. On the day itself, I spoke with several potential colleagues. I gave a presentation on my previous research experience. The other conversations stayed grounded in that background and how it related to the group's work. It w…

OfferOther0
The RealrealAccount Executive
Reported Jul 2026

The Realreal Account Executive interview: role play and sales feedback

After speaking with the recruiter, I had a video interview with two team members that lasted about three quarters of an hour. They explained what the role expected, discussed my sales background and how I would approach the job, and left room for my questions. It was structured without feeling hostile, and I had time to think through my answers. Some conversations went into how quickly I would ra…

Technical Screen0
Uber DriversData Scientist
Reported Jul 2026

Uber Drivers Data Scientist interview: framing consumer fraud risk

The first round was about risk. I completed one SQL task and then answered a question about a confusion matrix. The follow-up on consumer fraud risk was what threw me. When I explained the risks as I saw them, they did not seem impressed, and that feedback came across quite directly. I did not move to later stages. It felt as though the bar was not only technical correctness. How I framed fraud r…

RejectedTechnical Screen0
UberData Scientist
Reported Jul 2026

Uber Data Scientist interview: SQL and consumer fraud risk

The interview was centered on risk. I worked through an SQL question and then a confusion-matrix-style question, and I felt technically comfortable with both. The problem came when the discussion moved to consumer fraud risk. I answered, but the reaction suggested that the way I framed the risk analysis and reasoning had not landed. That difference in how we saw the quality of the answer stayed w…

RejectedTechnical Screen0
TwilioProduct Manager
Reported Jul 2026

Twilio Product Manager interview: three rounds in under a week

My process was unusually quick: three interview rounds in under a week, with five interviewers across them. Each person covered a different area, including engineering partnership and culture-fit discussions, so I was not having the same conversation over and over. I received an offer within about 72 hours of the last interview and accepted it. Even with the speed, the setup felt intentional beca…

OfferTechnical Screen0
TelefónicaSoftware Engineer
Reported Jul 2026

Telefónica Software Engineer interview: mobile architecture and offer

After I sent my CV, they called to ask about my experience and studies. I then went to a personal interview at the office. They told me there that I had been selected, so I did not have to wait or chase an answer. That part was quick and direct. In another part of the process, I first had an introductory interview, then an aptitude check and an English test. I later met the team to discuss the ro…

OfferTechnical Screen0
Zemoso TechnologiesSoftware Engineer
Reported Jul 2026

Zemoso Technologies Software Engineer interview: backend-heavy technical rounds

I went through two technical rounds and an HR discussion, and things moved quickly. In one experience, an offer letter was already arriving in about ten days. The interviews were practical, covering backend work along with some frontend work. About seventy percent of the technical questions were backend-focused. I discussed Node.js middleware, REST APIs, JWT authentication, and asynchronous progr…

Technical Screen0
ADPSoftware EngineerIntern
Reported Jul 2026

ADP Software Engineer interview: campus internship drive

I attended ADP's campus software-internship drive at DYPCOE Akurdi in Pune. It began with an online assessment, followed by two technical interviews and an HR interview. The structure was clear as it moved from coding into deeper technical discussion and then HR. The technical rounds emphasized fundamentals and connecting my background to the work they were evaluating. By HR, the conversation was…

Online Assessment0
Zoom Video CommunicationsSoftware Engineer
Reported Jul 2026

Zoom Video Communications Software Engineer interview: WebRTC and CodeSignal

A recruiter scheduled a hiring-manager conversation and four additional interviews. Most of those conversations went fine, but one engineer seemed to have decided what the interaction would be before it began. He used barely any of the expected time and did not appear interested in learning about my background. That conversation came down to WebRTC protocols. I covered SIP, RTP, the ICE framework…

Technical Screen0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: LeetCode and leadership pressure

My first interview was about an hour and had two easy LeetCode-style questions. The final stage was tougher: two separate LeetCode sessions, a system-design session, and an LLD session. Leadership Principle prompts came up in every session, so it was never only about getting a solution. The technical questions were easy to medium overall, but the leadership questions were harder for me. I also lo…

Technical Screen0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: leadership-principle loop

Amazon's loop was four to five back-to-back interviews, roughly 45 to 60 minutes each. The panel included a potential hiring manager, one or two team members, a senior leader, and a bar raiser. The pace was relentless because I had to stay sharp across several perspectives. Leadership Principles were spread across the panel. Each interviewer owned a couple, and together they covered all of them.…

0
Wolverine TradingSoftware Engineer
Reported Jul 2026

Wolverine Trading Software Engineer interview: CoderByte trading assessment

An early conversation led quickly to a CoderByte assessment built around trading concepts. The coding was lighter than the systems-style prompts I had seen elsewhere, but it depended on using the right trading vocabulary and mapping it to simple logic. Timing and execution made the difference, and the platform's format pushed me to be precise. The live coding interview gave me more room to explai…

RejectedOnline Assessment0
Zoom CommunicationsSoftware Engineer
Reported Jul 2026

Zoom Communications Software Engineer interview: WebRTC gap

My recruiter arranged time with the hiring manager and five engineers, so I met a lot of people in a short, back-to-back stretch. Most conversations were fine. One engineer, though, seemed to have decided what he thought before we had really started. He used less than the allotted time and did not seem interested in my background. It felt as though he had not reviewed my resume. The loop eventual…

RejectedTechnical Screen0
ABBSoftware Engineer
Reported Jul 2026

ABB Software Engineer interview: logical test and office meeting

I applied through Workday, was contacted, and chose a time for a recruiter call. That simple portal setup moved quickly into a more demanding process than I had expected, although it seemed well managed. I first took a cognitive or logical test and then had an online Teams round. After that I met people in person at the office, including the department for the role, HR, and possibly other manager…

Online Assessment0
LSEG (London Stock Exchange Group)Software Engineer
Reported Jul 2026

LSEG (London Stock Exchange Group) Software Engineer interview: assessment centre

I began with timed assessment activity and then an online assessment centre running from late morning into the afternoon. It included a group round, a technical interview, and a motivation-focused interview. The questions were mostly standard, but it felt competitive because every part seemed tightly measured against other candidates. The process then had aptitude, coding, and group-discussion co…

Online Assessment0
JP Morgan ChaseSoftware Engineer
Reported Jul 2026

JP Morgan Chase Software Engineer interview: HackerRank and Super Day

The first step was an online HackerRank assessment with multiple tasks. The questions felt like easy-to-medium LeetCode problems, and it was a real gatekeeper rather than a quick formality. Afterward I had an HR screen, where recruiters helped arrange a longer interview. I was invited to a three-hour Super Day. The interviews were packed back to back across behavioral, design, and coding tracks,…

Online Assessment0
IntactData Scientist
Reported Jul 2026

Intact Data Scientist interview: claims case study and feedback

I started with a recruiter and HR conversation about my background, what I wanted next in my career, and whether my work style might fit culturally. Later I met the lead data scientist and data science manager for a second round. That discussion went deeper into my past projects and technical experience. The technical portion covered general GenAI topics and an insurance claims case study. The fo…

RejectedHR Screen0
EPAM IndiaQA Automation Engineer
Reported Jul 2026

EPAM India QA Automation Engineer interview: technical breadth and delays

The recruiter call went well. After that, though, the process became a long wait. I heard nothing for about two weeks, followed up by email and LinkedIn, then waited another week for a reply saying the recruiter was waiting on the hiring team. I followed up again about a week later, and the technical interview was finally scheduled almost a month after the first call. That interview covered Java…

In progressTechnical 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