Software Engineer applicants have rated the interview process at Thinkful with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 25% positive. To compare, the company-average is 36.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 14 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Thinkful overall takes an average of 18 days.
Common stages of the interview process at Thinkful as a Software Engineer according to 4 Glassdoor interviews include:
Phone interview: 33%
Presentation: 22%
Drug test: 11%
One on one interview: 11%
Group panel interview: 11%
IQ intelligence test: 11%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Thinkful in Mar 2019
Interview
The interview process consisted of a phone screen, a take-home technical assessment, a follow-up video assessment, and a background/reference check. I spent the recommended amount of time on the take-home and was able to finish an imperfect MVP with a few basic tests. The follow-up assessment built on the take-home and involved answering questions from engineers at Thinkful including the VP of engineering.
Interview questions [1]
Question 1
If you had to make sure this part of the UI was updated in real-time, how could you go about doing that?
I applied online. The process took 2 weeks. I interviewed at Thinkful (New York, NY) in Apr 2019
Interview
1. A call with the recruiter about your resume, background, and why you want to join Thinkful, etc.
2. A take home assessment which they say it takes about 2 - 3 hours but really takes like 8+ hours. You have to modularize react code, connect data from an API, create a backend server, and implement testing (they ask you alot about it during the technical).
3. Technical interview consists of asking you about your take home, emphasis on testing portions, and asking you to write a function/method on the spot in the take home assessment. After that it's a system design question.
Interview questions [2]
Question 1
Testing: What tests did you implement in the code and why?
The interviewer was rude, argumentative, and overly confident in his technical skills (making several wrong assertions during the framework discussion). It was the first interview I've ever had to cut short out of disinterest in moving forward.
Interview questions [1]
Question 1
How do you design DB models with performance in mind?