READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 94 of 153
Interview experiences · Netskope
Netskope Software Engineer selection update followed by four-week delay
Things began quickly. Talent acquisition called me about an opening, I applied right away, and I was given interview slots. The interviews felt good, friendly, and positive. Afterward I was told that I had been selected and was asked for details, but communication stalled. More than four weeks passed. When I emailed about offer paperwork, I was only given new dates. The delay stopped feeling like…
Interview experiences · Nevada Staffing
Nevada Staffing Software Engineer interview: Python, RAG, and AI focus
My process began with a recruiter call, then my profile was selected for a formal interview stage. The role description centered on Python, retrieval-augmented generation, and AI, and the interviews followed that technical direction. I had two technical rounds where I needed to connect my experience to that stack. The pressure was real, and I did not reach an offer. Location: Fremont, CA. Overall…
Interview experiences · New Relic
New Relic Backend Engineer Interview Experience — String Compression, Longest Increasing Path, and a Kafka Trace-Grouping Design
Question 1: Implement a method that does basic string compression by counting consecutive repeated characters. If the compressed string is not shorter than the original string, return the original string. Discuss time complexity and space complexity Discuss edge cases Discuss code optimization Question 2: Longest Increasing Path in a Matrix. You can only move in four directions (up, down, left, r…
Interview experiences · New Relic
New Relic Software Engineer Interview Experience: good rounds followed by silence
The early part moved quickly. I had technical rounds that went well in a single day, then a hiring-manager conversation a few days later. That conversation felt positive, and communication during it was easy and on track. What threw me off was everything afterward. HR went quiet, and when I messaged, I got nothing back. After about a week of silence, I wanted feedback, even negative feedback, bec…
Interview experiences · New Relic
New Relic Software Engineer interview experience: SDE-2 Codility DSA
I interviewed for an SDE-2 track and was rejected after the first technical round. It was a DSA-focused coding session on Codility, centered on data structures and algorithms. The interviewer gave a brief introduction and moved straight to the coding questions. The prompts used real-life scenarios rather than only abstract problems. I did not move past that initial technical checkpoint, and it fe…
Interview experiences · The New York Times
New York Times Data Analyst Interview Experience — Five Rounds, Three References, Then Rejected
It's been 4 years since this interview without my even noticing, and along with wishing everyone a happy new year, I figured I'd share the general interview process for this company. I went through 5 rounds of interviews with this company in total, and the process was pretty drawn out. At the end they also wanted me to track down three references (a peer, a direct manager, and a manager I had col…
Interview experiences · Nextdoor
Nextdoor Senior Software Engineer Interview Experience — Solved Both Screens, Then Rejected
This was for a Senior general SDE role, so there were two phone screens. Both were known questions. I had prepared every question in the question bank, written each one out once, and prepared all the follow-ups. I don't think there should have been any problems with my answers. Merge weekday time intervals: I could define the input and output formats myself. I chose ["Mon 09:00", "Mon 17:00"]. In…
Interview experiences · NIKE
NIKE Software Engineer interview: repeated follow-ups and hostile response
The process felt odd and frustrating from the start. I received a virtual interview call only after several follow-ups with HR, even though I had not been invited to an ongoing face-to-face hiring drive. After the interview, I contacted HR for an update and expected a normal status message. Instead, the response was essentially a demand that I stop texting. There was no clear closure, and that ho…
Interview experiences · Ninjatrader
NinjaTrader Software Engineer Interview Experience — Log Parser and Anomaly Detector Coded Against Pytest in an IDE
An interview at NinjaTrader, a small brokerage. Server Log Analyzer and Anomaly Detector Problem environment: an IDE with server.log (sample logs), analyzer_stub.py (skeleton code), and test.py (pytest unit tests). You have to implement the functions below. Input data spec (JSON Schema): the input is multi-line text, and each line is a JSON string containing these 4 required fields: timestamp: a…
Interview experiences · NIO
NIO Software Engineer interview: coding, React timer, and offer declined
After a recruiter call, I went through a short, fast technical process with a few behavioral touches. One version had four rounds split between coding and a manager conversation. Another was compressed into two rounds in one day, with a mentor or manager discussion and HR. When it was on-site, it took a few hours end to end, and HR was responsive about scheduling. The coding included easy-to-medi…
Interview experiences · Nokia
Nokia Network Engineer interview: unexpected technical questions at first contact
I expected the first Nokia call to be a casual introduction, with technical work scheduled later. Instead, the interviewer began asking technical questions immediately, without warning or transition. Although the role was described like a networking internship, I was asked software and coding questions. I had prepared for an introductory conversation, so I did not feel I had a realistic chance to…
Interview experiences · Nokia
Nokia QA Engineer interview experience: talent call and in-person assessment
The process opened with a short talent-acquisition call about my background and a quick overview of the company. From there, scheduling moved quickly toward the main interview. The official stage was an in-person interview paired with an assessment. It felt like one block designed to look at practical skill and how I thought under scrutiny. If they decided to continue, the next step was an online…
Interview experiences · Nokia
Nokia Software Engineer Interview Experience: C++, telecom questions, and an interactive panel
I had a conversation with a manager and engineers focused on C++ and general software-engineering knowledge. HR and the manager were in the room together, and the technical discussion felt grounded in what engineers actually do, at least to me. There were also telecom questions. That caught me off guard because telecom was new to me, but it did not feel as if they were trying to trick me. Another…
Interview experiences · Nokia
Nokia Software Engineer interview: paper technical questions
I began with an HR screen about availability and simple personal questions, then moved into several technical rounds with written, paper-based prompts. The first technical interview had five straightforward paper questions. Two later interviews involved different groups of engineers, a couple of people per session, and more paper questions. In a separate technical path, I met a manager and team m…
Interview experiences · Nokia
Nokia Software Engineer interview: unexpected technical questions at first contact
I expected the first Nokia call to be a casual introduction, with technical work scheduled later. Instead, the interviewer began asking technical questions immediately, without warning or transition. Although the role was described like a networking internship, I was asked software and coding questions. I had prepared for an introductory conversation, so I did not feel I had a realistic chance to…
Interview experiences · Nomura
Nomura Business Analyst interview: responsive fit-focused process
The recruiter was easy to schedule with and responded quickly. The early conversation felt like a friendly fit check built around my background, and I left optimistic about the role and company. Later I had a phone discussion with a manager and an in-person office meeting. The interviewers were calm and professional. They asked thoughtful questions that clarified expectations, but nothing felt ov…
Interview experiences · Nooks
Nooks Software Engineer Interview Experience — Web Crawler BFS Screen, Twitter Design Onsite, Rejected
This is a small company in SF that does phone-sales tech (cold-calling/telemarketing technology). Phone screen: a BFS problem dressed up as a Web Crawler question. Follow-up: the BFS needs to make API calls — how do you avoid bottlenecks, DDOS attacks, and so on. Onsite: Live debugging: build a full-stack app for a "YouTube Party." This one was kind of fun — the problem is posted publicly on Gite…
Interview experiences · Nordstrom
Nordstrom Account Executive interview: long waits and conflicting interviewer expectations
The process started out looking standard, but it soured because of how it was run and communicated. There was back and forth and long waits, which made it feel less organized than it should have been. At one point, I waited a long time outside before reaching hiring personnel, and the tone I received felt condescending rather than welcoming. Once I reached the interview space, I discussed communi…
Interview experiences · Nordstrom
Nordstrom Software Engineer Interview Experience — Referral to Four Onsites, Bombed the Frontend Round
I got into this team's interview process through a friend's referral. The team was hiring a Full-Stack Engineer (SDE II). It ended up being one HR call, one phone screen, and four onsite rounds. Besides the usual "why are you switching jobs" and "why Nordstrom" questions, what was different from other companies was that they directly asked about my salary expectations and gave me the package righ…
Interview experiences · Northern Trust
Northern Trust Business Analyst aptitude test and four-to-six-week process
The first major step was a virtual aptitude assessment. It mixed quantitative and language sections: time and work, percentages, distance reasoning, vocabulary, and logic. One account described roughly 100+ questions in about an hour, which matched my experience of a long test that required careful time management. I then had a telephonic confirmation and a personal interview with the hiring team…
Interview experiences · Northern Trust
Northern Trust Business Analyst interview: one practical virtual round
The process was quick and had one round. A recruiter-style invitation led to a virtual conversation with two interviewers for about half an hour. The discussion was domain-related and tied to the process I would work on, including challenges from my own workflow and whether I could work EMEA shifts. The focus was narrow and practical rather than broad. I was struck by how directly they connected…
Interview experiences · Northern Trust
Northern Trust Financial Analyst interview: passed stage, then silence
The process went on long enough that I lost trust in it. After what seemed to be the final stage, including an assessment day where I felt confident, I was told I had passed and was moving forward. I also completed the last interview, then communication stopped. I received no response after the final interview, including after I emailed HR and the interviewers. In another part of the timeline, I…
Interview experiences · Northern Trust
Northern Trust Financial Analyst interview: relaxed panel and behavioral fit
After I applied, the process felt smooth and laid-back. I spoke with a small panel, and the conversation was comfortable because the interviewers were kind and easy to talk to. Most questions were behavioral, aimed at understanding how I had worked before and handled different situations. They also wanted to hear what I knew about Northern Trust and my previous roles, but the discussion was not h…
Interview experiences · Northrop Grumman
Northrop Grumman Software Engineer final round: limited technical discussion and quick rejection
My process started with a recruiter screen. About a week later, I sat through what was essentially the final round. That conversation mixed behavioral questions with only a few technical prompts. I don't remember anyone asking me to go deeply into my background, and the technical part never became a real technical discussion. The interview felt fairly light overall, and the timeline moved quickly…