It is a place with very interesting technical challenges. If you are looking for great technical problems and bright people to work with, then this is the right place.
Also, it has a get-things-done culture: things develop very rapidly and it is a short distance from idea to execution.
The biggest disadvantage of working here is the on-call burden. You are required to carry a pager on a rotation basis, and it binds you down whenever you have it. Some teams have a very heavy on-call load, which interferes with regular development.
Using support teams to reduce the support and operational burden on software engineers would let them focus on what they do best, rather than try to fix operational problems and deliver new products simultaneously.
It was good, but they didn't respond to me for a long time after 14 days. I asked them why, but they didn't respond back.
Initial phone call with a recruiter, followed by a 90-minute coding assignment. This consisted of standard LeetCode-style algorithm and data structures problems, loosely related to the specific role and easy to prepare for by using normal resources.
Only one round for the intern position. The first part of the interview was technical questions. I got one "out of the box" question and one LeetCode question created by the interviewer, not on the list. The second part of the interview was behaviora
It was good, but they didn't respond to me for a long time after 14 days. I asked them why, but they didn't respond back.
Initial phone call with a recruiter, followed by a 90-minute coding assignment. This consisted of standard LeetCode-style algorithm and data structures problems, loosely related to the specific role and easy to prepare for by using normal resources.
Only one round for the intern position. The first part of the interview was technical questions. I got one "out of the box" question and one LeetCode question created by the interviewer, not on the list. The second part of the interview was behaviora