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
You passed through the weekend offer event. At the first step, you should solve at least 2 of 4 tasks in an online contest platform. The second interview is an online interview where you should solve 2 algorithmic tasks. The first one is easy, and
Everything was smooth and done online. It consisted of four stages: * Live-coding screening * Live-coding * Systems design * Finals (meeting different team leads and choosing a team) It was pretty hard, but I hustled through. Firstly, I tried to a
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
You passed through the weekend offer event. At the first step, you should solve at least 2 of 4 tasks in an online contest platform. The second interview is an online interview where you should solve 2 algorithmic tasks. The first one is easy, and
Everything was smooth and done online. It consisted of four stages: * Live-coding screening * Live-coding * Systems design * Finals (meeting different team leads and choosing a team) It was pretty hard, but I hustled through. Firstly, I tried to a