Lots of interesting and challenging projects, great people, personal growth.
Salary, lots of built-in house technologies instead of using open source.
Typical interviews include exercises from HackerRank (mostly Cracking the Coding Interview) and usual questions. You can prepare by solving different problems from HackerRank or LeetCode. It's preferable to focus on arrays and strings.
Asked two questions to two pointers, solved both problems within 40 minutes. Asked some questions about the Python language. Then we just talked. Then the next interview had two problems: geometry and DFS finding a path in a graph.
I applied through a recruiter and was invited to a phone interview. It included both personal and technical questions, which were not that hard. It was not easy to communicate with the recruiter because she was standing in a very loud room, and it
Typical interviews include exercises from HackerRank (mostly Cracking the Coding Interview) and usual questions. You can prepare by solving different problems from HackerRank or LeetCode. It's preferable to focus on arrays and strings.
Asked two questions to two pointers, solved both problems within 40 minutes. Asked some questions about the Python language. Then we just talked. Then the next interview had two problems: geometry and DFS finding a path in a graph.
I applied through a recruiter and was invited to a phone interview. It included both personal and technical questions, which were not that hard. It was not easy to communicate with the recruiter because she was standing in a very loud room, and it