Me postulé a través de un reclutador. El proceso tomó 2 semanas. Acudí a una entrevista en Amadeus (Waltham, MA) en jun 2016
Entrevista
Applying for a position which, in nutshell, should have been supporting legacy C++ code for legacy salary.
Stage 0: a chat with HR/recruiting specialist.
Stage 1: automated quiz on codingame.com consisting of 40+ questions ranging from "how do you get a pointer to variable: &v, *v, or getptr(v)" to "identify this design pattern" to "program a simple task in 20 minutes".
Advice: spend a weekend practicing on codingame.com to solve at least "Easy" section and read through at least Wikipedia section on design patterns: they seem to have some affection to this stuff.
Stage 2: chat over Skype with a tech dude. Mainly, about your past experience, no actual tech quiz.
Stage 3: onsite interview, as usual.
Preguntas de entrevista [1]
Pregunta 1
Write a program that prints the temperature closest to 0 among input data. If two numbers are equally close to zero, positive integer has to be considered closest to zero (for instance, if the temperatures are -5 and 5, then display 5). Time limit: ~20 minutes.
// This is exactly a task from CodinGame's "Easy" section
Acudí a una entrevista en Amadeus (Bogotá, Cundinamarca)
Entrevista
Se hacen 3 entrevistas, una con hr, luego va la entrevista de code challenge y finalmente una para conocerte mas. El code challenge con ejercicios de leet code y es presencial
Preguntas de entrevista [1]
Pregunta 1
Que arquitecturas que he implementado y por que las he usado
Acudí a una entrevista en Amadeus (Londres, Inglaterra)
Entrevista
The interview process consisted of one behaviour and then one technical. Leetcode style questions. Object oriented programming questions. The more questions you answer the harder the follow up questions get.
Iterview with HR:
They check if you are a good fit for company values
Direct management:
Again check if fits with team culture and technical and academic background and experience
Technical interview:
some that i've seen includes system design, theoretical knowledge on software dev like concepts of o.o.p.
for programing usually check if a given code works why it works and why its failing also check for errors in syntax and semantics