Real, anonymous reports from people who interviewed for Software Engineer at Rocket, newest first and distilled into what to expect across the loop.
I started with a recruiter phone screen where the focus was mostly fit and motivations—why I wanted to join the company, plus general background questions. After that, I moved to interviews on the team side, typically on video. Those sessions were largely behavioral, but they were also anchored in my past experiences, so I ended up going deep into projects and decisions I’d made rather than doing anything abstract.
I went into a group-style discussion round where the format was a bit chaotic: four team leads were asking questions, and the flow didn’t feel coordinated. One person would jump in with technical questions, and then someone else would switch abruptly to behavioral topics, so I had to constantly reset my answers.
The interview process typically begins with a recruiter phone screen focused on fit, motivations, and background. This initial conversation sets the tone for the subsequent technical discussions.
Candidates undergo a technical assessment that often includes coding tasks, which may involve real-world problem-solving rather than traditional algorithm questions. The assessments can vary in format, including online coding tests and take-home assignments.
Later stages often involve panel interviews where multiple interviewers ask questions in a somewhat chaotic format, mixing technical and behavioral topics. This can lead to a disjointed experience for candidates.
Technical interviews may require candidates to demonstrate understanding of design principles and coding practices, with an emphasis on explaining their thought process and decisions during coding tasks.
Candidates report challenges with the assessment environment, including invasive monitoring tools and unclear instructions, which can detract from their performance and overall experience.
Feedback from interviewers can be inconsistent, with some candidates feeling that rejection reasons were vague or arbitrary. Clear communication throughout the process is noted as an area for improvement.