I don't know you, but given your words I can't really tell if your problem is your programming skills or algorithms. If I was hiring I'd look for these things

I don't know you, but given your words I can't really tell if your problem is your programming skills or algorithms. If I was hiring I'd look for these things 1. The person needs to be reliable, I need to be able to depend on them, they need to be able (within reason) to think for themselves and solve problems in a good, none-convoluted, well documented and future-proof way. 2. The person needs to be able to learn for themselves and master a topic. That doesn't mean this is a school test, sometimes the solution is: "Boss we would be stupid if we built this ourselves, there is this great open source project I found" 3. The person needs to be able to communicate clearly and honestly. Notice how most of these aren't related to the programming at all? They are more about how you conduct yourself and what people can see in you. My advice to you would be to work on one or two "bigger" projects to which you can point when you are sitting across in the interview. If you are clever and pursuing different topics is your driver, choose something where you can apply all of those skills. Maybe you find something that would involve Blender and Spring? Blender has a python API so you can remote control many things. The most important part is however that you get those projects to a good state. The reason such projects are a good thing is because it would show me that you are able to organize yourself, you can get things done, you manage to combine your skills etc. and above all: Solving problems motivates you. And even if you had those projects and you sit across and talk to me like all of that bores you I am not sure I'd give you a chance.