Fetch Android Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Fetch.
Fetch
Android Engineer
Intern Average Positive experience No offer 2 rounds
Interview process
Take home Technical screen Recruiter call
Interview formats
Coding Technical Behavioral
Got an OA where I had to build a simple app, and then the interview was mostly about digging into why I made certain coding decisions. They covered stuff like Coroutines, flows, architecture, activity lifecycle, and configuration changes. Towards the end, there were a few behavioural questions.
Confirmed questions2 questions
- What is the definition of coroutines?
- What are the reasons for using coroutines over threads?
Fetch
Android Engineer
Entry Average Negative experience No offer 2 rounds
Interview process
Take home Recruiter call
Interview formats
Coding
This was a total waste of my time. Like others mentioned, I got a take-home test that took me about half a day. I spent a bit more time than planned because I added more than the minimum to try and impress. A couple days later, I got an automated email saying they were going with other candidates. No feedback at all. I get getting rejected, I've been rejected hundreds of times. But if you're going to give a coding assessment that takes hours, the least you can do is show some respect for people's time and give feedback from a real person or engineer. If my experience or resume was the issue, why even move me to the assessment stage? If my skills weren't what they needed, I'd be fine with an initial automated email. Please do better with valuing people's time. Coding assessments can take hours or even days for some. Don't follow up with an automated email; it doesn't help engineers grow. If the issue is too many candidates, send fewer people to the assessment so you have time to actually give feedback personally or via email/phone.
Confirmed questions1 question
- My recruiter sent me a coding assessment.
Fetch
Android Engineer
Mid Difficult Neutral experience No offer 5 rounds
Interview process
Recruiter call Take home Onsite Technical screen Panel Group Presentation
Interview formats
Coding Technical System Design Coding Technical
Got an email saying my resume looked good, then immediately had a coding assignment. Since I did well, they had me come in for a whole day. First, I had to figure out how I'd design a screen. Then I met someone non-technical. After that, I did a whiteboard leetcode session, which honestly didn't help much in figuring out how I'd do designing a screen or feature. To wrap up the day, when I was totally exhausted, they had me do a live-coding problem-solving exercise using a UI framework I'd never used before.
Confirmed questions4 questions
- Discuss how you would design and build a specific feature.
- Discuss how you would design a screen.
- Complete a coding problem on a whiteboard.
Fetch Android Engineer Interview Questions
Quoted word for word from Fetch interview reports.
“What is the definition of coroutines?”
Read reports →“What are the reasons for using coroutines over threads?”
Read reports →“Could you build a basic app that makes an API call and then shows the retrieved data within a list format?”
Read reports →“Solve a coding problem live using a UI framework you're unfamiliar with.”
Read reports →“What would be your approach if a specific feature was not supported by Compose?”
Read report →“Describe a situation where you had a disagreement with a colleague.”
Read report →“What are your thoughts on specific Android development aspects related to the take-home project?”
Read report →“Tell me about the app you developed.”
Read report →“Can you explain how you went about building your application?”
Read report →Formats, difficulty and experience
Across all 11 Fetch interview reports.