READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 73 of 153
Interview experiences · Instacart
Instacart Software Engineer Interview Experience — A Full-Stack CodeSignal Challenge With No Tests to Check My Work
I recently completed an Instacart CodeSignal assessment that was very different from the usual LeetCode-style rounds. It was a full-stack repository-based assessment, and some sections required me to have conversations with an AI "Product Manager" before making changes. Very annoying. Because unlike other CodeSignal rounds there are no tests to test against!! So I had no idea how well I did and u…
Interview experiences · Instacart
Instacart Software Engineer Interview Experience — A Single CodeSignal OA Question With Five Escalating Follow-ups
The first step was an OA on CodeSignal. There was a lot of identity verification along the way — anti-cheating checks. It was one question with multiple follow-ups, getting progressively harder. The OA email said you didn't need to finish everything, and honestly I don't think it's possible to finish it all — 90 minutes, 5 parts. The problem gave you template code. Implement account creation: cre…
Interview experiences · Instacart
Instacart Software Engineer Interview Experience — AI Debugging and Unclear Coding Assumptions
The author reports an unsuccessful Instacart backend interview process involving CodeSignal assessments and human-led coding. The first onsite segment included a 90-minute library-application exercise and two hour-long coding interviews. AI was available for the application task, but only to explain code and help localize bugs, not to provide direct fixes. The author says the required changes ult…
Interview experiences · Instacart
Instacart Software Engineer Interview Experience — Five-Round AI Online Assessment
I barely scraped by. As far as I can tell, there's currently only one question in the question bank — a library book search/borrowing system. There's already a very detailed writeup of this question in another post, so I'll just add a few of my own thoughts here: For round 1 and round 4, when talking to the AI PM, try to put all your questions into a single prompt and have the AI PM answer everyt…
Interview experiences · Instacart
Instacart Software Engineer Interview Experience — Hit With a Brand-New Question, Failed on BQ
A totally new question I'd never seen before, and I was the one who got hit with it. I feel like every question in this loop had a pretty large amount of code, so everyone should practice a lot. I think I failed because of the new question and the BQ — I prepared for BQ the Amazon way, but in practice it felt more like a casual conversation, and I wasn't quite ready for that. Coding round: the cl…
Interview experiences · Instacart
Instacart Software Engineer Interview Experience — L5 Interviews in Canada and Team Matching
It took almost a month after I applied for HR to reach out. I had almost thought I'd been rejected. The OA was the vibe-coding OA that people have been talking about a lot on the forum lately. After doing it myself, I felt that ten minutes to communicate with the AI product manager was nowhere near enough, unless I used speech-to-text input. Onsite 1: Calculate Equation Expression. Onsite 2: A re…
Interview experiences · Instacart
Instacart Software Engineer Interview Experience — Library OA, Pricing, and Inventory Design
I translated this passage into Chinese as follows: All the questions I received were exactly the same as those in another post. 0) OA: A full-stack CodeSignal repository test, with AI. A book/library management system. 1) Coding problem 1: The first problem was translating expressions (T1 = T4). 2) Coding problem 2: Calculate the total price of products in an array of strings, in the format sku|p…
Interview experiences · Instacart
Instacart Software Engineer Interview Experience — Two Coding Rounds, a Manager BQ Chat, and a System Design Round
Two rounds of coding, and both were problems that had already been posted elsewhere before. The first one: the input is a transaction record and a set of discounts, and the discounts come in two types — one is a straight percentage off, the other is buy x get y free. The result you need to return is the best (lowest) price. There were 3 parts total, and I only got through the second part before t…
Interview experiences · Instacart
Instacart Software Engineer Interview Experience — VO Split Into VO1/VO2, Karat AI-Coding Round
I got hit with Instacart's VO reform. The onsite is now split into two parts, VO1 and VO2 — if you fail VO1, there's no VO2, that's just it. VO1 has three rounds: First, the Karat round, which is AI coding. I hadn't used AI tools in a while so I wasn't used to it, and I only got through the fourth question before time ran out. The questions were: Given a codebase on a bus route simulation: How do…
Interview experiences · Instacart
Instacart Software Engineer Interview Experience — Waiting on Team Match After the Exact Same Loop as Last Year
My virtual onsite (VO) was two weeks ago, and I got the result last week — I'm through, and now I'm waiting on team match. Coding round 1: two questions, both about shopper deliveries. The first one referenced something specific that doesn't translate cleanly from how I originally wrote it, so I can't say more about it here. The second one was a bit more involved, but if you'd already seen the fi…
Interview experiences · Insulet
Insulet Software Engineer Interview Experience: smooth start and month-long wait for decline
I applied online and heard from a recruiter within about a week to arrange an initial phone screen. That led to a technical interview with hiring managers. The communication became unusual afterward because I sent follow-ups to both the hiring manager and the recruiter. I waited just over a month before Workday notified me that I had been declined. The early scheduling had been relatively smooth,…
Interview experiences · Intact
Intact Data Scientist interview: claims case study and feedback
I started with a recruiter and HR conversation about my background, what I wanted next in my career, and whether my work style might fit culturally. Later I met the lead data scientist and data science manager for a second round. That discussion went deeper into my past projects and technical experience. The technical portion covered general GenAI topics and an insurance claims case study. The fo…
Interview experiences · Intel
Intel Software Engineer interview
My interview focused on digital electronics. We covered Verilog and CMOS fundamentals, then moved to RTL design and questions meant to test how I reasoned through engineering tradeoffs. The interviewers were professional and mixed conceptual questions with coding and circuit-design problems. They were looking beyond recall: whether I could reason from fundamentals into an implementation and conti…
Interview experiences · Intel
Intel Software Engineer Interview Experience: virtual manager panel without semiconductor background
After a recruiter call, the interviews moved quickly but felt structured and organized. About a day before the live session, I got a brief call about my background, with a little casual conversation before the following day's discussions. The next day, I had a virtual interview with the hiring manager and two other managers. It felt professional and straightforward. Each interviewer asked a coupl…
Interview experiences · Intel
Intel Software Engineer interview: metrology technical final round
My process had three rounds, with the last one explicitly technical. That discussion focused on metrology and current industry practices. It did not feel overwhelmingly difficult as long as I had done some research beforehand. The first two rounds were more like screening and behavioral check-ins. I was asked about prior work and how I handled situations, and each interviewer kept the conversatio…
Interview experiences · Intel
Intel Software Engineer interview: two long office technical rounds
I began with a short hiring-manager conversation to confirm my background and logistics. Then I had two technical interviews in the office, each lasting about two hours. In the first technical round, three engineers interviewed me together. They used LeetCode-style coding questions, so I needed both a correct solution and a clear explanation of how I got there. The second technical session kept t…
Interview experiences · Interactive Brokers
Interactive Brokers Software Engineer Interview Experience — A 1-Hour OA With Math Puzzles and a Progressive Tax Bracket Coding Problem
Last week I got a call from an IB recruiter asking if I wanted to try out for an SDE role. After I confirmed, I quickly got an OA scheduled — one hour. The OA was split into two parts. Part 1 was middle-school-level math multiple choice. F(x) = 3x - 1, f(f(x)) = 1, what's x? Answer: 5/9 I don't remember this one at all — it should have been a pretty simple question. A square is made up of three e…
Interview experiences · Intercontinental Exchange
Intercontinental Exchange Business Analyst interview: poor communication
One short conversation felt like a quick check on whether my background matched what the team needed. It did not, and the process did not move forward. I was also asked a puzzle-style question that felt easy. In a separate screening, I answered basic questions about my experience and Snowflake, then did not receive clear follow-up. Another interview was worse: people were late, one took a persona…
Interview experiences · InterSystems
InterSystems New Grad Software Engineer Interview Experience — OA, HR Screen, and a Three-Interview Onsite Day
I applied around early September 2025, and got the OA right away — not sure if it was automatic. The OA was strange, it had three parts, including SAT-math-style questions, I don't remember it too clearly. In October they scheduled an HR call, which just asked some basic information and confirmed my graduation date and things like that. Around mid-November they asked for my interview availability…
Interview experiences · Intuit
Intuit Data Scientist Interview Experience — TurboTax Take-Home, Growth Team Onsite, and a Slow Recruiter Process
First there was a TurboTax home assignment, then a 45-minute presentation plus Q&A. In this part they ask about the recommendations you make based on the data, whether your assumptions are reasonable, and what other data you could look at. I remember there being a question like that, and I didn't have a good answer at the time. The task was predicting whether tax filing succeeds or not, and there…
Interview experiences · Intuit
Intuit Machine Learning Engineer Interview Experience — Measuring Meeting-Free Work Time
The report presents an Intuit AI Science technical-screen exercise reconstructed from images. The task uses a year of company meeting records to assess how much uninterrupted coding time employees have during business hours. Each attendance record identifies an employee and a meeting, together with joining and leaving times. Candidates are asked to determine the longest available interval for eac…
Interview experiences · Intuit Management Consultancy
Intuit Management Consultancy Frontend Engineer interview experience: AI workflow and take-home review
After I applied, the Uptime Crew process felt structured. It began with a proctored online assessment with three parts: a LeetCode-style DSA problem, SQL, and Bash. The Bash section was harder than I expected, and the DSA question was around the difficult end of medium to hard. I had a limited window to start, somewhere around a week/90-minute timing, and the proctoring made it feel high stakes.…
Interview experiences · Intuit
Intuit Software Engineer interview
The recruiter screen began casually with background and fit questions. They also asked for my views on AI, which felt more like checking my perspective than testing technical knowledge. That tone did not hold in every recruiter interaction. One recruiter became defensive when I was candid about my leveling expectations, and the exchange turned frustrating. In another recruiter-led rejection, the…
Interview experiences · Intuit
Intuit Software Engineer Interview Experience — Phone Screen With an AI Prompting Round, Then Silence
Got a reach-out from HR two weeks ago and scheduled it. The phone screen was 45 minutes of algorithms + 30 minutes of AI conversation Q&A, all in one call. 45 min algorithms: One medium-difficulty problem One easy problem — basically detecting in a React environment whether user input is a valid palindrome 30 min AI: Mainly about whether you know how to use current gen AI tools and whether you ca…