There's not much room for juniors to come in as the company is distributed. I don't believe that someone extremely junior could get what they need.
The average age in the company is older as a result of not hiring juniors. This is not really a con, just unfortunate that people can't experience Elastic until they are further on in their career.
Onboarding can be disorienting. Distributed companies can highlight mental health risks due to social isolation. It requires self-management.
There is sometimes some ambiguity in direction, which is challenging to some people. You have to be comfortable standing up for yourself and tackling problems, as you do get a lot of autonomy and freedom. However, that means that the quality of the individuals working in a team is forefront in its success.
There's explosive growth, which causes the need to shuffle and redesign the company and working styles. You need to be comfortable and open to handle the change.
Keep focusing on the source code. Over-communicate it again and again and again, because it's working. The source code and the culture are so important, and it was transmitted to me within a few months. If we can keep the source code moving through the new hires, I don't know what the limits of the company are.
People seemed to be nice, and I really enjoyed participating in every stage of the interview. Unfortunately, it took too long, with many interviews having to be rescheduled due to unavailability and the recruiter taking too long to give feedback. Pe
I was first contacted by HR for an hour-long interview to discuss the position and my experience. I then had a live coding interview with two mid-senior engineers. The problem itself was not very difficult, but there was very limited time for a prop
I applied through a recruiter. The process took four weeks. It was a nice experience overall with a few rounds of technical and behavioral interviews. It seems they value the behavioral part more since their positions are remote-first. There were ea
People seemed to be nice, and I really enjoyed participating in every stage of the interview. Unfortunately, it took too long, with many interviews having to be rescheduled due to unavailability and the recruiter taking too long to give feedback. Pe
I was first contacted by HR for an hour-long interview to discuss the position and my experience. I then had a live coding interview with two mid-senior engineers. The problem itself was not very difficult, but there was very limited time for a prop
I applied through a recruiter. The process took four weeks. It was a nice experience overall with a few rounds of technical and behavioral interviews. It seems they value the behavioral part more since their positions are remote-first. There were ea