Real, anonymous reports from people who interviewed for Mobile Engineer at Fetch, newest first and distilled into what to expect across the loop.
After applying, I was sent a take-home coding problem. I worked through that first stage remotely, then about a week later I had a live, hour-long interview where we reviewed what I’d done and they added a small technical problem on top.
The recruiter touchpoint led into a practical sequence of interviews that felt like a full morning of screens. I spent that block talking with a product manager and other engineers on the team, and the format was very focused on doing real engineering thinking rather than abstract discussion.
Candidates typically start the interview process with a take-home coding assignment that requires building a small app or completing a coding challenge, often involving specific technologies like Swift or REST APIs. The time commitment varies, but candidates report feeling that the expectations can be high without clear context.
The technical interviews often involve a thorough review of the take-home project, where candidates are expected to explain their code choices and discuss related technical concepts, such as concurrency and architecture. The atmosphere can range from collaborative to intense, with a strong emphasis on practical engineering thinking.
Interviews typically include behavioral questions that assess candidates' communication skills and cultural fit, often integrated into the technical discussions. The tone of these interactions can vary significantly, with some candidates reporting a positive and respectful atmosphere, while others experienced a more negative or condescending approach.
The interview process can be lengthy and structured, often involving multiple rounds that may include technical, behavioral, and cross-functional interviews. Candidates noted that the process felt like an extensive evaluation day rather than a series of disconnected interviews, which could be exhausting.
Candidates frequently reported issues with communication throughout the process, including generic rejection emails and a lack of meaningful feedback after interviews. This left many feeling uncertain about their performance and the decision-making process.
While many candidates appreciated the professionalism and structure of the interview process, the outcomes often resulted in rejections without clear explanations. Some candidates felt that the process did not align well with their expectations or the role's requirements, leading to a sense of frustration.
