> Interviews ask abstract and theoretical computer sciency type questions and in real life I would usually google my way to a solution on those types of questions, so I do very poorly on the spot.
Fwiw some of us ask abstract questions with the sole purpose of breaking you out of coding mode and into thinking mode. I wanna see how you break down a problem you haven’t encountered before. Not how you google a solution to a known problem. If you’re talkinng to me, I already trust that you can write code and google solutions.
One of my fav questions to ask is “Design a system to protect a skyscraper from flooding in a scifi Manhattan of 2140”
Right. I'm not good at those kinds of questions. I can code quickly but rigorous thought takes time for me. I need to ponder a design question for a while or work on two or three prototypes before I feel like I know what to do.
FWIW I've also seen the opposite. A developer who was a very good thinker and talker, but got stuck for two weeks on an issue with a Google API. It took me five minutes to figure out what was wrong. Not cause I'm smart, actually the opposite, I have to break problems down to things I can understand and it's that process which lends itself well to fixing bugs.
But I'm sure he would've run circles around me when designing an API or architecting out multiple systems.
Fwiw some of us ask abstract questions with the sole purpose of breaking you out of coding mode and into thinking mode. I wanna see how you break down a problem you haven’t encountered before. Not how you google a solution to a known problem. If you’re talkinng to me, I already trust that you can write code and google solutions.
One of my fav questions to ask is “Design a system to protect a skyscraper from flooding in a scifi Manhattan of 2140”