READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 91 of 153
Interview experiences · Mistral AI
Mistral AI Software Engineer Interview Experience — Two CodeSignal Rounds, Ran Out of Time on the DP Question
French AI company, the interviewers all seemed to be based in France, but the position itself is in NYC, and the recruiter is on the US side too. I talked with the hiring manager for half an hour, then moved into the phone interview stage. Two phone interview rounds: coding + system design, both done on CodeSignal. Overall I felt the bar was pretty high. Coding Three questions total. The first tw…
Interview experiences · MITRE
MITRE Software Engineer interview: recruiter alignment, presentation, and panel questions
I started with a short recruiter screen that confirmed my resume matched what I said I had done. It was a straightforward conversation about my background and what I wanted, rather than a highly formal step. Once that alignment was clear, I moved to the next stage fairly quickly. The next round combined a panel-style technical interview with a presentation. I organized my thoughts for the present…
Interview experiences · Mixpanel
Mixpanel Data Scientist Interview Experience — Four Retention SQL Questions in a 45-Minute Screen
Straight to the useful stuff. My Mixpanel Data Scientist phone interview was a SQL screen, around 45 minutes, with someone from the DS team. Table structures, restated as I understood them, roughly like this: users: user_id, signup_date, plan_type, ... events: user_id, event_ts, ... There were four questions, each building on the previous one, all about retention analysis. Q1: How many users had…
Interview experiences · Mixpanel
Mixpanel Data Scientist Interview Experience — Pandas Tasks and Open-Ended Retention Prediction
Following up on my previous SQL post: This was the Python screen in the same Mixpanel DS phone-interview round, about 45 minutes. There were four questions: two hands-on pandas tasks and two open-ended questions. Aggregate the users and events dataframes separately. Merge the two dataframes and check for duplicates. An easy one. Open-ended: Which features might predict retention? Explore the data…
Interview experiences · Molex
Molex Software Engineer three-step fundamentals and resume interview
After I was shortlisted, I went through three stages: a technical round, an advanced technical round, and an HR conversation. Every stage came back to engineering fundamentals and my resume. How I explained my work and approached a problem seemed to matter as much as the answer itself. The technical rounds were tied to my projects, tools, and claimed skills rather than random puzzles. They felt a…
Interview experiences · Moloco
Moloco Data Scientist Interview Experience — A SQL and Open-Ended EDA Phone Screen, Rejected Days Later
Sharing an interview report for a niche ad company. A recruiter reached out to me on LinkedIn about an opening on a Product Analytics Data Science team. Before the interview they sent over a prep doc saying the technical phone screen would cover SQL + Python/R, with the focus on data manipulation, not modeling. The prep doc also mentioned they might ask about past project details and what I learn…
Interview experiences · Moloco
Moloco Machine Learning Engineer Interview Experience — Ranking Design, Two Pointers, and ML Fundamentals
The phone screen was a conversation with the hiring manager that included a project deep dive and behavioral questions. The onsite included another project deep dive and a system design question related to ranking. The coding question used two pointers to find the longest consecutive run of 1s. The follow-up asked how to handle an especially long input across multiple machines. I was also asked a…
Interview experiences · monday
monday Account Executive interview: scheduling and stalled follow-up
The recruiter call focused on my background, especially selling into the Israeli market, the clients I had worked with, and my day-to-day sales process. Scheduling was difficult because the HR representative offered narrow time slots while very busy. I tried to work around that, including a very late WhatsApp attempt to connect and a last-minute message that she was sick. After the call, the proc…
Interview experiences · monday
monday Software Engineer interview: feedback through system design
After a recruiter call, I went into a coding interview where I did only limited coding and spent much of the time explaining my reasoning. The process moved step by step, and the recruiter followed up with feedback after that stage. That feedback helped me understand what they were looking for. The next interview put even less weight on heavy coding and more on walking through my approach. Then c…
Interview experiences · monday
monday Software Engineer interview: notification coding rounds
After a recruiter call, I completed a video technical interview in their coding interface. I had to simulate push notifications to teammates by implementing functions, running the code, and checking the output with dummy input. The next coding round also involved notifications, this time preventing duplicate notifications from reaching subscribers. I got a working straightforward solution, but a…
Interview experiences · MongoDB
MongoDB Account Executive Interview Experience: clear recruiter expectations
The recruiter call set clear expectations about the timing and what came next. The interviewers were nice and direct, and I felt they were helping me understand the process rather than simply describing the job. The conversations fit what I expected for the market and role, and the compensation discussion was consistent with other companies I had considered. I was pleasantly surprised by how atta…
Interview experiences · MongoDB
MongoDB Customer Success Engineer interview: customer-meeting presentation
My process took a couple of months. It began with an HR screen, followed by a hiring-manager interview on the role and typical customer-success questions, then a peer interview covering databases and cloud-native infrastructure. The last stage was a presentation challenge framed as a customer meeting. I had a prep call before presenting to a fictitious customer panel, with interviewers playing di…
Interview experiences · MongoDB
MongoDB Software Engineer Interview Experience: live coding, database troubleshooting, and Linux
After a recruiter conversation about my background and skills, I had a technical round with live coding and deeper questions about problem solving and ambiguity. The process later switched modes with a team-lead-style discussion about troubleshooting scenarios, including how I would diagnose a slow database. There were several in-depth technical interviews on databases, Linux, and other areas lis…
Interview experiences · MongoDB
MongoDB Software Engineer Interview Experience — Positive Crawler Feedback, Then Rejection the Next Day
I have no idea why I failed this interview. I finished both the original question and the follow-up, and the interviewer said both my approach and code looked good. Then I was told the next day that I'd been rejected. Question: Implement: Single-threaded first → Follow-up = find the bottleneck + speed it up with concurrency (= LC 1242 Web Crawler Multithreaded) The interviewer explicitly said the…
Interview experiences · MongoDB
MongoDB Software Engineer interview: Karat screen and inconsistent next steps
I began with a recruiter conversation and then went straight to a Karat technical interview. The Karat portion had only a small number of questions, but it was clearly a serious gate. Mine focused on LeetCode-style problems, and I did not pass that stage. What disappointed me was that the process did not end immediately after Karat. Another technical round was still scheduled, which made the flow…
Interview experiences · Moody's
Moody's Software Engineer delayed-feedback interview experience
The interview itself felt productive and well matched to my background. It was scheduled for June 9. Communication afterward fell apart. I had no update for several weeks and tried reaching HR by phone multiple times without a response. After I followed up by text with an HR representative on July 3, I was told that I had not been shortlisted. The result was disappointing, but the lack of timely…
Interview experiences · Moody's
Moody's Software Engineer Interview Experience — Onsite System Design for a Product Inventory Service
System Design Design a Product Inventory & Pricing Service for an e-commerce platform Functional requirements: get product details, update product price, update inventory when a user places an order. System requirements: this is a read-heavy system, so we needed to discuss the Consistency vs Availability tradeoff, plus authorization for inventory updates. Technical approach discussion: SQL vs NoS…
Interview experiences · Moody's
Moody's Software Engineer Interview Experience: unclear AWS-heavy office interview
I was asked to attend an interview at the office, but the questions did not seem relevant to what I understood the role to require. Much of the discussion felt textbook-like, and I could not tell what the interview was actually trying to evaluate. They focused on how AWS works internally and on specific steps, but the phrasing made it hard to connect my answers to the expected skills. I did not g…
Interview experiences · Moody's
Moody's Software Engineer interview: interval DSA, AWS, and manager interruptions
My first interview began with a LeetCode-style DSA problem about intervals that felt medium to hard. We also discussed AWS concepts including ECS, ECR, Lambda, and Step Functions, so it was not purely abstract coding. The next stage was with the hiring manager. I expected a normal discussion of my projects, but the manager quickly drove the conversation toward the answers he wanted. He cut me off…
Interview experiences · Morgan Stanley
Morgan Stanley Data Scientist Interview Experience — Phone Screen Then a Live-Coding Tech Round
Phone screen: they asked me a simple Python question, then a statistics question, and then a Black-Scholes model question (I passed). The next round was the tech interview, covering Gen AI and statistics questions. They told me to have paper and pen ready, and said they'd also ask me Python coding, and possibly a stress testing framework question. The interview started with Gen AI — they asked me…
Interview experiences · Morgan Stanley
Morgan Stanley Financial Analyst interview: timed fit and finance prompts
After applying, I started with a HireVue that was mostly behavioral. I had to think on my feet within the time set for each question. A recruiter-style call followed and felt more focused on understanding me than on deep technical testing. The next round involved senior people and mixed behavioral questions with finance context and light technical reasoning. I had to explain my thinking aloud. On…
Interview experiences · Morgan Stanley
Morgan Stanley Quant (Strats) Interview Experience — Three Back-to-Back Technical Rounds on Options Pricing and Algorithms
Morgan Stanley Quant (Strats). There are 2-3 rounds total, and I just finished round two. I'm not sure if round three will be a superday or just a chat with the MD. Round one was a straightforward LeetCode-style question, the same for everyone regardless of team — 30 minutes of live coding. Not hard, it tested a greedy algorithm, and once you saw it was greedy it clicked instantly. Round two was…
Interview experiences · Morgan Stanley
Morgan Stanley Quantitative Researcher Interview Experience — Three VO Rounds from a Brainteaser to Black-Scholes Robustness
Virtual Onsite interview experience The VO had 3 rounds total, each about 30 minutes. Round 1 Mainly resume questions + probability questions + a brainteaser. The interviewer first asked some project-related questions based on my resume, then asked some probability questions. At the end there was a brainteaser: there's a dog running on a circle of radius 1, at speed 4. You're at some point inside…
Interview experiences · Morgan Stanley
Morgan Stanley Software Engineer interview: difficult introductory questions
My first introductory round was rough from the beginning. The questions felt difficult right away. What unsettled me was the interviewers' response: my answers did not satisfy them, and it seemed as though they wanted very specific responses instead of exploring my reasoning or allowing the discussion to develop. I could not make sense of the intent. The questioning felt as if it was constructing…