real interview stories, told over a cup of tea ♡
Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
3935 results
- ML Infra Loop With Misleading Prep, No OfferSnapchat · Software Engineer · Onsite · Jul 2026Rejected
I interviewed for Snap SDE ML infra in September. Posting my rejection story as a reference for whoever comes after. Phone screen: an unusual problem, data stream processing. Every incoming data point can be stored into a stored cluster (you decide from the data itself whether it belongs to an existing cluster or is the first data point of a new cluster). You also have to implement a function tha…
- ML Infra Questions, Not a MatchTower · Machine Learning Engineer · Technical Screen · Jul 2026Rejected
After getting rejected at the QR stage earlier, I got picked up by another MLE team. Through this I also learned a bit about how some quant firms work: different teams (pods) seem to hire independently, and the teams share one company-wide infra while their strategies are isolated from each other. The title for this role was MLE, but it actually sounded more like they needed someone for ML infra…
- Molex Software Engineer three-step fundamentals and resume interviewMolex · Software Engineer · Technical Screen · Jul 2026
After I was shortlisted, I went through three stages: a technical round, an advanced technical round, and an HR conversation. Every stage came back to engineering fundamentals and my resume. How I explained my work and approached a problem seemed to matter as much as the answer itself. The technical rounds were tied to my projects, tools, and claimed skills rather than random puzzles. They felt a…
- monday Account Executive interview: scheduling and stalled follow-upmonday · Account Executive · HR Screen · Jul 2026
The recruiter call focused on my background, especially selling into the Israeli market, the clients I had worked with, and my day-to-day sales process. Scheduling was difficult because the HR representative offered narrow time slots while very busy. I tried to work around that, including a very late WhatsApp attempt to connect and a last-minute message that she was sick. After the call, the proc…
- monday Software Engineer interview: feedback through system designmonday · Software Engineer · Technical Screen · Jul 2026Rejected
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…
- monday Software Engineer interview: notification coding roundsmonday · Software Engineer · Technical Screen · Jul 2026
After a recruiter call, I completed a video technical interview in their coding interface. I had to simulate push notifications to teammates by implementing functions, running the code, and checking the output with dummy input. The next coding round also involved notifications, this time preventing duplicate notifications from reaching subscribers. I got a working straightforward solution, but a…
- MongoDB Account Executive Interview Experience: clear recruiter expectationsMongoDB · Account Executive · HR Screen · Jul 2026
The recruiter call set clear expectations about the timing and what came next. The interviewers were nice and direct, and I felt they were helping me understand the process rather than simply describing the job. The conversations fit what I expected for the market and role, and the compensation discussion was consistent with other companies I had considered. I was pleasantly surprised by how atta…
- MongoDB Software Engineer Interview Experience: live coding, database troubleshooting, and LinuxMongoDB · Software Engineer · HR Screen · Jul 2026
After a recruiter conversation about my background and skills, I had a technical round with live coding and deeper questions about problem solving and ambiguity. The process later switched modes with a team-lead-style discussion about troubleshooting scenarios, including how I would diagnose a slow database. There were several in-depth technical interviews on databases, Linux, and other areas lis…
- MongoDB Software Engineer interview: Karat screen and inconsistent next stepsMongoDB · Software Engineer · Technical Screen · Jul 2026Rejected
I began with a recruiter conversation and then went straight to a Karat technical interview. The Karat portion had only a small number of questions, but it was clearly a serious gate. Mine focused on LeetCode-style problems, and I did not pass that stage. What disappointed me was that the process did not end immediately after Karat. Another technical round was still scheduled, which made the flow…
- Moody's Software Engineer delayed-feedback interview experienceMoody's · Software Engineer · Jul 2026Rejected
The interview itself felt productive and well matched to my background. It was scheduled for June 9. Communication afterward fell apart. I had no update for several weeks and tried reaching HR by phone multiple times without a response. After I followed up by text with an HR representative on July 3, I was told that I had not been shortlisted. The result was disappointing, but the lack of timely…
- Moody's Software Engineer Interview Experience: unclear AWS-heavy office interviewMoody's · Software Engineer · Onsite · Jul 2026
I was asked to attend an interview at the office, but the questions did not seem relevant to what I understood the role to require. Much of the discussion felt textbook-like, and I could not tell what the interview was actually trying to evaluate. They focused on how AWS works internally and on specific steps, but the phrasing made it hard to connect my answers to the expected skills. I did not g…
- Moody's Software Engineer interview: interval DSA, AWS, and manager interruptionsMoody's · Software Engineer · Technical Screen · Jul 2026
My first interview began with a LeetCode-style DSA problem about intervals that felt medium to hard. We also discussed AWS concepts including ECS, ECR, Lambda, and Step Functions, so it was not purely abstract coding. The next stage was with the hiring manager. I expected a normal discussion of my projects, but the manager quickly drove the conversation toward the answers he wanted. He cut me off…
- Morgan Stanley Financial Analyst interview: timed fit and finance promptsMorgan Stanley · Financial Analyst · Other · Jul 2026
After applying, I started with a HireVue that was mostly behavioral. I had to think on my feet within the time set for each question. A recruiter-style call followed and felt more focused on understanding me than on deep technical testing. The next round involved senior people and mixed behavioral questions with finance context and light technical reasoning. I had to explain my thinking aloud. On…
- Motive Account Executive interview: manager discussion and a promised quick decisionMotive · Account Executive · Other · Jul 2026Offer
After an initial screening call, I spoke with a sales development manager. The recruiter said I should hear a decision within about 24 hours. A third interview would follow if I advanced. The sequence felt clear and tightly organized: screen, manager, then potentially one more round. The speed and how much each step mattered made it feel difficult, even though the process was straightforward. I h…
- Motive Account Executive interview: sales manager, leadership, and onboardingMotive · Account Executive · Other · Jul 2026Offer
My process had three main rounds. I started with an internal recruiter, then had the important second round with a sales manager. That stage felt decisive for whether I advanced. The final round was with senior leadership and focused more on culture and fit than anything overly technical. The timeline was longer than I expected. I was told the entire hiring process could take around a month becau…
- Motorola Software Engineer interview: month-long gap after coding caseMotorola · Software Engineer · Technical Screen · Jul 2026
I started with a LeetCode-style technical case. It took about a month before HR contacted me, then I had a technical interview with my possible manager. The process was direct and meant to assess both practical ability and a discussion about the day-to-day role. I did not receive an offer. What I remember most is the long wait between the case and HR, which made the middle of the process feel slo…
- Motorola Solutions Software Engineer feedback and communication experienceMotorola Solutions · Software Engineer · Jul 2026Rejected
At first, the process seemed to be moving in a reasonable direction and I thought the interview would give me momentum. Still, the outcome did not match how I experienced those early stages: I was not selected. I later understood that the decision involved communication skills and some missing technical skills. The harder part was the feedback process. After interviews, I chased updates through a…
- Mphasis Software Engineer interview: background verification followed by rejectionMphasis · Software Engineer · Jul 2026Rejected
I had a client-side interview and moved into background verification the next day. A few days later, the consulting firm told me that my profile had been rejected. That was disappointing because I had already cleared a stage that suggested progress. By the time I learned the decision, there was little room for clarification, only the message that I was not moving forward. I never received an offe…
- Mphasis Software Engineer interview: Python rounds then client SRE and CI/CDMphasis · Software Engineer · Technical Screen · Jul 2026
My process had a focused sequence of rounds. First, I had a technical interview with Python questions ranging from basic to advanced, and I cleared it. A second Python-focused round followed the same basic-to-advanced pattern, and I cleared that one too. The client round was completely different. It did not include Python questions. Instead, the client focused on site reliability concepts and CI/…
- Mufg - Mitsubishi Ufj Financial Group Financial Analyst interview: positive rounds and no closureMufg - Mitsubishi Ufj Financial Group · Financial Analyst · Onsite · Jul 2026Rejected
The process felt pleasant while it was happening, but the ending left a bad taste. After applying online, I went through in-person or online conversations with several senior interviewers. The onsite experience in particular felt warm, with friendly people focused more on fit than hard technical questioning. I discussed my background and how I matched the role. Even across VP or MD-level conversa…
- MUFG Financial Analyst interview: welcoming rounds followed by no responseMUFG · Financial Analyst · Jul 2026Rejected
I applied online and moved into interviews fairly quickly, but the process ended with a lot of silence. The later conversations were welcoming and centered on fit and behavioral questions. At one point I met several senior interviewers together, and it felt more like checking whether my background matched the role than an interrogation. The difficult part was the follow-through. After the rounds,…
- Munich Re Financial Analyst Interview Experience: Half-day in-person loopMunich Re · Financial Analyst · Jul 2026Offer
After a recruiter call, I waited about a week for a technical screen grounded in the work and how I would approach it. The process then moved to an in-person track: a direct point of contact followed by interviews with peers and managers. The office portion lasted about half a day and included lunch, which was a pleasant surprise. The interviews were organized and professional without being overl…
- National Debt Relief Account Executive interview: virtual self-reflectionNational Debt Relief · Account Executive · HR Screen · Jul 2026
My virtual interviews took place in two steps, beginning with a recruiter-style conversation and continuing to a second round. The first part was standard: questions about me professionally, my strongest attributes, and how I handled failure or falling short. The second interview kept the same focus on my work history and how I reflected on mistakes. The second interview started about half an hou…
- National Grid Business Analyst interview experience: HR then hiring managerNational Grid · Business Analyst · HR Screen · Jul 2026Offer
I had a straightforward interview process. My first conversation was with an HR representative. They were very formal, and that initial discussion did not get into technical questions. The technical part began in the second round, when I met the hiring manager. I did not have any peer interviews at all. Overall, the sequence felt simple and linear, rather than an assessment of my skills by severa…
- National Oilwell Varco Software Engineer interview: calm whiteboard screenNational Oilwell Varco · Software Engineer · Other · Jul 2026
A recruiter conversation set expectations and made the process feel systematic. I received detailed information in advance and the interviews did not feel pressurized. The overall timeline seemed likely to run about one or two months. An early Zoom screen covered basics and me as a person: school or curriculum background, research interests, extracurriculars, and personality-style questions. A la…
- NatWest Group Software Engineer interview experienceNatWest Group · Software Engineer · Technical Screen · Jul 2026
A recruiter contacted me on LinkedIn and arranged a short technical discussion with two people. One interviewer gave a brief company introduction, then the conversation moved straight to technical questions with little discussion of my background. The other asked extensively about Java, thread safety, reactive paradigms, data structures, and cloud topics. The format threw me off. The interviewers…
- NatWest Group Software Engineer Interview Experience: DSA and backend discussion before HRNatWest Group · Software Engineer · Technical Screen · Jul 2026Offer
After recruiter outreach, I had an initial video technical discussion with two interviewers. One focused more on DSA-style questions, and the other on a particular backend topic. The conversation sometimes felt detached, but the goal was clear: work through coding fundamentals and then go deeper on data structures and related backend ideas. I remember bringing the usual laptop and setup into a pr…
- NatWest Group Software Engineer interview: delayed VAC invitationNatWest Group · Software Engineer · Online Assessment · Jul 2026Offer
The assessment was fairly straightforward, and the coding felt manageable. The video interview mattered most to me. I didn't hear back a week or so after finishing the test; the invitation for the VAC came much later, after roughly six weeks. Once it was scheduled, the VAC moved quickly. The video questions focused on my background and how I approached problems. It didn't feel like harsh technica…
- NatWest Software Engineer interview experienceNatWest · Software Engineer · Technical Screen · Jul 2026
A recruiter reached out on LinkedIn and set up an initial technical discussion of about 30 minutes with two people. One gave a short company introduction, then the questions began without much time for a personal introduction. The other interviewer asked a dense set of questions on Java, thread safety, reactive paradigms, data structures, and cloud topics. The atmosphere felt cold and detached. T…
- NatWest Software Engineer interview: coding test, video interview and VAC timelineNatWest · Software Engineer · Online Assessment · Jul 2026Offer
I took a coding test and then moved to a video interview, which felt like the most important part of the process. The coding portion was described as fairly simple. By the time I recorded and answered the video interview, I felt better prepared because I could practice first. VAC was also mentioned and seemed straightforward if I had prepared. I did not hear much right after the test. About 1.5 m…
