Your github profile (if you have lots of good personal projects that are well documented) can be very valuable at showing how you work to a potential employer.

Your github profile (if you have lots of good personal projects that are well documented) can be very valuable at showing how you work to a potential employer. Studying the OWASP top 10 will definitely help you understand the most common security problems (mistakes?) that developers make, and some guidance on how to avoid them. I like Cloudflare's summary: https://www.cloudflare.com/learning/security/threats/owasp-top-10/ https://www.cloudflare.com/learning/security/threats/owasp-t... You'll probably be pleasantly surprised that gaps in your knowledge will start to become evident. You'll notice a pattern in job postings that talk about tech you don't know about -- that'll be a good clue. You'll also know about related tech that sounds interesting to you -- and you'll probably naturally just learn about it. Oh -- and as for not knowing if you know enough to get hired: Just start going on interviews. The software interview is an art unto itself (and you might want to check out several excellent books at that already exist on the subject). Just being good at tech won't get you a job -- you need to be good at communicating. Going on interviews with companies (and approaching them as experiments) will let you know what you need to get better at. If you get an offer, you'll know you're getting good at it. :-) (Hint: You don't ever have to accept an offer if you don't want to)