Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso DoorDash
Colloquio
Interviews were all related to iOS development, very real-world like. But they do expect you to know how to code very fast and without having to lookup the APIs.
1. Recruiter screening.
2. Virtual online coding with an IOS engineer. Need to implement an end-to-end system (get the data, display in UI)
3. Onsite had 1 system design, 1 coding challenge where you have to implement the system that you designed, 1 debugging round and 1 behavioral.
Domande di colloquio [1]
Domanda 1
Have to know how to create an app from end-to-end, without asking for help or looking it up.
Thank you very much for your feedback. We greatly appreciate your perspective on the DoorDash interview process. If you have any additional feedback please email recruiting@doordash.com.
Altre recensioni di colloqui per IOS Engineer presso DoorDash
They were clear in the directions for what to expect. The interview was fair and straightforward. I probably bit off a bit more than I could chew but a competent developer (I’m self taught and learning more official docs currently) would do just fine
Domande di colloquio [1]
Domanda 1
Build a recipe app that loads JSON data and navigates to a view upon a button click.
Ho sostenuto un colloquio presso DoorDash (Toronto, ON)
Colloquio
Recruiter call then a live coding interview. Live coding interview consists of adding features to an app. You get started code and some instructions. You add the functionality while explaining your thought process.
Domande di colloquio [1]
Domanda 1
An option to use UIKit or SwiftUI for the live coding portion.
Ho sostenuto un colloquio presso DoorDash (San Francisco, CA) nel mese di feb 2025
Colloquio
Recruiter reached out on LinkedIn, quick intro call - background, past projects, why DoorDash. A few high-level iOS questions (UIKit, Core Data), nothing deep. Then got the take-home, took ~5 hours - extend an Xcode project, load & display JSON data. Kept it modular. Tech phone screen with an iOS engineer - mostly take-home discussion, (why you structured things a certain way and trade-offs) Some Swift follow-ups (structs vs. classes, GCD, memory management). Know your take-home inside out. Onsite had 4 rounds - 1st was coding on an existing project, debugging + extending functionality. 2nd was live coding, LC medium-hard, focus on performance & clean code. System design was an iOS architecture problem - scalability, state management, API design. Last was behavioral - teamwork, past challenges, handling conflicts. Key is to be sharp on Swift, system design, debugging. Mocked with ex-DoorDash engineers at Prepfully - helped a lot. Got the offer!
Domande di colloquio [1]
Domanda 1
disadvantages of using the Singleton design pattern
