Software Engineer applicants have rated the interview process at Rocket with 2.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 40% positive. To compare, the company-average is 61.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 19 days to get hired, when considering 93 user submitted interviews for this role. To compare, the hiring process at Rocket overall takes an average of 19 days.
Common stages of the interview process at Rocket as a Software Engineer according to 93 Glassdoor interviews include:
Phone interview: 36%
Group panel interview: 14%
Presentation: 9%
One on one interview: 8%
Skills test: 8%
Background check: 8%
IQ intelligence test: 6%
Personality test: 6%
Drug test: 5%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at Rocket (Reno, NV) in Apr 2021
Interview
3 rounds, one with a recruiter that initially contact me (he was actually great and diligent), one with some senior devs that ask some technical questions, then if you get by that you have a 2 hour assessment with more devs, 1 hour coding on Hackerrank and another hour of technical questions again.
Two hours of technical questions is a bit much, not a fan of these types of interviews. I am not a dictionary and any developer knows we often use Google for things. It's a frustrating interview process, I provide ample work within my portfolio and I'm more of a do-er than a let's memorize every fancy technical term thrown my way. My work speaks for itself not my ability to memorize monotonous catch phrases.
The coding assessment also was awful. First question was a simple find the sum of numbers in an array. Very real world. Then there was a Fibonacci problem (I don't have a typical CS background and never bothered with algorithms like this since it's rarely used in the real world for most web devs), the third was calculating the area of a triangle based on coordinates (again, I haven't touched geometry since HS), and the final was two arrays and picking the max shares you can buy given your set limit (more real world-ish).
All in all, not a fan of this type of an interview process. Evaluate my past work, or have me work on something a little bit more relevant to what people do day in a day out as a web dev.
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.