I wouldn't approach it with this attitude. Preparation is good, but really the most important thing to do is be able to look at a problem and identify what appr

I wouldn't approach it with this attitude. Preparation is good, but really the most important thing to do is be able to look at a problem and identify what approach is correct. Coding rounds are fairly predictable and are a great equalizer, which is why companies use them. Focus on being able to identify what data structure and which algorithm to use and you're already halfway there! > To get a perspective on this: think from the perspective of a FAANG interviewer. Say, they are 3 years out of college and have been asked to take an interview. Do you really think they'll be cooking up fresh new interview questions or just going on leetcode and picking their fav question so that they can get done with the interview and get back to their sprint deadline? This is a bit absurd! Interviewers are trained and constantly calibrated so that all candidates have as much of a fair chance as possible. Questions come from a common bank, engineers are not expected to come up with their own. Anyways to the original question - try studying something like leetcodes explore section and get familiar with each concept one at a time. Then read problems and just try to identify the approach, then read the solution. If you still struggle with this type of interview, then just focus on companies which have take home projects. There are tons of great companies out there outside of big tech!