hahaha <3 thanks ninu, I'm not Google material, that is for the exceptionally chosen and talented.
Hit Ninu up and talk. What harm does it do. It if turns out you need to "bone up" a bit, bow you have a clear path that can get you employment at a later date. Google defers job offers all the time (or so I understand).
If you don't know your Floyd Warshall from your Tarjan from your Manacher then you'll just fumble around thinking you got close unless you have the remarkable gift of being able to derive these from scratch in a whiteboard situation. Also I cannot stress enough how difficult - and entirely pointless - a whiteboarding interview is.
edit: I didn't mean this to come across pessimistic and critical. I just think it's important to serve a dose of reality regarding the standard expected (and hopefully some pointers towards the kind of algorithms theory you should be not only comfortable with but also able to reproduce on a whiteboard under pressure).
The HN guidelines ask you to edit this sort of thing out of your comments: https://news.ycombinator.com/newsguidelines.html. We'd appreciate it if you'd err on the side of civility.
Interviewer: Do you know C?
Candidate: I wrote a tiny bit years ago, but not really.
Interviewer: Please write some C.
Also "data structures, algorithms" aren't the basics. The bullshit whiteboard puzzle crap algorithms stuff is irrelevant to 90% of actual programming. Including at Google.
In general Google does not have a good track record for hiring people with non-standard backgrounds except via acquisitions (where magically they do just fine) or if it's someone with a lot of experience. E.g. at least as of 5 years ago to be a product manager you needed a Computer Science degree. Knew one really good product manager who wouldn't have been hired by Google under those rules but had slipped in under older, more lenient rules. He only had a Computer Engineering degree and MBA.