Decent comp. A good place to learn. An ambitious company with a clear vision, sound financials, and lots of really smart people, most of whom are surprisingly humble.
The company's high ambitions often result in a high workload and tight deadlines. Sometimes product requirements are unclear, but engineers still need to make it happen. This can be very frustrating. It is often unclear where the work or the requirements originated; thus, understanding the "why" can be a challenge.
When tasking a department with an undertaking, understand how much effort or resource will be required from other departments and help re-prioritize.
The interview process was very unique. It wasn't like asking just one random LeetCode question, resulting in a binary fail/pass situation based on that single question, which happens at many other companies. Here, it started with an online assessmen
Here's the process: * Recruiter screen * Take-home task * 1-hour interview with engineers * 1-hour interview with engineering managers * 30-minute interview with in-house recruiter on culture fit I had plenty of time to ask the questions I needed.
The first round was a screening by a recruiter, who was helpful and nice. After that, I was sent a HackerRank challenge. It was mostly related to microservices architecture and problem-solving. The next step was a technical interview, where we disc
The interview process was very unique. It wasn't like asking just one random LeetCode question, resulting in a binary fail/pass situation based on that single question, which happens at many other companies. Here, it started with an online assessmen
Here's the process: * Recruiter screen * Take-home task * 1-hour interview with engineers * 1-hour interview with engineering managers * 30-minute interview with in-house recruiter on culture fit I had plenty of time to ask the questions I needed.
The first round was a screening by a recruiter, who was helpful and nice. After that, I was sent a HackerRank challenge. It was mostly related to microservices architecture and problem-solving. The next step was a technical interview, where we disc