Regarding all those job specs listing a million different technologies - most job specs list a lot, very few would actually expect you to know them all. Especially for entry-level jobs.
Speaking from experience as someone who hires developers, if you've got good knowledge of a couple, or even one, of the relevant technologies that's great. I can't speak for everyone, but personally I'm more interested in whether you are keen/able to learn more technolgies if needed, and have a solid understanding of language-agnostic principles like OO, design patterns, data structures, etc that are relevant to the role.
By all means learn SQL, that's no bad thing. But it's very easy to get bogged down learning different things and waiting for the perfect job spec to appear - trust me, it won't. Get a CV together with a cover letter or personal statement that outlines the points you've made above (you've applied machine learning algorithms, got experience in Python, willing to learn other technologies), and get applying :)
I think I've managed to find a good balance between working, learning new things, and applying to jobs. My resume is written in such a way that my skills are mostly represented through the projects I've done, via easily digestible bullet-points. I don't yet know if it's for better or for worse, but I've always found random lists of skills and languages to be somewhat clumsy sans context.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good first post :)
Regarding all those job specs listing a million different technologies - most job specs list a lot, very few would actually expect you to know them all. Especially for entry-level jobs.
Speaking from experience as someone who hires developers, if you've got good knowledge of a couple, or even one, of the relevant technologies that's great. I can't speak for everyone, but personally I'm more interested in whether you are keen/able to learn more technolgies if needed, and have a solid understanding of language-agnostic principles like OO, design patterns, data structures, etc that are relevant to the role.
By all means learn SQL, that's no bad thing. But it's very easy to get bogged down learning different things and waiting for the perfect job spec to appear - trust me, it won't. Get a CV together with a cover letter or personal statement that outlines the points you've made above (you've applied machine learning algorithms, got experience in Python, willing to learn other technologies), and get applying :)
Thank you for the compliment and the response!
I think I've managed to find a good balance between working, learning new things, and applying to jobs. My resume is written in such a way that my skills are mostly represented through the projects I've done, via easily digestible bullet-points. I don't yet know if it's for better or for worse, but I've always found random lists of skills and languages to be somewhat clumsy sans context.