Got a call from Google!

Asked for two months to study: Discrete mathematics, Calculus, introductions to algorithms, design patterns, CTCI and linux/unix OS workings in general.

I know I'll be banging my head against the wall and I don't have my expectations too high. But regardless I feel like this is a good excuse to speed up my studies and push myself in the direction I want to go already. It'll be a win-win even if I don't land the position because I'll definitely gain a ton in the process of preparing.

I will be expose to all of this material (except for calculus because I've been learning it for a couple of months) for the first time so I know it'll be a challenge and I am looking forward to it.

If any of you have any tips on good study habits that'll be much appreciated; I currently like to read most of my material and supplement with videos/tutorials... Khan is great but they lack material on discrete mathematics unfortuantely. Thanks in advance!

Wish me luck (:

Still looking for my first full-time dev role. After being endlessly rejected from every dev job I've applied for, it starts to eat away at your confidence. Makes me wonder if I'm not as competent as I believe I am. :/

Fortunately, I landed a coding interview with Google! It is my dream job to work at Google, so the fact that they even acknowledged me & my skillset makes me so happy and reaffirms my belief in my capabilities. :D

It's pretty odd, that after applying to 20+ open Google positions relevant to my skill level & location and often with references included, then having been rejected from all of them, that I finally got a chance with them when one of their recruiters found me on LinkedIn and liked what she saw. I cleared the screening call, and made it to the first coding interview.

Of course, even with all the interview prep I've done, it was all practically for naught since they caught me off guard with a crazy conceptual problem anyway. (Well, actually, was I 'caught off guard' if I was already expecting to be caught off guard? o.0) I struggled heavily in the first half of the interview, but found my footing towards the end. So I knew I screwed up and that it was highly unlikely for me to get the job.

Nonetheless, Google had the decency to reject me not via an automated email, but through an actual direct phone call with my recruiter. (The cruelty of the automated application rejection system in our society is a whole rant of its own, for another time.) My recruiter told me that they felt I wasn't ready but they liked what they saw, so they will be revisiting me in exactly a year to reconsider me.

To know that I wasn't fully rejected, and that my dream company Google sees real potential in me, is highly reassuring. It means I'm not a lost cause; I simply need to keep looking. Google will want me more strongly once I have the experience that comes from a fresh grad's first full-time job.

Craziest prep for interview :

Step 1 : Given sufficient time for the scheduled interview by any company, start by searching "How to prepare for Google interviews". Awe at the information before you and get all pumped up to jump in.

Step 2 : Starting with Algorithms, study each one and try not to mix any of them in confusion. In case you are stuck in whiteboard coding, close your eyes, take deep breath and visualize Don Kunth. If that doesn't help, well you are ruined anyway.

Step 3: Practice coding without internet connection, till you are able to write code while you talk about how the weather is really great today. Libraries and methods should flow like poetry. SO is sin.

Step 4: The X programming language which you added to your resume because you can write Hello World, head over to Wikipedia and read more about it just in case.

Step 5: Read some xkcd comics so you can impress the interviewer with some humor. You can try Dilbert too.