Laid-back environment. Lots of autonomy. Working with really talented people. Diverse staff.
Outdated tech stack. Extremely conservative in terms of technological innovation and risk-taking. Lousy feedback process. Not remote-friendly. Once-a-week deploys, zero documentation; doesn't follow any industry methodologies such as Scrum or Kanban.
It was lengthy and a bit disorganized, and it didn't follow the outline they give on their website, but I think that's for the best as it seemed much shorter. It began with a recruiter, then led to a live online assessment with other interviewers. I
The OA is kinda funny for a Java company. They asked two hardish HackerRank questions in a two-hour interview format. The first was simply implementing an in-memory cache (why would you do this in Java?). However, the question was so vague and did no
It starts with a HackerRank coding test as the first round, followed by an in-person interview where you have to describe your approach to solving problems and system design. The third round is system design.
It was lengthy and a bit disorganized, and it didn't follow the outline they give on their website, but I think that's for the best as it seemed much shorter. It began with a recruiter, then led to a live online assessment with other interviewers. I
The OA is kinda funny for a Java company. They asked two hardish HackerRank questions in a two-hour interview format. The first was simply implementing an in-memory cache (why would you do this in Java?). However, the question was so vague and did no
It starts with a HackerRank coding test as the first round, followed by an in-person interview where you have to describe your approach to solving problems and system design. The third round is system design.