Bug in Google interview code
Had an onsite recently. In one of the interview I wrote the whole code but there was a bug in the code which interviewer had to spot and I fixed but later on I tried that fix after the interview and looks like it didn’t fix the bug. How do the interviewer will rank me in this case? Its hard to write perfect code in the whiteboard but Google is being notorious to expect that from the candidates. Is it a no hire?
100% fail. Start looking elsewhere
You’ll likely be blacklisted by google, who shares blacklists with the rest of the top tier companies :(
Thats how u ended up where u r right now, dude?
I actually passed my google onsite but will be at Facebook in a couple months. So no :)
Did you claim that your fix actually fixed the bug? Because in such cases, Google is known to sue candidates for falsification.
Fuck me! Even I am feeling like trolling myself. lol
What you need in interviews is to convince the interviewer that your code is working. I wrote code in interviews that looks to be working but I knew it doesn’t work for not-immediately-obvious reasons (such as modifying a collection in a foreach loop), and got a pass. I probably did that at G Interviews as well.
@Mmkayy Do you recommend clearer code to a more efficient but harder to follow code for Google interview. There are some nice solutions on Leetcode discussions, but are not obvious that they work if you are not familiar with the specific technique.
Efficiency is an objective measure that you can quantify with O() notation. Clarity is subjective, less critical and you can’t measure it objectively.
It's time to quit tech and go back to school. It's not too late to be a doctor or lawyer.
Sorry to hear that. Can you share what was interview level(medium or hard) ?? Was questions from leetcode ??
All the questions were medium to hard. No leetcode.
What kind of bug? If it is something trivial like forgetting to handle an edge case, but otherwise your solution will solve the main problem, then the interviewer score you slightly lesser than the best score. But if it is a glaring mistake that will render entire solution useless, then your score will be low. That said, if you score really good on other interviews, then the recruiter may choose to move forward with the hiring packet. Speak with your recruiter. Sometimes they may be able to arrange for a second round of remote coding interviews if they think there is potential.
I guess I got low score in that interview. That bug was one of that glaring one as you defined. My recruiter said it’s mixed/borderline feedback. So he is looking to match a team before the HC
If your resume is strong, then this may still work out, if you can get good team match. But with a mixed/borderline score, the HC will most likely reject it. Can you ask if your recruiter can arrange for two more remote coding interviews to balance the current score. This can be done.
Instant no hire.
This. Say bye to all your dreams.
Sux :(