READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 58 of 153
Interview experiences · Dropbox
Dropbox Software Engineer interview with a monitored CodeSignal test and Deep Dive
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…
Interview experiences · Dropbox
Dropbox Software Engineer interview with a proctored CodeSignal assessment
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…
Interview experiences · Dropbox
Dropbox Software Engineer interview with CodeSignal and code review
My Dropbox process followed a fairly standard rhythm: CodeSignal first, then technical and behavioral interviews, with recruiter check-ins between stages. After I applied, I received the online assessment and moved into interviews focused on coding and problem-solving. The structure felt straightforward, with clear checkpoints between steps. The technical interviews covered algorithm and data-str…
Interview experiences · Dropbox
Dropbox Software Engineer interview with multi-week gaps between stages
My interview process stretched over a long period, and the gaps between stages made it hard to keep momentum. There were multi-week pauses, and the schedule didn’t feel tightly managed from one step to the next. Some interviewers were very new, so the flow sometimes felt more like they were learning the rubric than evaluating me. The technical parts were awkward too. The coding setup didn’t work…
Interview experiences · Drw
Drw Customer Success Engineer interview: Three back-to-back interviews followed by a location rejection
I started with an internal recruiter reaching out about a very senior trade support type of role. My first call was with HR, and it felt like it went well. I then spoke with the hiring manager about my background, the team, and what the role involved. The conversation felt a little unfocused on their side, but it was still decent overall. The role I initially interviewed for didn't work out becau…
Interview experiences · Drw Holdings
Drw Holdings Customer Success Engineer interview, role reopened
I interviewed for a Software Engineer path that grew out of a need for someone very senior in trading support. The process moved at a moderate pace and focused heavily on experience fit. I first spoke with an internal recruiter about my background and why I was interested, then moved to a hiring manager interview. That conversation focused mainly on my experience and learning about the team and r…
Interview experiences · Drw Holdings
Drw Holdings Quantitative Analyst interview: probability, Fermi questions, and a market-making game
My process started with an online assessment and then moved to a video interview. The OA felt manageable compared with some of the harsher versions I'd heard about. It covered linear algebra and probability, and the live interview extended those topics into more traditional quant reasoning. The interview included expected value and basic probability questions, a few Fermi-style problems, and some…
Interview experiences · Drw Holdings
Drw Holdings Quantitative Analyst seven-question math test and technical round
I remember the process feeling intense from the start. It began with a timed math test containing seven questions. The limit was about 45 minutes, and the topics included linear algebra, probability, optimization, and brain-teaser-style problems. The questions were difficult and required quick work, so I felt that small mistakes could compound fast. After the initial stage, I had a Zoom technical…
Interview experiences · Drw Holdings
Drw Holdings Quantitative Analyst: technical interview and superday with a brief brain teaser
I had a relatively short, structured process that began with an HR screen, followed by one technical interview and then a superday. The interviewers were thoughtful and easy to talk to, and they seemed willing to give feedback throughout the process. The technical portion focused on quantitative thinking. It didn't feel like they were trying to trick me with obscure material. The goal seemed to b…
Interview experiences · Drw Holdings
Drw Holdings Quantitative Analyst timed probability assessment
I started with a timed online math and probability assessment. The questions felt genuinely hard, and the time limit was strict. My impression was that it tested how quickly I could work through probability mechanics. When I didn't make it through that stage, the process effectively ended there. In another attempt, I got further and kept running into probability and options concepts. After an ini…
Interview experiences · Drw Holdings
Drw Holdings Software Engineer interview with a 2.5-hour Codility assessment and superday
I went through an online assessment and technical sequence that moved quickly from testing to rejection, with very little positive feedback. The Codility OA was LeetCode-style. The technical interview covered algorithms and data structures, along with operating systems, networking, and system-design topics. In one version of the process, the final stage was a superday after the first technical ro…
Interview experiences · Drw Holdings
Drw Holdings Software Engineer interview with a 45-minute C++ technical round
I ran into a C++-heavy interview loop where the main challenge was low-level correctness and syntax rather than just LeetCode-style problem solving. The process started with an assessment and then a short first interview. In a 45-minute C++ technical interview, I was tested on C++ knowledge and low-level details, with less emphasis on pure LeetCode. In a similar journey, I solved a LeetCode-like…
Interview experiences · Drw Holdings
Drw Holdings Software Engineer, OA-first process and technical onsite
I went through an OA-first process that ended with an intense technical onsite. The structure was clear, but I didn't receive an offer. The online coding assessment had several LeetCode-style questions. I scored highly, then didn't hear back about the next step. Another version of the process began with a proctored OA. After that, I had a technical interview with an engineer from the team I was m…
Interview experiences · DRW
DRW Intern Software Engineer Interview Experience — A 3-Problem Codility OA With a 5-Part Robot Pathfinding Puzzle
I applied to DRW Singapore for the SWE C++ Internship. The first round was a Codility OA, 150 minutes for 3 problems. There are n people, each with a distinct ability value in [1, n]. You're given a[i], the ability value of the i-th person. n is guaranteed to be a power of 2, with n <= 200,000. Then several rounds of a tournament are held. In each round, players are paired off left to right (#1 v…
Interview experiences · DRW
DRW New Grad Quantitative Researcher Interview Experience — Auto-Rejected Before the OA Deadline Even Hit
I cold-applied online to DRW's US New Grad Quantitative Researcher role. Less than a week after applying, I got an online assessment invite. The email said the OA link would expire in seven days, and there was no other deadline notice anywhere. Then, five days later, I got an email saying I hadn't finished the OA in time, and I was flat-out rejected. But the OA link was still valid, so I went ahe…
Interview experiences · DRW
DRW New Grad Software Engineer Interview Experience — A Greedy Deletion Problem on a String of 1s and 2s
I got a string greedy problem: Given a string digits made up only of '1' and '2', which represents a positive integer. You can delete 0 or more characters from it, and after the deletion: the number of remaining '1's must be even; the number of remaining '2's must also be even; and, while satisfying those first two conditions, the final integer should be as large as possible. Note that you can on…
Interview experiences · DRW
DRW New Grad Software Engineer Interview Experience — A Greedy String-Parity Coding Problem
I ran into a greedy string problem. Given a string digits made up only of the characters '1' and '2', representing a positive integer, you can delete zero or more characters. After deleting, the requirements are: The remaining '1's must appear an even number of times. The remaining '2's must also appear an even number of times. Subject to those two conditions, the resulting integer should be as l…
Interview experiences · Drw
Drw Quantitative Analyst interview focused on competitor strategy
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…
Interview experiences · Drw
Drw Quantitative Analyst interview: options intuition, probability, and a superday
My process started with an online assessment focused mostly on probability. The math felt grounded enough to be solvable, but it was still demanding under the time limit. After that, I had a semi-technical HR conversation, followed by the technical interview phase. The technical portion combined behavioral questions with quantitative problems. I was asked about options pricing and the underlying…
Interview experiences · Drw
Drw Quantitative Analyst interview with timed probability and option-pricing questions
The process felt structured from the start. I went through an HR screening and then entered a technical interview phase. The tone there was more laid-back than I expected, and the interviewers were thoughtful and willing to keep things moving. Overall, it felt standard, with a clear sequence from screening into technical evaluation and no random detours. The math and probability section involved…
Interview experiences · Drw
Drw Quantitative Analyst math test and options theory interviews
After a recruiter call, the process moved into a math and probability test. It was difficult enough that it didn't feel like a formality. Then came an HR screen followed by several interviews across different teams, with questions focused heavily on probability and option intuition. Early in the process, I was told that option theory was something they taught internally and wouldn't necessarily b…
Interview experiences · Drw
Drw Software Engineer interview reaching the fourth technical round
I made it as far as the fourth technical round. The process felt like a series of technical screens that built on one another. Eventually, I reached a C++-focused interview with a C++ problem. After that, the conversation shifted to my personal projects, which was a welcome change from the problem-solving questions. I had already completed an HR call earlier in the process. Overall, the structure…
Interview experiences · Drw
Drw Software Engineer interview with a one-hour coding assessment
The process began with an online coding assessment that took me about an hour, even though it was described as a roughly two-hour test. I felt confident after finishing it, but I didn’t hear anything afterward and received a rejection notification a couple of days later. I also interviewed with DRW for a technical role in Singapore, and that process took much longer than I expected. I completed e…
Interview experiences · DTCC
DTCC Business Analyst interview: hiring-manager conversation followed by silence
After a recruiter call, I interviewed with the hiring manager. The conversation was straightforward, but I never really heard back after it. More than a month passed, and the recruiter stopped responding to update requests. The prolonged silence made what should have been a final stage feel flat and unprofessional. I received no clear next step or even a simple status message, only a waiting game…