Flexibility, autonomy, good practices, and continuous evolution.
Too much refactoring and poor objectives definition
First HR call, then a second round with a live code pairing session for an hour. I am heavy on front end and light on back end, and I have practiced LeetCode questions on Data Structures.
After contacting via mail, we had a phone interview discussing previous experience and job opportunities. The discussion revolved around general systems and engineering questions and ended with a detailed layout of Uber's teams in New York and the re
It was a mix of technical and behavioral questions. It took a few days to schedule, however, it was easy to reach out and plan when it would best fit our schedules.
First HR call, then a second round with a live code pairing session for an hour. I am heavy on front end and light on back end, and I have practiced LeetCode questions on Data Structures.
After contacting via mail, we had a phone interview discussing previous experience and job opportunities. The discussion revolved around general systems and engineering questions and ended with a detailed layout of Uber's teams in New York and the re
It was a mix of technical and behavioral questions. It took a few days to schedule, however, it was easy to reach out and plan when it would best fit our schedules.