Interview Process Breakdown:
Overall, everyone was very friendly. The office is great, and the lunch was quite decent. A lot of weight is placed on cultural fit, so be friendly and open.
After preparing for more difficult interview questions, I was completely thrown off track when asked to implement a couple of very basic iOS tasks, such as table/collection views and autolayout. There was also no boilerplate code to even get the app on screen. For an experienced engineer, who may be used to adding features to an existing application or using Xcode boilerplate code (read: most people), this was annoying and not a good measure of anything, in my opinion.
I was disappointed because I don't think the two questions I flubbed were a good representation of day-to-day skills. I was doubly disappointed because I was told there would be a paired-coding session involving debugging, etc., which sounded a lot more worthwhile.
At the end of the day, I had prepared for a senior position but was thrown by junior/entry-level questions.
Here's the text to clean up:
Given an app with three screens and many components, discuss how you would implement it. This is a general screen to assess knowledge of the SDK.
Two algorithm questions (already discussed on Glassdoor):
Implement a simple table or collection view with alternating cell layouts, avoiding boilerplate code.
The following metrics were computed from 1 interview experience for the Pinterest iOS Engineer role in San Francisco, California.
Pinterest's interview process for their iOS Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Pinterest's iOS Engineer interview process in San Francisco, California.