Analyze the company's source code as a good starting point.
During the last few months, new people have come with no clear strategy.
3 interviews: 1. Presentation of the company, not many questions. 2. Technical questions about your current day-to-day work. 3. Live code challenge. The only problem for me was the last step. I did a live code challenge, where it is very difficult
Over two months, I've been interviewing with Elastic. I am very pleased with my conversation with the founder, as he has been the only one to share some real feedback about what they are looking for in a hire. Or at least he talked me through his tho
Process was quite quick and impersonal. One day after applying to the position, I got a standard email with the subject "Time to chat with Elastic!". The email was an invitation for a 20-minute discussion about the role and my background with a recr
3 interviews: 1. Presentation of the company, not many questions. 2. Technical questions about your current day-to-day work. 3. Live code challenge. The only problem for me was the last step. I did a live code challenge, where it is very difficult
Over two months, I've been interviewing with Elastic. I am very pleased with my conversation with the founder, as he has been the only one to share some real feedback about what they are looking for in a hire. Or at least he talked me through his tho
Process was quite quick and impersonal. One day after applying to the position, I got a standard email with the subject "Time to chat with Elastic!". The email was an invitation for a 20-minute discussion about the role and my background with a recr