Reddit mentions of 12x9 DS DE Lapboard w/Mkr

I went through the Google interview process not too long ago. Here's my recommendations:

• Don't focus all of your effort on one concept. You will have at least four different types of problems and there is no guarantee that DP will apply. While this is an anecdotal n=1 observation, I did not have any DP problems. You should still look into DP so that you may better understand where to apply it and the basics of applying it, but don't neglect other areas (graphs for example).
  
• Grab cracking the coding interview and practice on a white board. I used a small travel whiteboard that you can get on amazon for ~$6.00. (Though, based on the reviews, I also grabbed some better markers.)
  
• Practice easy questions to warm up, then give yourself 30-40 minutes to solve the more challenging questions.
  
• Don't focus on memorizing the exact implementation of different algorithms. Know their basic flow and different places to optimize, but more importantly know where to apply them and what their complexity is.
  
• Remember to talk through the problem before solving it. Your interviewer will often give you some indication of whether or not it's the solution they want to see. When actually writing the code, don't feel obligated to explain every line as you're writing it. If you feel like you're making a good decision, explain what it is and why in a sentence or two, but otherwise focus on getting your thoughts on the board. You should explain your solution at some point, but unless they ask questions about it, don't feel obligated to talk while you write.
  
• Don't try to solve every part of the problem at once. If you hit something you're not sure how to solve, call a function that does not yet exist and tell them you'll come back to its implementation.
  
• You mentioned being able to solve things in 23 minutes. I don't think that really applies. Some interviewers will give you one hard problem which may be optimized several ways. They will expect you to implement a solution and spend the rest of the time optimizing it. Other interviewers will give you perhaps 4 problems, but all of them are inter-related and earlier solutions to problems are used as components to later problems. You may also be given one or two small warm up problems before a larger problem. However, it is unlikely that you will be given two very different and complex problems and have 23 minutes to complete each one. Furthermore, completing every problem isn't a requirement. Demonstrating good problem solving skills is. Don't focus on a specific amount of time, focus on the problem solving process. This is also true because it will take you less time to solve the problems in the interview because of guidance from your interviewer.