Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso DoorDash nel mese di set 2019
Colloquio
I applied online and got contacted by the recruiter. First task was a take home project over the weekend. Preferred language of choice is swift. Though my current job is in Objective-C, I was trying to make a switch to swift so decided to do the project in swift anyways.
The second round was a phone screen with one of the iOS engineers and the recruiter had mentioned that it would be a discussion on the take home project. Unfortunately, it was not just a simple going over the project. In fact, we didn't go over the project at all !!! It was a freaking iOS deep dive with good amount of focus on swift !!! I tried to convey that my experience was mostly Obj-C and purpose of doing it in swift was to show that I can learn something quick and still come up with a good project. I guess it became a chicken and egg problem.
Honestly, I blame the recruiter here. He didn't convey properly as to what to expect in the phone screen, otherwise I would have been definitely well prepared even with swift questions. But the devs had something else in mind. It would have saved time for all of us.
Domande di colloquio [1]
Domanda 1
Drawbacks of using storyboards
difference between protocols and inheritance
difference between structs and classes
mutating structs and mutating classes
difference between unowned and weak
Explain retain cycle with example
Drawbacks of using singleton
Difference between MVC and MVVM
what is MVVM-bindings
escaping vs non-escaping closures
what is responder chain
Difference between GCD and operation Queues
Frames vs Bounds
Thank you so much for sharing your feedback - we are very sorry to hear that your interviewing experience with us did not meet expectations. We strive to ensure that each candidate feels welcomed, respected, and prepared in their interactions with our hiring team, and we are committed to utilizing your valuable insights to improve for the future. If you have additional feedback that might help us better our candidate experience, please send to recruiting@doordash.com.
Esperienza positiva
Colloquio nella media
Candidatura
Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso DoorDash (New York, NY)
Colloquio
The first round was a phone screen with a recruiter. I then spoke to an engineering manager. We jumped straight into Xcode, where I was tested on my live iOS coding ability.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso DoorDash nel mese di ago 2024
Colloquio
Phone initial interview, Leet code, another Leet code, data structure, architecture, culture, management. I think Paypal is a good company to work for but the interview process for iOS developer positions does not make sense. All the interviews that I had were with backend developers that do not know anything about the Swift language and the hiring manager did not know in what part of the interview process I was. The first two LeetCode interviews were a waste of time since they do not prove how good of an iOS developer you are. They need to understand that we are not backend developers, yes it is important to know data structures to make your time complexity fast, but more important than that is ask the candidate to do things related to the job with iOS DEVELOPERS not Java or any other languages. I bet that backend developers would have the same feelings if they had interviews with iOS DEVELOPERS that do not know anything about their languages. Paypal you need to review your interview process ASAP.
Domande di colloquio [1]
Domanda 1
Unfortunately I did not have the chance to answer questions related to iOS because it was never asked to me, since the interviewers did not know Swift.
Ho presentato la mia candidatura di persona. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso DoorDash (Midtown New York) nel mese di apr 2024
Colloquio
Interview process was a nightmare. They gave me an Xcode project to open and to work with, with stubbed out methods. I had two interviewers, and when we started they weren't sure who was going to interview me. One person was shadowing the interviewer and they seemed confused as to who was going to be doing what. The interviewer was not helpful and had a really heavy accent, and I had a hard time understanding what he was saying (English is my native language). I had to ask what he was saying 2-3 times because I could not understand him. I finally got the requirements working in about 45 minutes but ran out of time, as they cut off my interview with five minutes to spare. It was also a live coding environment, so you couldn't look anything up including old projects or syntax and I don't think it was a proper test of what the working environment should be. Most of the time was spend trying to understand how the test project was set up and what the interviewer was saying.
