real interview stories, told over a cup of tea ♡
Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
3935 results
- Plaid Account Executive interview ending with a panel interviewPlaid · Account Executive · Other · May 2026Rejected
The early steps were remote, and the process eventually became a mix of Zoom and in-person conversations. It moved through multiple stages, ending with a panel interview. The atmosphere was smooth across the rounds. Everyone I met was polite and professional, and the staff communicated clearly about what came next. I never felt blindsided by the logistics or the structure, which made it easier to…
- Recruiter Outreach and a Pre-Drawn Architecture DiagramUber · Software Engineer · Senior+ · Onsite · May 2026Offer
A recruiter contacted me first, and I figured I'd give it a shot, since Uber had been sitting on my target list for quite a while. Coding: Ahead of the phone screen and the coding onsite rounds, I put most of my prep time into LeetCode problems that were tagged with the company. Python is my pick for coding interviews. The syntax is compact enough that I get time to finish the main problem and an…
- Rejected 30 Minutes After Pushing on the ProcessWaymo · Frontend Engineer · Senior+ · Onsite · May 2026Rejected
I interviewed for a senior frontend engineer role, on the simulation team. Probably not much help to most people but in case someone needs it. Phone screen Part 1 — I don't remember the exact details, but it was related to n-ary tree recursion. Roughly, if a node's value contains a certain substring, you need to remove the entire subtree. Return the filtered tree. Part 2 was building a UI based o…
- Rejected After Stumbling on the Venmo Case MathCapital One · Product Analyst · Onsite · May 2026Rejected
Since a lot of people on the forum helped me out a lot, I'm still posting this report even though I ended up getting rejected, which is a shame. Behavior: The usual three — success, helping others, and failure. Remember to prepare detailed examples, there will be follow-ups. DC: I made slides, mostly focused on visualization, since at my current job I present to an MD every day so this felt famil…
- Remitly Software Engineer interview: live coding and power-day onsiteRemitly · Software Engineer · Technical Screen · May 2026Rejected
My process started with an HR phone call. I then had a fairly structured technical interview with a live coding problem and enough time to think through the approach, followed by a separate values and discussion segment. After that, I went through what felt like a larger "power day" onsite with multiple interviewers across different roles. Some rounds focused on my resume experience. The technica…
- Remitly Software Engineer online technical screeningRemitly · Software Engineer · Online Assessment · May 2026
After a recruiter call, I had an online technical screening split between getting to know me and solving a problem. It wasn’t a simple "here’s the pattern" LeetCode exercise, and it didn’t feel realistic to finish in a tight window without running into gaps. I spent a lot of time making sure I understood what was being asked and what passing behavior should look like. The coding round wasn’t just…
- Rivian Backend Engineer interview with delayed feedback and missing follow-upsRivian · Backend Engineer · HR Screen · May 2026No response
I went through a frustrating, logistics-heavy interview process for a Software Engineer role. The difficulty felt average, and communication was often delayed or missing. The recruiter or HR screen covered basic engineering questions, production-line and equipment questions, and behavioral topics. The hiring manager meeting included more role-fit questions, after which communication slowed down.…
- Rivian Software Engineer interview with panel interviews and a project presentationRivian · Software Engineer · HR Screen · May 2026Rejected
I went through a fairly organized, conversation-heavy process. It started with an HR call, followed by a longer meeting with the hiring manager. After that, I had panel-style interviews with several interviewers from different teams. Each round included time for questions and follow-ups. The format combined behavioral and technical fit without feeling like a trick. In one of the later sessions, I…
- Rivian Software Engineer interview with robotics debuggingRivian · Software Engineer · May 2026
The process felt fairly straightforward from the beginning. The interviewers were friendly, and we spent a lot of time discussing my actual projects and what I worked on day to day. Early on, I realized the role had been described in a way that blended into a systems engineering focus in the autonomy space, and the questions matched that impression. One round focused on systems thinking and how I…
- Rivian Software Engineer interview: nearly a month waiting for feedbackRivian · Software Engineer · May 2026
My recruiter and the early rounds went smoothly. The recruiter was responsive and welcomed my questions, so the first part of the process was easy to navigate. After the second interview, the tone shifted because of what happened afterward. I waited almost a month to hear back about the rejection. When I asked for feedback, I didn't receive any, and no one gave me useful pointers about what speci…
- Rocket Lab Systems Engineer interview with a ground-systems project presentationRocket Lab · Systems Engineer · HR Screen · May 2026
The interview started cleanly. I spoke with a recruiter first about my background and motivation, then met with the team's manager. The next step was a presentation on an engineering project, which led directly into technical questions. The conversation stayed easygoing rather than adversarial. The technical discussion focused on engineering fundamentals and problem-solving. We talked about how I…
- Samsara Software Engineer interview with Level 2 and Level 3 roundsSamsara · Software Engineer · Other · May 2026Offer
My interview journey felt like it was built around a lot of rounds and gatekeeping. The process was described as two main stages: Level 2 first, followed by Level 3 if I cleared everything in Level 2. I was told I had to pass all the Level 2 interviews to move forward. Once I became eligible for Level 3, I would go through another set of managerial and technical rounds to finish. Even with that s…
- Self-Written Test Cases in the Screens, Then an IC1 OfferSnowflake · Software Engineer · Onsite · May 2026Offer
Hi all! I got an offer from Snowflake for the IC1 level, and I'm posting my loop here in case it helps someone who's getting ready. It began with a recruiter contacting me, followed by a first conversation with the hiring manager. We went over the team, when the interviews would happen, and what they were looking for. Nothing surprising, but it gave me some context before the real interviews. Nex…
- ServiceTitan Account Executive interview with mismatched role-play expectationsServiceTitan · Account Executive · HR Screen · May 2026Offer
The process started well. The recruiter was polite and interested, and I felt there was a genuine handoff to the next round. The sales-manager stage then took a sharp turn. The managers didn't seem prepared, and the expectations didn't match what I had been told beforehand. The material said the mock exercise would involve simple objection handling and wouldn't require deep product knowledge. Dur…
- ServiceTitan Customer Success Engineer interview with recruiter, manager, and panelServiceTitan · Customer Success Engineer · HR Screen · May 2026
My process felt refreshingly straightforward and well organized. It started with a recruiter screen, followed quickly by a conversation with the hiring manager. The recruiter was warm, and the scheduling and handoff felt seamless, which set a good tone from the beginning. The hiring manager round was thorough and engaged. The interviewer seemed prepared, and the conversation moved naturally. I di…
- ServiceTitan Customer Success Engineer: recruiter screen ended after twenty minutesServiceTitan · Customer Success Engineer · HR Screen · May 2026No response
My recruiter screen started badly and never recovered. The questions were fairly basic for customer success, including how many accounts I’d managed and a scenario involving an escalation and churn risk I’d handled. The recruiter spoke extremely fast and seemed focused on specific keywords instead of trying to understand me. I had little room to ask questions, and the call ended early, after abou…
- Seven Rounds, Batch Write Three Times, No OfferDatabricks · Software Engineer · Senior+ · Onsite · May 2026Rejected
Databricks AI platform team, Staff level. I reached out to the hiring manager directly on my own and got the interview that way — it went straight to the VO (virtual onsite), skipping the phone screen. The initial loop was 5 rounds, then they added 2 more rounds afterward, and I still got rejected. I think I answered well. This is just how Databricks is — they don't really seem to have much since…
- Spotify Backend Engineer interview with unexpected domain questionsSpotify · Backend Engineer · Technical Screen · May 2026Rejected
I started with an initial screening, which led to a technical screen divided into three parts: a discussion of my project, domain questions, and LeetCode-style coding. I expected the domain questions to relate to the project I’d discussed, but the atmosphere felt cold. During the domain section, the interviewer seemed to jump around and choose questions on the spot. I got a lot of basic, exam-lik…
- Spotify Data Engineer interview with a demanding coding roundSpotify · Data Engineer · HR Screen · May 2026
After a conversation with a recruiter, I had a coding-focused round that I expected to be straightforward. It turned out to be difficult. The round was with two senior engineers, and the pace felt demanding. I remember feeling that I needed to be much more fluent with interview-style practice than I actually was, and that gap made the interview harder than it should have been. I didn't receive an…
- Spotify Data Engineer interview: 12-minute phone screenSpotify · Data Engineer · May 2026
My process started with a recruiter chat about my background and visa status. The phone screen was pretty quick, and the scheduling felt a little chaotic. I realized the interviewer was in a rush, and the call, which was supposed to last about half an hour, ended after roughly 12 minutes. Even with the short, hurried conversation, I was selected to move on to the next round. I felt like there was…
- Spotify Data Scientist interview: five-week wait for feedbackSpotify · Data Scientist · HR Screen · May 2026
My process started with a recruiter screen, followed by a technical round with two MLEs. That part was focused and direct. The final step was a behavioral interview with the hiring manager. It took about five weeks to hear back. They still came back with feedback after making a decision, which made the wait feel less abrupt than I expected. Location: United States. Overall feedback: Positive. Off…
- Spotify Full Stack Engineer interview: Backend Tech Screen changed to Web Tech ScreenSpotify · Full Stack Engineer · HR Screen · May 2026
I had a phone screen followed by a technical interview with two senior software engineers. The interview invite initially said "Backend Tech Screen." The night before, the recruiter sent an updated invite that kept the same time. I noticed the change while checking the details, then apologized for sending too many messages. On the day of the interview, I got front-end questions instead. Only afte…
- Spotify Software Engineer interview with a difficult technical panelSpotify · Software Engineer · HR Screen · May 2026
My first contact was a recruiter call covering the usual basics: my background and resume, why I was interested in Spotify, why the role suited me, current compensation and expectations, work authorization and visa status, and my availability. The later interviews were noticeably harder than the early stages. I reached a technical round with a hiring panel led by a senior-level engineer, and the…
- Spotify Software Engineer interview: DSA, system design, and behavioral loopSpotify · Software Engineer · HR Screen · May 2026
My process started with an HR screening, followed by a technical and behavioral screen with two engineers. That round used a HackerRank-style setup and included what felt like standard DSA questions. I then went through a full loop with several interview slots: two more DSA coding rounds, one system design round, and one behavioral interview. The format was methodical. Each interviewer seemed to…
- Spring Boot Machine Coding Round and Lessons From 13 Interviews and 5 OffersNielsen · Software Engineer · Other · May 2026Offer
I spent about 3-4 months preparing, and I kept prep and applying separate instead of doing both at once. In the end I interviewed with 13 companies and got offers from 5 of them. Most were startups, with a few big multinationals in the mix. What worked best for me was starting with the problems that come up most often, for both DSA and design. For DSA I went through a popular 150-problem list, an…
- The Voleon Group Data Scientist interview with OLS regression and Linux tasksThe Voleon Group · Data Scientist · Technical Screen · May 2026
My interview began with a first round that felt like two parts combined. I was either given a dataframe or asked to do a simple join, then I had to run an EDA pass and perform an OLS regression in Python. I focused on p-values and R-squared, and I had to explain the regression assumptions and residual-style checks as I discussed the results rather than just report the numbers. The second half foc…
- Two First Rounds and Progressive Matrix QuestionsCitadel · Software Engineer · Onsite · May 2026Rejected
I asked a lot of people, and they all said they had two first-round interviews. I received both as well, but I did not make it to the second round. The first one: I was asked only one question: share some especially difficult problems you worked on recently and explain them. For the coding portion, a prefix tree or trie was enough to solve it. The question was very similar to a search suggestion…
- Vanta Account Executive fourth-round interviewVanta · Account Executive · Other · May 2026
My Vanta Account Executive process felt long, but it made me think more than I expected. It had five steps, and I reached the fourth round. The difficult part was not knowing where I stood relative to the other candidates. I kept waiting to understand what that stage meant in terms of the competition, and the uncertainty lingered. I appreciated the intentional, thought-provoking nature of the rou…
- Vanta Account Executive interview with an AI note-taking setupVanta · Account Executive · May 2026Rejected
The Account Executive process felt miserable from the start and never recovered. I showed up late, then got distracted by messages during the interview. The interviewer seemed to be reading from a checklist. There was almost no curiosity about my answers, no real follow-up, and no acknowledgment beyond moving to the next question. The most jarring part was that they seemed to be using an AI note-…
- Zipline Software Engineer interview with an industry-expert recruiterZipline · Software Engineer · May 2026Rejected
A recruiter reached out to me on LinkedIn and quickly talked up her background. She described herself as an industry expert and implied that she could "sniff out" whether I really knew what I was talking about. That framing threw me off before I had a chance to explain my experience. I didn’t want to feel put on the defensive, especially since I had already done significant work and expected a mo…
