J'ai postulé en ligne. J'ai passé un entretien chez Tinder (Los Angeles, CA) en juin 2017
Entretien
The interview process was kind of weird, especially at the end. First I talked to recruiter over the phone to describe my current position after that they scheduled a phone interview that I passed then I had my onsite interview and after that another phone interview with a Director.
After passing all of the interviews the recruiter sent me an email saying the job opening was not longer available and I was not ready for a senior position.
Questions d'entretien [4]
Question 1
Implement the following method signature` boolean isPalindrome(int n)`
We're sorry to hear you didn't have a positive interview experience. Thanks for sharing your feedback as it helps us identify opportunities for improvement in our recruiting process. Thanks for your review and we wish you the best on your job search!
Autres retours d’entretien d’embauche pour un poste comme Android Engineer chez Tinder
J'ai postulé en ligne. Le processus a pris plus d'une semaine. J'ai passé un entretien chez Tinder en oct. 2016
Entretien
Applied online. After a phone call with recruiter, a phone interview was scheduled. Was asked about my previous experience and some questions on Android fundamentals. Was asked about animations, how one would perform time consuming operations and how would you talk to the main thread from a handler not on a main thread.
J'ai postulé via la recommandation d'un employé. Le processus a pris 2 semaines. J'ai passé un entretien chez Tinder (Los Angeles, CA) en juin 2016
Entretien
From employee referral, contacted via email then quick 10 minute recruiter phone screening (no technical questions). Flown out for an on-site interview, accommodations arranged by the company.
On-site had two stages:
1) A couple hours to make a simple Android app, given a few very loose specs/ideas to choose from. Then present the app and code to panel of Android engineers and answer questions about design decisions and Android in general.
2) Two one-on-one whiteboard coding interviews. Standard whiteboard questions similar in difficulty/depth to what one might see at an on-site Google interview.
It was a fun interview. I had a great time even though I didn't get an offer.
Questions d'entretien [1]
Question 1
[Follow-up to whiteboard question] If you had to process more nodes than could be stored in memory, how would you change your code?
