Fetch Test Automation Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Fetch.
Fetch
QA Automation Engineer
Entry Difficult Negative experience No offer 3 rounds
Interview process
Take home Recruiter call Technical screen
Interview formats
Coding Technical Behavioral
The interview process started with a take-home project that took a few hours to complete. Initially, I noticed the project was titled 'SDET', which seemed different from a QA Automation Engineer role, but I proceeded with it. Following that, there was a recruiter interview which went well. The next step was a technical interview with a team member to discuss the project and my experience. The confirmation email stated we'd discuss the submitted exercise, but what wasn't clear was that beyond the take-home part, a live coding extension of the project was required. If the project wasn't structured for this extension, it would be problematic. The interviewer mentioned that QA Automation Engineers and SDETs are considered the same at this company, which was another point of concern. Overall, the process didn't seem set up for candidate success. They expected candidates to research the company, but that research wasn't part of the discussion. They also need to be clearer about the role they're hiring for. The wide salary range was also a bit of a red flag. QA candidates should be cautious when considering Fetch, and good luck to them.
Confirmed questions1 question
- Can you adapt your take-home project to identify a counterfeit among 20 coins, based on its original design for 9 coins?
Fetch
Software Development Engineer in Test
Mid Difficult Positive experience Accept offer 4 rounds
Interview process
Take home Technical screen Recruiter call Onsite
Interview formats
Technical Behavioral
So I had this technical exercise to do first. Then a technical interview where we talked about that exercise. After that, I met with the hiring manager to get a good idea of the team and company. Then there were two panel interviews with people from the manual and automated QA teams, which gave me a better feel for the team.
Confirmed questions1 question
- What do you find most crucial in a test framework?
Fetch
Senior Software Development Engineer in Test
Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Technical Behavioral
Despite a tight schedule, they accommodated the interview process. It had 3 stages: first a recruiter chat, then a call with the hiring manager, and finally multiple onsite interviews. I got feedback just 10 minutes after my last onsite interview. It was a really good experience overall.
Confirmed questions3 questions
- Can you describe the core components of an automation framework?
- Tell me about your experience testing mobile applications using automation.
- Could you answer some fundamental questions about Object-Oriented Programming?
Fetch Test Automation Engineer Interview Questions
Quoted word for word from Fetch interview reports.
“Could you create a command-line utility for fetching geolocation data?”
Read reports →“Could you submit an automated test that uses our internal site?”
Read reports →“Can you describe the core components of an automation framework?”
Read reports →“Can you adapt your take-home project to identify a counterfeit among 20 coins, based on its original design for 9 coins?”
Read reports →“Can you complete a coding exercise where you compare gold bar weights on a website to identify a counterfeit?”
Read report →“What do you find most crucial in a test framework?”
Read report →“Could you answer some fundamental questions about Object-Oriented Programming?”
Read report →“Tell me about your experience testing mobile applications using automation.”
Read report →Formats, difficulty and experience
Across all 8 Fetch interview reports.