Envié una solicitud electrónica. Acudí a una entrevista en Logz.io (Kyiv, ) en feb 2021
Entrevista
The first step is an interview with a recruiter, which is a standard one.
The second step is a 30 min questionnaire, which has 3 real life cases where you need to provide a solution.
The third step was expected to be a 1h technical interview, but was rather a product(which looks to be great) and company promotion and answering my questions, with just a few tech questions at the end.
The fourth step is a 2h coding session(create a pipeline) with 1h of follow up questions. It was taken on Sunday.
The task by itself has mistakes in a description. It says you may use any open source libraries, but at the end you cannot use Spring.
It also doesn't mention, that you are expected to create a library, not an app. I created an app and came to a trap with it.
The interviewer was neither motivated nor interested, looking too much of a time at his phone.
The interview by itself I would like to call a "guessing session".
You need to guess what is in the mind of the interviewer, any proposed solutions are declined until you come to the only one "correct" solution.
Preguntas de entrevista [1]
Pregunta 1
For pipeline: configuration, caching, time limit throttling
Call from a recruiter, interview with team lead to check your knowledge and background and personality,
talking about what they do in their work what problem they are facing etc ...
Preguntas de entrevista [1]
Pregunta 1
FileSink: Question
Write a component (i.e. a Class) which writes log messages (i.e. Strings) to the file system.
The component should be designed to be non-blocking.
The component should write to a single active file.
It should be thread safe, such that multiple threads can write to it concurrently.
It's configuration parameters should be:
directoryPath - The directory in which the log files will be saved
Your class should implement the following interface:
public interface FileSink {
void write(String logMessage);
}
Test your answer by writing tests (through JUnit or a main method) which validates the following scenarios:
Writing one line
Writing multiple lines
Writing multiple lines from multiple threads
Make sure your test verifies that all the messages written to the FileSink are actually there
Each thread should write 10,000 unique messages
Each test should validate that the scenario actually worked (not manually by inspecting the output)
Important Note: Make sure to have a working software by the end of the time limit.
Time limit: 2 hours
Good luck!
Solicité el puesto a través de un captador. El proceso duró 3 semanas. Acudí a una entrevista en Logz.io (Kyiv, ) en may 2020
Entrevista
Company had well-defined steps of interview, and in general process went smoothly. Unfortunately, the recruiter who introduced me to the company was not very agile. When company decided not to continue the process, interviewer simply did not provide any feedback at all - so I had to contact the company directly. There was no clear feedback from the company either, just the standard "not a match for us".