That application was for students who were contacted by recruiters. The application for the general public opens around September/October. In the future, don't hold off on applying until you find a referrer. Googlers can also submit referrals after you submit your application. More on reddit.com

I received the questionnaire back in November. I haven’t heard anything else. Should I be worried? More on reddit.com

You might get rejected if you don't pass the OA, but not because you applied in June. Why would they even send you the OA if this was the case? More on reddit.com

Google interviewer here. While I can't give any specifics like our rubric or questions we ask, I can give advice about my personal experience with interviewing and general interviewing advice that can be applied at really any company asking leetcode-style questions. While my experience has only been for full time rolls, both of my interview loops when trying to get into Google had heavy recursion segments with graph/tree traversal so I'd focus on that especially. Outside of that, just generic leetcode mediums are the difficulty of questions I was asked. Remember that knowing why the solution works and being able to explain it can be more important than the solution itself. I run interviews and if a student didn't say a word but wrote down the exact solution I was looking for, I have no datapoints to judge off of and, for all I know, could've cheated. We look for problem solving skills and how you handle the problems and followups. I've passed students before that didn't get the correct solution down in time but showed that they understood it thoroughly and couldve coded it if they had a couple more minutes. I recommend you interview in this pattern: Verbal explanation of the first solution you can think of Think further if there are any obvious optimizations or different approaches that are more optimal. Once you're settled on an algorithm, do a quick check that it works in the most basic test case Pseudocode. This is the most important step for both you and the interviewer Check that the pseudocode works, again with the most basic test case Actual code Test against 2 test cases. One basic and one edge case. Things to remember: You can ask for help. As an interviewer, we're not expecting you to be completely independent during the interview and solve it without us giving a hint. It's okay to say "I don't know" so long as you took some time to think about what's blocking you. If you need time to think, say something to the tune of "give me 10 seconds to think real quick" If you forget a library function or have a super basic functionality you don't feel like implementing (think like splice in JS) it's okay to ask if you can assume it exists with some name you come up with. If the interviewer isn't okay with it, s/he will let you know. I didn't expect to write a comment this long and got carried away, and I'm feeling lazy so I'm not doing any proofreading so some of it might not be the easiest to understand. I'm happy to clarify further though if needed. Good luck! More on reddit.com