SalesRabbit Interview Questions
& Process

So, the interview process was a little mixed up because the CEO wanted to chat with me before he left for a business trip. He was super nice and knew a lot, asking general questions about tech stuff like CoreData and GCD, and my experience with them. He also asked why I wanted to get into iOS and about my varied work history. He gave me the lowdown on the company, and I was pretty impressed. A few days later, the head of engineering called, told me about the rest of the interview process, and set up a time for me to come in. When I went in, I had a relaxed chat with the head of engineering again about lighter topics. After about 30 minutes, he brought in two of the iOS Engineers. They asked general questions, checked out my apps, and then we did a whiteboard challenge. It was pretty simple and low-stress, mostly syntax stuff, no tricky bits. After the engineers left, the head of engineering came back to wrap things up and explain what else was coming. Later that day, I got an email with an online coding challenge that had 4 logic questions. The next week, I went back for an in-person interview with the CEO. Again, no surprises, just a good conversation with standard HR questions. He then looked over my apps again and told me more about the company. He seemed really positive and said if my references checked out, they were keen to hire me. A few days later, I got the offer call and started the next week. They definitely had chances to make things difficult, but they were focused on a smooth process and finding a good team fit.

There were 5 interviews in total. It started with a pre-screening call from a recruiter. Then, there was an interview focused on industry experience with the hiring manager and another engineer. After that, I had a technical skills test called a "pairing," where I had to troubleshoot different scenarios interactively with two senior engineers. This was followed by a culture interview with two people, where they asked questions about how I've handled situations like overcoming adversity, my personal work ethic, and my personability. The final stage was a meet and greet with the C-Suite. Be prepared for potential scheduling changes. It's tough to find a 1-2 hour block for multiple engineers, especially on Mondays or Fridays because work can be very fluid and things come up. Everyone I spoke with was flexible, and any schedule disruptions were handled quickly once known. The tech pairing was a fair way to assess skills, and I found it interesting. The "test" seemed designed to gauge my depth of knowledge and how I'd handle things I didn't know. The main interviewer shared knowledge but it required me to stay sharp as we moved quickly between topics. I'd advise candidates to embrace the instruction given, as there was no frustration when I didn't know something. I could admit gaps, get instruction, and we'd move on. It was very efficient. Aside from the tech pairing, the other interviews seemed aimed at filtering out people who weren't being genuine. I received feedback throughout, which was great, and all my questions were answered honestly.

The interview process was pretty disorganized. They rescheduled interviews a bunch and I had to come on-site multiple times because they didn't have people scheduled correctly the first times. For one of the jobs, they wanted JavaScript knowledge for API stuff, but then in the coding part, they had a PHP page ready instead. It felt weird to be tested on the wrong language, especially since it wasn't even required or mentioned in the job post. The interviewers seemed unsure and unprepared, like they were just pulled in and didn't really know the role, so they asked questions that didn't really fit. For both roles, nobody got back to me by the deadlines. The people were nice enough, but they really need to get more organized and professional with their interviews to respect candidates' time.

Had a chat with HR to get a feel for the role and learn more. I asked about the salary range but was told there was no info on the budget for this position and was instead asked to share my salary expectations. That was the first red flag. Next, I was asked to do a take-home code assignment, which took around 3 hours. This was the second red flag. Overall, HR was nice to talk to, but the interview process looks like it is going to be very long (5 interviews total, which is longer than Google). Luckily, I landed a job at Google the next day so all good.