When I was an undergrad, my team won the Facebook Hackathon at our university in 2011, so they gave each of us job interviews.  None of us got an offer, but the irony is that one of my other team members went on to work at Instagram, which was then acquired by Facebook less than a year later.  I&#x27;m pretty sure that was about the most expensive way FB could have hired him.<p>During my interview, the interviewer asked me where I was getting my CS degree from, and I replied that I wasn&#x27;t getting a CS degree — my major was chemical engineering.  He was silent for a few seconds, so I&#x27;m pretty sure that wasn&#x27;t the answer he was expecting.<p>What I remember about the interview process is that I was asked to implement some kind of odd search&#x2F;sort algorithm.  I remember thinking &quot;why would I have this memorized off the top of my head when I could easily Google the best algorithm suited for the task?&quot;<p>In high school, I don&#x27;t think there was ever a chemistry or math exam that I didn&#x27;t get a perfect score on, but I would also take much longer to finish than the other students.  I frequently ran over the allotted class time and worked well into the lunch period (luckily, I had nice teachers who allowed me to do this).  In college, I remember perplexing the physics professor, because I got 70s-80s on the quizzes throughout the semester, then I got a 113 on the final exam.  I told him the only difference was that I was given 20 minutes for the quizzes, whereas I had 3 hours to complete the final exam.  The extra time made all the difference.<p>So I wonder if a lot of companies are missing out when they look for 1) people who have a lot of simplistic CS algorithms memorized and 2) people who can work quickly on the spot.  I may not be able to write a FizzBubbleRedBlackSort algorithm on a whiteboard in ten minutes, but give me a week and I&#x27;ll have you a parallelized implementation of quantum monte carlo that runs on a hundred thousand cores.