Live data from Hacker News

How I (almost) got an internship at Google

ecarmi.org

131–137 of 137 posts

Re: How I (almost) got an internship at Google

#131
post #36

My story: After my technical phone interviews, I got "accepted" as an intern, meaning I was in the Intern Pool of Rot, where I waded and waited for a team to fish me out. I waded and waded for a couple of months, hoping for a kind suitor. The HR woman always told me that she was "optimistic" about my prospects, so I rejected offers from other companies. Then a really cool opportunity came, and I accepted that offer b…

Same here. Twice in a row. First time, I was told a manager would call me to explain me which team I was being matched with. I received the call to tell me I had an offer... two days after the deadline set by the University. And it is not like this deadline is unknown to employers. Second time, again, I received an offer. This time, I had to call, one week before the deadline, after two weeks of hearing nothing from…

I've had bad experiences with Amazon, Facebook, and Microsoft. Amazon's recruitment process was lengthy and somehow all records they had for one of my interviews mysteriously vanished and I had to start all over again. With Facebook, I didn't get too far into the process, but our campus recruiter has a reputation for being disorganized.

I'll give MS recruiters the benefit of the doubt, as all other candidates I met had positive experiences. They just matched me with the wrong team, and it seems like the recruiter overlooked some paperwork related to scheduling and traveling.

Other sloppy recruitment experiences include some with trading companies such as Jane Street; one such company rejected me by saying "we're only looking for juniors" after calling me on-site. The only truly positive experience I've had is with a YC startup (I was eventually rejected).

Nothing, however, compares with how bureaucratic and mismanaged Google was. I went through a smooth but lengthy recruitment process the first time, and was given a rejection letter after 1 month. Second time, I had to do some juggling between 4 recruiters before getting the paperwork settled for my first interview. I was out of the country and clearly told a recruiter that I should be reached by a different phone number, after which I was asked "are you legally allowed to work in the United States?" even though I'd already answered that in the paperwork they had given me, and I had clearly stated I was studying in the US. Then, I end up scheduling interviews for 2am and 3am my time. The 3am interviewer is not informed about the change in phone number, and is a no-show.

A couple of interviews and 6 weeks later, I get no response. So I end up sending a follow-up mail to my recruiter, who, the very next day, tells me I've been put in the rotting pool. I get no more feedback after 3 weeks, and send another mail. Apparently, I'm still in this rotting pool. I'm guessing this is just equivalent to getting a rejection.

As for interview questions, Google isn't any different from other large companies. I found it odd that they still require candidates to code in Google Docs rather than some Etherpad equivalent that formats code.

So far, searching for an internship has been just a ridiculous time sink. I'd probably get more experience by hacking on my own projects, but that's no guarantee of job safety.

Re: How I (almost) got an internship at Google

#132
post #99

Earlier quoted context omitted.

Getting them to write code is actually pretty good. As for binary search, I wouldn't necessarily be able to bang it out in two hours in C, but I'd easily be able to bang it out in that time for any language I use regularly. And with sufficient testing I'd take a good stab at converting to C. Though I agree sometimes it can be a coin toss. Once I was asked to write some code that would take dates as inputs and do some…

By "other forms of testing" do you mean something like integration testing or do you mean manually checking things? If you run their code and within 10-30 seconds of looking at the result you can spot something wrong with it, then besides being poor coders, they're also poor testers. Since presumably the result that you're looking for is what they should be testing. A while back I worked on a web app with developers…

By other forms of testing I mean ALL other forms of testing. People sometimes fall into traps of thinking that their favourite form of testing is better than all the others, and so they neglect the others. I'm not talking about throwing out automated tests (for instance), they are great for doing regression testing amongst other things. But to only have your automated tests and nothing else seems like folly to me.

I take the point about them being poor coders and testers, though one of them was very highly regarded as a programmer (he presented well). The thing with testing is that you cannot predict everything in advance. Even with full code coverage you cannot cover every path through the code, and as soon as your code escapes into userland all sorts of whacky interactions can take place. The last, and best defence is to actually run the code and see what it does. your eye will pick up problems you never would have otherwise predicted.

With respect to the excellence of your TDD colleagues, perhaps they would have never broken it if they had less overwhelming confidence and more "well, it doesn't hurt to check"? That minor nitpick aside, I congratulate them. I think as programmers we should aspire/strive to be better than average, to be good at our art, and it sounds like they found a way that worked for them and fulfilled that goal.

Re: How I (almost) got an internship at Google

#134

Earlier quoted context omitted.

I agree that this is the most valuable way to judge a candidate, but unfortunately I don't think it would work for most students and most companies (been through it all) because: a) students have a fair bit of school work to do, and: b) most companies can't afford the kind of talent that finds the time to work on other projects outside their normal coursework. Now, for Google that might not be the case — they certain…

Students can (and should?) put the school work on Github or Bitbucket or whatever. Plus side to that is higher chance of getting to look back in later years. I desperately regret losing track of some old projects, just for missing out on poking fun at my undergrad naivete.

Definitely, but unfortunately a lot of one-off code meant for school assignments isn't valuable for anything else. And I wouldn't want GitHub to be littered with random things that aren't — and don't need to be — FLOSS projects, but instead serve as résumé pieces.

Re: How I (almost) got an internship at Google

#135

Earlier quoted context omitted.

In my spare time I'm working on making the next million for my company. Oh, when I'm not working for my company? I'm with my family or friends. I feel like the energy I could spend doing a side project is probably better spent getting these last two features in, or fixing those lingering bugs, or getting that automation solid, etc.... It seems really odd to actually penalize someone who leaves it all on the floor. It…

is that the guy you want on your team? The guy who will tell his next employer, "Company XYZ paid the bills, but my real cool work is this GitHub project I did on the side" I'll bite. Yeah. I want that guy. I want that guy because he's got energy and enthusiasm to burn, and I'm confident I can give him a place to use it.. Additionally, we'd love to see more open source projects come out of what we're working on.. I f…

It really depends on the situation. At my last job the pay wasn't great and there was no profit sharing or stock options. At least they had interesting projects for me to work on, but still they got me for 8 hours and I did my own projects on the side.

My current employer has profit sharing, I love the work we do and there's always more interesting work to do than a 10 hour day allows. So now the projects I do at home are my pet projects for work that excite me but aren't part of my core tasks.

The question is "Is this someone passionate about programming?" and involvement with open source projects are a great way to find that out, but it's not the only way.

Some one who shows initiative and puts in extra work for a company they're excited about show's just as much passion for programming.

It's that programmer who puts in their hour and a half of coding in between reddit posts and forgets about it when 5 oclock hits that you want to stay away from.

Re: How I (almost) got an internship at Google

#137
post #136
post #133

Earlier quoted context omitted.

Because linear is O(n) and binary is O(log(n))?

Oh, sorry - didn't notice that was a requirement.

I don't think it was an explicit requirement, it just would be very wasteful to do a linear search on a sorted list.
Post reply on HN