Great article. Wanted to comment on this "The first project I did on my own was jeansbargains ... I built it and then realized that I did not want to spend the time looking for deals to put on it" This seems to run as a common theme in many engineer friends (including myself, several times.) When approached with a sales-like problem, such as a opening a store or a SaaS product, or even starting a social network, we d…
> does it have a name? The division of labour. Different people have different strengths and preferences. Gains are made from trading on those differences.
Overcoming Impostor Syndrome
21–24 of 24 posts
Re: Overcoming Impostor Syndrome
#22Re: Overcoming Impostor Syndrome
#23>In college, I never took a course on Compilers or Programming Languages... >I got the job through a summer internship, which allowed me to bypass the rigorous 8-interviews-in-a-day hiring process. And I lucked out... completely escaped having to code over the phone. I'm not trying to troll. However, I honestly do consider you landing a Google engineering internship/job with those school background (and zero coding e…
In my experience, Google's interview process is very random. You never know when you're going to get some jackass who wants to ask you some aha-problem question. When I was at Google we had some interns who were forced to reinterview, and some of the best were knocked out by a question about betting on the color of shells chosen in complete darkness or some such nonsense.
Side note -- I had impostor syndrome at Google because I had only gotten through the interviews, and never done any CS coursework.
Re: Overcoming Impostor Syndrome
#24Earlier quoted context omitted.
This of course brings to mind Yegge's interview loop theory: http://steve-yegge.blogspot.com/2008/03/get-that-job-at-goog...
Argh, and I was contemplating applying for a product manager role at google. After reading this i wont be applying anytime soon -it's been over 10 years since I studied data structures and algorithms.