I had a first call from the recruitment team where the interviewer told me about the company and the working conditions. I had the chance of explaining my expectations briefly, and we agreed to start the selection process. The first stage was a technical exercise where I had to code a Java simple solution. It was not allowed to use any external library or framework, except for testing. The code’s expectations were not closed, so I had some freedom to choose the solution’s best design. I had no pressure to finish the problem in a short amount of time, but the initial estimation is one week. A senior developer could complete a good solution in 10-12 hours in a row with good testing coverage and documentation. I didn’t pass this stage because the reviewer didn’t like how I solved it. It was a bit sad to receive only one paragraph of feedback, but it was consistent about the design’s mistakes. One of the detected issues was a misunderstanding about the compilation environment, so I would suggest asking the compilation JDK to participate in this selection process. I didn´t have any chance to discuss or defend my work anyway. Consider clarifying any doubt about the exercise. You should have well-defined what kind of metrics will examine the reviewer in the correction of your code. Finally, I would suggest participating in this process because this company’s people are very kind and supportive and this little effort could have a good reward.

El proceso consistió en: Entrevista telefónica para presentar la empresa y comentar la experiencia del candidato. Prueba de código, implementar un pequeño motor de búsqueda en Java. Entrevista técnica con 2 miembros del equipo en el que se revisa la prueba y se formulan preguntas. Entrevista con un Manager para comentar el plan de carrera dentro de la empresa.