Onsite

1. Coding Round
   a) https://leetcode.com/problems/add-binary/
   solved it with minor comments from interviewer
   b) https://leetcode.com/problems/fraction-to-recurring-decimal/
   i could not solve this problem, during my preparation for the interview i left this problem to be solved later. I went through samples and explained only my thoughts, had 1 edge case that i could not handle. Then i decided that my onsite is already ruined from this point. I do not think that such problems should be asked, rather there many topics better as trees and etc to ask onsite.
2. jedi interview (behavioral questions)
   at last had this problem https://leetcode.com/problems/product-of-array-except-self/
   he asked to explain, that was not a problem for me.
   i suggested approaches with division and multuplication of left and right parts.
   -- Lunch
3. System Design of Uber. He liked my design. He was really nice guy, i felt he was interested in my success.
4. Coding Round.
   a) https://leetcode.com/problems/verifying-an-alien-dictionary/
   b) https://leetcode.com/discuss/interview-question/432086/Facebook-or-Phone-Screen-or-Task-Scheduler/394783
   i did well on this round, the interviewer was a nice guy

To conclude,
Do not explain every single variable, you will just waste your time as i did.
i have made huge preparation, i feel really exhausted after so huge work and being rejected. I solved 342 problems on my own, with different approaches. I don't know what to say i am just a "ZERO LUCK MAN". At normal conditions i can solve all this questions, but i should not had to be confident, PLEASE TRIPLE check your code before submitting, writing on whiteboard is kinda different. That was my second onsite in my career and i was so close to my dream. In addition, i assume some of the developers no offence was really mediocre at Algos and DS.