Taro Logo

iOS Engineer Interview Experience - San Francisco, California

July 1, 2016
Negative ExperienceGot Offer

Process

The process consisted of:

  • A 30-minute phone interview with a recruiter.
  • A coding challenge, which took approximately 5-6 hours over 2 days.
  • An on-site interview lasting 4 hours.

The phone interview and on-site were not technical, which was unusual given I was applying for a technical role. The individuals I met with tried to promote Slack as a great engineering company. I did not get the impression it would be a good place to work as an engineer or engineering manager. The engineering team is still small but already felt quite disconnected. The director and engineering manager I met with seemed overly focused on advertising Slack's culture and work environment, even though I did not get the impression they actually enjoyed working there themselves. My interviewers also seemed apathetic about conducting interviews.

The coding challenge was fairly standard. I spent several hours on it but never received any feedback. Although it likely led to my offer, I was frustrated that no one asked about my solution or how I approached it.

The entire interview process felt a bit dishonest and out of place, to be honest. I have another offer that I will be taking.

Questions

Coding challenge, a pretty standard build-an-app that is working end to end.

Was this helpful?

Interview Statistics

The following metrics were computed from 3 interview experiences for the Slack iOS Engineer role in San Francisco, California.

Success Rate

0%
Pass Rate

Slack's interview process for their 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 Slack's iOS Engineer interview process in San Francisco, California.

Slack Work Experiences