READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 92 of 153
Interview experiences · Motive
Motive Account Executive interview: manager discussion and a promised quick decision
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…
Interview experiences · Motive
Motive Account Executive interview: sales manager, leadership, and onboarding
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…
Interview experiences · Motorola
Motorola Software Engineer interview: month-long gap after coding case
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…
Interview experiences · Motorola Solutions
Motorola Solutions Software Engineer feedback and communication experience
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…
Interview experiences · Mphasis
Mphasis Software Engineer interview: background verification followed by rejection
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…
Interview experiences · Mphasis
Mphasis Software Engineer interview: Python rounds then client SRE and CI/CD
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/…
Interview experiences · Msft
Msft Software Engineer Interview Experience: linked list, kth largest, and URL shortener
A former colleague referred me, and the process began with a technical phone screen. The DSA questions were genuinely difficult for me. One involved reversing a linked list, and another asked for the kth largest element in an array. About a week later, I moved to an onsite. The coding round centered on system design for a scalable URL shortener.
Interview experiences · Msft
Msft Software Engineer Interview Experience: organized fit, collaboration, and technical-depth loop
After connecting with the recruiter through LinkedIn, I began with a screening call about my background and interest in the role. Once that went well, I moved into a deliberately paced loop with clear communication about the next steps. The early interviews focused on fit and collaboration before going deeper technically. A hiring-manager-style discussion covered my leadership approach, prior exp…
Interview experiences · MUFG
MUFG Financial Analyst interview: welcoming rounds followed by no response
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,…
Interview experiences · Mufg - Mitsubishi Ufj Financial Group
Mufg - Mitsubishi Ufj Financial Group Financial Analyst interview: positive rounds and no closure
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…
Interview experiences · Munich Re
Munich Re Financial Analyst Interview Experience: Half-day in-person loop
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…
Interview experiences · National Debt Relief
National Debt Relief Account Executive interview: virtual self-reflection
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…
Interview experiences · National Grid
National Grid Business Analyst interview experience: HR then hiring manager
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…
Interview experiences · National Oilwell Varco
National Oilwell Varco Software Engineer interview: calm whiteboard screen
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…
Interview experiences · Natixis
Natixis Network Engineer interview: fifteen coding problems
After a phone screen, I had two more rounds with hiring managers. The pace was fast but structured. The first two conversations were straightforward; the third was the real stamina test. That last interview was a full sheet of LeetCode-inspired coding problems: roughly fifteen questions in about forty-five minutes. Many were easier problems, but the time limit made the exercise intense. Some requ…
Interview experiences · Natoora
Natoora Data Analyst Interview Experience — Grilled on ETL and LLM Claims After Admitting No Pricing Background
The interviewer cared a lot about how real and grounded the projects on my resume were, especially the logic behind the data flow (Data Infrastructure). If you have flashy words like LangChain or LLM on your resume, you need to be ready to get asked "why didn't you just use plain SQL/Python?" Interview Process Recap The interviewer first confirmed whether I had pricing experience — I said straigh…
Interview experiences · NatWest Group
NatWest Group Software Engineer interview: delayed VAC invitation
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…
Interview experiences · NatWest Group
NatWest Group Software Engineer Interview Experience: DSA and backend discussion before HR
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…
Interview experiences · NatWest Group
NatWest Group Software Engineer interview experience
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…
Interview experiences · NatWest
NatWest Software Engineer interview: coding test, video interview and VAC timeline
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…
Interview experiences · NatWest
NatWest Software Engineer interview experience
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…
Interview experiences · Navan
Navan Account Executive interview: ranking five accounts in the presentation
My process took long enough to feel intentional and was split across three main stages. It started with a TA team call that served as a screening step, followed by time with a manager. After that, I did a practice cold-call session and then spoke with a director, which made the interview feel more real rather than purely conversational. The final stage was a presentation that brought together wha…
Interview experiences · Navan
Navan Account Executive interview with a 2 to 3 week case-study process
After a recruiter call, I moved into a manager interview about a week later, followed by a couple more conversations with sales leaders. The process lasted about 2 to 3 weeks rather than dragging on, and I spoke with several people on the sales side. Most of the questions focused on personality and fit. Themes like "tell me about yourself" came up alongside standard sales questions. For the final…
Interview experiences · Navan
Navan Account Executive interview with informal-first structure and vibe fit
My first step was a recruiter screening call that became one of the most discouraging conversations I'd had. The interviewer's delivery felt oddly automated, as if my answers weren't being heard. I'd finish a response, and they would immediately move to the next question without any reaction or follow-up. The whole thing felt pointless. The same problem showed up differently as I moved into what…