Harder programming questions do a worse job of predicting outcomes
Google recruiters call me a lot. I think I&#x27;d do a good if not stellar job working there. I&#x27;ve passed multiple FAANG interviews and been very successful as a senior developer.<p>In my email I have an &quot;interview prep packet&quot; from them that essentially tells me to brush up on algorithms and read Cracking the Coding Interview to prepare for their interview process.<p>I&#x27;m fairly happy in my job. If they offered more money or a really interesting project I&#x27;d consider working for them. But I&#x27;m pretty lazy about redo-ing college algorithms class during my free time at home to go work there, so I probably won&#x27;t.<p>There&#x27;s an opportunity cost with interviews like this where an M.S. and long career of getting shit done counts for very little and memorization of undergrad level topics that you can look up in two minutes in Knuth if you have a problem that requires it can make or break an interview.<p>I&#x27;ve made a career fixing a ton of horribly shitty, inefficient code that&#x27;s been produced exclusively by people who pass these interviews.