Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

4457 stories

Likes earn the author +10 XP for the first 3 likes each day

PlangridSoftware Engineer
Reported Jul 2026

Software Engineer interview at Plangrid: React and system design

The recruiter first discussed the role, my background, and the process, which put me at ease. The hiring-manager conversation was mostly behavioral: why I chose software engineering, resume projects I was proud of, and how I approach teamwork and communication. It also included a few technical basics, including C++ and DSA. The next steps were a live React interview, system design, and culture fi…

0
Palo Alto NetworksAccount Executive
Reported Jul 2026

Account Executive interview at Palo Alto Networks: cut-off Zoom call

What began as a normal Zoom interview stopped abruptly after about forty minutes. I tried to reconnect and followed up repeatedly, but heard nothing for roughly a week. When someone finally responded, it was simply to say they were no longer considering candidates. The early cutoff and lack of closure left me confused about whether the interview had ended properly on their side or whether I was s…

0
Oscar InsuranceSoftware Engineer
Reported Jul 2026

Software Engineer interview at Oscar Insurance: timed unfamiliar pattern

A recruiter contacted me a couple of days after I applied and scheduled a technical round about a week later. I had been warned that the questions would be difficult and tightly timed. That proved accurate: I had 30 minutes for a challenging pattern I had never seen before, got partway through it, and could not finish in the time box. The short window made the experience stressful from the beginn…

0
Northrop GrummanSoftware Engineer
Reported Jul 2026

Software Engineer interview at Northrop Grumman: behavioral panel

A recruiter email laid out the early screen, including standard and role-specific questions. I then met a panel made up of a hiring manager and two tech leads. The process centered on communication and fit: they wanted STAR-style behavioral answers and kept returning to how my experience looked against the role. It was not especially technical and did not require a presentation. I mostly discusse…

Offer0
New RelicSoftware Engineer
Reported Jul 2026

Software Engineer interview at New Relic: delayed Portland process

After the recruiter call, I waited almost two weeks before the hiring manager scheduled the Portland interview. On that call, the manager seemed disengaged and did little to build momentum, so the conversation felt flat and uninterested in my experience. Another couple of weeks passed with no update. The recruiter eventually said the search had narrowed and they were pausing candidates, followed…

Rejected0
Nevada StaffingSoftware Engineer
Reported Jul 2026

Software Engineer interview at Nevada Staffing: tolerance and heat transfer

After recruiter contact, I submitted a take-home test and then interviewed. The first question was about a gasket and an L bracket compressing an L gasket. It sounded simple, but I overthought the tolerances and missed the correct limit. In a second pass through the technical loop, the tone itself made things harder. The interviewer pulled specific details from my resume and then abruptly moved t…

Take-home Project0
Morgan StanleySoftware Engineer
Reported Jul 2026

Software Engineer interview at Morgan Stanley: four-hour first in-person interview

My first in-person interview was hard mainly because I had never gone through that format before, not because the material felt impossible. I did enjoy learning about the team and the company, and I appreciated the effort the interviewers put into the conversation. The day lasted four hours. By the end, both the interviewers and the team seemed tired, and that fatigue made the experience heavier…

Onsite0
ServiceTitanSoftware Engineer
Reported Jul 2026

Software Engineer interview at ServiceTitan: slow coding sequence

After a recruiter call, I went through several straightforward coding rounds. They focused on medium LeetCode-style data structures and algorithms. The interviewers were calm and practical, asked clarifying questions, and stayed interested in how I was thinking. I cleared multiple rounds that kept testing much the same skill set, but the whole process took about a month. Several-day pauses appear…

0
Volkswagen Group ItaliaSoftware Engineer
Reported Jul 2026

Software Engineer interview at Volkswagen Group Italia: offer timeline

My process had several stages and moved more slowly than I expected. I went through two technical discussions, then final document verification and a salary conversation. It eventually became an offer-acceptance process, and I received an offer letter. The surprising part was timing. More than three weeks passed before I joined the organization after accepting. The paperwork did move forward, but…

Offer0
SwiggyAccount Executive
Reported Jul 2026

Account Executive interview at Swiggy: practical fit screen

My phone screen matched the role and my background closely. We went over my experience, then practical fit questions: whether I could travel, how I handled negotiation, and whether I was comfortable using the local language in day-to-day work. It was not a gotcha conversation. They seemed to be checking whether my profile fit what the team needed. Afterward, I was told another interview would be…

Offer0
Super Micro ComputerSoftware Engineer
Reported Jul 2026

Software Engineer interview at Super Micro Computer: coding loop

The loop had a predictable shape, even though I was not selected. It began with three medium LeetCode-style coding rounds, continued to system design, and ended with a cultural-fit conversation. The interviewers were pleasant and the atmosphere stayed positive. What bothered me was the format more than any particular prompt. The coding rounds felt dated and close to traditional LeetCode preparati…

Rejected0
TeslaSoftware Engineer
Reported Jul 2026

Software Engineer interview at Tesla: gasket tolerance

Before the interview, I completed and submitted a take-home test. The interview then opened with a problem that sounded simple, involving a gasket and an L bracket compressing that gasket. The interviewer treated it as straightforward, but I overthought the calculation and missed the correct tolerance limit. The subject itself was not complicated. The precision of the calculation was what mattere…

Take-home Project0
SupermicroSoftware Engineer
Reported Jul 2026

Software Engineer interview at Supermicro: virtual loop

I started with a recruiter screen, then completed an online assessment before a virtual loop with several interviewers. Each conversation blended technical material with Amazon Leadership Principles. The coding was DSA-heavy: I had to contrast brute-force and optimal approaches, explain time and space complexity, and work through a sliding-window problem systematically instead of rushing to code.…

Online Assessment0
StrykerAccount Executive
Reported Jul 2026

Stryker Account Executive interview: intimidating territory-manager conversation

I began with the territory manager, which felt unusual to me for a medical-sales role. The tone was intimidating. I felt pressed on how hard they needed someone to work, and it came across as condescending compared with conversations in my current work. The questions themselves were straightforward and not overly complex, but the vibe threw me off early. As the process continued, the direct, no-n…

Other0
ADPConsultant
Reported Jul 2026

ADP Consultant interview: a month-long wait and stalled application status

What stayed with me was the duration and lack of clarity. I started with a video interview that let me record answers more than once, followed by a skills assessment. I was then scheduled to meet a manager and hiring manager and was told I would hear back by the end of that week. Instead, the email came a full month later and said they had moved forward with someone else. In a separate part of th…

No responseOnline Assessment0
Abnormal AISoftware Engineer
Reported Jul 2026

Abnormal AI Software Engineer interview: feature implementation in an existing codebase

My technical interview focused on AI-assisted coding. I was placed in a fairly large existing codebase and first had to make sense of it with AI tools. Then I used that understanding and AI support to implement a feature and write tests for the changes. It felt less like a pure algorithm check and more like a test of whether I could turn a task into working code while using AI in a controlled way…

Technical Screen0
Abnormal AISoftware Engineer
Reported Jul 2026

Abnormal AI Software Engineer interview: AI agents used throughout a real-work loop

After a recruiter call, I met a hiring manager to discuss my background, projects, and what I hoped to learn from the team. Everyone was welcoming and responsive, and the handoffs between rounds were clear. The technical work centered on AI rather than classic LeetCode prompts. In a large codebase, I used AI to understand the structure, implemented a feature with AI assistance, and wrote tests. T…

HR Screen0
WiseSoftware Engineer
Reported Jul 2026

Wise Software Engineer interview: supportive pairing and contradictory design guidance

After a recruiter chat, I entered technical rounds of about an hour each. The pair-programming panel was mostly friendly and helped when I got stuck. I tried to collaborate and explain my thinking, and one interviewer said at the end that I had done better than most senior IC candidates, but I still did not advance. System design felt less stable. Two interviewers pulled in different directions:…

Technical Screen0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: sliding window and a debugging leadership story

I had a phone round with two focused prompts. One was a medium sliding-window problem, and I had to explain how I would approach it. The other was about leadership: describe a time I debugged an error, including the issue, how I researched and debugged it, and what I put in place to prevent it from recurring. It felt difficult because it paired a concrete algorithm with a detailed accountability…

Technical Screen0
AmazonSoftware Engineer
Reported Jul 2026

Amazon Software Engineer interview: coding rounds, system design, and a narrow-feeling evaluation

I had three coding rounds with LeetCode-style medium problems, then a system-design round and a cultural-fit conversation. The interviewers were friendly and the environment was pleasant, which made the pressure easier to manage. Still, the process felt dated to me. LeetCode practice carried much of the load, and cultural fit was treated as a single conversation rather than something developed th…

Technical 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