My interview was exactly how an interview ought to be like: Figure out if someone can code by coding with them and see if they enjoy working with your team.
Aside from the usual behavioral/whiteboard questions, I was given an option of doing a take home project or pairing programming on a small project. I opted for a hybrid of the two and made a simple project which we then iterated on during my interview. By pairing with different members of the engineering team I got to see how scrappy the team was and how quickly they could get stuff up and running. That was definitely a plus in helping me make my decision to join Iterable.
Throughout my interview I felt as though I got to ask just as many questions to them as they did of me. That gave me a great sense as to what the team was like and the direction of the company. I got to find out everything from financials, to the feature roadmap, to how company decisions were made.
Describe all your projects you have listed on your resume, including binary tree searches and architecture and design.
The following metrics were computed from 1 interview experience for the Iterable Mobile Software Engineer role in San Francisco, California.
Iterable's interview process for their Mobile Software Engineer roles in San Francisco, California is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Iterable's Mobile Software Engineer interview process in San Francisco, California.