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
- Canonical Software Engineer interview with multiple assessments and late-stage roundsCanonical · Software Engineer · Online Assessment · Mar 2026Rejected
I interviewed for the Software Engineer role through a drawn-out but structured process. I completed several assessments, followed by interviews covering coding, systems concepts, and behavioral collaboration. I started with a written-style screen, then completed logic and personality testing. The technical stages included long interview sessions, another technical segment later in the process, a…
- Canonical Software Engineer interview with questionnaire and Python assessmentCanonical · Software Engineer · Online Assessment · Mar 2026
I interviewed for the Software Engineer role through a multi-assessment process that started with a long questionnaire and two tests, before any deeper technical discussion. I answered around 30 questionnaire questions. The first assessment was a non-standard test made up of different types of tasks. The second assessment focused on Python. I didn’t receive an offer. Early filtering leaned heavil…
- Canonical Software Engineer online assessments with unclear follow-upCanonical · Software Engineer · Online Assessment · Mar 2026Rejected
I interviewed for the Software Engineer role through a process that was quick to schedule but ultimately unclear. It involved questionnaires and online tests, followed by either an early decline, no follow-up, or a rejection with little explanation. I filled out a form-like application and completed a detailed written interview about my background and problem-solving. I also took an aptitude-styl…
- Cart System Design Screen Plus BehavioralUber · Engineering Manager · Senior+ · Technical Screen · Mar 2026
I recently interviewed for a manager position at Uber. Overall the experience was pretty good — both interviewers were easy to talk to and felt pretty nice & chill (not quite what I expected from Uber based on my old stereotype, lol). Writing up the System Design question and what I think you need to prepare for it, as a reference for anyone else interviewing for something similar. 1) System Desi…
- Clipboard Health Frontend Engineer, repository take-home and debugging follow-upClipboard Health · Frontend Engineer · Take-home Project · Mar 2026Rejected
I went through a largely take-home-driven process that was somewhere between average and difficult. It usually started right after I applied and often ended with a rejection after little actionable feedback. For the automated or online take-home, I cloned a provided repository, often involving Node.js, NestJS, React, or a backend API, and built logic to calculate results in the style of "top work…
- Clipboard Health Software Engineer interview with PR and TDD workClipboard Health · Software Engineer · Take-home Project · Mar 2026
I interviewed for a Software Engineer role through a difficult, multi-step technical process. It included pull request work and written technical thinking before I was turned down. I submitted code through a pull request and then had a follow-up interview that referred to a technical design document. I completed a TDD-style write-up for a feature and then went through another PR or related assign…
- Clipboard Health Software Engineer interview with two API scriptsClipboard Health · Software Engineer · Take-home Project · Mar 2026In progress
I interviewed for a Software Engineer role with an overall average difficulty. I spent a short burst writing scripts and then waited. For the assignment, I wrote two API scripts after being brought into a process that referenced "top workers/workplaces" data. I submitted them and waited. Afterward, I had a follow-up interview where they reviewed what I produced. I didn't receive an offer, and I'm…
- Clipboard Health Software Engineer interview: assessment-first process with documentation reviewClipboard Health · Software Engineer · Take-home Project · Mar 2026
I interviewed for a Software Engineer role through an assessment-first process that moved quickly into interviews. The first step was a coding and logic assessment. If the results looked promising, I was scheduled for later interviews. In one interview, we discussed what I had done in the take-home assignment and how I had approached the problem. I then completed another documentation-style asses…
- Cloudflare Account Executive interview with a mock discovery callCloudflare · Account Executive · Mar 2026
From the recruiter call onward, the process moved quickly, though it was also confusing at times. I met multiple interviewers, including hiring managers and people from different functions. Some of them seemed impatient, as if they were looking for a specific "sales-ready" trait instead of trying to get to know me conversationally. The recruiter was nice, but the introductions and context weren’t…
- Confluent Account Executive interview and the IBM acquisitionConfluent · Account Executive · Mar 2026
I started with a recruiter conversation about how the recent IBM acquisition might affect hiring. The recruiter was transparent, but I came away with more uncertainty than clarity, especially about what the acquisition would mean for the day-to-day work in the Inside Sales role. In the later interviews, I kept asking for specifics: how the role fit into the larger sales organization, what the KPI…
- Crowdstrike Account Executive: fast-tracked interviews and a final panelCrowdstrike · Account Executive · HR Screen · Mar 2026
My process started with a straightforward recruiter conversation, followed by a small number of follow-ups rather than a long gauntlet. I had been in contact with the hiring side early on, and after a conversation they sent me an application link and connected me with the recruiting team. The conversations stayed professional and focused heavily on my cybersecurity sales background and how it fit…
- Crowdstrike Software Engineer interview with seven difficult coding questionsCrowdstrike · Software Engineer · Online Assessment · Mar 2026
After applying, I went through an earlier pipeline that included college-placement-style steps and then an online assessment. The multiple-choice section was manageable for me, but the assessment overall felt harder than I expected, especially since the role was for an internship. The biggest problem was the mix of questions. I could solve the multiple-choice problems, but the seven coding questi…
- Crowdstrike Software Engineer interview: recruiter redirect after a 10-minute delayCrowdstrike · Software Engineer · Mar 2026
My first step with CrowdStrike was a recruiter call over Zoom. The interviewer joined almost 10 minutes late, which made the start a little awkward, but they were professional and polite once we began. We covered the usual basics about my background and work history, and the conversation stayed fairly light. What stood out was that they asked whether I might be a better fit for a similar role on…
- Crowdstrike Solutions Engineer interview: remote hiring-manager and sales interviews followed by silenceCrowdstrike · Solutions Engineer · Mar 2026No response
A recruiter contacted me, and the process became a remote interview cycle with a hiring manager and members of the sales team. I kept moving through the interviews and felt that I had passed the rounds, so I expected the next steps to come quickly. Instead, the process went silent after I finished. I emailed for an update, but I still didn’t hear back. The lack of communication felt careless and…
- Debug a Real Codebase, Then an LLM API RoundScale AI · Software Engineer · Onsite · Mar 2026
Phone Screen It was the "party" question that's already been posted on the forum, pretty easy. Debug This round felt a bit harder. The question was the "assign project" one that's already on the forum, and the main issue was that time was tight. It's a new codebase with several files, and you need to go back and forth through it a lot (would've been a lot easier if I could've just used AI for thi…
- Discord Software Engineer interview: chat-server coding and virtual onsiteDiscord · Software Engineer · HR Screen · Mar 2026
I interviewed for a Software Engineer role through a recruiter screen, a technical screen, and a virtual onsite. Overall, it felt like a standard process with mixed outcomes and a few awkward moments. During the recruiter screen, we discussed my experience and fit, including behavioral questions. In one case, I was unexpectedly asked to describe a trade-off situation. The technical screen was a l…
- Discord Software Engineer interview: relaxed recruiter screenDiscord · Software Engineer · HR Screen · Mar 2026
I had a low-stakes, recruiter-first experience for a Software Engineer role, with a quick and mellow timeline. The recruiter screen was a relaxed conversation about my background and why Discord. We also discussed the team and the hiring motivation, and the overall mood was friendly and calm. I didn’t receive an offer. The stage felt easy and conversational, but it didn’t lead to any further move…
- Distributed Coding, AI Safety, and Hardware ReasoningAnthropic · Software Engineer · Onsite · Mar 2026Rejected
The author describes four interviews for an infrastructure-oriented Anthropic role. Distributed coding covered mode and median computation using supplied messaging interfaces, with attention to partitioning and communication costs. A separate programming exercise converted sampled call stacks into function events and explored recursion and limited recent-history data. The culture discussion consi…
- Distributed Node-Counting System Design QuestionOpenAI · Software Engineer · Technical Screen · Mar 2026
I've interviewed with OpenAI several times recently. This question gives you a root node and an initial API, sendAsyncMessage(nodeId, message). You need to implement receiveMessage(fromNodeId, message) yourself, and ultimately count how many nodes exist in the whole network. On the surface it looks a bit like DFS, but it's dressed up as a more realistic distributed scenario. Each node can be thou…
- Docusign Account Executive interview with multiple presentationsDocusign · Account Executive · HR Screen · Mar 2026Rejected
I went through an Account Executive hiring process that felt average to difficult. It dragged on for months, with several rounds, shifting timelines, and a lot of work for the candidate. The early recruiter conversations seemed promising. I then had additional interviews with hiring managers, followed by separate presentations that I had to prepare and deliver. Those presentations took substantia…
- Docusign Software Engineer interview with three LeetCode-style roundsDocusign · Software Engineer · HR Screen · Mar 2026
My process started with a recruiter call about my background, the role, and the team I was targeting. After that, I had three LeetCode-style coding rounds, each lasting about an hour, along with a behavioral interview. The timeline stretched over several weeks, and I waited around three weeks after the final round to hear back. The technical difficulty wasn't the main issue for me. One round felt…
- Dropbox Product Manager take-home case and presentationDropbox · Product Manager · HR Screen · Mar 2026
After a recruiter screen, I moved into a sequence that increasingly felt like a full product loop. It included a hiring manager conversation, several meetings with product and other stakeholders, a take-home product case study, and a final presentation. The process took about a month. I was told it would be fast, but scheduling became stop-and-start, with meetings being moved on short notice. The…
- Dropbox Software Engineer interview with a proctored CodeSignal assessmentDropbox · Software Engineer · Online Assessment · Mar 2026
I started with Dropbox’s automated assessment. The CodeSignal-style test was proctored and had multiple levels that became stricter as I progressed. I could use Google in a very limited way, mainly for documentation about specific functions I was trying to use, but I still had to solve the core tasks under increasingly tight constraints. After that, I had a recruiter phone screen and moved into t…
- Dropbox Software Engineer interview: OA, phone screen, and delayed feedbackDropbox · Software Engineer · Online Assessment · Mar 2026Rejected
The early stages of my Dropbox process were the most frustrating. I had an OA and then a phone screen where the HR contact didn’t really dig into my background or ask many questions about me. Most of the call was about next steps, and then the process went quiet. What threw me off was how poorly the later communication matched what I was being told. I was repeatedly led to believe things were goi…
- Drw Quantitative Analyst interview focused on competitor strategyDrw · Quantitative Analyst · Other · Mar 2026
What started as an unusually strategic conversation quickly felt unlike a normal hiring process. My initial discussion was with the head of the business, and the focus wasn't on my background or skills. Instead, I was questioned about what the firm's competitors were doing, where they were making money, and what ideas they might be using. The tone made it seem as though the goal was to learn abou…
- Easy Phone Screen, HM Chat, Then I Dropped Before the OnsitePatreon · Data Engineer · Other · Mar 2026Withdrew
Posting my full Patreon loop from February, which I never wrote up. A former coworker referred me into the data team. There don't seem to be many Patreon interview write-ups, so I'm contributing one too. Feb 27: 1st round They gave me a big pile of JSON data that looked like users' personal data, with names, addresses, payment methods and so on, and asked me to do some basic data processing. At f…
- Experian Software Engineer, unclear team details and concurrency discussionExperian · Software Engineer · Other · Mar 2026
I went through a fairly standard multi-stage process, but the experience felt messy. It began with a recruiter phone call where the interviewer spoke extremely quickly and the connection kept breaking. It was difficult to ask questions or clarify anything. Next, I had an online interview with a manager. The interviewer was late, and the conversation didn’t feel grounded in what the team actually…
- Failed on the Onsite's Third RoundSnapchat · Software Engineer · Onsite · Mar 2026Rejected
I interviewed here earlier this year. Snap didn't seem to have any exact LeetCode-original questions, so I'm writing this mostly from memory. Round 1: You're given a list of timestamp events (unordered, can repeat), something like [12:00:01, 01:02:02, 03:03:03]. Implement a query function: given a start time and end time, compute how many events fall in that window. For example, [01:02:01, 01:02:…
- Four HackerRank OA Questions, Cleared in One PassBytedance · Data Scientist · New Grad · Online Assessment · Mar 2026
TikTok (ByteDance) 2026 new-grad OA on HackerRank, four questions, cleared all of them in one pass. Q1: Given a string, ignoring case, count how many positions have s[i] != s[i+1]. Just walk through it once. Q2: Simulate addition — for each digit, add the digit's contribution directly into the answer. Straightforward simulation, that's all it takes. Q3: Given a 0/1 array, you need to support two…
- Four OA Problems, Not Enough TimeUpstart · Software Engineer · Online Assessment · Mar 2026Rejected
Time was way too tight, the problems were super long and wrapped in scenarios, so I spent forever just reading through them. I didn't pass all the test cases on questions 3 and 4, so I definitely failed this one. Let me vent for a second too. I was job hunting around this same time last year, and it clearly feels way harder this year. Can people actually get all 4 of these problems bug-free withi…
