READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 124 of 153
Interview experiences · Microsoft
Software Engineer interview at Microsoft: respectful recruiter screen
The recruiter screen was prompt and professional. The recruiter explained the role, asked about my background, and clarified expectations, so the conversation did what an early fit check should do. I did not advance or receive an offer. The process felt clear and respectful, but the experience reminded me that an early screen can still be decisive even when the conversation goes well. Location: U…
Interview experiences · Morgan Stanley
Software Engineer interview at Morgan Stanley: four-hour first in-person interview
My first in-person interview was hard mainly because I had never gone through that format before, not because the material felt impossible. I did enjoy learning about the team and the company, and I appreciated the effort the interviewers put into the conversation. The day lasted four hours. By the end, both the interviewers and the team seemed tired, and that fatigue made the experience heavier…
Interview experiences · NBCUniversal Advertising Products & Solutions
Software Engineer interview at NBCUniversal Advertising Products & Solutions: interview experience
After the exam, I went through a college-placement-style process with three interview rounds and an HR step. The second round felt most like an on-the-spot test because it combined basic programming questions with a few puzzles. The other rounds were more introductory. The flow was straightforward for me, and I felt able to answer what each interviewer asked. Location: Thanjāvūr. Overall feedback…
Interview experiences · Nevada Staffing
Software Engineer interview at Nevada Staffing: tolerance and heat transfer
After recruiter contact, I submitted a take-home test and then interviewed. The first question was about a gasket and an L bracket compressing an L gasket. It sounded simple, but I overthought the tolerances and missed the correct limit. In a second pass through the technical loop, the tone itself made things harder. The interviewer pulled specific details from my resume and then abruptly moved t…
Interview experiences · New Relic
Software Engineer interview at New Relic: delayed Portland process
After the recruiter call, I waited almost two weeks before the hiring manager scheduled the Portland interview. On that call, the manager seemed disengaged and did little to build momentum, so the conversation felt flat and uninterested in my experience. Another couple of weeks passed with no update. The recruiter eventually said the search had narrowed and they were pausing candidates, followed…
Interview experiences · Northrop Grumman
Software Engineer interview at Northrop Grumman: behavioral panel
A recruiter email laid out the early screen, including standard and role-specific questions. I then met a panel made up of a hiring manager and two tech leads. The process centered on communication and fit: they wanted STAR-style behavioral answers and kept returning to how my experience looked against the role. It was not especially technical and did not require a presentation. I mostly discusse…
Interview experiences · Northrop Grumman
Software Engineer interview at Northrop Grumman: interview experience
A quick recruiter touchpoint confirmed my background and interest, then I moved into a relaxed virtual interview with the team. It was low-pressure even while live. The interviewers seemed more interested in understanding my work than testing me, and I had room to discuss my resume and ask what the job looked like day to day. The questions were mainly behavioral and experience-based. They asked a…
Interview experiences · Ntt Data Europe & Latam
Software Engineer interview at Ntt Data Europe & Latam: interview experience
After a recruiter call, I went through two technical discussions and then an assessment round. It was professionally run and technically grounded, with interviewers who seemed clear about what they were asking. The process did not feel chaotic or excessively difficult. It felt like a fair test of how my experience matched the role. The tone stood out as much as the content. I felt comfortable fro…
Interview experiences · NTT DATA
Software Engineer interview at NTT DATA: interview experience
I went through two technical discussions and one assessment round. The structure seemed meant to confirm that I could do the work rather than repeat buzzwords. The overall atmosphere was professional and calm, and the interviewers came across as technically solid. The technical conversations followed my resume in a natural way, and the assessment did not feel like a gotcha. I felt the interviewer…
Interview experiences · Oscar Insurance
Software Engineer interview at Oscar Insurance: timed unfamiliar pattern
A recruiter contacted me a couple of days after I applied and scheduled a technical round about a week later. I had been warned that the questions would be difficult and tightly timed. That proved accurate: I had 30 minutes for a challenging pattern I had never seen before, got partway through it, and could not finish in the time box. The short window made the experience stressful from the beginn…
Interview experiences · Palo Alto Networks
Software Engineer interview at Palo Alto Networks: interview experience
I started with an online assessment and then had three virtual technical rounds. The first was a system-design-and-coding-style prompt where I implemented a solution. It soon turned into debugging existing code to fix a bug, with the focus on making the code work under constraints rather than on theory. In the final round, I had to modify the code again in an object-oriented way, changing both it…
Interview experiences · Perk
Software Engineer interview at Perk: interview experience
After recruiter outreach, I had a short HR call, but the recruiter moved quickly from question to question without much engagement or follow-up. The technical part was roughly where I expected it to be. After I finished, though, I received no feedback or clear yes-or-no answer, and my follow-ups went nowhere. I had been told to expect an email within a week if I progressed, but weeks passed witho…
Interview experiences · Plangrid
Software Engineer interview at Plangrid: React and system design
The recruiter first discussed the role, my background, and the process, which put me at ease. The hiring-manager conversation was mostly behavioral: why I chose software engineering, resume projects I was proud of, and how I approach teamwork and communication. It also included a few technical basics, including C++ and DSA. The next steps were a live React interview, system design, and culture fi…
Interview experiences · Prime Video
Software Engineer interview at Prime Video: three coding rounds
The process was predictable: three medium LeetCode coding rounds, then system design and a cultural-fit conversation. The interviewers were pleasant, and the atmosphere did not feel adversarial. Still, I saw the format as dated. I kept questioning the use of LeetCode tasks as a proxy for real engineering ability and whether the culture-fit conversation added something meaningful to the coding sig…
Interview experiences · Qualys
Software Engineer interview at Qualys: interview experience
The first technical interview mixed front-end and back-end fundamentals. React and Redux came up with Node.js, along with an output-style coding question, basic DSA, and at least one question about my project experience. The next technical round stayed in that territory with Java coding, SQL queries, design patterns, resume questions, and more React, JavaScript, and Node.js. What made the process…
Interview experiences · Robert Slack
Software Engineer interview at Robert Slack
After I applied online, I waited a while before the recruiter-led process began. I first completed a HireVue coding-and-video portion, then spoke with a recruiter about the role and next steps. I was later sent a link to schedule a meeting with the hiring manager. The later technical conversations focused more on fit and background knowledge than deep algorithms. I spoke with multiple interviewer…
Interview experiences · Rocket Lab
Software Engineer interview at Rocket Lab: Large take-home assignment followed by long silences
The process started with a recruiter reaching out, and scheduling moved quickly. I had a short phone conversation, then met with a senior software engineer and received a take-home test. I completed it promptly over the weekend and sent it back as requested. After that, everything stalled. There was no review of the submission and no clear rejection. I kept following up, but I never received a di…
Interview experiences · Rupeek
Software Engineer interview at Rupeek: DSA and system design
My SDE 3 process took about three weeks and had four rounds covering DSA and design. After an initial coding or assessment stage, I tackled medium problems such as coin change and trapping-rain-water-style questions. Another round covered Java, Spring, REST APIs, fundamentals, and design decisions. The design work included low-level design for a health-app-style scenario and high-level design for…
Interview experiences · Safran
Software Engineer interview at Safran
The interview was very technical from the start and centered on the fundamentals of elasticity. I had to work through a problem involving stress calculations for a cylindrical structure and, as best I remember, derive a related formula or theorem. My French was assessed alongside the technical material. The interview was clearly challenging, but I found it interesting because the topics were conc…
Interview experiences · Salesforce
Software Engineer interview at Salesforce: Futureforce offer
I applied to the Futureforce tech accelerator and received a HackerRank OA with two or three LeetCode questions. After about a month, I advanced and attended an online preparation presentation with engineers for the system-design discussions ahead. The interview combined behavioral discussion of projects and AI use with a LeetCode question and follow-ups. A week later, I received and accepted an…
Interview experiences · Schweitzer Engineering Laboratories
Software Engineer interview at Schweitzer Engineering Laboratories: in-person multi-part day
The process had three main stages. I started with a phone screen, then had a technical interview on Zoom, followed by an in-person day with several components rather than a single technical conversation. That in-person sequence included a security interview, a presentation, another technical interview, and a management interview. Moving among coding-style thinking, presentation, and people- and l…
Interview experiences · ServiceTitan
Software Engineer interview at ServiceTitan: slow coding sequence
After a recruiter call, I went through several straightforward coding rounds. They focused on medium LeetCode-style data structures and algorithms. The interviewers were calm and practical, asked clarifying questions, and stayed interested in how I was thinking. I cleared multiple rounds that kept testing much the same skill set, but the whole process took about a month. Several-day pauses appear…
Interview experiences · Siemens Healthineers
Software Engineer interview at Siemens Healthineers
After a recruiter call to schedule everything, I went through two virtual rounds. The first technical round covered OOPS, .NET Core, and design patterns, followed by two programming questions. One involved a stack; the other asked me to swap two variables without using a third. I tried to work through them step by step because the round felt geared toward practical engineering. The second round m…
Interview experiences · Siemens
Software Engineer interview at Siemens: interview experience
An agency recruiter set up my first interview after an initial chat. It was an online conversation with an engineering manager, and at that point the process seemed to be moving toward something more hands-on. I was told the next stage would have been an onsite, more technical interview, but I never reached it. The manager conversation itself was calm and conversational. I could explain my backgr…