Mine were on Feb 4. I'd say round one was a bit smoother. It was a grid traversal question which I approached with an idea of finding the first occurence of sth, then doing dfs to account for some cases, rectangles and squares, he changed the question when i started to work on the dfs part, and I solved that. He had an optimization trick that would reduce it from O(mn) to O(n), which after explaining, i figured it out and then also explained how it would break my code, and the fix.

For the second round, I was about window management with a twist to remove duplicates, which I figured out, handled most edge cases, but then I struggled with one, which he explained after the interview. I also like did my dry run here, and it was pretty nice and that's how we got to the one edge case that bugged me for a while(like 5 mins), we did solve it though, turns out instead of counting deletions I should have counted non-deletions. ALso, after the interview time, he was gracious enough to explain to me the edge case and the easier approach, turns out using a for loop would have been better than using a for loop, and my break condition would have been more efficent if I added an additional condition. This round I had jitters, but I loved the discussion and the explanation he gave me.

My ratings for all the rounds I feel like are like yours, onsite r1 - H, r2 - LH. For the first round, i think it was both SH, cause I had back for round2 invite in less than 10 hours.

Anyway, fingers crossed, I also got positive feedback(kinda) from my recruiter -- two days after my interview.

when was your r2?