I want to share my experience with the LeetCode community. Although I got rejected, I would like to give my 2 cents. Please do solve some quality problems, dont focus on solving more and more problems, just think about the problems and give it enough time to sink in. I have seen people cracking Google interviews just by solving 40 50 leetcode problems and have seen people getting flunked even after doing 200+ problems. The Only thing which can save you in interviews is your thinking ability. So, do some logical thinking everyday and read some Engineering Blogs that can help enhancing your Logical Thinking.
Round 1
Given a byte[] array, write a function byte[] readBits(int numBits) starting from LSB towards MSB. for ex, if function called to read 3 bits, read the last 3 bits from the byte and mask the remaining bits with zero. The algorithm has to be designed in such a way that we should read the bits based on the given input and save remaining bits for subsequent reads.
Round 2
RateLimiter Java: We need to write a function to rate limit the functions based on the time, for example, if we pass Runnable and time to a function, system should detect if the function is authorised to run. Basically, we want to limit the functions to run given the time. second part to this was we are also given a total number of executions it can run during that time frame. It was more like a sliding window concept.
Round 3
This was a NP Hard problem, Interviewer asked to write an algorithm to find Perfect Squared Square. You can find some examples of Perfect squared square online.
Here is how the Perfect sqaured square looks like, every square inside a square with distinct sizes.

Round 4
Given a String, validate if it is a valid identifier. If any characters in a string are appearing more than 3 times consecutively, the string is invalid else valid. Follow up to design a algorithm to find such valid identifiers and design a system.
Round 5 (behavioral)
Comments
For some reason , I am not able to reply to any of the comments because of a LeetCode bug it seems, but here are few comments.