5 ms·
Yeah I remember the Google interview a few years back. I did it mostly for fun, and because their recruiters kept contacting me. So there we were, building a t
by rdtsc 11y ago
Yeah I remember the Google interview a few years back. I did it mostly for fun, and because their recruiters kept contacting me.
So there we were, building a tree out of a forest of existing smaller trees or such. That was after they couldn't find my resume, and used a 5 year old one they found some place. They seemed annoyed and tired. By that time I felt nothing short of me proving P!=NP would have help changed their mood. I mean, they didn't even ask me what I knew, what I worked on lately. Heck, I could have been herding goats for the previous 5 years, but if I could have solved that tree problem, well, Googleplex here I come, I could have been herding goats there, maybe as part of some a green eco-initiative project...
I guess half way through I just kind of decided that Google must be a pretty bad place to work at and kind of gave up. I was tempted to ask them how often they had to build the tree out of subtrees at Google. Or in this case how many times did they really have to invert the binary tree, but I am nicer that than, maybe they really did have a pretty shitty day.
Ever since then I've declined to interview at Google. I get contacted every year like clockwork "Wanna try again?", "No thanks, good luck inverting binary trees though..."
- desdiv 11y ago>...I could have been herding goats there, maybe as part of some a green eco-initiative project... Truth is stranger than fiction: http://googleblog.blogspot.sg/2009/05/mowing-with-goats.html http://googleblog.blogspot.sg/2009/05/mowing-with-goats.html
- deleted 11y ago[deleted]
- melling 11y agoI was told by someone many years ago to always take a copy of my resume with me to an interview. That advice has paid off a couple of times. These days I also keep an email draft ready to send.
- x0x0 11y agoWhile that's good advice, I don't follow it. If a company doesn't have their shit together enough to coordinate an interview schedule and get the right people into the right room at the right time with my resume in their hands, ideally in their hands ahead of time, I don't want to work there. It's a basic competence test.
- epalm 11y agoOne reason bringing your resume is a good idea is because scumbag recruiters sometimes modify your resume, inserting the right keywords to get you the interview in the first place.
- therealidiot 11y agoI find if you use PDFs it happens significantly less
- Bootvis 11y agoUnfortunately and apparently some recruiters have interns to convert those PDF's into their shitty doc-template. It happened to me a few times. Every time I had my CV ready and this seemed to help. Knowing LaTeX reflects very positively on you in some circles.
- Lawtonfogle 11y agoOr they just get all the more butchered. Last time a recruiter was done with my resume, it looked so bad that I would've never interviewed me.
- datashovel 11y agoI try to avoid headhunters who think keywords matter (which, sadly, is most of them).
- Ricker 11y agoExactly, I find it's just ticking off every item that's mentioned in the job description. Using the exact same words works best.
- notNow 11y agoDon't you have a PDF copy of it already on your smartphone?
- strathmeyer 11y agoThey don't start looking at your resume or asking what you have been up to until you pass the technical interviews. Which means that if you resume or experience isn't up to snuff, the interviews are a complete waste of time for you because of a decision that takes them five minutes to make.
- Lawtonfogle 11y agoThat seems backwards to me. The resume is supposed to help determine who to spend time interviewing with. If you do good in the interviews, what is on the resume doesn't much matter except for standard background checks.
- _pmf_ 11y ago> That was after they couldn't find my resume, and used a 5 year old one they found some place. Well, searching is not really Google's core competency.
- kozukumi 11y agoOh God this brings back memories. I was actually offered a job at Google (by some miracle) but turned it down. The interviews (7 in total) were an awful experience. I had to solve problems that I had not looked at since my masters and were mostly theoretical CS things which nobody outside of academia ever has to actually use. I had a brief read through of their coding style a few days before so I solved it in a very Google way which is what most likely got me the job. Even though doing it their way was just awful (in terms of implementation). There is no doubt that Google's search algorithms are the best but I can't help but think the rest of their services are only high performing because they can through their enormous data centre resources at the problem. I also hated the attitude of the interviewers and engineers I met. They were so up their own asses. Their way was the best possible way and if you didn't agree well fuck you! I have only turned down two jobs in my career that I 100% do not regret and Google is one of them.
- buyx 11y agoI actually once had to build a tree from subtrees for work (I was modelling some kind of process as a tree, given pairs of data). It was good fun, and a break from the mundane CRUD-based work I usually do. I did it with a whiteboard initially, and ended up producing a fairly robust solution. The difference was that I was able and to try various approaches out without pressure. I had access to my old algorithms textbook as a safety blanket. Some friends dropped by and we went out for supper, and I chewed over my ideas with them. I also had two weeks to solve the problem, and even though it took one Friday night to solve the problem, being given 2 weeks to produce a working solution put me at ease. Doing something like that in a high-stakes interview would be nearly impossible for me.
- meshko 11y agoYes, the thing I hated the most about my Google interview experience was that there was no discussion whatsoever of my previous projects. But there was the question "What would you like to do?" and I realized later that I should have hijacked that question to talk about my past projects I enjoyed the most.