When you don't pass technical interviews, you make a resolve to practice more and pass them. [I run http://InterviewKickstart.com http://InterviewKickstart.com

When you don't pass technical interviews, you make a resolve to practice more and pass them. [I run http://InterviewKickstart.com http://InterviewKickstart.com for a living] Following are some very common mistakes people make when preparing for technical interviews. 1. They code, but they don't invite feedback on their code. Nor do they compare their code with other people's code. So they solve problems, but they never know if their solution was sufficient. They don't get better, despite solving problems. Avoid this mistake: When you prep on leetcode.com or some such, read other people's solutions line by line, understand and compare. Yes, that takes time. 2. They don't do mock interviews with practicing engineers Avoid this mistake: Find a friend or mentor who works at a brand name company and do a strictly graded mock interview or two (or more). That will reveal a lot of things your coding practice won't. You could also practice with fellow learners (interview each other), which will help lower the stress in actual interviews (though won't be as useful as doing it with a practicing engineer). 3. They practice very few problems Avoid this mistake: If you're coming from a top-20 4-year CS program, or you have an IQ of 130+, you won't need a lot of practice. But for everyone else, don't stop until you've practiced at least about 150 problems. Anything less won't help and worse, might give you false confidence. And when you're in the interview, try asking the interviewer if you can solve the same problem on your computer or on a piece of paper. You'll be surprised how many people will let you do it. HTH.