In my opinion, Software development is a lot more than just being able to write code or make an app. It's about being able to write code that is readable and ma

In my opinion, Software development is a lot more than just being able to write code or make an app. It's about being able to write code that is readable and maintainable. It's about thinking a few steps ahead before you even lay down the code, and being able to work in a team that is going to help you accomplish your goals. That company that turned you down probably did so because you showed them that your only capable of working on your own stuff that might have a lot of 'non-standard' idiosyncrasies in its architecture. I'd try to take a look at info on common patterns (a la Gang of Four), Architectures (MVP, MVC, MVVM, Flux, etc), and some of the most common (and yes, somewhat trite) interview puzzles, if only so that you can speak to your interviewers in a common language. Nobody wants to hire someone who they can't communicate with using a standard professional language. Patterns, architectures, and puzzles are just a part of that language.