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

IntelSoftware Engineer
Reported Jul 2026

Intel Software Engineer interview: two long office technical rounds

I began with a short hiring-manager conversation to confirm my background and logistics. Then I had two technical interviews in the office, each lasting about two hours. In the first technical round, three engineers interviewed me together. They used LeetCode-style coding questions, so I needed both a correct solution and a clear explanation of how I got there. The second technical session kept t…

Onsite0
MeeshoSoftware Engineer
Reported Jul 2026

Meesho Software Engineer interview: structured real-work questions

I applied for a Software Developer role at Meesho and went through a well-structured interview sequence, although it did not lead to an offer. The interviewers were professional and grounded, and their questions seemed tied to real engineering work rather than abstract trivia. The flow stayed organized throughout, and it was easy to engage with the team while still being pushed on relevant subjec…

Other0
J.P. MorganSoftware Engineer
Reported Jul 2026

J.P. Morgan Software Engineer interview: timed screening and panel

After applying, I took an online screening before speaking with an engineer. It combined multiple-choice questions and one coding problem to finish in about two hours. In the live rounds, DSA and OOP fundamentals remained central. The pace seemed aimed at seeing whether I could reason through normal problems rather than repeat memorized tricks. There was a deeper technical phone screen with an ex…

Online Assessment0
JohnsonSoftware Engineer
Reported Jul 2026

Johnson Software Engineer interview: unclear recruiter process

Recruiters contacted me after I applied, but the process was hard to understand from the beginning. Their conversations were direct and gave little detail about what to expect or how long things might take. After the interview, I stopped hearing anything about the role. I could not gauge whether I was progressing or whether another step was coming. It did not feel transparent, and the lack of upd…

No responseHR Screen0
JD Finish LineAccount Executive
Reported Jul 2026

JD Finish Line Account Executive interview: relaxed store conversation

I applied online, received a call to arrange an interview, and then went to the store to speak with a manager. I usually did not wait long after arriving. The manager explained the basic role before asking questions. Most discussion concerned my previous experience and customer service. I was asked why I wanted the job, what I liked about the store, my availability, and how I would handle particu…

OfferHR Screen0
IQVIABusiness Analyst
Reported Jul 2026

IQVIA Business Analyst interview: graphs, SQL, and aptitude

I had a technical, assessment-heavy process. It began with an HR or recruiter-style resume conversation, then moved to a formal technical screen focused on analytics and reasoning. I worked through line-graph analysis and puzzle-style questions. Later rounds mixed data work with logic: SQL, spreadsheet skills, Excel questions, more puzzles, and a separate aptitude test covering logical reasoning…

HR Screen0
Manpower BelgiumBusiness Analyst
Reported Jul 2026

Manpower Belgium Business Analyst interview: requirements, SQL, and OS

The interviews centered on business analysis and stayed more functional than purely technical. After the recruiter step, I had a short technical screen of around twenty minutes that moved quickly through business-analysis topics. I discussed requirement gathering and BRD-style documentation, then shifted to capital-markets fundamentals and SQL queries. The interviewer seemed to want evidence that…

HR Screen0
LuxoftSoftware Engineer
Reported Jul 2026

Luxoft Software Engineer interview: tense client-style call

The round felt tense and difficult immediately. The interviewer came across as abrasive and one-sided, spending time explaining their own points without really listening to what I said. I got through the client-style call, but it was hard to navigate. By the end, I did not feel the difficulty was simply about my performance. The communication style made the interaction harder than it needed to be…

Other0
JOHNSON HEALTH TECH TRADINGSoftware Engineer
Reported Jul 2026

JOHNSON HEALTH TECH TRADING Software Engineer interview: expected assessment

A recruiter contacted me after I applied, and the first exchange was quick and direct. I had a short phone conversation about my background and fit, and it sounded as though an assessment would follow. Then I stopped hearing anything for a while. The recruiter did not give much information about timing or the full length of the process. I waited without updates, and that uncertainty felt rough be…

No responseHR Screen0
Johnson ControlsSoftware Engineer
Reported Jul 2026

Johnson Controls Software Engineer interview: virtual manager and team

After an HR call, I interviewed with the engineering manager. That first conversation was mostly about my experience, and it felt relaxed and fluid. Soon afterward, I met three people from the team in another smooth, conversational interview. Once those rounds were done, I received an offer. Everything happened virtually, with no site visit required, which kept the path straightforward from start…

OfferHR Screen0
Johnson & JohnsonSoftware Engineer
Reported Jul 2026

Johnson & Johnson Software Engineer interview: recruiter silence

I did not find the process transparent. Getting an interview after applying was difficult, and when recruiters finally contacted me, their communication was direct but short on details. I never got a clear sense of how long the process would take. I received the invitation and completed a recruiter conversation, then things essentially went quiet. I heard nothing further about the position. The u…

No responseHR Screen0
KLASoftware Engineer
Reported Jul 2026

KLA Software Engineer interview: smooth process without feedback

The process felt unusually smooth from the start. After an initial step, they contacted me again to interview for the same role, and the flow stayed organized. During the interviews, I felt I answered every question and had not missed anything fundamental. The frustrating part came after the final interview, when I received no feedback, follow-up notes, or explanation of what happened next. Even…

0
KyndrylSoftware Engineer
Reported Jul 2026

Kyndryl Software Engineer interview: networking fundamentals

The opening screening was smooth and casual. They asked about my education and willingness to relocate, and the tone was comfortable rather than interrogative. The later interview was more direct, but the interviewer was polite and gave me space to answer without feeling rushed. Most questions covered computer-networking basics. It was not a heavy-coding exercise; they wanted to see whether I und…

OfferHR Screen0
QuantiphiSoftware Engineer
Reported Jul 2026

Quantiphi Software Engineer interview: Unstop assessment and shortlist

The process felt Unstop-driven from the start, especially for campus hiring. The online assessment had roughly 80 questions, including MCQs and a few coding tasks. I solved three coding questions in a language of my choice, and that portion felt medium to hard. Selection then moved forward according to my performance. I faced another assessment before reaching interviews. Those conversations repe…

Online Assessment0
PwC IndiaConsultant
Reported Jul 2026

PwC India Consultant interview: calm behavioral and case flow

After a recruiter conversation, I had a normal flow combining behavioral questions with a case about how I thought. The behavioral discussion was familiar: who I was, my motivations, and how I might fit the role. There were no major surprises. The case was less about arriving at a single right answer than showing my reasoning. The people I met were calm, and I did not feel grilled or blindsided b…

OfferHR Screen0
Prime VideoSoftware Engineer
Reported Jul 2026

Prime Video Software Engineer interview: four difficult global rounds

I had four one-hour interviews with people in different countries, and it was the hardest interview experience I had done. Even so, nobody was disrespectful. Everyone stayed attentive and respectful. The mix was technical and behavioral. One round covered troubleshooting, leadership-principle questions such as Bias for Action, and GenAI fluency. Another used coding problem solving tied to Deliver…

Other0
Northern TrustFinancial Analyst
Reported Jul 2026

Northern Trust Financial Analyst interview: passed stage, then silence

The process went on long enough that I lost trust in it. After what seemed to be the final stage, including an assessment day where I felt confident, I was told I had passed and was moving forward. I also completed the last interview, then communication stopped. I received no response after the final interview, including after I emailed HR and the interviewers. In another part of the timeline, I…

No responseOther0
Prudential Ins Co Of America InFinancial Analyst
Reported Jul 2026

Prudential Ins Co Of America In Financial Analyst interview: reserves and SQL

After a recruiter touchpoint, I had four interviews in total: an initial screen and three follow-ups. The process was much harder than I expected, and the interviewers wanted answers on the spot. The questions included actuarial-adjacent Financial Analyst material such as reserves and coding-style concepts. There was also a SQL segment about joins and how they are used. The technical questioning…

HR Screen0
PlangridAccount Executive
Reported Jul 2026

Plangrid Account Executive interview: next-day executive pitch

The process quickly became presentation-heavy. I met with my line manager for about an hour, then was asked to prepare a pitch presentation for a top executive the next day. The request was clear, but the short notice and the way it was handled felt extremely unprofessional. The contrast stayed with me: substantial work was required quickly, then about three months passed before I finally receive…

Other0
Palo Alto NetworksSoftware Engineer
Reported Jul 2026

Palo Alto Networks Software Engineer interview: project decisions and AI

After applying, I had a recruiter phone screen about my experience and the technologies I had used. Soon afterward, the technical discussion focused on how I had built real projects: one project in depth, the design decisions I made, and the trade-offs behind them. That conversation also included how I had considered adopting AI in my current work. Coding-related exchanges were woven into the pro…

HR 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