Live data from Hacker News

Google rejected me and now I'm building a search engine

daoudclarke.net

1–10 of 151 posts

Re: Google rejected me and now I'm building a search engine

#5
I'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 "but if I had to guess" or similar. Sounds like the interviewer definitely came on strong but being able to ace the psychological part of an interview is often as important or more important than the actual solution.

Re: Google rejected me and now I'm building a search engine

#6
This user already submitted this same article yesterday and it was flagged:

https://news.ycombinator.com/item?id=40850725

Rather than this clickbaity "Google rejected me" story about something that happened 15 years ago, here's a link to the actual project:

https://github.com/mwmbl/mwmbl

Re: Google rejected me and now I'm building a search engine

#7
post #3

Good luck competing with the Alphabet monopoly. See Peter Thiel books on the monopoly.

Are you trying to say you should not compete with a monopoly? That's a completely asinine take.

You should try and avoid competition but taking on a failing monopoly like Google is a great thing to try and strive for.

Re: Google rejected me and now I'm building a search engine

#8
post #5

I'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.

Re: Google rejected me and now I'm building a search engine

#9
It 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, saying if he wanted people to google that a "thousand Indians graduating in computer science every day" could google it.

I tried to argue that I was looking to be employed for my problem solving skills and experience rather than rote knowledge, but he was really angry. He literally said to be verbatim, "Let me give you some interview advice, NEVER tell an interviewer you'd google something". He also made a mildly off-colour remark that if he "wanted someone just to google, [he] could hire one of thousands of fresh graduates coming out of India".

It was an experience so bad that it inspired me to create a glassdoor account just to leave negative feedback, something I've never done before or since. The recruiter was absolutely pissed, and still doesn't provide me leads, which is kind of annoying since he's the most active C#/.Net recruiter in my area.

But my point is that some people have absoultely atrocious interview manners. Interviews are a two-way street and I discovered that there was absoultely no way I'd want to work with them. (Even when I just thought they were a team lead rather than the CEO it was enough to put me off.)

Re: Google rejected me and now I'm building a search engine

#10
post #5

I'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…

Asking questions irrelevant to the position is also a pretty good red flag that you don't want to work there.
Post reply on HN