When you don&#x27;t pass technical interviews, you make a resolve to practice more and pass them.<p>[I run <a href="http:&#x2F;&#x2F;InterviewKickstart.com" rel="nofollow">http:&#x2F;&#x2F;InterviewKickstart.com</a> for a living]<p>Following are some very common mistakes people make when preparing for technical interviews.<p>1. They code, but they don&#x27;t invite feedback on their code. Nor do they compare their code with other people&#x27;s code. So they solve problems, but they never know if their solution was sufficient. They don&#x27;t get better, despite solving problems.<p>Avoid this mistake: When you prep on leetcode.com or some such, read other people&#x27;s solutions line by line, understand and compare. Yes, that takes time.<p>2. They don&#x27;t do mock interviews with practicing engineers<p>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&#x27;t. You could also practice with fellow learners (interview each other), which will help lower the stress in actual interviews (though won&#x27;t be as useful as doing it with a practicing engineer).<p>3. They practice very few problems<p>Avoid this mistake: If you&#x27;re coming from a top-20 4-year CS program, or you have an IQ of 130+, you won&#x27;t need a lot of practice. But for everyone else, don&#x27;t stop until you&#x27;ve practiced at least about 150 problems. Anything less won&#x27;t help and worse, might give you false confidence.<p>And when you&#x27;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&#x27;ll be surprised how many people will let you do it.<p>HTH.