2015, February, I was first phone interviewed by a xiaoge and then followed by onsite. The office is nice. Free food, free drink. NIce work place.
2015, February, I was first phone interviewed by a xiaoge and then followed by onsite. The office is nice. Free food, free drink. NIce work place.
Interview questions [1]
Question 1
get unique IPs from a big file. Their expected answer is use linux command and pipe. AWK, etc
The process took 3 weeks. I interviewed at Tinder (Los Angeles, CA)
Interview
90 minutes of your time via a CodeSignal, 20 min HR screen, 1 hr technical interview, and then the onsite which i believe was supposed to be 3 technical + 1 behavioral. for most experienced engineers, I don't believe the questions they ask are too difficult: i'd place them around leetcode mediums and easys. The codesignal went well and so I made it to the 1st technical interview. The question in and of itself wasn't very difficult, however, the engineer I spoke to wasn't very receptive to alternative approaches. I suggested an alternative on how to optimize the code we worked on and... he didn't like it very much as he had a preconceived approach in mind. As far as complexity is concerned, it would have been just as efficient. Something tells me that as a potential team member, he's very clearly the type to push his own agenda. When he was trying to explain the pre-conceived approach he had in mind, I hadn't understood it very well. There were moments during our zoom interview where I could see him laughing on screen, which... just completely made my nerves way worse than necessary. Compared to other interviews that I have had in the past, their difficulty is very reasonable. However, I think there needs to be better training on the interviewer's side as having a candidate very visibly see their interviewer laugh on screen is.... not helpful in the slightest. There have been other interviews here mentioned where past interviewers have also been just as arrogant, so this is not the first incidence of the "culture"
Interview questions [1]
Question 1
General OOP, optimizing the methods written and understanding the complexity. However, interviewer was not receptive to alternative approaches and spouted his own agenda.
Started with a phone screen with an incredibly amicable recruiter: very warm and inviting, even over the phone. Then, I had a phone interview with an engineer where I spoke about my background and then did a OOP problem over Codepad. Finally, was invited onsite, where I spoke with multiple people. Two of the interviews were design, and two were coding problems. The design interviews were relatively challenging for me: they ask about your previous projects/work and delve into one of them and think about how they're created.