I applied through a staffing agency. The process took two weeks.

It seems after looking through the other interview reviews here that TripActions is trying hard to raise their Glassdoor ratings, because my experience was completely different from the rest. The steps were a phone screen with the hiring manager, taking fifteen minutes, followed by an on-site interview lasting three to four hours.

The phone screen with the hiring manager was simple and pretty typical. We spent some time talking about my background and my interest in the company, and I then asked questions about their culture, the engineering side of things, day-to-day life, and more. The on-site interview was a different, more disorganized experience than on-site interviews I've had with other companies in the past, and I'm glad I didn't get the offer from them in the end.

• Phone Screen: A fifteen-minute call with the hiring manager.
• On-site Interview: A three to four-hour session consisting of coding exercises and discussions.

It first started off with signing in in the lobby. I signed in on their iPad and, after waiting a few minutes, met with the hiring manager who just said hi and went immediately to his desk to do something for a few minutes. There was no handshake or anything, and I was then escorted to the interview room where I spent the next ten minutes or so waiting for him to come in. I then spent the next two hours coding up an Android app exercise that involved some networking and an autocomplete feature, which I'll include below.

I've done a similar app the night before that was exactly the same apart from the autocomplete feature, but I ran into a REQUEST_DENIED bug and realized that their provided API key wasn't working properly. I was then blamed for writing buggy code even though an app I worked on the night before this interview had the exact same code and worked perfectly. Next, we had a discussion on two Android problems, which I'll also include below this review. They were simple as I've implemented them in my personal and professional apps before, but what stood out to me was the fact that the hiring manager kept saying "I don't care" whenever I asked him if my answer made sense.

After this came two short thirty-minute interviews. The first was with an iOS engineer who clearly looked like he was in a rush and, while chatting about the company and engineering-related things, kept checking his phone for the time. The second interview was with a designer and was the highlight of my time at TripActions. We talked about material design and the reasons why it's great and popular on Android apps.

For two hours, you create an Android app with an EditText widget that, while the user types in some city name, displays a list of autocomplete suggestions in a list below the widget. You'll be using the Google Maps API for the autocomplete feature results.

For fifteen minutes, say your Android app contains a login feature. When your app first opens, if the user is already signed in, the user should see the home page of the app. If not signed in, the sign-up page will be displayed. After completing this step, the sign-up page should close and bring the user to the homepage. There was one answer.

For fifteen minutes, you implement an infinitely scrollable list. There was one answer.