READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 95 of 153
Interview experiences · Northrop Grumman
Northrop Grumman Software Engineer interview, background and clearance questions
I had a single-round interview that felt pretty straightforward. It started with a general question about my background and career path, then moved quickly into a classic "hardest" or "most challenging task" question. I was also asked about any previous clearance and defense-related experience, which anchored the conversation. There weren't any complicated coding challenges or deep discussions of…
Interview experiences · Northrop Grumman
Northrop Grumman Software Engineer interview: quick Zoom fit check
The recruiting path was unusually quick and easy. After a short HR screen, I had one Zoom interview that ran just under an hour. I spoke with a functional manager and a senior lab member; a technical manager was meant to join but did not. The questions were light and mostly about my background and experience. I stumbled over my words at times, but no hard technical grilling followed, and I still…
Interview experiences · Northrop Grumman
Northrop Grumman Software Engineer interview with a one-hour behavioral round
I started with a recruiter introduction call, followed by a one-hour behavioral interview with a manager. The questions were fairly standard for an entry-level software engineering track, and they didn’t go deeply into complex technical trivia. There was no presentation, and the process felt organized and smooth. I spent most of the interview explaining my experience clearly and answering behavio…
Interview experiences · Northrop Grumman
Northrop Grumman Software Engineer onsite with LeetCode-style questions
I was contacted and ended up in an in-person interview focused on LeetCode-style questions. It felt more intense than the behavioral-heavy rounds I'd heard about. Once I was in the room, the interview was clearly testing problem-solving. I didn't get immediate closure afterward. A recruiter followed up and scheduled another phone conversation, so the process wasn't over right away. The format was…
Interview experiences · Northrop Grumman
Northrop Grumman Software Engineer onsite with senior engineers
I had a straightforward onsite interview in a conference room with a couple of senior engineers. The difficulty felt entry level, and the focus was on discussing my background and how I described my experience. The room dynamic stood out. The senior interviewers listened closely, and I had to explain clearly what I had worked on and how I approached engineering tasks. It was a direct, in-person c…
Interview experiences · Northrop Grumman
Northrop Grumman Software Engineer, panel with C++ and fundamentals questions
After the initial steps, I had a panel-style technical conversation with several senior engineers. It covered behavioral questions and technical fundamentals, including data structures and algorithms and databases. There was also a clear C++ focus. We discussed my past experience in the context of how I approach problem-solving, then moved into C++ fundamentals and basic scenario-based questions.…
Interview experiences · Northrop Grumman
Northrop Grumman Systems Engineer interview with panel questions
My process felt more substantial than many of the earlier easy screens I'd done. It combined technical and behavioral questions in a structured way. It started with a Microsoft Teams session where I answered questions in front of a panel. Some prompts followed the STAR format, while the technical questions connected to my past work. The technical portion included theory along with practical expla…
Interview experiences · Northwestern Mutual
Northwestern Mutual Financial Analyst recruiter process and three rounds in a week
After the recruiter touchpoint, the process was organized quickly and moved without much drama. I completed three rounds in about a week. When my schedule changed, the details were confirmed instead of becoming a source of friction. The conversations were friendly and professional. They asked about my background and education, what interested me, and what motivated me. Nothing felt like a trick q…
Interview experiences · Notion Labs
Notion Labs Software Engineer Interview Experience: fast updates and a thoughtful close
A recruiter reached out, and the process moved quickly after that. I received email updates soon after each stage, and every interviewer I met was friendly and easy to work with. The whole experience gave me the sense that candidate experience mattered to them. The recruiter call focused on logistics, but its warm and understanding tone put me at ease before the technical work. Nothing in the res…
Interview experiences · Notion Labs
Notion Labs Software Engineer interview: TypeScript team and canceled virtual onsite
The process felt scripted from the start. A recruiter matched me with a team whose role required TypeScript, even though I hadn't applied specifically to that team. After a phone screen that sounded positive, I heard nothing for two weeks, including after I followed up. When I finally heard back, I had a conversation with the hiring manager. He was surprised to learn that the technical step had a…
Interview experiences · Notion Labs
Notion Labs Software Engineer interview with practical React work
My process started with a recruiter introduction. The technical part quickly made the experience feel practical rather than gimmicky. The first live screen lasted an hour and focused on React. The problem was broken into smaller steps, so I could build the result while explaining my approach. After that, I attended a virtual onsite with more technical rounds and hands-on work tied closely to day-…
Interview experiences · Notion Labs
Notion Labs Solutions Engineer interview: technical screen and months without closure
I went into the process expecting something simple and informative. It started with a recruiter screen covering the usual background questions, my timeline, and my interest in Notion. The recruiter was straightforward and explained how the process worked. I was told I'd hear back quickly, but after that conversation I kept waiting. Silence became the main pattern after the early stages. I later r…
Interview experiences · Notion Labs
Notion Labs Solutions Engineer interview with a take-home project and panel demo
My process started with a recruiter and then moved through several formal, time-consuming technical steps. I had a hiring manager screen, a conversation with a teammate, and an extensive take-home project that ended with a panel demo. There was also an interview with the sales team. After I submitted everything, I was told I'd hear back within a few days. Instead, communication stalled. I eventua…
Interview experiences · Notion Labs
Notion Labs Solutions Engineer interview with delayed updates after the final round
My early interactions were polite, but the process dragged and became difficult to follow. I had a recruiter screen, a conversation with the hiring manager, and a product demo as part of the standard flow. The recruiter also helped me prepare for the different rounds, which was useful. What threw me off was how slow everything moved and how little I understood about where I stood. At one point, I…
Interview experiences · Notion Labs
Notion Labs Solutions Engineer onsite and presentation
My process had enough moving pieces to feel like a real campaign rather than just a couple of interviews. I started with recruiter and early screens that were fairly organized. The recruiter prepared me and kept me updated, even when the schedule slowed down because people were out of the office. After the onsite, there was an additional leadership conversation and reference checks, and the recru…
Interview experiences · NPCI
NPCI Full Stack Engineer Interview Experience: core Java, OOP, and a React question
The interview began immediately with an introduction about me, then moved into core Java and OOP fundamentals. I was asked about inheritance and how I would implement it in a small Java program. I needed to explain the code clearly, including what it did and how its pieces worked together. The discussion went deeper into Java-internals topics. I was asked about the diamond problem and how HashMap…
Interview experiences · NTT DATA
NTT DATA Consultant interview: offer that did not meet expectations
HR contacted me within about a day of my application, and we aligned on the role and the team's needs. About a week later, I had an interview that was transparent about the position and expectations. They asked about relevant experience and used a practical case to assess my strategic and analytical thinking. The difficulty felt manageable and depended more on clear communication than trying to c…
Interview experiences · Ntt Data Europe & Latam
Ntt Data Europe & Latam Consultant interview: same-day offer declined
HR reached out quickly after I applied, and the process had a clear timeline. About a week later, I had the main interview discussions. The interviewers were transparent about the role and what the team needed, and I came away feeling that they were mapping my background directly to the team's priorities. The rounds combined case solving with behavioral conversations. The cases called for familia…
Interview experiences · Ntt Data Europe & Latam
Ntt Data Europe & Latam Software Engineer interview: confusing graduate assessment-centre timing
I attended a graduate assessment centre arranged as a group interview, and the logistics overshadowed everything else. I was told to be there at 8:45 for a 9:00 start, but no one was at the front desk for a while. Around 9:10, I was still waiting with no clear guidance. At the introduction, I learned that the assessment was actually scheduled for 9:30, so I had effectively been asked to arrive 45…
Interview experiences · Ntt Data Europe & Latam
Ntt Data Europe & Latam Software Engineer interview: foundations and projects
The technical interview began with an introduction and moved into practical topics from my background. We discussed version control and GitHub, HTTP basics, database management, prompt engineering, and a project I had worked on. The material was moderately straightforward, although the interviewer's framing was not always clear about what they wanted me to answer. Even so, the direction stayed te…
Interview experiences · NTT DATA
NTT DATA Software Engineer interview: graduate assessment-centre logistics
The interview itself was not technically difficult, but the logistics threw me off immediately. I attended a graduate assessment centre scheduled to begin at 9:00 and was told to arrive early. At about 9:10, I was still waiting at the front desk with no staff in sight. During the introduction, I learned that the session was actually supposed to start later, around 9:30, and that the expected arri…
Interview experiences · NTT DATA
NTT DATA Software Engineer interview: unclear Java questions
The technical interview leaned heavily on Java and software fundamentals. I expected clear, role-focused questions, but the interviewer was not always clear about what was being asked, so it was hard to judge how much detail an answer needed. The conversation also covered version control and GitHub, HTTP basics, database management, a project I had worked on, and other practical experience. That…
Interview experiences · Nubank
Nubank Senior Software Engineer Interview Experience — Chargeback Ingestion and a Database Read Bottleneck
Problem: Design a Chargeback Ingestion System Design a system that processes card chargeback/dispute transactions. The system receives chargeback-related transaction events, validates and deduplicates them, tracks their processing state, persists them, and eventually exports eligible transactions into CSV files. These CSV files must be sent to Mastercard via FTP/SFTP. The difficulty felt all righ…
Interview experiences · Nuro
Nuro Data Scientist Interview Experience — Merging Overlapping Vehicle-Run Intervals in SQL and Python
Dataset description The dataset had several fields: set id, run id, start time, end time, and set number. The set ids ran from 1 to 6 and represented different recorded segments from autonomous-vehicle sessions. For example, set 1 was about 30 seconds long, set 2 was 23 seconds, set 3 was 19 seconds, and so on. The run id identified the trip. It used a time-string format such as 20250101_122334,…