[flagged]
Google rejected me and now I'm building a search engine
31–40 of 151 posts
Re: Google rejected me and now I'm building a search engine
#32> He continued to ask more questions about numbers of bits. I couldn’t answer any of them without a lot of help. He didn’t ask me about my PhD work building a new theory of natural language semantics. This strikes me as fairly petty “I didn’t answer wrong, you asked me the wrong questions!”. Honestly it’s the recruiting process working as intended - folks with this type of attitude don’t make good team members in my…
Well we got Mono and eventually open source .NET from that, so it can work sometimes.
Re: Google rejected me and now I'm building a search engine
#33I'm sure the post's author doesn't need interview advice anymore but in case there are any prospective interview candidates out there, completely freezing during an interview is a super negative signal. Even if you need to manually multiply out 2's on a whiteboard it would be more productive than saying "I don't know". In my experience the only reason you should say "I don't know" is if you're going to follow it with…
I don't know is the correct answer. I would have brought out "get me your boss" them followed by "your recruiter is an (r-word)"
Re: Google rejected me and now I'm building a search engine
#34I'm sure the post's author doesn't need interview advice anymore but in case there are any prospective interview candidates out there, completely freezing during an interview is a super negative signal. Even if you need to manually multiply out 2's on a whiteboard it would be more productive than saying "I don't know". In my experience the only reason you should say "I don't know" is if you're going to follow it with…
> completely freezing during an interview is a super negative signal.
I am sure you also go to your employers and tell them that asking super unnatural questions in a super unnatural pressure environment is also a super negative signal.
You do this right? Right?
Re: Google rejected me and now I'm building a search engine
#35I'm sure the post's author doesn't need interview advice anymore but in case there are any prospective interview candidates out there, completely freezing during an interview is a super negative signal. Even if you need to manually multiply out 2's on a whiteboard it would be more productive than saying "I don't know". In my experience the only reason you should say "I don't know" is if you're going to follow it with…
That’s pretty dumb. I want to work with people who say “I don’t know.” Edit: to clarify, your advice is good, what you said isn’t dumb. That criteria is dumb, in my opinion. I don’t want my colleagues to spend a bunch of my time guessing on an answer I could easily lookup or find on a calculator.
In the context of the interview, the "I don't know" is said in a situation where there is no coworker or resource to fall back on. These kinds of questions happen all the time, and the business will generally not accept "I didn't know the answer so I abandoned the whole project - sorry". If you don't know the answer, you work to find it, or you try to work around it.
Re: Google rejected me and now I'm building a search engine
#36Good luck competing with the Alphabet monopoly. See Peter Thiel books on the monopoly.
Disruption is the way for David to defeat Goliath. See automobile startup taking on horse industry, or electricity taking on candles.
Re: Google rejected me and now I'm building a search engine
#37[deleted]
Re: Google rejected me and now I'm building a search engine
#38I'm sure the post's author doesn't need interview advice anymore but in case there are any prospective interview candidates out there, completely freezing during an interview is a super negative signal. Even if you need to manually multiply out 2's on a whiteboard it would be more productive than saying "I don't know". In my experience the only reason you should say "I don't know" is if you're going to follow it with…
> Sounds like the interviewer definitely came on strong …
Possibly, but I’m sure these aren’t exact quotes after 15 years and I expect they reflect how the author remembers feeling a lot more than the actual conversation.
Re: Google rejected me and now I'm building a search engine
#39It wasn't google, but last year I had the worst interview experience of my life when I was berated for not being able to remember if a System.Tick was 10nanoseconds or 100nanoseconds. I remarked that in the circumstances I'd need to know, that I'd google it and check the documentation to make sure I got it right. The interviewer (who I later found out was the founder/CEO) absolutely laid into me for that answer, sayi…
Damn, if the founder/CEO was this obnoxious in the interview, can you imagine what it would be like to actually work there?
The minute that he showed aggression or anger, I 100% would have just walked out. Life is too short for that nonsense.
Re: Google rejected me and now I'm building a search engine
#40I'm sure the post's author doesn't need interview advice anymore but in case there are any prospective interview candidates out there, completely freezing during an interview is a super negative signal. Even if you need to manually multiply out 2's on a whiteboard it would be more productive than saying "I don't know". In my experience the only reason you should say "I don't know" is if you're going to follow it with…
Indeed. Those interviews measure whether you can dutifully perform the dance the organization wants you to.
But if that doesn't come naturally to them, "prospective interview candidates" might also consider if that's really a problem. There remain plenty of fantastic engineering opportunities that don't involve memorizing dance steps.