There are too many:
Nobody likes to document and write comments in code. There are no requirements to do this, no general code style, and no requirements to write tests, etc. So this totally depends on the project and its team lead. The incoming barrier for a new-comer is pretty high as the code is not documented at all.
Another issue is too many unsuitable functional approaches for coding in Java that often result in bad-readable code.
It was the first stage algorithm interview, after which I had two more algorithm sections and one architectural section. On the architectural stage, I was asked to design the backend for a traffic-jam app like Traffic Alert. After the entire proces
The overall experience was disheartening, especially considering the time and effort invested. The recruitment team was very unprofessional and lacked experience working with senior-level candidates. The interview phases, which comprised one archit
4 tech interviews. Simple algorithms tasks. Two tasks: Coding (also algorithms). Two tasks: Algorithms tasks. Two or more tasks: System design interview. Team meetings, may be multiple teams.
It was the first stage algorithm interview, after which I had two more algorithm sections and one architectural section. On the architectural stage, I was asked to design the backend for a traffic-jam app like Traffic Alert. After the entire proces
The overall experience was disheartening, especially considering the time and effort invested. The recruitment team was very unprofessional and lacked experience working with senior-level candidates. The interview phases, which comprised one archit
4 tech interviews. Simple algorithms tasks. Two tasks: Coding (also algorithms). Two tasks: Algorithms tasks. Two or more tasks: System design interview. Team meetings, may be multiple teams.