Taro Logo

iOS Developer Interview Experience - New York, New York

November 1, 2017
Neutral ExperienceNo Offer

Process

Typical tech interview. Introductory phone call followed by a coding test, followed by a final interview that includes technical questions and white-boarding. Everyone was nice, and the whole process was pretty standard.

My only gripes are when they told me they were going to proceed with other candidates; they felt the need to do this over the phone. This caused me to rearrange my schedule to take a somewhat awkward phone call when, in my opinion, an email would have sufficed. Perhaps they felt this was a courtesy and an opportunity to give feedback. But, I think a phone number included in the email, if a candidate wanted to discuss the decision further, would have been better.

Also, I was told by human resources that the team valued testing (unit test and test-driven-development, TDD), but that it was fine if I didn't have experience with it. I told them that in my first interactions with them, at my current place of employment, testing and TDD were not done, so I didn't have lots of day-to-day practice with it. But, needing more experience with TDD was the only feedback I was given when they decided to pass. This made me feel like I could have been eliminated from the process much earlier, and that experience with TDD, while presented as a nice-to-have, was actually a need-to-have. This would have saved myself and them a bit of time, as the coding test is quite involved, and the final interview is around 3-4 hours.

Questions

Basic Swift questions.

What is an optional? What is a generic? When would you use guard?

They also asked, I think mistakenly, when I would use const. But const is not a keyword in Swift. I told them I never used const in Swift, but that I have used a nested struct with static lets`. I'm not sure if they considered that correct. I think this question might be left over from Obj-C days.

There was an interesting pair programming part of the interview where you fetch JSON and write tests for the fetching and parsing that into objects while using the VIPER coding pattern.

The time given for it was kind of too short though, and I didn't feel like I could demonstrate any real coding prowess. Also, the scaffolding code seemed to not be behaving in the expected manner, so the interviewer took over to make some adjustments, which also ate into the time allotted.

Write a function that returns whether an array of Ints has two elements that sum to a given number.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Stash iOS Developer role in New York, New York.

Success Rate

0%
Pass Rate

Stash's interview process for their iOS Developer roles in New York, New York is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral100%
Negative0%

Candidates reported having mixed feelings for Stash's iOS Developer interview process in New York, New York.

Stash Work Experiences