Not sure if there are any.
It just takes a long time to get anything done. Too many processes.
I feel like some people on the team do not have strong knowledge in Java. Some of the Java questions they were asking were very basic J2SE questions, and they were arguing with the wrong answer. For example: if developers do not write a 'try catch' t
Phone screen for an hour with some code sharing. Technical in nature. In-person sessions with 5 or 6 engineers, one after another, for about 45 minutes to one hour each. Focus on algorithms and whiteboard coding. Some questions are tricky and can t
The interview experience was positive. I would rate it medium difficulty, with standard algorithm questions. As I was interviewing for a full-stack role, there were also some JavaScript UI questions. The process included one phone screen and six on-s
I feel like some people on the team do not have strong knowledge in Java. Some of the Java questions they were asking were very basic J2SE questions, and they were arguing with the wrong answer. For example: if developers do not write a 'try catch' t
Phone screen for an hour with some code sharing. Technical in nature. In-person sessions with 5 or 6 engineers, one after another, for about 45 minutes to one hour each. Focus on algorithms and whiteboard coding. Some questions are tricky and can t
The interview experience was positive. I would rate it medium difficulty, with standard algorithm questions. As I was interviewing for a full-stack role, there were also some JavaScript UI questions. The process included one phone screen and six on-s