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

MedtronicSoftware Engineer
Reported Jul 2026

Software Engineer interview at Medtronic: fit and collaboration

After an HR call, I spoke with the hiring manager in a process that felt direct and centered on competencies. They asked about my experience, including whether I had worked in medical devices, then discussed my projects and the way I worked on a team. Even the technical questions focused on my reasoning rather than only the final answer. Because I had interned at another company site, I already k…

0
LinkedInAccount Executive
Reported Jul 2026

LinkedIn Account Executive interview: fast recruiter-to-mock-call loop

The recruiter conversation was quick and friendly, and the process moved fast. Within minutes of applying, I received an email to schedule the first screening call. I spoke with three people in total: a recruiter, a hiring manager, and a panel-style mock call. The hiring team was great throughout. I answered their questions and felt they were listening. By the end of the last round, I had receive…

OfferHR Screen0
Jpmorgan Chase &Business Analyst
Reported Jul 2026

Jpmorgan Chase & Business Analyst interview: strong first feedback then silence

I received strong feedback on the same day as my first-round interview, which made me optimistic. Then a long period passed without an update, and the silence started to feel strange. When I followed up, I was told they were working on it. Eventually I moved on because I found another job in the meantime. I never saw the process close properly after that promising first impression. The interview…

WithdrewTechnical Screen0
Jpmorgan Chase &Financial Analyst
Reported Jul 2026

Jpmorgan Chase & Financial Analyst interview: HireVue fit screen

I began with an online HireVue. The questions were about why the firm and role, finance basics, and behavioral topics. I had around 30 seconds to prepare before answering, with a limited number of takes depending on the question. The timing made even straightforward questions feel tight. The prompts also covered why I wanted banking, teamwork, and market awareness or trends. The format seemed fai…

Online Assessment0
Jane StreetQuantitative Analyst
Reported Jul 2026

Jane Street Quantitative Analyst interview: probability games before superday

I had several Zoom interviews, with three technical rounds before a superday. The questions were built around games presented by the interviewers and relied heavily on probability and game thinking. The early games were more straightforward and closer to deterministic setups. Later rounds brought more randomness and more game theory. In the more open-ended game rounds, I needed to optimize outcom…

RejectedTechnical Screen0
MicroStrategySoftware Engineer
Reported Jul 2026

MicroStrategy Software Engineer interview: office start and virtual rounds

The first round was face to face in the office, which gave it a different feel from the later virtual interviews. The technical questions stayed moderately difficult, leaning on solid foundations and scenario-based reasoning instead of obscure edge cases. I had a timed assessment before the technical discussions, then technical conversations, more meetings with a leadership and management perspec…

RejectedOnline Assessment0
Prime VideoSoftware Engineer
Reported Jul 2026

Prime Video Software Engineer interview: DSA and Leadership Principles

The process leaned heavily on DSA, Leadership Principles, and some low-level design. I felt the evaluation was split between algorithmic problem solving and how I communicated through the Leadership Principles lens. The DSA rounds varied in difficulty but were LeetCode-like. They included medium problems and at least one hard question with DP and graph themes. I had to explain my thinking, time a…

Technical Screen0
OdooAccount Executive
Reported Jul 2026

Odoo Account Executive interview: delays after recruiter and final rounds

The hardest part was the waiting, not the first interview. I started with a recruiter conversation about my account-management background and was told I would hear back by the end of the week. The week passed, and my follow-ups brought no useful response. The same frustration appeared at the final stage. Even after a last interview and a promise of a timely decision, I waited for weeks. When a re…

No responseHR Screen0
OdooFull Stack Engineer
Reported Jul 2026

Odoo Full Stack Engineer interview: HTML validator and delayed decision

The process began with an HTML-tags validator. The task was simple in concept: decide whether an HTML snippet was valid, knowing that one incorrect tag or invalid structure would make it fail. After that I had two short, friendly HR interviews with different people. We talked about my interest and experience, my motivation for coding, and what I liked doing day to day. The conversations were rela…

RejectedOnline Assessment0
Northern TrustBusiness Analyst
Reported Jul 2026

Northern Trust Business Analyst interview: one practical virtual round

The process was quick and had one round. A recruiter-style invitation led to a virtual conversation with two interviewers for about half an hour. The discussion was domain-related and tied to the process I would work on, including challenges from my own workflow and whether I could work EMEA shifts. The focus was narrow and practical rather than broad. I was struck by how directly they connected…

Technical Screen0
mondaySoftware Engineer
Reported Jul 2026

monday Software Engineer interview: feedback through system design

After a recruiter call, I went into a coding interview where I did only limited coding and spent much of the time explaining my reasoning. The process moved step by step, and the recruiter followed up with feedback after that stage. That feedback helped me understand what they were looking for. The next interview put even less weight on heavy coding and more on walking through my approach. Then c…

RejectedTechnical Screen0
PinterestMachine Learning Engineer
Reported Jul 2026

Pinterest Machine Learning Engineer interview: ML theory and quick rejection

The loop was short but rough. In the initial conversation, I tried to explain my projects, but the interviewer did not seem willing to listen. I then had a technical machine-learning session covering core theory, including vanishing gradients and ensemble methods such as bagging and boosting. There was also a LeetCode-style problem for about 30 minutes. The process ended quickly, and I received a…

RejectedTechnical Screen0
Oscar InsuranceSoftware Engineer
Reported Jul 2026

Oscar Insurance Software Engineer interview: ghosted after coding

I started with a recruiter call and moved quickly into a LeetCode-style interview. If that went well, I had been told to expect another LeetCode interview and a system-design discussion. I felt I did well across the steps. Then the communication dropped away. I was ghosted after the interviews, and when nothing happened I followed up about a week later. The rest of the process had felt normal, so…

No responseTechnical Screen0
Oscar HealthSoftware Engineer
Reported Jul 2026

Oscar Health Software Engineer interview: silence after coding

The recruiter call was routine, followed by a LeetCode interview. If that went well, I was told the next steps would be a two-hour LeetCode session and a system-design interview. I thought I had done well enough and left feeling that the rounds had gone well. Then the company went silent. I followed up after about a week and still never heard back. That was the frustrating part. Everything before…

No responseTechnical Screen0
Ntt Data Europe & LatamSoftware Engineer
Reported Jul 2026

Ntt Data Europe & Latam Software Engineer interview: foundations and projects

The technical interview began with an introduction and moved into practical topics from my background. We discussed version control and GitHub, HTTP basics, database management, prompt engineering, and a project I had worked on. The material was moderately straightforward, although the interviewer's framing was not always clear about what they wanted me to answer. Even so, the direction stayed te…

Technical Screen0
NTT DATASoftware Engineer
Reported Jul 2026

NTT DATA Software Engineer interview: unclear Java questions

The technical interview leaned heavily on Java and software fundamentals. I expected clear, role-focused questions, but the interviewer was not always clear about what was being asked, so it was hard to judge how much detail an answer needed. The conversation also covered version control and GitHub, HTTP basics, database management, a project I had worked on, and other practical experience. That…

Technical Screen0
OpenTextSolutions Engineer
Reported Jul 2026

OpenText Solutions Engineer interview: practical design discussions

After a recruiter conversation, I went through a comfortable set of interviews. The team felt friendly and professional rather than rigid. Technical questions stayed close to my experience and the design decisions I had actually made. There was a system-design discussion, a coding component, and some low-level design questions. Even as the topics broadened, the tone stayed conversational. The man…

Technical Screen0
OpenTextSoftware Engineer
Reported Jul 2026

OpenText Software Engineer interview: campus online assessment

My first step was a timed online assessment. It started with multiple-choice questions and then moved into DSA coding. There were a couple of coding problems, including one like Longest Common Prefix, and the overall difficulty felt manageable. In my version, there were 15 multiple-choice questions and two DSA coding questions in a short window. It was part of campus recruitment, so it felt like…

RejectedOnline Assessment0
Ss&C Technologies HoldingsFinancial Analyst
Reported Jul 2026

Ss&C Technologies Holdings Financial Analyst interview: clipped technical screen

I did not feel much emotion during the process. It was very businesslike and clipped. They skipped the usual introduction and went straight into technical questions. When I asked questions back, the answers were extremely short, as though they were trying to keep each reply to a few words. Most of the interview was a barrage of technical checks, with perhaps one situational prompt mixed in. The p…

Technical Screen0
SIXTSoftware Engineer
Reported Jul 2026

SIXT Software Engineer interview: campus DSA cutoff

The campus drive began with an online assessment containing two medium LeetCode-style coding questions. About 20 of roughly 150 students were shortlisted for interviews. My first technical round covered time and space complexity and a medium dynamic-programming LeetCode problem. I did not make it past that first technical interview. Candidates who did move on had a second interview, and a smaller…

RejectedOnline Assessment0

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