Earlier quoted context omitted.
Which elite schools? I went to MIT and didn’t have to do any of this.
It's a Caltech and Stanford thing. MIT isn't really elite.
Oh not in Utica, it's more of an Albany expression.
How to Ace the Google Interview: Ultimate Guide
71–80 of 239 posts
Re: How to Ace the Google Interview: Ultimate Guide
#72Earlier quoted context omitted.
I completely agree. Even Google suggest to "practice writing syntactically correct code on a whiteboard". This is clearly a useless skill as a software engineers except in getting a job at companies that do whiteboard interviews. Did you try to refactor code on a whiteboard? How are they able to find people that are able to efficiently debug problems? When I interview people I tell them, "Bring your own laptop set up…
Elite schools do that in undergrad; e.g. as an initial scored lab exercise, write this recursive fractal shape using Logo, parallel Delaunay triangulation with prefix sums , dynamic programming solving oligopoly problem or single-value Paxos pseudocode on a piece of paper in 10 minutes (I am being serious). If you can cope with it, it immediately shows up in the interview and you are considered a member of the club,…
Course numbers or it didn't happen
Re: How to Ace the Google Interview: Ultimate Guide
#73Earlier quoted context omitted.
I completely agree. Even Google suggest to "practice writing syntactically correct code on a whiteboard". This is clearly a useless skill as a software engineers except in getting a job at companies that do whiteboard interviews. Did you try to refactor code on a whiteboard? How are they able to find people that are able to efficiently debug problems? When I interview people I tell them, "Bring your own laptop set up…
I’ve heard that Google allows you to type code into a computer now during an interview. A welcome improvement in the state of the art. Still no access to a compiler or debugger, but baby steps.
I had to write code exclusively on white board last month. Only laptop in the room was interviewers which he was using it exclusively to furiously copy the code i was writing in the whiteboard.
He said it will compile it and submit report when he gets back to his desk. :/
Re: How to Ace the Google Interview: Ultimate Guide
#74You can bypass the whole charade by knowing 2-3 people within Google that can provide "assurance" you are good enough. Whiteboard testing is for grunts/unknowns without network. Another way is to be a significant contributor to some popular open source project.
How does this actually work?
Re: How to Ace the Google Interview: Ultimate Guide
#75This is getting ridiculous. These guides to interviewing at specific companies are starting to sound like the video game cheat code books of old. If the process is so nuanced that there's an entire industry around these types of guides (and Google even highly recommends you buy them!), then the process is fundamentally flawed. But we already knew that, and as long as others are still playing the game, we are forced t…
learn with the intent to become a better engineer, even if you don't hit the google mark (which is arbitrary anyway), you will become a better engineer. That is the philosophy most people should use when trying to aim for these companies. Don't cram, learn.
I think this might be better mindset to approach it, instead of pure will power. correct or not.
Re: How to Ace the Google Interview: Ultimate Guide
#76The amount of time required to 'learn' the Google interview would be time that could be spent learning more universally applicable skills. Is it true that an experienced developer would not be able to pass the interview without studying using a similar guide? If so, then the interview process is... fubar.
Hard to even get the interview. I've applied a few times as a senior Dev and was rejected based solely on my cv with the feedback of "work on your algorithms"...
Based on their perception of my algorithmic experience from my CV? Google's a weird one.
Re: How to Ace the Google Interview: Ultimate Guide
#77You can bypass the whole charade by knowing 2-3 people within Google that can provide "assurance" you are good enough. Whiteboard testing is for grunts/unknowns without network. Another way is to be a significant contributor to some popular open source project.
[deleted]
Re: How to Ace the Google Interview: Ultimate Guide
#78This is getting ridiculous. These guides to interviewing at specific companies are starting to sound like the video game cheat code books of old. If the process is so nuanced that there's an entire industry around these types of guides (and Google even highly recommends you buy them!), then the process is fundamentally flawed. But we already knew that, and as long as others are still playing the game, we are forced t…
I had a coderpad facebook phone screen last week, interviewer said " that code the won't compile, can you see why?" .. It was missing a semicolon. on a related note, I write scala on daily basis but scala is not that well suited for coding interviews, I found.
Facebook likes their interview nonsense, but stores passwords in plaintext. I think the credibility of the system is in question
Re: How to Ace the Google Interview: Ultimate Guide
#79You can bypass the whole charade by knowing 2-3 people within Google that can provide "assurance" you are good enough. Whiteboard testing is for grunts/unknowns without network. Another way is to be a significant contributor to some popular open source project.
> You can bypass the whole charade by knowing 2-3 people within Google that can provide "assurance" you are good enough.
This is not a thing. Everyone goes through the same level-adjusted loop.
> Another way is to be a significant contributor to some popular open source project.
LOL no. Google is literally famous for rejecting major open source contributors for not knowing how to reverse a binary tree.
Re: How to Ace the Google Interview: Ultimate Guide
#80Genuine Question: Apart from maybe the money or a nice resume entry, why would you/do you want to?
There's no way this is actually a genuine question. It's the same reason anybody wants a job anywhere: because they'll eventually become homeless if they don't find a job.
There are many rungs on the ladder between Google and homeless.