J'ai postulé en ligne. Le processus a pris 3 jours. J'ai passé un entretien chez Tenor en oct. 2017
Entretien
Chat with HR and recruiters was normal and went fine. I was sent a 2.5 hour programming challenge which I completed and covered all test cases along with some I came up with.
3 days later I was rejected with no feedback and was completely ghosted. Not a very positive interview experience and waste of my time.
Questions d'entretien [1]
Question 1
Create the classic "Connect Four" game and print out the board when game is over
J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Tenor
Entretien
Started off well enough. Recruiters and engineers were pretty friendly. Until they eliminate you as a candidate and completely ghost you.
Got through the mini coding challenge and phone screens ok. During the onsite, I admit I fell short solving a couple of their problems. But I was eager and as respectful as possible. They decided to cut the onsite short by a couple hours and escorted me out abruptly.
A basic courtesy rejection email at the minimum would have been just fine with me but didn’t happen. Especially after the hours that I spent on the coding challenge, the hours of research I did on their products, my commute, and parking fees to get to their onsite. The rejection itself was not disappointing but rather the lack of courtesy to follow up in any way for a candidate that made it pretty far and invested significant time into the interview process. Kind of reflects poorly on the organization.
J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez Tenor (San Francisco, CA) en juil. 2017
Entretien
Initial Phone Screen, followed by Coding Challenge, followed by a phone call with some interview by the CTO, and then onsite interview. The whole process took about 2-3 weeks. You will get a call from one of the founders with the verbal offer followed by the paperwork if you accept.
Questions d'entretien [1]
Question 1
You will be emailed a coding challenge and have to hours to complete. You can send them an update within 24 hours. I had a pretty good solution with my first version and did a slight cleanup & improvement within the 2 hours. Focus on good code structure and more generalized solutions. Think about things beyond the exact example.
For the onsite interview, I spoke with 6-7 people. I actually had to come back for a second onsite interview because a couple of people had a last minute problem and could not conduct their interviews that day. While it cumbersome to drive back again, they were smart people worth talking to.
About half the people you speak with will give you technical questions. Some will be architecture questions on a whiteboard. This involved some pseudo code as part of a larger problem about scaling. There was one actual coding interview via code collaboration as the engineer was remote.
I met all 3 of the founders. These were more to learn about the company with some behavioral interview. I was very impressed with the vision and how the company positioned itself so well along the way to take advantage of opportunities.