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
- AKUNA CAPITAL Software Engineer interview with four C++ technical roundsAKUNA CAPITAL · Software Engineer · Online Assessment · May 2026Offer
My process started with a HackerRank online assessment and quickly moved into several technical interviews. The first programming question didn’t feel like a typical LeetCode problem. It was more like a medium-level simulation, and it pushed me to think about how the system behaved instead of simply deriving a clean algorithm. After the assessment, I went through four technical interview rounds.…
- An Elevator Problem With a Follow-up That Was Basically a Second QuestionPinterest · Software Engineer · Technical Screen · May 2026No response
Two weeks ago I did the phone screen for Pinterest, and I still haven't heard anything, so let me post the question while I wait. The recruiter told me beforehand that this round would just be one coding question, and at the time I felt pretty relaxed — I figured forty-five minutes for one problem would be plenty either way. Turns out I was being naive. The question was this: given a set of eleva…
- An Extensible Expense Rule EngineRippling · Software Engineer · Technical Screen · May 2026
In the Rippling phone coding interview, I was given a set of expenses and rules. I needed to run every rule against every expense and identify each rule that the expense violated. An expense looked like this: Example rules included: Total expense should not be greater than 175. A restaurant seller should not have an expense greater than 45. An entertainment expense should not be charged. The meth…
- ASML Software Engineer interview: HireVue assessment and one-hour backend and Java discussionASML · Software Engineer · Online Assessment · May 2026Offer
My first step was a video assessment, followed by a more direct interview with team members. The video round felt like a standard HireVue-style screening. I had to record responses and keep my answers focused. After that, I had a one-hour conversation with two people, focused on backend work and Java. What I remember most about the hour was that it centered on what I could talk through, especiall…
- ASML Software Engineer interview: HireVue, coding test, and senior-engineer discussionASML · Software Engineer · Other · May 2026
My process was fairly compact. I started with a HireVue round where the system recorded my responses, although there was no strict time limit for each answer. It was a set of questions about me, and then the process moved quickly to a more traditional technical conversation. The second round included a group-style meeting with two senior engineers, along with a coding test. I was nervous about th…
- BairesDev Software Engineer automated testing with math and puzzle questionsBairesDev · Software Engineer · Online Assessment · May 2026
Most of my time went into automated testing. I spent several hours answering a large set of questions and received no meaningful feedback afterward, which made the experience feel very impersonal. The math section started with easy questions and continued in much the same way. There were also puzzle-style items that felt more like filler than a reliable signal. The tone and relevance threw me off…
- Box Account Executive final presentation processBox · Account Executive · HR Screen · May 2026
I interviewed for the Account Executive role at Box and went through a fairly standard process over a few rounds. The difficulty felt moderate, although the experience varied between feeling supported and wanting more clarity. The process included a recruiter screen about my background and fit for the role. There was also a virtual manager or hiring manager interview. In some accounts, that conve…
- Box Software Engineer interview that grew to seven roundsBox · Software Engineer · May 2026Rejected
The process started out promising and turned into a long endurance test. I went through several rounds with a professional, easy-to-talk-to interview team. Around the middle of the process, I was told that I had cleared everything. The hiring timeline kept stretching after that. I then entered a "cooling-off" period of about four weeks with no communication. Just when I thought the process was ov…
- Box Software Engineer interview with a two-hour technical screen and LLD roundBox · Software Engineer · Technical Screen · May 2026Rejected
My Box Software Engineer interview felt like a classic LeetCode-style process, with more emphasis on data structures than algorithms. The first technical screen lasted about two hours. The interviewer joined at the beginning and again at the end just to discuss the results. The next coding and DSA round took about an hour, with the interviewer on the call the entire time. After that, there was a…
- Brex Software Engineer interview with debugging and high pressure system designBrex · Software Engineer · Technical Screen · May 2026Rejected
I went through a recruiter call and then several technical rounds. The whole process felt hostile and disrespectful of my time. Even when the interviewers were outwardly neutral, I didn't feel much respect for the effort involved in sitting through multiple steps. The hardest part was that I never got clear feedback about why I was rejected, so I was left guessing where things went wrong. The tec…
- Cold Recruiter Screen, Rejected Before I Parked the CarDatabricks · Forward Deployed Engineer (FDE) · Senior+ · HR Screen · May 2026Rejected
Databricks recruiters are really arrogant. I took the recruiter's call today while driving to the office, and it turned out to be the right call — I didn't waste much time. I'd honestly forgotten when I casually applied for this senior FDE role. Right off the bat she asked, coldly: "Where are you located, specifically which city?" I said I was in the Bay Area — I was worried that naming a specifi…
- CoreWeave Software Engineer interview: concurrency screen and timed CoderPad taskCoreWeave · Software Engineer · Technical Screen · May 2026
I moved quickly once a recruiter contacted me. We scheduled a phone call for the next day, and the conversation felt efficient. We discussed why I wanted to join, what I considered my biggest mistake in my current role, my compensation expectations, and other fit questions. After that, I had a technical screen with a senior engineer focused on concurrency and multithreading. It was the kind of co…
- Datavant Software Engineer, debugging a few-hundred-line codebaseDatavant · Software Engineer · Other · May 2026Rejected
I went through a focused process centered on debugging. It began with a recruiter screen and then moved to a technical round where I had to debug an existing codebase. In the setup I saw, it was on the order of a few hundred lines and included multiple nested classes. The expectation was straightforward, step-by-step debugging: I worked through the code until the tests passed. I made good progres…
- Detecting Fraudulent Transactions Within 60 MinutesBloomberg · Software Engineer · Technical Screen · May 2026
Coding Interview | Fraud Transactions I recently interviewed with a coding problem about fraudulent transactions, so I am recording it here. The problem roughly gave me a transaction list: I had to find the fraudulent transactions under two rules: A single transaction with an amount greater than $2,000 is immediately considered fraudulent. Transactions from the same account within 60 minutes are…
- Docusign Software Engineer interview with a behavioral-only sessionDocusign · Software Engineer · Other · May 2026
I had a lightweight, behavioral-focused experience for a software engineer internship track. Before anything technical happened, the recruiter arranged the process and checked what scheduling worked for me. The logistics felt fairly smooth, and I appreciated that the recruiter stayed in contact and helped map out the timing. When the interview took place, it stayed entirely behavioral. There were…
- Dropbox Software Engineer interview with a monitored CodeSignal test and Deep DiveDropbox · Software Engineer · Online Assessment · May 2026Rejected
I started with a heavily monitored CodeSignal test. I had to keep my camera and microphone on, record my full screen for the entire test, and upload identity details. After I passed, the process quickly became chaotic. Communication broke down almost immediately. I kept waiting while the recruiter seemed to disappear for days, later attributing the delay to a company outing. When scheduling final…
- Duolingo Software Engineer interview with multiple phone screens before the onsiteDuolingo · Software Engineer · Onsite · May 2026
The process took much longer than I expected and didn't feel organized. I went through a standard recruiter screen, followed by several additional phone screens, before finally reaching an onsite. The recruiter and each later step made it seem as if things were moving forward, but the overall experience felt tedious and drawn out. By the time I reached the onsite, I was tired of the pacing and re…
- Eight Rounds, Remote Onsite Interviews, and Slow FeedbackBalyasny · Software Engineer · Onsite · May 2026In progress
BAM had the longest timeline, from late May to mid-July. As of now, I'm still pending, but I noticed that someone with Singaporean citizenship who interviewed around the same time as me has already been working there for a month. So I've probably been rejected. Writing this up to keep a record. The role was a QD position in one of BAM's Singapore pods, but the actual job description was really fo…
- Epic Software Engineer onsite: evolving patient-database design and backtrackingEpic Systems · Software Engineer · Onsite · May 2026
I started the day with an online video overview that lasted about forty-five minutes. It covered what Epic does and the software it provides. After that, I moved into one-on-one conversations with engineers. One was a lighter discussion where I could ask questions and hear about their experiences. The next engineer conversation was more technical and felt like a system design prompt that kept bui…
- Epic Software Engineer, difficult assessment led to an offerEpic Systems · Software Engineer · Online Assessment · May 2026Offer
I started with a quick phone interview with an existing employee. It was mainly a fit check, and then I moved directly into scheduling an assessment. The assessment was genuinely hard, longer and more challenging than I expected, and it was the part that required the most effort. After finishing it, I made it far enough to receive an offer. I ultimately declined because a better opportunity came…
- Five Onsite Rounds in Two Days, Two Hards, and a Last-Minute Add-On RoundBytedance · Software Engineer · Onsite · May 2026
Five rounds plus one add-on round, the most intense interview I've had this year. Fair warning up front: the intensity here is not the same league as other places. Five rounds packed into two days, two of them straight-up hard, and then they tacked on an extra round at the last minute. By the evening after I finished I was basically wrecked. Some interviewers were Chinese, some were not. All the…
- Five Onsite Rounds Including a Superhero Dispatch SystemStripe · Software Engineer · Onsite · May 2026Rejected
The Stripe recruiter reached out saying I could interview for L3, so I figured I'd give it a shot. It wasn't like I absolutely had to go, though, because I'd heard it's really cutthroat. In the end I didn't pass, and it stings a bit — I still feel like I have something to prove. So I wanted to turn that frustration into an interview writeup to help everyone out. Two of the rounds were pretty new…
- Five Rounds, No Hard Problems, All About DepthLinkedIn · Software Engineer · Onsite · May 2026
Five rounds, with my approach and follow-ups for each. I've been lurking on this forum for years, and this interview process benefited a lot from it, so I'm writing up a full account to give back. As usual, I'll use homophone code names for the problems in the original, but I'll just describe them directly here. Overall impressions first. LinkedIn's interview pace is fairly restrained — not like…
- Four Onsite Rounds, Mostly Production Code Not LeetCodeCoinbase · Software Engineer · Onsite · May 2026
This company's interview format is pretty different from everywhere else, so it's worth writing up on its own. Of the four rounds, only one was a traditional coding round in the usual sense — the rest were all "here's a small requirement, write code that could ship to production." They use their own online environment, where you can run tests and also look things up in the docs. So pure template…
- Glean (CA) Backend Engineer interview: rejection after system designGlean (CA) · Backend Engineer · Other · May 2026Rejected
I interviewed for a backend focused role and was rejected after the system design round. The early stages weren't where the process ended. The later system design evaluation was the point at which I didn't make it through. The overall sequence matched what I'd heard from friends: a fairly consistent process that eventually led to the same system design stage. That round felt high stakes. The earl…
- Glean (CA) Software Engineer interview: difficult DSA problem-solving screenGlean (CA) · Software Engineer · Technical Screen · May 2026
My process started with a recruiter reach-out where we talked through the setup and the overall interview process. After that, I had a technical screen that felt more "in-house" than a generic LeetCode interview. It still relied on DSA knowledge, but the prompt put more emphasis on problem-solving within its structure. The question required me to apply data structures and algorithms. I could tell…
- Grammarly Account Executive interview: mock qualification call and AE debriefGrammarly · Account Executive · Other · May 2026Rejected
My process was shorter and felt focused on getting to a clear signal early. I started with a recruiter interaction where I talked through my background and interest. Then I had a second conversation that went deeper in a similar style, followed by a mock qualification and discovery call and an AE debrief. What surprised me was how quickly the mock call fed into the decision. I expected more conve…
- Grammarly Software Engineer interview with a smooth recruiter experienceGrammarly · Software Engineer · May 2026Offer
Everything was handled smoothly from the beginning, and the recruiter experience really stood out. Communication was responsive, so I never had that awkward waiting period that can drag out a process. The schedule was predictable, and the interviewer conversations were engaging rather than intimidating. Once I moved into the rounds, the interviewers were knowledgeable and supportive, and the tone…
- Grammarly Software Engineer interview with HackerRank and technical codingGrammarly · Software Engineer · Online Assessment · May 2026
My process started with a HackerRank coding assessment. After that, I had an HR screening round that felt more like a checkpoint than a detailed conversation. The main work came next in a technical coding interview, followed by additional rounds that combined engineering depth with questions about cultural fit. The process felt difficult mainly because the technical portion required real problem-…
- Grammarly Software Engineer interview: supportive technical assessmentGrammarly · Software Engineer · HR Screen · May 2026Offer
After the recruiter call, the process moved quickly and felt professionally run. The recruiter was very responsive and easy to work with, and the interviewers were supportive and engaged. Instead of feeling interrogated, it felt like a real conversation in which they were genuinely interested in my background. The technical portion was calmer than I expected. I completed a technical assessment, f…
