Software Engineer applicants have rated the interview process at Goodreads with 3.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 35.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 21 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Goodreads overall takes an average of 14 days.
Common stages of the interview process at Goodreads as a Software Engineer according to 2 Glassdoor interviews include:
Phone interview: 33%
Other: 17%
Skills test: 17%
Personality test: 17%
Group panel interview: 17%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 weeks. I interviewed at Goodreads (South San Francisco, CA) in May 2019
Interview
1st: General Interview 2nd: Personality fit 3rd: Live coding interview First 2 were quite good, really easy to speak through. Didn't get to learn a whole lot on the position. Coding interview part was fun. I messed up on that part which was a good learning experience. It was my first one at the time and was weird doing the live coding together
Interview questions [1]
Question 1
General personality questions Live coding question related to a chess question - write a function to visit each square on the board
I applied through a recruiter. The process took 2 weeks. I interviewed at Goodreads (San Francisco, CA) in Oct 2013
Interview
The "best" (worst) part of the initial communication is that after exchanging emails with the recruiter and agreeing on the interview date, I wasn't sent the quite usual email of "our company is located at <address>, please sign the attached NNN ". You may think that was little but searching for the company address is not optimal, what if they *just* moved? Later on... I was actually asked for the signed NNN after I arrived at the reception on the day off. Great.
After the interview, possibly the same recruiter didn't send feedback. No email, nothing at all actually.
I had about four interviewers, with one of them very professional and likeable perhaps he was happy outside of work with his sporting endeavors (judging by the clothing). The others were just average. One was a bit edgy and surprising to ask me a question about coding in Ruby, where the job wasn't for that and I had explicitly stated I haven't done that. I thought I read his stuff well enough for never having touched that.
Other questions were: traversing through a matrix, arranging layouts on a mobile device screen and so on.
There was a phone screen + coding; additional exercise;; and then an on-site interview.