Re:My Google Interview and Lessons Learned
by brian-armstrong on Monday June 20, 2016 @12:37PM
(#11939142)
I've noticed a trend where Javascript people are unwilling to learn other languages, confining themselves to being in one small little niche forever. Hasn't it always been said that good programmers will make an effort to become familiar with multiple languages?
Re:My Google Interview and Lessons Learned
by pm90 on Monday June 20, 2016 @12:53PM
(#11939263)
In his case I think the decision was correct. Once you have at least a year of experience in one language as a fresh programmer, you understand the quirks, paradigms, design patterns etc. You have a mental model of what a programming language looks like so you can evaluate other languages from that standpoint.
Once that experience is there, then yes, I agree that its usually not difficult to learn a new language.
Re:My Google Interview and Lessons Learned
by apocalyptic0n3 on Monday June 20, 2016 @01:30PM
(#11939543)
That may be true, but I languages can be taught and learned on the job, and frequently are. When giving an interview, you're generally more concerned with processes, how the person thinks and solves problems, how they learn on the fly, etc. In each interview we give, we generally set them up for JS and PHP (we are a PHP shop), depending on the question but also give them the option of switching to a language they are more comfortable with. We can teach you PHP relatively easy; I came in with no PHP experience and was able to start building in Silex in under a month. What we care about is understanding basic architecture, database interaction, OOP principles, some design patterns, etc.
So I think his choice to stick with what he knows and focus on learning algorithms was a good one. He could learn Java or Go or Ruby prior to the interview and then find out that he was placed on a project developing in Python, assuming he took the job. Languages are generally easy to learn and teach; best practices, algorithms, design patterns, etc. are what's hard.
Re:My Google Interview and Lessons Learned
by tgoldenberg on Monday June 20, 2016 @08:39PM
(#11942736)
So the 2 programming languages I am comfortable at are Ruby and JavaScript (which most boot camps teach). I am familiar enough with Python and Java to understand and write code, but wouldn't feel comfortable taking them on for a Google interview. And as for Ruby, I don't see myself using it professionally in the future, so it made sense to double-down on JavaScript. It definitely positively impacted the JS code that I write for work.
Re:My Google Interview and Lessons Learned
by ergothus on Monday June 20, 2016 @02:56PM
(#11940349)
I can't speak to the trend, but it's worth considering where these "Javascript people" came from. For example, I'm currently a Javascript dev. I learned rudimentary C, C++, Pascal, and a couple of Assembly languages in high school/college, but quickly got into Perl (and the Web) for my job. After several years of developing in Perl I learned Java to show the execs looking to do "enterprise" development that I was a team player. I hated Java, and when the chance came to switch, it was going to be either Python or Javascript, and Javascript was something I had picked up some experience with, so it was the first one to get me hired. I'd consider my experience to be fairly familiar to most full-stack or backend developers.
In contrast, I run into a lot of frontend developers that came from the opposite direction: HTML, then CSS, then Javascript. Their relationship to different languages and how it can be useful to their skillset is completely different from mine. If they are uninterested in learning any other language, it's likely because:
* They have no experience to say it will be useful to them, since they are planning to continue to develop in Javascript for the foreseeable future.
* The other "languages" they know (HTML & CSS) are NOT helpful in their JS skillset. So by extension, they have experience teaching them that learning other "languages" isn't helpful.
I'd be skeptical too if someone that didn't code in my language of choice was saying that I should expend effort when my experience says otherwise: it sounds too much like an ivory tower someone speaking pompously.
Now, in my case, I DO know other languages and I know how they can benefit me. (Even language experiences I hated, such as my 5 years as a Java dev, were certainly instructional and useful in my current practices). But that's BECAUSE of my experiences, not DESPITE them. So I can see how someone with a different experience would respond differently. (Heck, I tend to look down on all strict-typing languages because of my Java experience, despite hearing from others that Java is not a great example to learn from).
Re:My Google Interview and Lessons Learned
by brian-armstrong on Monday June 20, 2016 @03:28PM
(#11940663)
I hope you can get past your aversion to nicer type systems. As someone who has watched things break in production too many times, the math is very clear to me that a little time spent pleasing the type system saves MUCH more time that would have been spent debugging something in production that a simple compilation pass would have caught.
Re:My Google Interview and Lessons Learned
by ergothus on Monday June 20, 2016 @04:23PM
(#11941228)
I don't recall single a production bug in my code caused by a type issue (excluding null/undefined cases, where typing is rarely helpful), whereas I've lost countless hours to teaching a compiler what it should already know. (And I have plenty of bugs, they just tend to be logical rather than type based).
That said, I also try to use a lot of unit tests, so there HAVE been more than a few pre-prod issues having to do with types. I just view the time spent on these as still less than what a strictly-typed language would require. Fixing the 1 in a 100 situation that is quickly exposed in a test is less effort than being verbose 100 times.
I will admit that there are some test cases that typing would make much easier - but not enough to yet sway me. I'll also say that strong typing (ala Python) is far less painful to me than static typing (ala Java).
I'll try to keep an open mind, but until I start seeing production bugs that make it worth more development pain, it's unlikely to occur.
* I'll also note that I think my web experience makes me prefer coercion, because everything has to keep switch to/from strings. Though I'm sure the strict-typing crowd will see that as evidence that typing has all the more need to be enforced :)
Re:My Google Interview and Lessons Learned
by sa1 on Tuesday June 21, 2016 @12:54AM
(#11943588)
Dealing with null and undefined cases is a significant practical advantage of a modern type-system. Compilers can catch most of them.
Also you can encode your logic in types - The Curry-Howard Correspondence (https://en.wikipedia.org/wiki/Curry–Howard_correspondence) says this is always possible in sufficiently advanced type-systems. While this goal hasn't been realized in mainstream programming languages, we have been moving towards it for a long time.
So when you say that you only have logical errors, not type errors and can't recall any type issues, do keep in mind that those are exactly the kind of things type-systems aim to solve.
But I can't blame you since Java and similar languages provide the only mainstream experience of static types.
Re:My Google Interview and Lessons Learned
by agumonkey on Monday June 20, 2016 @12:41PM
(#11939180)
Languages I don't know, but paradigm and domains is godsend for your brain after you're over the mental uphill. After going into FP and now reading about Prolog a lot, a huge lot of ideas are blending in few concepts, recursive space exploration, trimming, continuations, graph theory ...
I wonder if it's what is expected from college graduation (we saw all these topics there after all) or if I'm late to the game but it's quite a joy nonetheless.
Re:My Google Interview and Lessons Learned
by k__ on Monday June 20, 2016 @01:48PM
(#11939701)
True story.
But fact is: JavaScript the opposite of a small little niche.
Not because you can do everything with JS (which you probably can't) but because a few things you can do with it are considered rather valuable at this moment.
Switching to a different language isn't that big of a deal for a advanced programmer.
Re:My Google Interview and Lessons Learned
by danilocesar on Monday June 20, 2016 @01:06PM
(#11939360)
"After the usual explanation that it was a “close call”, I asked what I could have done better and was told that I needed to be more consistent."
Probably he just gave another "usual explanation" from his handbook.
That's the problem when you have a recruiter as a proxy between you and your interviewer, specially when you get the negative answer. When they get the "No" answer, you are not profitable anymore. You are now a liability. A time-consuming problem they have to deal with. With that couldn't-be-more-generic-feedback, it seems to be your case.
Would be better to reach your interviewers directly and get feedback from them.
Re:My Google Interview and Lessons Learned
by khedoros on Monday June 20, 2016 @01:51PM
(#11939731)
Google gave me the answer "Unfortunately, we can't provide you any feedback from the interviewers." A couple weeks later, they sent me a questionnaire for me to provide them feedback.
I suppose that if I'd made notes of each interviewer's name, I could've taken a guess at their Google e-mail addresses and tried to contact them directly, but that's definitely not something they would've made easy for me.
Re:My Google Interview and Lessons Learned
by kyrra on Monday June 20, 2016 @01:23PM
(#11939488)
In Google's case there are a lot of people in the pipeline that all need to respond before you get an answer. All your interviewers need to get their feedback in. Any internal or external referrals need to provide feedback. And once that's all together, it needs to be presented to a hiring committee (and there are more steps after this that can take time).
(Good) recruiters at Google strive to get their candidates answers as soon as possible, but the most they can do, at times, is hound the person that is holding up the process.
Re:My Google Interview and Lessons Learned
by khedoros on Monday June 20, 2016 @01:46PM
(#11939686)
My second interview out of college with EMC led to about a month and a half of waiting, but resulted in an offer at higher pay than I had expected.
A more recent interview with Google got me a "no" in about 4 business days. Whatever else I could say about the process, at least they stuck to their promised window.
Re:My Google Interview and Lessons Learned
by wallflower on Monday June 20, 2016 @01:25PM
(#11939507)
In the olden days, companies would typically say it would take 2-3 weeks to give you a response. This was because they needed buffer time between extending an offer to their first-choice candidates, waiting for them to accept or turn down, time for salary negotiations (before the offer is final), extending an offer to their second-choice - and so on.
Nowadays, I think it may be a breakdown of the hiring or communication process. If there is a recruiter (outside) involved, the recruiter will likely not get communications about the ongoing hiring process since they involve candidates that the outside recruiter does not handle. If it is an inside recruiter, the inside recruiter might not even get communications if there are other inside recruiters competing to fill a position (silos, darwinism, bonus pools).
It would be nice if the hiring software platforms automatically sent a workflow-based notification based on where you were in the pipeline (e.g. 'did not pass go, did not collect $200'). However, I think that transparency into hiring processes advantages the candidates over the hiring company. The hiring company's advantage is that it (usually) has the power and controls information asymmetrically. There are most likely exceptions for exceptional candidates (think Google/Facebook AI team candidates) in which they don't play the hiring game but are simply trying to smooth the process.
This is why having an internal advocate is essential for getting into a company's hiring pipeline and knowing where you are in that pipeline (did the pipeline break for you, were you discharged into an outflow pipe after the on-sites etc).
Hiring is optimized for the employer's yield of quality employees, not for the non-accepted ("rejected") employees. Even though there are legal issues involved with specific reasons for non-hiring (e.g. worst case - discrimination lawsuits), it still benefits the company to be cautiously turtle slow with even black/white binary responses (no, yes - you are hired).
Since some of the most egregious companies (e.g. Google) have some of the most talented software engineers, you can imagine it is more a function of the culture (e.g. false positives are bad - it is acceptable to have false negatives) than the software/communication platforms underlying the hiring process.
Re:My Google Interview and Lessons Learned
by SoulMan on Monday June 20, 2016 @01:10PM
(#11939384)
Right. I think its the problem with some (probably majority) of recruiters attitude. They will be after you for resumes and referrals but once you apply and don't get through or resume is not impressive the do not bother to inform you , even don't respond to your curious email. Even for internal referrals I have chased them for months just to get to know that resume was not "fitting"
Re:My Google Interview and Lessons Learned
by SoulMan on Monday June 20, 2016 @01:29PM
(#11939539)
The problem with internal referral is that your friend keeps texting you every day what happened to the resume he had sent and your company recruiter does not respond to the your emails/IMs.
Re:My Google Interview and Lessons Learned
by kafkaesq on Monday June 20, 2016 @03:49PM
(#11940837)
The act of suddenly ceasing all communication with someone the subject is dating, but no longer wishes to date. This is done in hopes that the ghostee will just "get the hint" and leave the subject alone, as opposed to the subject simply telling them he/she is no longer interested.
Re:My Google Interview and Lessons Learned
by SoulMan on Monday June 20, 2016 @12:39PM
(#11939162)
I am not sure how Google/Amazon/Facebook judge a programmer by asking to write "production ready" code on few sheet of paper where one can not rearrange blocks, edit. How many does it in real world ? Unless its 1977 and you are doing FORTRAN in punch cards.
Re:My Google Interview and Lessons Learned
by honkhonkpants on Monday June 20, 2016 @01:31PM
(#11939555)
Much of the interview process is used to determine if the candidate can program a computer at all. It's pretty obvious in the opening minutes if I ask you to write out a simple function in your chosen strong language (such as strlen, if you said C) whether you can or cannot do this. If you can stand there and write out something like:
Then at least I know that you've ever programmed in this language before, which sets you apart, strangely enough, from 95% of the applicants. I won't even care if you write the return type as int instead of size_t, as long as you're obviously aware that every function declaration must have a return type (or whatever the requirements of your language might be).
From there we can start talking about graph traversal or whatever, to determine what you know about complexity analysis.
It's really not about "production-ready code" but fluency. When you speak your native language you don't constantly bumble and make errors and leave out important words. It should be the same when you write code in your favorite programming language, and whether you can or cannot do so becomes readily apparent in technical interviews.
Re:My Google Interview and Lessons Learned
by vonmoltke on Monday June 20, 2016 @04:10PM
(#11941099)
> Then at least I know that you've ever programmed in this language before, which sets you apart, strangely enough, from 95% of the applicants.
At best, it sets you apart from 95% of interviewees. I rarely get the chance to prove I can actually program. Even then, I think that is a gross exaggeration.
Re:My Google Interview and Lessons Learned
by bogomipz on Monday June 20, 2016 @03:22PM
(#11940606)
Is it true that they don't care what language you know, and that it doesn't have to be one of either - Java, C or C++?
I have heard that what they are looking for is your problem solving skills and your ability understand the problem space and the tradeoffs.
But then I've also heard that if you are not proficient in a statically typed language that will hurt your candidacy. I am not sure if this true. I would that is someone has good CS skills and good problem solving ability that they could pick up any language statically typed or not.
Curious what someone more in the know regarding Google/FB/AWS has to say on the matter.
Re:My Google Interview and Lessons Learned
by bogomipz on Monday June 20, 2016 @03:51PM
(#11940864)
So the idea is that as long as you have good CS fundamentals and problem solving skills, what language(s) you know doesn't matter as you will likely be able to be pick those up as you go?
Re:My Google Interview and Lessons Learned
by leothekim on Monday June 20, 2016 @01:20PM
(#11939465)
I've seen Google interview questions before, and I don't find them unreasonable except for the fact you're forced to write things out on a whiteboard. The bigger problem I have is the 5 on-site interviews. Coming up with a solution that is 100% correct and optimal and well-coded for all 5 interviews would be physically and mentally exhausting for me. I have two young children, so sleep deprivation is my constant reality. Not to say no one else in my position can do this, but I certainly can't.
Re:My Google Interview and Lessons Learned
by pklausler on Monday June 20, 2016 @12:54PM
(#11939279)
You know, if I knew nothing about the law, but assumed that I could skim a couple books and pass the bar exam, I'd have to be some kind of combination of arrogant, disrespectful, and crazy.
Re:My Google Interview and Lessons Learned
by bradleyjg on Monday June 20, 2016 @01:16PM
(#11939438)
That's not a great example. There's a six week bar exam course that most law graduates take because law school doesn't do anything to prepare students for the bar exam. Take any reasonably intelligent person with strong written English skills, have him take one of these six week courses including doing all the homework, and he'd likely be able to pass the bar.
Practicing law is a different story. Although a significant percentage of law school has very little relevance to the day to day practice of law it would be an exaggeration to claim that law school doesn't do anything to prepare you for practice as I claimed for the bar exam.
Re:My Google Interview and Lessons Learned
by tgoldenberg on Monday June 20, 2016 @08:42PM
(#11942744)
Except I never approached Google. They approached me. They sent me an email with a header that said "You are app-solutely fabulous." (I know, so dorky it's suspicious) Do you think it's arrogant, disrespectful or crazy for me to take on the challenge head on? I learned a great deal from the process and I'm certainly not forbidden from interviewing again in the future. But this is just my approach to things.
Re:My Google Interview and Lessons Learned
by dudul on Monday June 20, 2016 @11:54AM
(#11938826)
"In each one, I was given a technical problem and asked to whiteboard my solution."
Can't believe Google is still doing this crap. 5 whiteboarding exercises, seriously? How dumb is that. One OK, two why not. But maybe part of the interview could be spend talking about, you know, architecture, past experience, workflow, etc.
Re:My Google Interview and Lessons Learned
by overcast on Monday June 20, 2016 @12:26PM
(#11939063)
Google, and the other big players, will continue doing this, as long as people keep lining up to their doors in droves. When you literally have the pick of the litter, you can do whatever you want.
Re:My Google Interview and Lessons Learned
by 27182818284 on Monday June 20, 2016 @01:34PM
(#11939584)
For what it is worth--at this point I don't think Google has the pick of the litter. I know brilliant people that aren't even considering Google compared to SpaceX, Uber, etc.
Re:My Google Interview and Lessons Learned
by munificent on Monday June 20, 2016 @12:49PM
(#11939234)
> But maybe part of the interview could be spend talking about, you know, architecture, past experience, workflow, etc.
Google does to do that for many candidates, but if you're a recent school grad, you probably don't have as much past experience to talk about, so the interviewer will instead tend to focus on coding questions.
Basically, the longer your work history is, the more questions you'll get about what you have done versus demonstrating what you can do.
Re:My Google Interview and Lessons Learned
by linkregister on Monday June 20, 2016 @12:54PM
(#11939277)
I've interviewed at Google 3 times. I have never been asked about my experience. In fact, citing relevant experience during the question has resulted in a negative reaction from interviewers. I think the Google interviewing ethos is to hire generalist engineers, and necessary specialization will follow.
There are exceptions, of course: Google Zero, Google X, but I maintain for SWE and SRE, it's all about the whiteboarding.
Re:My Google Interview and Lessons Learned
by drdaeman on Monday June 20, 2016 @12:21PM
(#11939033)
Depends on how the whiteboard is meant to be used.
It must be perfectly fine if it's meant to draw figures and overall ideas about the solution. That's what whiteboards are for. Sometimes a picture's worth a thousand words, and drawing diagrams or illustrations is frequently indispensable for actually solving a complex problem (as opposed to having a picture in the head, or described in writing).
But I'd say it's borderline offensive to ask a person to write any realistic code (i.e. not very-high-level pseudocode that's more of a human-readable notes than something for a machine) on a whiteboard.
Never been to Google, so no idea what they ask for.
Re:My Google Interview and Lessons Learned
by mashlol on Monday June 20, 2016 @01:22PM
(#11939481)
They ask you for code. Real, runnable code. The interviewer types it verbatim from what you wrote on the board...
I don't think they necessarily care if it compiles, or if you forgot whether it was Set.has() or Set.contains(), but for some reason they do not allow pseudocode.
Re:My Google Interview and Lessons Learned
by ikeyany on Monday June 20, 2016 @12:39PM
(#11939154)
I don't see the issue. Coding on a whiteboard is more about demonstrating your problem solving ability, not your raw knowledge of programming. If they ask you to implement something like a maze solver, having the exact answer seems less important than communicating the steps needed to create such a solver (e.g. making sure you truly understand the question, taking note of possible bottlenecks or corner cases, having an 'obvious' solution and proving why it's slow/wasteful, etc.).
That being said, everyone knows you need to have a solid understanding of data structures and algorithms to be seriously considered, but I don't think Google is necessarily looking for software prodigies.
Re:My Google Interview and Lessons Learned
by kafkaesq on Monday June 20, 2016 @12:52PM
(#11939252)
Coding on a whiteboard is more about demonstrating your problem solving ability,
Whilst explaining verbally to others your every single step of your thought processes while you are doing fine-grained analysis the problem (something which one almost never has to do in real engineering environments), and under incredibly unrealistic time pressure ("these people will either love me or hate me, depending on what I say in the next 5 seconds.")
And typically to solve "problems" that bear little or no resemblance to the kind of problems that you'd actually be tasked with solving on a day-to-day basis at most of these roles. But which instead seem to solve other, ulterior purposes -- in particular, to shore up the interviewer's own insecurities:
"Gosh, I wish I knew how to find good people for this job. And heaven forbid if the candidate should ask me to explain our business model... But if we ask a bunch of Google-style questions at the whiteboard... I guess that means we must be in same league as Google."
Re:My Google Interview and Lessons Learned
by ikeyany on Monday June 20, 2016 @02:07PM
(#11939868)
I've never seen someone put a scarier spin on "showing your work".
Fine-grained analysis? Again, you're not expected to be a master, but it's not asking a lot for you to break down a seemingly complex problem into something workable (e.g. The maze solver example above could be approached with choosing a right turn whenever you approach an intersection...does that seem very fine-grained to you?).
Incredibly unrealistic time pressure? Again, in most interviews I've had/conducted, you're not expected to just know the answer. If you do, that's great, but you make it seem like they're waiting to pounce on you the moment you struggle. I've never seen that in interviews for larger companies.
Re:My Google Interview and Lessons Learned
by griffinmichl on Monday June 20, 2016 @12:07PM
(#11938911)
A company like google has the resources to basically just make their interview an IQ test with the assumption that they can throw smart people into any role they need them in.
Re:My Google Interview and Lessons Learned
by jcadam on Monday June 20, 2016 @12:46PM
(#11939213)
I'd rather they just sit me down in a quiet room and have me take a formal IQ test (Wonderlic, etc.). Seems like it would be a more efficient use of time for all concerned.
Seriously, we could get this done in three steps:
1. Phone screen including Fizzbuzz-level programming challenge.
Re:My Google Interview and Lessons Learned
by gergles on Monday June 20, 2016 @01:13PM
(#11939412)
It's legal, just difficult to defend, because there are racial differences in IQ. So, there is a presumption by the EEOC that you are discriminating based on race if you give an IQ test.
You can get around this by conducting a study that finds IQ is better correlated to performance on a particular role than any other nondiscriminatory measure, but good luck with that, and good luck proving that when you get sued by someone. It's just too risky, despite not being illegal.
Re:My Google Interview and Lessons Learned
by dragonwriter on Monday June 20, 2016 @01:28PM
(#11939530)
It's absolutely legal. Like any other screening tool that has significantly differential impact by race, it's only legal when it is sufficiently demonstrably related to performance in the specific jobs for which it is used as a screening tool.
There is a popular myth that it is illegal because of a case where it was found to be illegal in the specific manner in which it was used.
Re:My Google Interview and Lessons Learned
by CobrastanJorji on Monday June 20, 2016 @01:17PM
(#11939442)
Pretty sure that's not the case. When I worked for IBM back in the day, their interview did in fact involve an actual IQ test administered online as a first screening step.
Re:My Google Interview and Lessons Learned
by Godel_unicode on Monday June 20, 2016 @04:40PM
(#11941385)
As with all things employment law, it's more complicated than that. Briefly, the test must be "professionally developed" and relevant. Thus the whiteboard programming exam is an admissable proxy for an IQ test.
Re:My Google Interview and Lessons Learned
by honkhonkpants on Monday June 20, 2016 @01:36PM
(#11939595)
Nobody cares about your experience or preconceptions about architecture because your experience will be pretty much irrelevant at Google which uses almost no third-party code and has a homegrown solution to everything, and because Google's software architecture is radically different from any other company's and you have to adapt to it, not the other way around.
Re:My Google Interview and Lessons Learned
by riyadparvez on Monday June 20, 2016 @12:24PM
(#11939048)
I concur with you. I do not have any allergy towards whiteboard questions. Couple of whiteboards is reasonable, but five of them seems totally unnecessary.
Re:My Google Interview and Lessons Learned
by crimsonalucard on Monday June 20, 2016 @12:32PM
(#11939101)
I've talked to a research scientist at facebook who commented on this exact issue. They've debated this, the issue is that architecture, past experience, workflow are all things that can be taught to anyone.
Google and similar companies aren't in the business of hiring anyone who can just learn anything. Given enough time anyone can develop skills to be a programmer. However, google is in the business of hiring people who are intellectually superior. People who can do things that can't necessarily be taught.
You complain about 5 whiteboard problems because most likely you won't be able to solve 5 whiteboard problems. This does not mean you're a bad programmer. However, the guy who can solve those problems without an issue has a higher probability of having higher intelligence and better programming skills than you.
Re:My Google Interview and Lessons Learned
by sbov on Monday June 20, 2016 @01:15PM
(#11939421)
I disagree, the type of whiteboard questions you get can completely get taught, and practicing helps. Intellect certainly helps, but it helps in every activity.
If I wanted to put a negative spin on it: Google is filtering for people with lots of free time on their hands and spend that free time on intellectual pursuits. This makes them more likely to spend their free time staying at work rather than going home and doing something else.
Re:My Google Interview and Lessons Learned
by palakchokshi on Monday June 20, 2016 @12:42PM
(#11939187)
But the whiteboarding questions and their successful completion by the author clearly shows Google is hiring for skills that the author was able to learn in 1 month. Architecture, workflow, use of proper design patterns, etc. are things you learn from past experience.
Re:My Google Interview and Lessons Learned
by khedoros on Monday June 20, 2016 @02:10PM
(#11939899)
There's "successful completion", and then there's what Google is looking for. They want optimal code, and they want you to explain your thought process as you're writing. They want you to hit all the subtle corner cases without being prompted (and for you to verbally note why you coded it that way).
You solved the problem if you give them the O(n^2) answer, but they're looking for the more complicated O(n) answer, because then they'll get to present you with the 2nd and 3rd variations on the question, rather than spending time refining the first.
Re:My Google Interview and Lessons Learned
by curiouscat321 on Monday June 20, 2016 @12:52PM
(#11939255)
I've noticed that some people seem to way overprepare for Google interviews in particular. I get that they're hard, but how much practice do you really need for, say, a phone screen?
Re:My Google Interview and Lessons Learned
by sulam on Monday June 20, 2016 @01:29PM
(#11939537)
I interviewed a coding bootcamp person in SF and found them to be quite competent and able to handle stuff at a level I've seen from engineers with 3-5 years of experience in the field, along with their CS degree. Other interviewers also had a positive experience with this person and we made an offer, but in the end they decided to take a competing offer...from Google.
Re:My Google Interview and Lessons Learned
by buckbova on Monday June 20, 2016 @12:35PM
(#11939129)
Well, he wasn't offered the job. So, we'll never know how prepared.
Practice does help for these whiteboarding style questions.
I completed a bunch of https://www.hackerrank.com/ problems prior to my last set of technical interviews and it definitely helped keep me sharp. My day to day CRUD work is rarely helpful in that regard.
Re:My Google Interview and Lessons Learned
by crimsonalucard on Monday June 20, 2016 @12:44PM
(#11939201)
I know, but I would argue you need a year of this stuff and really deep intuition. One month of hackerrank isn't enough. The problems google throws at you are not trivial.
Re:My Google Interview and Lessons Learned
by linkregister on Monday June 20, 2016 @12:52PM
(#11939248)
It looked like he was putting in 4+ hours per day. He implemented all of these algorithms in code. I think it's pretty amazing. It took me about the same amount of time to implement a B+ tree variant for my Data Structures class in college. Pretty impressive on his part. Either that or I'm unimpressive ;)
Once that experience is there, then yes, I agree that its usually not difficult to learn a new language.
So I think his choice to stick with what he knows and focus on learning algorithms was a good one. He could learn Java or Go or Ruby prior to the interview and then find out that he was placed on a project developing in Python, assuming he took the job. Languages are generally easy to learn and teach; best practices, algorithms, design patterns, etc. are what's hard.
In contrast, I run into a lot of frontend developers that came from the opposite direction: HTML, then CSS, then Javascript. Their relationship to different languages and how it can be useful to their skillset is completely different from mine. If they are uninterested in learning any other language, it's likely because:
* They have no experience to say it will be useful to them, since they are planning to continue to develop in Javascript for the foreseeable future. * The other "languages" they know (HTML & CSS) are NOT helpful in their JS skillset. So by extension, they have experience teaching them that learning other "languages" isn't helpful.
I'd be skeptical too if someone that didn't code in my language of choice was saying that I should expend effort when my experience says otherwise: it sounds too much like an ivory tower someone speaking pompously.
Now, in my case, I DO know other languages and I know how they can benefit me. (Even language experiences I hated, such as my 5 years as a Java dev, were certainly instructional and useful in my current practices). But that's BECAUSE of my experiences, not DESPITE them. So I can see how someone with a different experience would respond differently. (Heck, I tend to look down on all strict-typing languages because of my Java experience, despite hearing from others that Java is not a great example to learn from).
That said, I also try to use a lot of unit tests, so there HAVE been more than a few pre-prod issues having to do with types. I just view the time spent on these as still less than what a strictly-typed language would require. Fixing the 1 in a 100 situation that is quickly exposed in a test is less effort than being verbose 100 times.
I will admit that there are some test cases that typing would make much easier - but not enough to yet sway me. I'll also say that strong typing (ala Python) is far less painful to me than static typing (ala Java).
I'll try to keep an open mind, but until I start seeing production bugs that make it worth more development pain, it's unlikely to occur.
* I'll also note that I think my web experience makes me prefer coercion, because everything has to keep switch to/from strings. Though I'm sure the strict-typing crowd will see that as evidence that typing has all the more need to be enforced :)
Also you can encode your logic in types - The Curry-Howard Correspondence (https://en.wikipedia.org/wiki/Curry–Howard_correspondence) says this is always possible in sufficiently advanced type-systems. While this goal hasn't been realized in mainstream programming languages, we have been moving towards it for a long time.
So when you say that you only have logical errors, not type errors and can't recall any type issues, do keep in mind that those are exactly the kind of things type-systems aim to solve.
But I can't blame you since Java and similar languages provide the only mainstream experience of static types.
I wonder if it's what is expected from college graduation (we saw all these topics there after all) or if I'm late to the game but it's quite a joy nonetheless.
But fact is: JavaScript the opposite of a small little niche.
Not because you can do everything with JS (which you probably can't) but because a few things you can do with it are considered rather valuable at this moment.
Switching to a different language isn't that big of a deal for a advanced programmer.
Probably he just gave another "usual explanation" from his handbook. That's the problem when you have a recruiter as a proxy between you and your interviewer, specially when you get the negative answer. When they get the "No" answer, you are not profitable anymore. You are now a liability. A time-consuming problem they have to deal with. With that couldn't-be-more-generic-feedback, it seems to be your case.
Would be better to reach your interviewers directly and get feedback from them.
I suppose that if I'd made notes of each interviewer's name, I could've taken a guess at their Google e-mail addresses and tried to contact them directly, but that's definitely not something they would've made easy for me.
They're much happier with a recruiter giving a liability-free, if vague answer.
Please respond by the time you say you will, more or less.
It is amazing how many companies seem to be "unable" to come through on this very modest expectation.
(Good) recruiters at Google strive to get their candidates answers as soon as possible, but the most they can do, at times, is hound the person that is holding up the process.
The problem is that they continually bait candidates with promised turnaround times that very seldom have anything to do with reality.
A more recent interview with Google got me a "no" in about 4 business days. Whatever else I could say about the process, at least they stuck to their promised window.
Nowadays, I think it may be a breakdown of the hiring or communication process. If there is a recruiter (outside) involved, the recruiter will likely not get communications about the ongoing hiring process since they involve candidates that the outside recruiter does not handle. If it is an inside recruiter, the inside recruiter might not even get communications if there are other inside recruiters competing to fill a position (silos, darwinism, bonus pools).
It would be nice if the hiring software platforms automatically sent a workflow-based notification based on where you were in the pipeline (e.g. 'did not pass go, did not collect $200'). However, I think that transparency into hiring processes advantages the candidates over the hiring company. The hiring company's advantage is that it (usually) has the power and controls information asymmetrically. There are most likely exceptions for exceptional candidates (think Google/Facebook AI team candidates) in which they don't play the hiring game but are simply trying to smooth the process.
This is why having an internal advocate is essential for getting into a company's hiring pipeline and knowing where you are in that pipeline (did the pipeline break for you, were you discharged into an outflow pipe after the on-sites etc).
Hiring is optimized for the employer's yield of quality employees, not for the non-accepted ("rejected") employees. Even though there are legal issues involved with specific reasons for non-hiring (e.g. worst case - discrimination lawsuits), it still benefits the company to be cautiously turtle slow with even black/white binary responses (no, yes - you are hired).
Since some of the most egregious companies (e.g. Google) have some of the most talented software engineers, you can imagine it is more a function of the culture (e.g. false positives are bad - it is acceptable to have false negatives) than the software/communication platforms underlying the hiring process.
But when they ghost you even after an internal referral? From someone you worked with previously?
That's when you really have to wonder what is going through these people's heads.
The real problems is that most companies just don't seem to care about candidate experience, period.
http://www.urbandictionary.com/define.php?term=ghosting
From there we can start talking about graph traversal or whatever, to determine what you know about complexity analysis.
It's really not about "production-ready code" but fluency. When you speak your native language you don't constantly bumble and make errors and leave out important words. It should be the same when you write code in your favorite programming language, and whether you can or cannot do so becomes readily apparent in technical interviews.
At best, it sets you apart from 95% of interviewees. I rarely get the chance to prove I can actually program. Even then, I think that is a gross exaggeration.
I have heard that what they are looking for is your problem solving skills and your ability understand the problem space and the tradeoffs.
But then I've also heard that if you are not proficient in a statically typed language that will hurt your candidacy. I am not sure if this true. I would that is someone has good CS skills and good problem solving ability that they could pick up any language statically typed or not.
Curious what someone more in the know regarding Google/FB/AWS has to say on the matter.
Is that still true then?
Did you get the job?
Practicing law is a different story. Although a significant percentage of law school has very little relevance to the day to day practice of law it would be an exaggeration to claim that law school doesn't do anything to prepare you for practice as I claimed for the bar exam.
Can't believe Google is still doing this crap. 5 whiteboarding exercises, seriously? How dumb is that. One OK, two why not. But maybe part of the interview could be spend talking about, you know, architecture, past experience, workflow, etc.
Google does to do that for many candidates, but if you're a recent school grad, you probably don't have as much past experience to talk about, so the interviewer will instead tend to focus on coding questions.
Basically, the longer your work history is, the more questions you'll get about what you have done versus demonstrating what you can do.
There are exceptions, of course: Google Zero, Google X, but I maintain for SWE and SRE, it's all about the whiteboarding.
It must be perfectly fine if it's meant to draw figures and overall ideas about the solution. That's what whiteboards are for. Sometimes a picture's worth a thousand words, and drawing diagrams or illustrations is frequently indispensable for actually solving a complex problem (as opposed to having a picture in the head, or described in writing).
But I'd say it's borderline offensive to ask a person to write any realistic code (i.e. not very-high-level pseudocode that's more of a human-readable notes than something for a machine) on a whiteboard.
Never been to Google, so no idea what they ask for.
I don't think they necessarily care if it compiles, or if you forgot whether it was Set.has() or Set.contains(), but for some reason they do not allow pseudocode.
That being said, everyone knows you need to have a solid understanding of data structures and algorithms to be seriously considered, but I don't think Google is necessarily looking for software prodigies.
Whilst explaining verbally to others your every single step of your thought processes while you are doing fine-grained analysis the problem (something which one almost never has to do in real engineering environments), and under incredibly unrealistic time pressure ("these people will either love me or hate me, depending on what I say in the next 5 seconds.") And typically to solve "problems" that bear little or no resemblance to the kind of problems that you'd actually be tasked with solving on a day-to-day basis at most of these roles. But which instead seem to solve other, ulterior purposes -- in particular, to shore up the interviewer's own insecurities:
"Gosh, I wish I knew how to find good people for this job. And heaven forbid if the candidate should ask me to explain our business model... But if we ask a bunch of Google-style questions at the whiteboard... I guess that means we must be in same league as Google."
Fine-grained analysis? Again, you're not expected to be a master, but it's not asking a lot for you to break down a seemingly complex problem into something workable (e.g. The maze solver example above could be approached with choosing a right turn whenever you approach an intersection...does that seem very fine-grained to you?).
Incredibly unrealistic time pressure? Again, in most interviews I've had/conducted, you're not expected to just know the answer. If you do, that's great, but you make it seem like they're waiting to pounce on you the moment you struggle. I've never seen that in interviews for larger companies.
In Google's case, for example -- to establish their "brand."
Seriously, we could get this done in three steps:
1. Phone screen including Fizzbuzz-level programming challenge.
2. IQ Test
3. Personality/Culture-fit interview.
You can get around this by conducting a study that finds IQ is better correlated to performance on a particular role than any other nondiscriminatory measure, but good luck with that, and good luck proving that when you get sued by someone. It's just too risky, despite not being illegal.
There is a popular myth that it is illegal because of a case where it was found to be illegal in the specific manner in which it was used.
https://en.m.wikipedia.org/wiki/Griggs_v._Duke_Power_Co.#
https://www.hiresuccess.com/blog/is-employment-testing-legal
Google and similar companies aren't in the business of hiring anyone who can just learn anything. Given enough time anyone can develop skills to be a programmer. However, google is in the business of hiring people who are intellectually superior. People who can do things that can't necessarily be taught.
You complain about 5 whiteboard problems because most likely you won't be able to solve 5 whiteboard problems. This does not mean you're a bad programmer. However, the guy who can solve those problems without an issue has a higher probability of having higher intelligence and better programming skills than you.
If I wanted to put a negative spin on it: Google is filtering for people with lots of free time on their hands and spend that free time on intellectual pursuits. This makes them more likely to spend their free time staying at work rather than going home and doing something else.
You solved the problem if you give them the O(n^2) answer, but they're looking for the more complicated O(n) answer, because then they'll get to present you with the 2nd and 3rd variations on the question, rather than spending time refining the first.
Practice does help for these whiteboarding style questions.
I completed a bunch of https://www.hackerrank.com/ problems prior to my last set of technical interviews and it definitely helped keep me sharp. My day to day CRUD work is rarely helpful in that regard.
ps: hackerrank is neat.
"Talk about the three main parts of TCP/IP"
"Talk about what you would do in a new BIND configuration file"
etc