You can work on products people love to use. You can notice how the company tries to change itself from an installed software company to SaaS. You will be able to work closely with product managers and together shape the product. Despite its size, the company is still rather open. By observing internal communication tools, you can get the feel of what's going on and participate in different activities.
Depending on the team you join, you might face a crappy and abandoned technology that no one else uses. If you wish to keep up with cool technologies, it might not be a good place for you. You will face a wall when it comes to making those products technically better – sacred APIs that cannot be changed, a scary plugin system, or a hacked Maven for builds. I would advise choosing teams that work on recently created products. Avoid more mature ones.
The company is growing a lot and plans to do so in the upcoming years. So, despite their great values, the atmosphere starts to feel like in any other "corporation" – a multi-level managerial structure, bad people management.
The interview process includes many rounds, such as an online coding test, general technical questions, a real, time-boxed coding assignment with TDD, and management and culture fit interviews. It can be tiresome to wait for the next interview round
The overall interview process was good, and I kind of liked my interaction with all the interviewers I met. They were intelligent people and knew what to expect from a potential candidate, and were friendly all the way. However, the discussion aroun
1st round Recruiter Screen: I got feedback in the end. 2nd round Karat's coding session: There was enough time to solve a mid-level coding question. 3rd and 4th round: The solutions were to use data structures questions like treemap and dequeue. Th
The interview process includes many rounds, such as an online coding test, general technical questions, a real, time-boxed coding assignment with TDD, and management and culture fit interviews. It can be tiresome to wait for the next interview round
The overall interview process was good, and I kind of liked my interaction with all the interviewers I met. They were intelligent people and knew what to expect from a potential candidate, and were friendly all the way. However, the discussion aroun
1st round Recruiter Screen: I got feedback in the end. 2nd round Karat's coding session: There was enough time to solve a mid-level coding question. 3rd and 4th round: The solutions were to use data structures questions like treemap and dequeue. Th