Me postulé a través de una agencia de empleos. El proceso tomó 1 semana. Acudí a una entrevista en Linden Lab (Brighton, Inglaterra)
Entrevista
Google style; multiple segments (5) of chat and questions on different technical areas, by different team members, both at manager level and with other developers I'd be working with. Included a whiteboard pseudocode problem-solving challenge and questions finding out whether I knew and understood basic ideas in technologies and design patterns/techniques for the skills involved in the role applied for. A chance to ask questions of the staff during each part too. Then at the end a non-computer related problem to solve a well-known physical puzzle/toy in a set state (only a few repeated pattern of moves away from solved), if I could.
Preguntas de entrevista [1]
Pregunta 1
What HTTP response codes are and to list some/what they're used for
El proceso tomó 2 meses. Acudí a una entrevista en Linden Lab
Entrevista
I was connected by the recruiter via email. One phone screening round with the Hiring Manager. After that 5 rounds virtual onsite interview with different team members. No technical questions asked in virtual onsite. Felt like a dummy position interview. They interview a million of other applicants and then reply back. Very fishy hiring process.
Preguntas de entrevista [1]
Pregunta 1
Tell me about yourself. No coding question or coding / technical exercise.
Me postulé a través de una recomendación de un empleado. El proceso tomó 2 semanas. Acudí a una entrevista en Linden Lab (San Francisco, CA) en jun 2015
Entrevista
1. Phone Screen
2. All-day on-site interview
Interview was okay. If the interview did not go well (even if it seemed like it did), they don't call back to tell you that you didn't get the job.
They are extremely focused on how to build REST applications so be prepared to answer architectural questions on how you would build certain types of systems.
Preguntas de entrevista [1]
Pregunta 1
What is Ruby on Rails good for? What would you build with it?
