Fetch logo

Fetch Ios Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 20 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
25% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Fetch.

Showing 3 of 20
Fetch logo
Fetch

iOS Engineer

Engineering · a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Technical screen Take home
Interview formats
Coding Technical

The application process started with a Capture the Flag challenge. After finding the four flags, I received a take-home assessment. I completed the take-home assessment, which involved creating a recipe app. Unfortunately, I was rejected after submitting it, receiving a generic email. It seems like a boilerplate response because a friend who applied for a different role got the same email after their take-home. This makes me doubt if my code was actually reviewed. I suspect they use an AI to evaluate the code, which is ironic given they advise against using AI for the assessment. I'd suggest not wasting your time on this company's interview process, which seems excessively difficult for a company that likely treats employees as mere numbers.

Confirmed questions1 question
  • Build a recipe application that fetches recipes from a given endpoint and presents them according to your design choices.
Fetch logo
Fetch

IOS Engineer

Engineering · a year ago

Senior Easy Negative experience No offer 3 rounds
Interview process
Take home Recruiter call Technical screen
Interview formats
Technical Coding

Pretty negative experience. They start with an automated email distributing an unpaid take home project lasting 4-5 hours, and this is before a recruiting call. Meaning you have to complete a five hour unpaid project (that requires unit test coverage) before getting internal information to help you decide if it's a position you're interested in. I didn't even know if the salary range was in my target before completing the project (it was below my target). This was a clear red flag but I decided to proceed for the practice and got an invite to the next round where there were a couple key problems. First of all, they didn't include vital information on how I would need to have my environment prepared which made the interview very messy. Second, I hate to say this because it's not the individuals fault its the company, but the interviewer didn't really know the nuances of what they were questioning me on.

Confirmed questions1 question
  • Regarding Swift 6, are you aware that it mandates the use of actors even when your class already implements thread safety through other methods?
Fetch logo
Fetch

IOS Software Engineer

Engineering · more than a year ago

Intern Average Positive experience Accept offer 3 rounds
Interview process
Take home Phone screen Technical screen Offer
Interview formats
Technical Coding

I applied online and got a take-home test with no deadline. After finishing that, I had a phone screen with an iOS dev who reviewed my project, asked questions, and gave advice on how to improve it. Then came the technical interview where I talked with several iOS devs about Swift, architecture, UIKit, and communicating with UX. At the end of that interview, I got an offer. The whole experience was fast, respectful, and they clearly put a lot of effort into making it a good process.

Confirmed questions1 question
  • Can you explain the difference between reference types and value types?

Fetch Ios Engineer Interview Questions

Quoted word for word from Fetch interview reports.

Regarding Swift 6, are you aware that it mandates the use of actors even when your class already implements thread safety through other methods?

Read reports

When a user taps on an item in the table view, can you show a detailed view for that event?

Read report

Can you explain the difference between reference types and value types?

Read report

Can you add functionality to mark an event as a favorite?

Read report

Build a recipe application that fetches recipes from a given endpoint and presents them according to your design choices.

Read report

Formats, difficulty and experience

Across all 20 Fetch interview reports.

Interview formats

Technical 43.6%
Coding 38.5%
Behavioral 10.3%
System Design 5.1%
Other 2.6%

Interview difficulty

Easy 25%
Average 65%
Difficult 10%

Candidate experience

Neutral 25%
Negative 50%
Positive 25%