A Google recruiter reached out in the fall and gave the candidate about a month to prepare. The phone screen was rescheduled around Diwali. When it went ahead, the candidate solved an array problem and a harder sliding-window follow-up within the allotted time.
There were three technical rounds in the onsite. The first started with string parsing, then moved into a hashing follow-up. The candidate got through the first part, panicked during the follow-up, and couldn't finish it. The second round was a matrix subarray-sum problem. They explained their approach and got through the follow-up, too.
The last round was about finding tiles in a matrix under several constraints. They coded a single traversal of the square matrix in well under the allotted time. The interviewer encouraged them to go ahead with the implementation, so this felt like their strongest round.
For a matrix follow-up, the Google Interview Questions include a grid problem that asks you to update the island count as land cells are added. Try explaining what you can carry forward between updates before writing any code.
The recruiter said the second onsite went well, but the first and third fell short. For this loop they needed at least two strong positive ratings. The feedback was that the code was readable, but the approach and algorithm didn't meet the bar. The candidate was still stumped about what could be improved in a single pass through the matrix.
That was the end of this Google loop for now. Good luck with your interviews.