I applied online. The process took 4 weeks. I interviewed at Rocket (Detroit, MI) in Jun 2017
Interview
There was an initial screening call where I was evaluated to see what positions I was the best fit for across the family of companies. I had already done this myself on their website and applied to the appropriate position so it didn't change much for me.
There was then another phone screen for the specific position, standard questions. They will also throw in some behavioral questions in these phone screens, so be prepared for that. I was then sent an online coding exercise which were general algorithmic problems of the type you would see on interview prep sites.
After that there was a phone interview which was a conference call with multiple engineers, talked about previous experience, etc.
Finally there was an on-site interview which was also with several team members at once. Was worried that this type of format might be more intimidating but it really wasn't. There were some technical questions but many of the questions focused on passion for software, side projects and interests. They seem to put a lot of weight on this. On the spectrum of aptitude vs. knowledge, I would say that Quicken definitely cares more about knowledge. They seemed focused a lot on the way I had done things in the past, which I felt was mostly irrelevant since I was applying to a new job, not my old one.
One frustrating aspect of the process was that the recruiters seem to not want to do any business via email, and only communicated by phone. This would be fine if they didn't insist on working the same hours as those they are recruiting. I can easily read and respond to emails from my desk, but I cannot take calls about other jobs. This is a big deal if you work in an office and have a 5-10 minute walk to find a private area to make these calls. So there ended up being a lot of unnecessary phone tag and I almost just gave up a couple times. This wasn't an issue with other companies as they all use email.
Interview questions [1]
Question 1
Questions about my primary programming language, OOP, design patterns, passion questions (side projects have you/are you working on, technologies you're excited about, programming languages you've learned in your free time, opinion on current trends in the industry etc.)
I applied through college or university. I interviewed at Rocket (Chennai) in Mar 2026
Interview
The first round was long coding, where we need to create an application for student availability during classes. We can draw either a class diagram or an uml diagram. Interaction with the hr and basic output matters.
The interview was well-structured and professional, with clear questions focused on real-world scenarios. The panel was respectful and engaging, creating a comfortable environment to discuss technical skills, problem-solving approach, and past experience.
I applied online. The process took 2 weeks. I interviewed at Rocket in Apr 2025
Interview
Four rounds/steps:
1. Phone screen
2. Online coding assessment
3. Team interview/coding interview
4. Architecture & Design
The phone screen was simple and nothing noteworthy. The online assessment had two videos recording parts and one coding assessment. One thing to note the online tool used for the coding assessment required in my opinion an invasive plugin that monitors browser tabs (which is removed after leaving the assessment). Additionally the assessment is rather poorly implemented, the instructions tell you that the response is JSON, but in fact the response it HTML/Text with JSON body for the payload. The team interview is where I ended applying for Rocket due to the following reasons, one of the employees conducting the interview was rather arrogant and condescending believing that her way was the only way, especially on code assessment section (which confuses me on why have the initial online coding assessment). The coding assessment was literally only 20 minutes long asking to implement a solution calling an API, however, the team did not disclose ahead of time that I would be expected to use my own IDE, which meant some quick set up work. The API(which was rather a poorly implemented API -never seen an API that implements pagination without allowing an input for number of items per page) was rather simplistic, however, as I alluded despite multiple ways to arrive at the same result that would not impact performance, she was adamant that her way was the only way. This is after her changing the problem 3 times after I arrived at a solution to the original problem. This was all in a short 20 minute window. She then rushed the interview with 10 minutes remaining for my questions, instead of allowing me to finish the last little change she requested. At the end she was all "we done this so many times, we know exactly what we are looking for." Which told me all I needed to know that Rocket employees do not practice there own isms that they link to in every email of the interview process. At the conclusion of the interview I felt no longer wanting to continue in the application process. I am sure I am not the only one that felt like the team rubbed them the wrong way.