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

PlangridAccount Executive
Reported Jun 2026

Plangrid Account Executive interview: strong early rounds and no follow-up

The beginning of my process was genuinely positive. People were friendly and professional, and I found the conversations engaging as I went through several rounds. I eventually gave a presentation and had a final skip-level interview with senior leadership. At that point, I felt good about how everything had gone. After that last round, the communication stopped. I waited without a clear update,…

No response0
PlangridQA Automation Engineer
Reported Jun 2026

Plangrid QA Automation Engineer interview: practical QA panel

After a recruiter call, I spoke with the hiring manager and then went to a technical panel with developers, QA, and devops. The hiring-manager conversation focused on behavioral questions. I also walked through an app I had tested and explained what they could expect from my approach. The panel was built around practical problem-solving. I got some leet-code style questions, while the group also…

0
PinterestSoftware Engineer
Reported Jun 2026

Pinterest Software Engineer interview: route reconstruction and Sparse Matrix

I expected Pinterest to be intense, but the technical interview was surprisingly light. There were only two coding questions, and both were straightforward enough that I felt a little underwhelmed afterward. One asked me to reconstruct routes from unordered travel tickets. The other was to implement a Sparse Matrix class. I had prepared with PracHub case studies, which gave me a useful structure…

Offer0
Palo Alto NetworksSoftware Engineer
Reported Jun 2026

Palo Alto Networks Software Engineer interview: three-hour mixed evaluation

I began with an online HackerRank completed on my own. Next came behavioral questions on HireVue, without video recording. A recruiter call followed with the usual request to walk through myself and similar basics, meant to confirm fit and direction before the deeper stages. The next step was the largest one. The recruiter said it would take around three hours, and that was how it played out: rou…

Online Assessment0
Oscar InsuranceSoftware Engineer
Reported Jun 2026

Oscar Insurance Software Engineer interview: technical funnel to manager screen

After I reached out on LinkedIn, a recruiter contacted me and the process followed a clean series of rounds. First came a technical phone screen. The next stage combined an algorithms-focused screen with a system-design screen, and the final step was a manager screen. Each round seemed to add another lens. It began with core technical ability, then divided into algorithms and system design, befor…

Technical Screen0
Oscar HealthSoftware Engineer
Reported Jun 2026

Oscar Health Software Engineer interview: algorithms, system design, and manager round

A recruiter contacted me on LinkedIn, and the process became three rounds. I started with a technical phone screen. The next round covered both an algorithms-style screen and system design, and the final stage was a manager screen. I would not say every detail went perfectly smoothly, but the structure held together: technical evaluation first, then a leadership conversation at the end. I was not…

Technical Screen0
Morgan StanleySoftware Engineer
Reported Jun 2026

Morgan Stanley Software Engineer interview: difficult introductory questions

My first introductory round was rough from the beginning. The questions felt difficult right away. What unsettled me was the interviewers' response: my answers did not satisfy them, and it seemed as though they wanted very specific responses instead of exploring my reasoning or allowing the discussion to develop. I could not make sense of the intent. The questioning felt as if it was constructing…

0
ProvidenceSoftware Engineer
Reported Jun 2026

Providence Software Engineer interview: three rounds and silence after onsite

My Providence process felt somewhat unstructured. There were three rounds: two virtual interviews on Teams, followed by an in-person interview at the office. The first two moved quickly, and I received feedback promptly after each one, so I had a sense of where I stood while the process was active. After the final in-person round, communication stopped. I waited a long time without hearing back,…

RejectedOnsite0
SpacexQA Engineer
Reported Jun 2026

Spacex QA Engineer interview: electrical background and mechanical questions

The call began simply enough, but it quickly became a frustrating mismatch. The questions went beyond a general introduction. I was asked what I knew about Starship, then the conversation moved into technical fundamentals. What bothered me was how my technical background seemed to be treated as irrelevant. The role description and my coursework were in electrical engineering, yet the technical qu…

0
Sii NetherlandsSoftware Engineer
Reported Jun 2026

Sii Netherlands Software Engineer interview: technical interview and quick offer

I had a very fast hiring process. First came an interview with a sales representative or business manager. The next day I had a technical interview, and by the day after that I already had an offer. The content itself was fairly conventional. What surprised me was that the role was for an external-client project, so I did not have to complete the client interview that often appears in these proce…

OfferTechnical Screen0
Sii Group ItalySoftware Engineer
Reported Jun 2026

Sii Group Italy Software Engineer interview: a fast client-project process

The process was fast and strongly oriented around the assignment. I started with a conversation with a business manager or sales representative. The next day I had a technical interview, followed immediately by another step that moved very quickly. The format surprised me because it was so conventional: direct questions centered on the role. The role was tied to a client project, but I did not ha…

OfferTechnical Screen0
SiemensSoftware Engineer
Reported Jun 2026

Siemens Software Engineer interview: technical depth and resume discussion

The Siemens process felt structured and focused on technical depth without becoming a huge drawn-out process. I went through rounds that mixed coding and probing with a manager discussion and an HR step. Throughout, the questions kept coming back to my resume. In the technical rounds, I discussed core data structures and algorithms as well as real-world problem-solving scenarios. I had to explain…

Technical Screen0
Robert HalfFinancial Analyst
Reported Jun 2026

Robert Half Financial Analyst interview: reading red flags in spending data

The recruiter-to-interview path was straightforward, and I got the impression they were moving quickly because they had several hiring needs. For the technical part, I received a spending spreadsheet for an account and had to identify patterns that might be red flags. The follow-up went past basic background questions. We covered my work history, salary expectations, and the software I had used.…

Technical Screen0
Restaurant Brands InternationalBusiness Analyst
Reported Jun 2026

Restaurant Brands International Business Analyst interview: data and project decisions

I went through a conventional process with several rounds. Some questions were specific to Restaurant Brands International, while others asked me to go deeper on my background. Early on, they wanted to know how I had used data and organized work in past projects. I was asked to describe one of the hardest projects I had handled, how I used data to get to the result I wanted, and the tools I used…

Other0
Volkswagen Group ItaliaSoftware Engineer
Reported Jun 2026

Volkswagen Group Italia Software Engineer interview: military-related work limited the fit

I did not get far. After applying, I learned that the only missions available were military-related, which immediately made the fit feel limited. I had one phone interview about my professional project, objectives, and related details. The conversation was fine, but the available work was already a blocker, so the process stopped early. Location: Paris. Overall feedback: positive. Offer status: n…

Other0
VerilySoftware Engineer
Reported Jun 2026

Verily Software Engineer interview: coding and an HR step

I applied online and then followed recruiter-driven scheduling. They reviewed my resume, explained the process, and moved me into a technical round before an HR step. The technical part matched what I expected for a software engineering interview there: coding-focused questions in the easy-to-medium range, with nothing that felt far off-script. It felt easier than processes with heavy design or d…

Technical Screen0
Veeva SystemsConsultant
Reported Jun 2026

Veeva Systems Consultant interview: behavioral and take-home case presentation

The process felt thorough and mostly well run, although it took a while. The early focus stayed on why I wanted to work there, what value I could bring, and how I presented on a case. There were multiple stages, with relatively short initial screens of around half an hour each and fairly quick feedback on whether I would move forward. Then I had a behavioral round about interactions with people a…

Take-home Project0
UST GlobalSoftware Engineer
Reported Jun 2026

UST Global Software Engineer interview: a rescheduled panel and basic coding

I expected a normal technical process and first got an HR invitation. I cleared the first technical round, but in the next round the panel said, only minutes after introductions, that it needed to be rescheduled. That made the process feel abrupt and hard to treat as a clean evaluation. A later attempt felt easier and more casual, with resume questions and basic array and hashmap coding. I felt t…

Technical Screen0
U.S. BankFinancial Analyst
Reported Jun 2026

U.S. Bank Financial Analyst interview: fit, Excel, and superday conversations

My interview path focused on fit and motivation, with enough structure that it felt clear. Early conversations with HR and a manager combined my interests with practical fit questions. We talked about real estate, my Excel skills, and which office I wanted to apply to. The later stages put the industry and my background at the center. I discussed my experience with accounting systems, where I saw…

HR Screen0
The City Of ProvidenceSoftware Engineer
Reported Jun 2026

The City Of Providence Software Engineer interview: silence after the third round

My process felt haphazard. I had three rounds: two virtual interviews on Teams and one in-person round at the office. The first two had prompt feedback, so things initially felt organized. After the third, in-person interview, I heard nothing for a long stretch. I eventually got a rejection email, and the silence beforehand was the biggest surprise. Location: Hyderābād. Overall feedback: negative…

RejectedOnsite0

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