Envié una solicitud electrónica. El proceso duró 1 día. Acudí a una entrevista en SlideShare (San Francisco, CA) en feb 2011
Entrevista
Overall it was pretty good. It was essentially a Skype chat where your are asked you to code two programs (one easy, one difficult) and he watches you via screen-sharing. You also go over your resume. I interviewed with the CTO, Jonathan, and he was extremely nice. I was able to get the first question correct, and my algorithm was the second one was correct, I just had a couple tiny bugs which I couldn't find during the interview, but he said I could email him the code as soon as I finished it.
Preguntas de entrevista [2]
Pregunta 1
Program the game FizzBuzz for numbers 1-100 in any programming language.
Write a program that takes in a tic-tac-toe board (3x3) as input (it can be in whatever representation or format you choose). You must determine which of the following four states the board is in: player X won, player O won, stalemate, continue playing.
I received an online link to do the online programming test at the very beginning. It lasts 40 mins and it is not too hard, very basic question. Then I received a call from HR and Skype interview from one technical person, another programming problem, I fail at this. I use too much time to solve the problem.
Preguntas de entrevista [1]
Pregunta 1
Why do you choose our company? How do you think you skills can contribute to our company
Envié una solicitud electrónica. El proceso duró 1 día. Acudí a una entrevista en SlideShare (San Francisco, CA) en abr 2012
Entrevista
A very hands on interview. Gave me a problem to code in (Ruby on Rails), and let me work on it for about 30 minutes before checking on me again. It involved ActiveRecord stuff.
Interviewer was friendly and also set out to teach me a thing or two along the way even as I stumbled my way through the interview. A good experience overall regardless of the outcome.
Preguntas de entrevista [1]
Pregunta 1
I didn't have much experience with caching and database querying tricks at the time (e.g. how to avoid N+1 query problem), so I stumbled there.
