Taro Logo

Senior iOS Engineer Interview Experience - San Francisco, California

April 1, 2023
Negative ExperienceNo Offer

Process

The interview process was pretty easy overall. 2 technical coding questions prior to the an on-site. Some interviewers however were very unprofessional and not well trained at all - moreover the calibration seems to be prioritizing irrelevant Xcode knowledge. The one technical coding interviewer did not start with any introductions or greeting at the beginning of the call. He also did not have the courtesy to write out any of the problem statement in the coderpad.

It was difficult to understand him to begin with, but only vocally saying the problem (which wasn't a trivial problem either) wasted a lot of time because I had to ask basic clarifying questions and rephrase what I believed to be the problem statement multiple times before I fully understood what he was asking me to do. At that point it was me who had written down what the problem was asking after all my questions in order to understand it. To make it worse, the "part 2" follow up of the question followed the same pattern where I was the one who had to write down the question after trying to clarify and understand what he was saying. The technical coding challenge should not be a riddle for me to figure out what the problem is asking at the most basic level.

The on-site compromised of a standard behavioral slot, a 2 hour Xcode project, and an iOS knowledge/architectural design panel. The last panel has very poorly calibrated "bugs" and "issues" you have to fix in an existing Xcode project. Rather than testing applicable knowledge such as identifying a memory leak (retain cycle) in the app, they test you on obscure Xcode IDE specifics that you'd never encounter in a real work setting (I can't give away the specifics of the question here). And even though I was able to identify the "what" was going wrong and what I "needed to do to fix it" immediately, it took me a bit longer to find the "how" to fix it within Xcode itself.

I did end up fixing the issue but because it took me a bit longer, (in the post-interview feedback they gave me) I didn't receive an offer because it "raised some serious concerns" that I was not able to find "insert specific Xcode thing here" immediately. Again, no project is ever set up this way so it's not immediately obvious in "how" to fix it. Other than that I thought I did well on all the sections so I was surprised I didn't receive an offer. My suggestion to the hiring team would be to re-calibrate the iOS specific problems to be more relevant to checking actual expertise and domain knowledge, and train interviewers to be more professional.

Questions

2 technical coding challenges (LeetCode style). On-site of behavioral, 2 hour Xcode project, and a bug fixing/architectural section.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Nextdoor Senior iOS Engineer role in San Francisco, California.

Success Rate

0%
Pass Rate

Nextdoor's interview process for their Senior iOS Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Nextdoor's Senior iOS Engineer interview process in San Francisco, California.

Nextdoor Work Experiences