READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 97 of 153
Interview experiences · NVIDIA
NVIDIA Software Engineer interview with a 45-minute resume discussion and coin riddle
I started with a short, focused first round that spent about 45 minutes on the details in my resume. The expectation was that I could explain my background confidently before the technical deep dive. Then the conversation shifted to core computer-science topics, and I had to use a whiteboard to show my reasoning. I got a practical DSA question and a brainteaser-style riddle. The riddle was easy t…
Interview experiences · NVIDIA
NVIDIA Solutions Architect interview: EVPN shifted to DevOps
The NVIDIA interview opened with EVPN questions, which I answered confidently. It then shifted almost entirely to DevOps, a direction I did not expect for a Solutions Architect position. Nothing in the rest of the conversation connected to my AI or HPC background. By the end of the call, I felt that much of the questioning did not match the advertised role. I did not receive an offer. My main tak…
Interview experiences · NVIDIA
NVIDIA Technical Marketing Engineer Interview Experience — First Onsite Round Covers ML Frameworks, Compilers, and Product Sense
Onsite interview 1/4. The first interviewer was 45 minutes, first asked about my resume, then an AI technical interview, since the role is technical marketing for AI Software. The interview was split into three parts. Part 1: Deep Learning Fundamentals Q1: In Machine Learning, what are the high-level trends happening at the framework level? I answered with the evolution from numpy to PyTorch to J…
Interview experiences · NVIDIA
NVIDIA Technical Marketing Engineer Interview Experience — One Round, Four Parts: Resume, ML Trivia, and Live NumPy Coding
Technical Marketing Engineer - NVIDIA AI. NVIDIA has five rounds total, two with coding and three without coding. My interviewer was a data scientist. She asked me how many coding rounds I'd already had, and I said only one, so she said okay, then this round has to include coding, we can't just do a pure Q&A chat. Here's the whole flow, four parts: resume, technical fundamentals, coding, and ques…
Interview experiences · NVIDIA
NVIDIA Technical Marketing Interview Experience — PyTorch vs Jax, Then a Question About Bashing AMD
Onsite interview 1/4. The first interviewer, 45 minutes, first asked about my resume, then it was an AI technical interview, since the role is technical marketing for AI Software. The interview had three parts. Part 1: Deep Learning Fundamentals Q1: In Machine Learning, what are the high-level trends happening at the framework level? I answered with the evolution from numpy to PyTorch to Jax. He…
Interview experiences · Nyc Staffing
Nyc Staffing Software Engineer Interview Experience: a mobile role with mismatched screening
My recruiter screen was about a week after I applied and felt generic. They asked a couple of questions about my resume but gave little detail beyond the posting. I then shared availability for a hiring-manager round that was scheduled about two weeks away. What I heard about the hiring manager made me think I would be a strong fit. A few days later, I was asked to arrange a technical screen. Aft…
Interview experiences · Odoo
Odoo Account Executive interview: delays after recruiter and final rounds
The hardest part was the waiting, not the first interview. I started with a recruiter conversation about my account-management background and was told I would hear back by the end of the week. The week passed, and my follow-ups brought no useful response. The same frustration appeared at the final stage. Even after a last interview and a promise of a timely decision, I waited for weeks. When a re…
Interview experiences · Odoo
Odoo Account Executive interview: product demo and pressured role-play
The interview opened with a group product demo in a random group. It quickly became a pitch challenge: I had to invent a business idea and sell it as if I were on stage. After my individual presentation, I was questioned right away about whether I could handle rejection pressure and keep a pitch organized under scrutiny. It then shifted into role-play. I received a short instruction sheet just be…
Interview experiences · Odoo
Odoo Business Analyst interview: software workflow exercises and a hiring pause
I had three structured rounds: a behavioral HR screen, a stage where I had to learn the company software, and a final stage where I showed those skills through different parts of the UI. The breakdown made me feel they were assessing both my thinking and whether I could follow their product workflow. The process moved from a recruiter call to a video call and then an onsite final interview. In th…
Interview experiences · Odoo
Odoo Full Stack Engineer interview: HTML validator and delayed decision
The process began with an HTML-tags validator. The task was simple in concept: decide whether an HTML snippet was valid, knowing that one incorrect tag or invalid structure would make it fail. After that I had two short, friendly HR interviews with different people. We talked about my interest and experience, my motivation for coding, and what I liked doing day to day. The conversations were rela…
Interview experiences · Okta
Okta Software Engineer Interview Experience — One-Hour Phone Screen with BQ and a CodeSignal Pagination API
Okta's interviews feel like they vary a lot by team. I read a few other write-ups and they were all pretty different. From the recruiter to the interviewers, the company culture seemed pretty good and everyone was nice. If I get rejected, it just means I wasn't good enough. Anyways, posting this for whoever interviews next. My phone screen was 1 hour: 25 minutes of BQ, 30 minutes of coding, 5 min…
Interview experiences · Okta
Okta Software Engineer interview: smooth recruiter screen and abrupt rejection
The recruiter screening felt as though it was going fairly well, but I received an automated rejection shortly afterward with almost no detail. The questions I remember were basic: tell me about yourself, why I wanted to work there, and why I was considering other roles. The process ended so quickly that I did not feel there had been much evaluation beyond that first conversation. Since the scree…
Interview experiences · Okta
Okta Staff Backend Engineer Interview Experience — A Token-Bucket Take-home and Cross-Domain Login
HM Screening A conversation with the hiring manager, mainly about past project experience, behavioral questions, and various real workplace scenarios. Take-Home Assignment Build a rate limiter in Node.js using the token bucket algorithm. Create an Express application that can read a configuration file. Expose an API that returns a rate-limit response. Technical Round - Code Review & Debugging Cod…
Interview experiences · Omnissa
Omnissa Software Engineer Interview Experience — Five Rounds from C# LLD to Notification Design
Round 1: Screening / Practical Coding (HackerRank) This was a practical low-level design coding problem based on a real scenario, and I was required to use C#. Given an existing repository class, I had to implement and complete every method in a Service class so that it passed the test cases. The main focus was how I organized the code, wrote clean code, handled edge cases, and thought through an…
Interview experiences · OneMain Financial
OneMain Financial New Grad Data Scientist Interview Experience — A Case on Ditching Traditional Branches for Digital
Had my interview today, so let me do a recap while it's still fresh. I got a VP who spent 15 years at Capital One before jumping to this company. He came in like a machine gun from the start — honestly it's a waste he's not a rapper. He jumped straight into a case: OneMain's credit card business has two flows — a traditional branch business and a digital business. Q1 was why OneMain would want to…
Interview experiences · OpenAI
OpenAI Backend Engineer Interview Experience — Tricky IDE Quirks and a Surprise Chess Game System Design
Let me start by saying you should try to avoid this interviewer if you can. He had a really heavy accent and I couldn't understand him at all, and when I asked questions partway through the interview, he just kept going silent. The question was the IP address problem. I got to the third part, the CIDR block part, but when I ran it the answer was wrong. After the interview ended I thought about it…
Interview experiences · OpenAI
OpenAI Data Scientist Interview Experience — A LinkedIn Cold Ask, a Take-Home, and a Python Debug Stumble
I didn't expect to actually get an interview invite from OpenAI — I'd only asked a recruiter about it on LinkedIn. My own level isn't really there, so I went into it purely as an experience, but the experience was great, worth writing up a post-interview reflection. Some background: I do data work at a big company, and my job search has mainly focused on experimentation and causal inference. Afte…
Interview experiences · OpenAI
OpenAI Data Scientist Interview Experience — Free-Trial Take-home and Four Final Interview Rounds
Take-home assignment + live review take home assignment related to free trial Explore the data, identify key insights, and make recommendations. Deliver a polished and concise slide deck. This is followed by a 1-hour live interview: 20–25 minutes: take home discussion 20–25 minutes: hands on sql 10 minutes: python debug Hiring Manager Interview 1 hour project deep dive with the hiring manager Ons…
Interview experiences · OpenAI
OpenAI Full-Stack Engineer Interview Experience — Ship a Working App, Not Just LeetCode
Before I get into it: this is a writeup of my full process interviewing for a Full-Stack role at OpenAI, along with my impressions, as a reference for people prepping. OpenAI's interviews are pretty different from traditional big-tech interviews (especially the pure-LeetCode-grinding kind) — it leans a lot more toward "real engineering + product sense + mission fit," so if you only prepped LeetCo…
Interview experiences · OpenAI
OpenAI Interview Experience — Nailed the Memorized Coding Question, Lost the System Design Round
I applied to OpenAI myself back in June. As the interview got closer, I saw on the forum that the interview reports all seemed to be about the same handful of questions, so I decided to prepare those thoroughly and really understand them before going in. I ended up rescheduling three times, and the recruiter got angry — said I'd rescheduled three times already, which meant the timing wasn't right…
Interview experiences · OpenAI
OpenAI Machine Learning Engineer Interview Experience — A malloc Phone Screen and a Surprise Debugging Round
Sharing an OpenAI interview report. Aside from the phone screen, everything was a question I'd already seen before — because I over-prepared from question banks and cared way too much about the outcome, I interviewed badly. I really regret it. The phone screen covered malloc, which others have already shared — the details aren't much different. There were two parts: first a naive first-fit soluti…
Interview experiences · OpenAI
OpenAI Machine Learning Engineer Interview Experience — A Rate-Limited Dependency Version Search Problem
First question: the topic was dependency version check. Part 1: they give you a list of dependency versions, for example [103.003.02, 103.003.03, 203.003.02]. Each version may or may not support the current feature, and you need to find the earliest version that supports it. Part 2: they gave a bunch of corner test cases, and some of the cases actually expose more requirements — your earlier assu…
Interview experiences · OpenAI
OpenAI Machine Learning Engineer Interview Experience — A Simulation-Style Infectious Disease Question
I interviewed onsite for a completely new question I had never seen before -- five parts in total, and I only managed to finish three, so I definitely failed this round. The prompt was described as "simulation style." Beforehand, people on the forum said it would probably be GPU-related, so that is what I prepared for, but it turned out to be about infectious disease instead. Posting this so othe…
Interview experiences · OpenAI
OpenAI Machine Learning Engineer Interview Experience — Four One-Hour Rounds in a Single Phone Screen
Sharing my recent OpenAI Research phone screen. Round 1: general coding, 1hr Debug a distributed system. They gave me a buggy job scheduler written in Python — I had to check for data races, deadlocks, lock contention, and whether the rate limiter was implemented correctly. Partway through I had to write my own test cases to confirm the scheduler actually worked, then calculate how long the sched…