You say that you get suck on algorithms and data structures, and that you are worried that your lack of a formal education may hinder your interview-ability. W

You say that you get suck on algorithms and data structures, and that you are worried that your lack of a formal education may hinder your interview-ability. Well, fret not. Little of what is taught in college has any relation to the types of questions asked in technical interviews. And although a lack of degree may influence an interview in more subtle ways, most interviewers are far more interested in your technical ability. So, scratch that nagging fear off your list, and proceed with the following steps. Step 1: Apply for lots of interviews. Yes, you will fail many of them, but it will also up the stakes and encourage you to take steps to improve. It's easy to want to learn. Having deadlines and commitments makes it harder to push things off to another day. Step 2: Keep track of every question that is asked in an interview. Make a spreadsheet of places you've interviewed at, and the questions they've asked. Begin to reflect on your interview, and jot down any terms you weren't familiar with. Step 3: Learn what those terms mean. Answer those questions you couldn't answer before. And most importantly: Understand what the interviewer was looking for in asking that question. Understanding of OO? Algorithms? Systems design? An understanding of the technology stack? Categorizing the questions in this way makes it far more manageable to digest. These are the categories you want to study. Wikipedia, Stack Overflow, Books. Go. Step 4: Repeat step 1. (You have now caught up to the average university graduate)