Software Engineer applicants have rated the interview process at Fetch with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 16% positive. To compare, the company-average is 30% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 7 days to get hired, when considering 19 user submitted interviews for this role. To compare, the hiring process at Fetch overall takes an average of 19 days.
Common stages of the interview process at Fetch as a Software Engineer according to 19 Glassdoor interviews include:
Skills test: 42%
Other: 25%
Phone interview: 25%
One on one interview: 8%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Fetch
Interview
1st step in the interview process is having a takehome. No interview or call with HR.
You have a generous amount of time to complete it. They perform 'tests' that take up to 48 hours for them to tell you your results.
However, I believe that they completely disregard the takehome results and just choose the best resume.
Given that they are citing 'compliance' reasons for not discussing what could be better, instead of doing the correct thing and wanting engineers to improve, you should avoid doing this company's interviews.
They sent me a take home assessment which is a program to write and take about 4 hours to finish, then followed up with a interview go over your assessment
Interview questions [1]
Question 1
Finish this assessment and turn in through greenhouse
You have to do a take-home exam. It is a simple API in Go that does some processing. Be careful, they will give you an option to provide a private repo as a submission but then you will receive a rejection email saying that your repo was private and team couldn't review it. This was after I had told the recruiter that I am happy to give the team/reviewer access. Just poor communication in general.
Interview questions [1]
Question 1
Write a simple reciept processing API in go. It is super simple if you know how to use hashmaps.