Most of the developers are great.
Good architecture.
Contributing to system design.
Great compensation.
Too many dependencies on other teams. Too much pressure.
Please trust your developers more to make decisions about parts of the system they own.
Very negative experience. The problem was quite easy to solve (building the Load Balancer and ServiceInstance). I managed to do that quite easily and in very little time, and had a test coverage of 92% on the LoadBalancer. Yet, I was still rejected
One interview with the recruiter evaluating your career path. After that, a request for a 1-hour coding challenge with two evaluators observing your performance. If this step is passed, I believe some more interviews could follow.
The interview process begins with a recruiter call. Next, a Java live-coding challenge requires you to design a load balancer. This is followed by technical and architectural interviews. Finally, a team fit session assesses collaboration and cultu
Very negative experience. The problem was quite easy to solve (building the Load Balancer and ServiceInstance). I managed to do that quite easily and in very little time, and had a test coverage of 92% on the LoadBalancer. Yet, I was still rejected
One interview with the recruiter evaluating your career path. After that, a request for a 1-hour coding challenge with two evaluators observing your performance. If this step is passed, I believe some more interviews could follow.
The interview process begins with a recruiter call. Next, a Java live-coding challenge requires you to design a load balancer. This is followed by technical and architectural interviews. Finally, a team fit session assesses collaboration and cultu