Earlier quoted context omitted.
This is like preparing for an iBanking or Management Consulting interview: undergrads and bschool students alike will spend months preparing for those. And it's "worth it", if they really have what you're after. For banking and consulting, analyst training is truly great. The signaling after those few years when you're a bright kid who studied history in undergrad, is pretty good too. And with Google, you can't deny…
it wasn't so long ago that nobody did this for tech, because we had a self-selecting industry that paid smart people very well, and those banker and consultant kids looked to us with a certain level of envy because we could naturally, seemingly effortlessly (not really), do what they studied years and years to do, which is make over 100 grand in your early 20's without really trying. those days are almost over. the b…
Why I Studied Full-Time for 8 Months for a Google Interview
141–150 of 202 posts
Re: Why I Studied Full-Time for 8 Months for a Google Interview
#142The very fact that "preparing for 8 months for a Google interview" is a thing highlights all the things that have gone wrong at Google and their widely panned bad recruitment practices. The process has become about recruiting people that are good at the silly process and not about recruiting the best people. Probably OK if Google is in 'megacorp looking to feed more skillled cogs into the machine' mode (which it most…
He studied C++, Unix, algorithms, data structures, and system design. Is learning that stuff a "silly process"?
Re: Why I Studied Full-Time for 8 Months for a Google Interview
#143Earlier quoted context omitted.
Finance.
It's questionable whether you'll make more money as a developer in finance than at Google. It'll certainly require a lot more politics and careful planning.
Smart techs go to tech companies. Smart & ambitious techs go to finance.
If you're at Google, you certainly won't participate in conversations with coworkers about how Google just tried to poach you with an offer soooo ridiculously low it's laughable.
Re: Why I Studied Full-Time for 8 Months for a Google Interview
#144Earlier quoted context omitted.
What's the obvious part?
I think it's the goal he chose that is making it obvious: devoting his time on earth to landing an entry level job at some company -- a hyper materialistic and anecdotal "goal" at best. Calling it a goal is funny because it has no value for life, to go all Nietzsche about it. This is just drinking the capitalistic kool-aid and confusing it with something loftier. I call this a mental issue.
"Much that passed for good with one people was regarded with scorn and contempt by another"[1]
Re: Why I Studied Full-Time for 8 Months for a Google Interview
#145Earlier quoted context omitted.
What are you talking about? Where in this article does the author treat Google like a religion? He specifically said it wouldn't be the end of the world if he didn't make it. He specifically said others shouldn't study that much. Another comment based on the headline and not reading the article? Bet you'll get those anti-google upvotes anyway.
What about: "The more I learn about Google, the more I want to work there. In brief, Google is a company that [...] gives employees the freedom to make good decisions for the user. [...] Nowadays candidates are chosen based on coding ability, technical knowledge, and Googleyness." As a user, it hasn't been my experience in a long while that Google gives employees the freedom to make good decisions for the user . Goog…
Not nearly true in any 'Data Driven' company...this dude has no idea who is arbitrating decisions in any reasonable size company...
Re: Why I Studied Full-Time for 8 Months for a Google Interview
#146Google is a great company to work for, but there are many great companies out there. Don't close off other possibly-great opportunities because you're focused on working for a single place. Some random thoughts:
- Hiring at Google, despite our best efforts, is a mostly-random affair. The process is optimized to avoid hiring bad engineers, at the expense of frequently rejecting good engineers. If you get rejected, it doesn't mean anything.
- The average kind of eng work at Google is much like that at any other extremely well-run coding shop. You may spend a lot of time working on backend code that unglamorously glues two communications protocols together. It won't require a deep knowledge of fancy algorithms, but it will require a dedication to code quality, sustainability, testing, and personal productivity.
- Or you may get to work on the Next Big Thing, but keep in mind that most NBTs never see the light of day. It's an exciting work environment, but you have to deal with a lot of chaos and a lot more politics and uncertainty.
- The benefits are great, the work environment is great, and the average quality of your coworkers is great. This is the best thing about Google. If I were going to work somewhere else, I would prioritize these aspects.
- Google, like all large companies, is an uneven experience. Some excellent engineers get hired here who never really "click" -- they get put on projects they don't find interesting, they don't get on with their coworkers, etc. The vast majority of your coworkers will be really outstanding, but there will always be at least one person who you think is kind of an idiot. Most managers are great, but there are still a few assholes. If yours is, then you won't have a good time. Google does its best to minimize all of these problems via things like how it handles promotion, but there's only so much it can do.
Long story short: self-improvement is its own reward. Doing things is how you prove the truth of that improvement. If you can combine that with a great work environment, you're pretty set.
Re: Why I Studied Full-Time for 8 Months for a Google Interview
#147Earlier quoted context omitted.
skate by without a proper understanding of algorithms and design patterns In your estimation, what are the most important algorithms and design patterns to know for web development ?
When I say web development, I am really talking about web application development. The same skills that apply to a native developer apply to a web developer. On the design pattern side, MVVM and MVC are integral to modern web development. Inversion of control and delegates are used in many JavaScript frameworks in server side frameworks like Node and .NET Knowing about different search algorithms comes in handy, as d…
Re: Why I Studied Full-Time for 8 Months for a Google Interview
#148Great write-up, thank you to the OP for putting this on the web! I have a few thoughts on it. First, I'm not all that surprised someone would study for 8 months for an interview at Google. I interviewed there (no hire) and gave myself 3 weeks. It wasn't close to enough time, and I've taken a lot of formal math and basic CS plus data structures. Just too rusty, especially at a whiteboard. I could easily have spent 3 m…
Did you factor in cost of living when doing the salary comparison?
Re: Why I Studied Full-Time for 8 Months for a Google Interview
#149Earlier quoted context omitted.
> it wasn't so long ago that nobody did this for tech Well, competition for jobs (especially the top ones) has never been so fierce. I remember my first job out of undergrad was programming for a (then) pretty well known hardware company. I cracked open a book on "how to write device drivers" the day before my interview and breezed through the interview and got the job. This would literally never happen today. Interv…
I thought developers were now a scarce resource.
Re: Why I Studied Full-Time for 8 Months for a Google Interview
#150I worked at Google. This makes me sad. Sad to see people are treating a for profit company like a religion. Google is a good workplace compared to other companies but it's not a religion and it's not perfect. As other commenters said it's not the thing it was before either. I left Google to work on something more interesting and I can't be happier. If we're going to hire people, I'm not putting any weight on their wo…
People spend years at medical school or law school to become a doctor or lawyer. I don't see the big deal at devoting a huge amount of concentrated time and effort to being an engineer at Google. If you got the free time and willpower (and the author does), more power to you. If he doesn't get the job, he's still got the knowledge. And 8 months is nothing compared to multiple years in college.
True, but both of those are professions. Qualifications that you carry irrespective of your employer. Being 'a Google engineer' is not the same thing, although people might like to imagine it is.