Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Cupenya (Amsterdam)
Colloquio
The interview process consisted of two parts, after a first informal discussion to get to know the company and the product, and followed by a team-meeting to get to feel the office flavor and a final meeting to discuss the contract proposal. I got to say that even if the whole process is not finely tuned or planned it was a good experience and gives them quite some confidence in assessing the candidate's skills and fit.
Domande di colloquio [3]
Domanda 1
In the first interview, a sketch of the architecture of the product is presented to me, and the question is what would I do to tackle a bottleneck between two of the components. In this scenario basically, which is something they had to deal with themselves for real, a consumer cannot keep pace with a producer.
In the second interview I am asked to cook up an algorithm to compute position (m, n) in a Pascal triangle; free implementation, pseudocode is still good. Together with the company CTO, who was the interviewer in the first interview, a backend and frontend developer also joined.
Define the domain model for a system dedicated to CRUD operations on graphs, together with at least the implementation for the all-paths algorithm. The objects the system work with are all fully connected graphs. This was an home assignment with a couple of days of time. As I am a medior developer already mastering the main target language, Scala, the focus was on the abstractions and big pictures rather than the actual code. Less experienced candidates were given the same assignment but with more time, so that they could produce a fully-working prototype and explore points like persistency.
