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

ADCI - KarnatakaSoftware Engineer
Reported Jun 2026

ADCI - Karnataka Software Engineer Interview Experience: four back-to-back onsite rounds

After the initial recruiter interactions, I had an onsite loop with four back-to-back rounds in one day. It was intense but clearly structured: two coding-heavy rounds with senior engineers, one hiring-manager round, and one behavioral round with a bar raiser. Leadership principles and data-structures topics appeared repeatedly through the day, so I could not really separate the behavioral piece…

Onsite0
IQVIAConsultant
Reported Jun 2026

IQVIA Consultant Interview Experience: interview content overshadowed by inconsistent follow-through

What I remember most is the chaos around the process rather than the questions. After recruiter contact, scheduling took weeks of chasing, and the call eventually ran late. It ended positively, with an indication that I would move forward once the team returned from vacation. After that came a long run of generic follow-ups that did not explain what was happening. The process included recruiter a…

Online Assessment0
MiraklAccount Executive
Reported Jun 2026

Mirakl Account Executive Interview Experience: AI video, HR, manager, and team fit

The process began in an unexpected way: my first step was a video interview with an AI. It served as an early check on whether my motivations made sense and whether my story was coherent. I then had a more traditional HR qualification conversation about my profile and skills. Next I spoke with my future manager in a more strategic discussion. We covered my ability to build automation systems and…

OfferHR Screen0
Milwaukee ToolSoftware Engineer
Reported Jun 2026

Milwaukee Tool Software Engineer Interview Experience: one manager conversation and no follow-up

I had one interview, a conversation with an engineering manager about the role and where I would fit. It went well enough that they said they would reach out to continue the process, but I never heard anything after that. I did not follow up because I had already decided I was not very interested in continuing. The experience felt unfinished, as if I had been left mid-stream instead of formally r…

No responseOther0
Manpower BelgiumSoftware Engineer
Reported Jun 2026

Manpower Belgium Software Engineer Interview Experience: broad fundamentals amid poor scheduling

The interviews focused on fundamentals, although the process quality did not feel great. The technical rounds began with detailed questions from my resume about projects, internships, and technical contributions. From there, the discussion expanded into OOP, data structures and algorithms, and language-specific concepts. On the backend, I was asked about APIs, databases, server-side architecture,…

OfferTechnical Screen0
LtimindtreeSoftware Engineer
Reported Jun 2026

Ltimindtree Software Engineer Interview Experience: a hands-on Java coding session

The interview began directly with technical questions. I shared my screen and wrote code in a simple editor during a session that lasted about half an hour. The pressure came from having to work hands-on rather than only talk through theory. The focus was Java fundamentals in a deeper, practical form. I covered Java concurrency and transaction handling, then OOP and core Java. There were under-th…

Technical Screen0
Koch Minerals & TradingFinancial Analyst
Reported Jun 2026

Koch Minerals & Trading Financial Analyst Interview Experience: fit and communication over technical depth

The rounds felt designed to test fit and how I expressed myself more than raw technical knowledge. The office was very professional, and the interviewers were respectful and welcoming. Still, the questions made me feel they were looking for something specific in the kind of analyst I would be. Behavioral prompts were a large part of the process. I described situations I had handled in ways that a…

0
KochFinancial Analyst
Reported Jun 2026

Koch Financial Analyst Interview Experience: values, behavioral examples, and English

The process began with a recruiter touchpoint, followed soon by a technical screen that surprised me because it did not focus much on hard technical questions. Most of it was behavioral. It felt as though the interviewers were looking for something very specific, although I could not tell exactly what they were targeting. Later conversations included many questions about company values. The conve…

Technical Screen0
Jones Lang LaSalleFinancial Analyst
Reported Jun 2026

Jones Lang LaSalle Financial Analyst Interview Experience: a one-hour fit-focused meeting

After applying through the company portal, I was shortlisted and heard from HR fairly quickly. The face-to-face stage moved fast after that. HR scheduled an in-person interview with a finance manager and director. It took about an hour and felt straightforward rather than especially technical. Most questions were behavioral and tied to my past experiences. They wanted to understand how I had hand…

Onsite0
LazardBusiness Analyst
Reported Jun 2026

Lazard Business Analyst Interview Experience: two short alignment conversations

I started with a short recruiter chat, about half an hour, about my background and why I was interested in the firm. The recruiter also asked whether I intended to relocate. It felt like a quick alignment conversation rather than a deep technical screen. About a week later, I had another half-hour discussion with a portfolio manager. We again covered my background and motivation, then moved into…

Other0
Red HatSoftware Engineer
Reported Jun 2026

Red Hat Software Engineer Interview Experience: four rounds disrupted by scheduling

A recruiter contacted me quickly after I applied, but reaching them afterward was frustrating. Once I was scheduled, the process became chaotic because scheduling was the biggest source of stress. I had four interviews: a hiring-manager call, two technical discussions, and a coding round. I had given availability for a week, and the schedule was set around it. Then my final-round interview was mo…

Technical Screen0
QuantiphiMachine Learning Engineer
Reported Jun 2026

Quantiphi Machine Learning Engineer Interview Experience: two theoretical modeling rounds

I had two rounds, and both were theoretical rather than hands-on coding. The first covered time-series and classification concepts, including deeper ML topics. I spent most of the time explaining my understanding and reasoning through how ideas applied instead of simply defining terms. The second round stayed in that same territory but felt more architectural. The questions explored how I think a…

Technical Screen0
Prime VideoSoftware Engineer
Reported Jun 2026

Prime Video Software Engineer Interview Experience: broad fundamentals and leadership themes

The process had a looping structure. It began with an online assessment, then moved through data structures and algorithms, basic OOP and DBMS concepts, and Amazon leadership principles. There was also an HR interview and a low-level design component, so the process covered a broad mix rather than one narrow subject. I learned about the steps as things progressed. The leadership-principle part st…

Online Assessment0
Prime VideoSoftware Engineer
Reported Jun 2026

Prime Video Software Engineer Interview Experience: high-pressure coding and design rounds

I began with a LeetCode-style coding round and solved two DSA problems, one medium and one hard. I had to explain my thinking, cover edge cases, and give time and space complexity. The interviewer kept asking about alternative approaches and the trade-offs behind them. Next came system design. I worked through a problem resembling a scaled Amazon-style service and discussed API design, data model…

Other0
Prime VideoSoftware Engineer
Reported Jun 2026

Prime Video Software Engineer Interview Experience: leadership, coding, and system design

After applying, I completed an online assessment and then spoke with a recruiter. About a week later, I entered an onsite loop. From the assessment through the final decision, the process took roughly a few months. The loop had multiple back-to-back rounds in one day, mixing technical and behavioral evaluation. Early on, the bar raiser focused on Amazon-style leadership principles. I used STAR-st…

Online Assessment0
Prime VideoNetwork Engineer
Reported Jun 2026

Prime Video Network Engineer Interview Experience: opaque online tasks without an offer

After applying, I went through something that did not resemble a traditional interview. I was told I would be "successful" after completing a set of tasks, but the process mostly involved online work, watching videos, and answering questions. There was no clear, standard interview to prepare for in the usual way. Feedback itself came fairly quickly. A few days later, I got an email saying I had b…

0
NPCIFull Stack Engineer
Reported Jun 2026

NPCI Full Stack Engineer Interview Experience: core Java, OOP, and a React question

The interview began immediately with an introduction about me, then moved into core Java and OOP fundamentals. I was asked about inheritance and how I would implement it in a small Java program. I needed to explain the code clearly, including what it did and how its pieces worked together. The discussion went deeper into Java-internals topics. I was asked about the diamond problem and how HashMap…

Technical Screen0
RBCSoftware Engineer
Reported Jun 2026

RBC Software Engineer Interview Experience: an easy behavioral interview without closure

The process was simpler than I expected. It started with a roughly 30-minute behavioral interview and situational questions that were not especially difficult. I was told I would hear about my application status within a week. Almost two weeks passed without an update, so I sent a follow-up email thanking them and asking about timing. That email was not answered either. I ended up without closure…

No responseOther0
Nyc StaffingSoftware Engineer
Reported Jun 2026

Nyc Staffing Software Engineer Interview Experience: a mobile role with mismatched screening

My recruiter screen was about a week after I applied and felt generic. They asked a couple of questions about my resume but gave little detail beyond the posting. I then shared availability for a hiring-manager round that was scheduled about two weeks away. What I heard about the hiring manager made me think I would be a strong fit. A few days later, I was asked to arrange a technical screen. Aft…

Technical Screen0
New RelicSoftware Engineer
Reported Jun 2026

New Relic Software Engineer Interview Experience: good rounds followed by silence

The early part moved quickly. I had technical rounds that went well in a single day, then a hiring-manager conversation a few days later. That conversation felt positive, and communication during it was easy and on track. What threw me off was everything afterward. HR went quiet, and when I messaged, I got nothing back. After about a week of silence, I wanted feedback, even negative feedback, bec…

No responseTechnical 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