Check out your Company Bowl for anonymous work chats.
Bowls
Get actionable career advice tailored to you by joining more bowls.
Followed companies
Stay ahead in opportunities and insider tips by following your dream companies.
Job searches
Get personalized job recommendations and updates by starting your searches.
Fetch interviews FAQs
Backend Apprentice applicants have rated the interview process at Fetch 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 30% positive. This is according to Glassdoor user ratings.
Candidates applying for Backend Apprentice roles take an average of 11 days to get hired, when considering 4 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 Backend Apprentice according to 4 Glassdoor interviews include:
Skills test: 33%
Phone interview: 33%
One on one interview: 33%
Here are the most commonly searched roles for interview reports -
The interview process was highly positive and engaging. I completed a coding challenge beforehand and received an invitation for an interview. Post-interview, they offered constructive feedback, which I found valuable and appreciated.
Interview questions [1]
Question 1
Before interview you have to do a coding challenge.
I applied online. The process took 1 day. I interviewed at Fetch (Chicago, IL)
Interview
Overall it was fine, It was a pretty long being around 5 hours, but it's just because they are expecting a lot out of you not just in terms of Basic software engineering but also database knowledge and system architecture.
Interview questions [1]
Question 1
They asked me how to develop the system architecture(Servers, databases, CDN, etc) and how to properly implement one in the imaginary company they made up for the question.
First they send you a take home project. If your project is good enough, you get an interview with an engineer going through your code; be prepared to answer production level questions. They seemed to expect a high level of experience for an apprenticeship position.
If you fail the interview, they'll give real feedback, which is appreciated.
Interview questions [1]
Question 1
If you were to use a database here, would SQL or NoSQL be better?