DriveWealth Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 20 interview experiences · FREE TO READ
Which role are you interviewing for?
11 roles · 20 reportsCandidate interview experiences
First-hand accounts from people who interviewed at DriveWealth.
DriveWealth
UX Designer
Mid Difficult Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Case
It was a long and kinda annoying process. They asked a lot of questions that didn't seem to have anything to do with the job, and they were kinda vague about how far you could go in the company. The recruiter seemed distracted or like they weren't really listening to my questions.
Confirmed questions1 question
- Given an obscure product problem, what would be your solution approach?
DriveWealth
QA Engineer
Entry Difficult Neutral experience No offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
Behavioral Technical
My interview experience with DriveWealth was really bad. The whole process felt really unprofessional. I did well in the first round, answering everything and finishing the tasks, but they still called me for a second technical interview. In that second round, the interviewer was super unprofessional, asking what seemed like ChatGPT questions and being distracted by their phone the whole time. It was annoying and frustrating. I definitely expected a more professional and structured interview, but it wasn't like that at all. Overall, a very negative experience.
Confirmed questions3 questions
- Can you tell me about the projects you've worked on in the past?
- What were some of the challenges you encountered during those projects?
- How did you handle and overcome those challenges?
DriveWealth
Software Engineer
Mid Average Positive experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite Background check
Interview formats
Technical Coding System Design Behavioral
The interview process at DriveWealth was pretty quick, only about two weeks total. It started with a recruiter call to chat about the company and the position. Then, I had a take-home coding challenge, which was in React and had a 3-hour time limit. After submitting the take-home, I had a technical interview with the hiring manager. We reviewed my take-home assessment and also discussed some System Design concepts. This interview lasted an hour. The final stage was a 30-minute behavioral interview with the CTO, focusing on my experience and some backend practices, even though the role is mostly frontend. Unfortunately, I received a generic rejection email without any specific feedback, which makes me wonder if they already had someone in mind or if it was a speculative posting. Still, the speed of the process was a nice change.
Confirmed questions3 questions
- Can you explain what Garbage Collection is in a backend context?
- Could you describe scenarios where an ArrayList would be preferred over a Linked List?
- What are the use cases for a Stack versus a Queue?
DriveWealth
Customer Success Lead
Lead Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Panel Presentation
Interview formats
Behavioral Technical Presentation
The hiring process didn't go exactly as originally planned. I was initially told that there would be a short exercise and 3 video interviews. After the 3rd interview I was surprised to be scheduling for a 4th and then even a 5th interview! However I didn't mind at all, I got to meet some amazing people and I had a fun time picking everyone's brain. The interviews were fair, more like casual conversations. The questions asked shouldn't be too difficult if you have genuine skills, knowledge, and experience that's related to the role I'm question.
Confirmed questions2 questions
- Can you share an instance where you introduced a new process?
- How would you lead in a situation lacking resources?
DriveWealth Interview Questions
Quoted word for word from DriveWealth interview reports.
“What's a way to set the length of a javascript array to 0 without re-declaring it?”
Read reports →“What does this Java 8 code output/do?”
Read reports →“Can you explain the syntax of Java 8?”
Read reports →“What if scenarios in Java 8?”
Read reports →“What are the use cases for a Stack versus a Queue?”
Read report →“Can you explain garbage collection and deadlock?”
Read report →“Can you explain what Garbage Collection is in a backend context?”
Read report →“Could you describe scenarios where an ArrayList would be preferred over a Linked List?”
Read report →“Can you list some potential reasons why a Spark job might be slower than anticipated?”
Read report →Formats, difficulty and experience
Across all 20 DriveWealth interview reports.