Taro Logo

Software Engineer Interview Experience - Detroit, Michigan

February 1, 2017
Negative ExperienceNo Offer

Process

One of the most time-consuming and haphazard interview scheduling I have ever come across. I reached out to a recruiter, and she set me up for an interview with another recruiter. The interview was mostly asking about behavioral questions: how did I solve this, what actions I took, salary expectations, and the like. She told me it would take her some time to find the team that would match my skills, whereas I had already expressed interest in one of the job positions on their career website. It was after a month that I finally received another interview call, but again, I had to go through the same recruiter call, similar to the one I had done before. What a waste of time! Instead of collaborating within the company, they simply chose to waste candidates' time and their own time by conducting these non-technical interviews. I would have preferred to speak with an engineer instead. It was a similar experience to what I had read previously on Glassdoor. They will give you a call whenever they would like to talk to you, instead of scheduling a call, which I found really weird.

Once I was scheduled for a technical phone screen, I didn't even know what position I was interviewing for. There were three people on the call besides me, and they asked me questions on HTML5 features, CSS properties, ES6 features that I liked most, how I handle cross-browser compatibility issues in JavaScript, Git commands, what my deployment process is like in my company, how I test, and things like that. I felt the interview went well, only to be told that my skills didn't match the team I interviewed with. They said they have many other openings and would schedule me with some other team once they see a match.

I was already out of patience with this company and speaking with endless recruiters. I didn't follow up with them after being told this. Thanks, I will not be applying here again, only to be made to talk with multiple recruiters who are trying to sell their company.

Questions

HTML5 features, CSS properties, ES6 features that I liked most, how do you handle cross-browser compatibility issues in JS, Git commands, what's your deployment process like in my company, how do you test apps?

Was this helpful?

Interview Statistics

The following metrics were computed from 35 interview experiences for the Rocket Mortgage Software Engineer role in Detroit, Michigan.

Success Rate

23%
Pass Rate

Rocket Mortgage's interview process for their Software Engineer roles in Detroit, Michigan is very selective, failing most engineers who go through it.

Experience Rating

Positive34%
Neutral20%
Negative46%

Candidates reported having negative feelings for Rocket Mortgage's Software Engineer interview process in Detroit, Michigan.

Rocket Mortgage Work Experiences