This might be an unpopular opinion here, but I would change how you pitch/market yourself. First, if a candidate talks about programming languages a lot (espec

This might be an unpopular opinion here, but I would change how you pitch/market yourself. First, if a candidate talks about programming languages a lot (especially if they're talking about Lisp and Haskell), that can be a sign that they're going to be unhappy working within the confines my team's Java/C++/whatever codebase, and that they're going to complain a lot and try to rewrite things in other languages. That's not a dealbreaker, but it's not a great first impression. Second, bragging about how many languages you know also codes as "junior engineer" or "recent graduate", even though the rest of your post makes it sound like that's probably not the case. Most teams are looking for someone who has demonstrated that they are really productive in at least one language, so focus your sales pitch on that. Again, this is just a first impression issue. Finally, I probably wouldn't claim myself as "expert" on anything, unless I was a top 10 committer to the project or I was specifically trying to bill myself as a consultant on that specific technology. Seeing "expert" sets off people's BS alarm bells, and they'll evaluate everything else you say with a more skeptical eye. It can also get you in trouble in interviews. Point #7 on this blog post explains it better than I could: https://steve-yegge.blogspot.com/2007/09/ten-tips-for-slightly-less-awful-resume.html https://steve-yegge.blogspot.com/2007/09/ten-tips-for-slight... Anyway, please read this as constructive advice rather than someone on the internet trying to tear you down. I'll echo what the other comments have said - practice coding interviews, apply to the big tech companies that have a presence in your area, and don't get discouraged if you don't get an offer right away. The big companies are full of people who had to interview 2-3 times to get an offer.