READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 93 of 153
Interview experiences · Navan
Navan Account Executive two-slide client case presentation
My interview process combined live discussions with a final case exercise. I started with an HR conversation, then met with the team and had additional conversations with managers. People were engaged, and the discussions focused on how I thought through situations. The main challenge was a case round. I had to write a client-style response and then present Navan using two slides. I had to turn t…
Interview experiences · Navan
Navan Senior Software Engineer interview with a flight aggregation LLD round
I went through a compact two-round process for a Senior Software Engineer role, and it ended in a rejection. The first step was an online assessment with two medium-level questions, and I had to use Java. After that, I moved to a low-level design round. The language requirements were strict there too: Java for part of the interview and Java or Golang for another part. The main prompt involved des…
Interview experiences · Navan
Navan Software Engineer: four-interview onsite for a fullstack role
I went through a fairly structured sequence for a fullstack role. After the earlier steps, I had a frontend-focused round, then a hiring manager discussion, and eventually an onsite with multiple interviews. The frontend round focused specifically on that part of the stack, while the hiring manager conversation centered on my experience and how it matched the role. The onsite was the longest part…
Interview experiences · Navan
Navan Software Engineer hiring manager conversation
My experience started with a conversation with the hiring manager, and it immediately felt off. I was asked to walk through my experience, but as soon as I began describing projects, she wanted to hear about a different project from my resume. I tried to adjust, but she seemed impatient and kept interrupting instead of letting me finish. As the call went on, I felt increasingly uncomfortable, lik…
Interview experiences · Navan
Navan Software Engineer interview with a 20-minute AI round
My first interaction used AI and felt jarringly different from a normal recruiter screen. The timer was set to 20 minutes, and it cut me off exactly at the limit even though I hadn't finished my answer. I remember thinking the pacing punished me more than it tested my actual understanding. I also wished there had been a typical early conversation with a recruiter to provide some context and make…
Interview experiences · Navan
Navan Software Engineer interview with CoderPad live coding and a one-hour manager round
After a recruiter call, I had about a week before the next step, which was a technical screen. It was a live coding session on CoderPad, where I worked through a LeetCode-style problem. The setup felt like solving the problem live while the clock was running, so I focused on reaching a correct solution instead of trying to make it fancy. I then moved to a hiring manager round that lasted about an…
Interview experiences · NBCUniversal
NBCUniversal Marketing Analytics Specialist interview: a promising start and silence
A recruiter contacted me, and I moved straight into first-round interviews. The conversations felt good, with nothing awkward, and I came away optimistic. Then communication stopped. I waited, followed up and still received no reply. I began to wonder whether the role was no longer moving forward or the process had stalled internally. The smooth beginning made the ending feel anticlimactic. I nev…
Interview experiences · NCS
NCS Software Engineer interview: campus coding test and deeper systems discussion
I was brought into an on-campus opportunity with an exam-like format. The technical round had MCQs and two coding questions, and I could choose Python, Java, C, or C++. It seemed to test basic coding speed and structured problem solving. Next came a face-to-face technical interview with senior people. They asked deeper questions and indicated that some backgrounds would require reasoning about sy…
Interview experiences · NeoSOFT
NeoSOFT Software Engineer interview: coding and client discussion
The NeoSOFT process moved through aptitude, coding, a managerial round, and HR. The coding questions were practical algorithm exercises: reverse a string without built-in methods, test for a palindrome, find duplicates, get the second-largest element, generate Fibonacci numbers, and remove duplicate array values. The interviewer was supportive and kept the conversation professional. I also went t…
Interview experiences · NeoSOFT
NeoSOFT Software Engineer Interview Experience: challenging technical discussion with clear HR communication
The process was positive and well communicated from start to finish. After the recruiter conversation, the technical discussion came a little later. It was challenging without being harsh. The interviewer was kind, asked questions grounded in real experience, and explained how the answers would matter in the work. HR communication also stood out. It was clear and responsive, without the awkward g…
Interview experiences · NetApp
NetApp System Software Engineer Interview Experience — A 45-Minute C/C++ and OS Assessment
Job description NetApp's flagship storage operating system. C, C++, and Unix/Linux system programming are required. Familiarity with the design and development of system software. A strong understanding of operating-system internals. Personal background I worked in China from 2018 through 2025, then came to Ireland for a master's degree in 2025. I have about six years of work experience, so I am…
Interview experiences · Netflix
Netflix Data Scientist Interview Experience — 11 Rounds, 10 People, and a Hiring Manager Swapped Mid-Loop
I just got an early update from the recruiter. The email said they're still gathering information, but unfortunately it's "not a perfect fit." I did 11 rounds in total and met 10 people. The whole process was absolutely ridiculous, spanning a full two and a half months. Referral HR screening: Netflix culture, personal background, why I'm job hunting First technical round: pure SQL, had to actuall…
Interview experiences · Netflix
Netflix Data Scientist Interview Experience — Eleven Rounds, Two and a Half Months, and a Hiring Manager Swap
I just got an early update from the recruiter. The email said they're still gathering information, but "not a perfect fit, unfortunately." I interviewed 11 times total, met with 10 different people, and the whole process was absurd — it dragged on for two and a half months. Referral HR screening: Netflix culture, my background, why I'm job hunting First technical round: pure SQL, had to actually…
Interview experiences · Netflix
Netflix Intern Data Scientist Interview Experience — A 75-Minute Causal Inference OA That Left Me Guessing
New here, and internships are so hard to find. This is the second OA I've gotten after countless mass applications, and long story short, it's been two weeks with no response so I'm assuming it's dead. The whole thing was about 75 minutes and had to be completed within a week. First there were two coding questions, and you could use Python or R — both coding questions were under the same setting.…
Interview experiences · Netflix
Netflix Intern Machine Learning Engineer Interview Experience — 90-Minute OA With 4 MC and 2 Coding Questions
I just finished the Netflix MLE Intern OA. It was timed at 90 minutes, with 6 questions total: 4 multiple choice and 2 coding. Below are the topics I remember. I don't fully remember the exact wording or details anymore, but I hope this helps others preparing for the same OA. The multiple choice questions were fairly basic overall. The topics I can recall: Bayes' formula; simple calculations invo…
Interview experiences · Netflix
Netflix Senior Software Engineer Interview Experience — Onsite Loop in the Ads Org: Topo Sort, System Design, and Two BQs
I passed this earlier this year, for the Ads department, which has been pretty popular lately. Since I'm planning to accept the offer, I'm not going to post the specific questions — search for the last three months of posts here and you'll find they're almost all the same type. I'll share some experience and feelings that I hope will be useful. Process-wise: they got back to me 1 day after the ph…
Interview experiences · Netflix
Netflix Senior+ Software Engineer Interview Experience — Four Onsite Rounds on the Ads Team, Then Ghosted During a Freeze
Posting to share my interview experience with a different team on the Ads side, hoping it brings me some luck. It's been two weeks since I finished interviewing and I've been ghosted — no message at all from HR, so it's probably just gone into a black hole. First, I asked if I could interview for Staff, but HR firmly said no, telling me that an outside L6 is an L5 here, and that I'd have a chance…
Interview experiences · Netflix
Netflix Software Engineer Interview Experience — An Open-Book Coding Screen That Still Ended in Rejection
I interviewed for the Member team — it was basically an open-book style interview, similar to a couple of other phone screen reports I'd seen. Problem Solving: Netflix homepage content dedup — for each row, the first n titles need to be deduplicated globally; after position n+1, you only need to make sure there's no duplicate within that row itself. Follow-ups: 1. what if n is different for each…
Interview experiences · Netflix
Netflix Software Engineer Interview Experience — Data Platform Loop, Rejected After the Final System Design Round
I think the team I interviewed for was data platform. A recruiter reached out because I had related experience a few years ago. From other posts I used to think the problem solving round and the coding round were different, but after going through it they feel like essentially the same thing. Netflix's interview process is very long, and different teams probably test different things, so you need…
Interview experiences · Netflix
Netflix Software Engineer Interview Experience — Passed VO1 With a Billboard Rotation Coding Round and an ML Job Scheduler System Design
Netflix's VO (virtual onsite) has two rounds — VO1 and VO2. VO1 is more general. VO2 leans into stuff related to the specific team you're interviewing with. I'll share VO1 here. Coding: movie billboard rotation. Don't use a heap — use two treemaps. Two followups total: 1) multi-threading, 2) how you'd scale it in production and how you'd store/access the data. SD: schedule ML jobs. The main point…
Interview experiences · Netflix
Netflix Software Engineer Interview Experience — Two Back-to-Back Coding Rounds and a No-Feedback Rejection
The questions were different from every interview report I had seen. There were two back-to-back interviews. First phone round — problem solving: Question: The ping times between cities are different. Starting from one city, find the fastest paths for broadcasting to every other city. Solution: Dijkstra's algorithm. Follow-up: If the ping times keep changing, how should the paths be updated? Solu…
Interview experiences · Netflix
Netflix Software Engineer Interview Experience — Two BQ Rounds Left Me With No Signal
Just finished my interview. L5 SDE, Ads team, onsite. Coding: Not a LeetCode problem, but it's basically a Tree DFS problem underneath. Not too hard, but remember to write your own code and actually test it yourself. SD: Ad frequency cap — a classic. DM: Demand-side table. Also a classic — the usual set of tables: advertiser / campaign / ad group / ad. BQ1: Honestly I couldn't really tell what ki…
Interview experiences · Netflix
Netflix Software Engineer Interview Experience — Two Phone Screens, Then a Week of Silence Before Rejection
Rejected. It doesn't feel like a hard fail — after the interview it took about a week to hear back, and when I followed up, HR said they were syncing up with the team, and in the end told me they were moving on with other candidates. My own sense is that I didn't perform badly, but definitely not perfectly — there were various small issues where I didn't give the optimal answer right away, or I m…
Interview experiences · Netflix
Netflix Software Engineer interview: seven interviews over more than two months
My Netflix Software Engineer process took a little more than two months from applying to accepting an offer. What surprised me was the number of steps. I went through seven interviews, a mix of technical rounds and behavioral conversations, so it felt like a long, involved process rather than a quick loop. The technical side covered coding and systems design style thinking. The difficulty felt hi…