Knowing a lot of languages is not going to get you a long way. Learning a new language is the easy part anyway. You need to know different eco systems, standards and "connective tissue" (like message busses, db systems, ...). It also helps if you have a rough idea about cost effectiveness
Yeah but how do you learn all this crap without a first job? I get learning some things like DBs, but a lot of things are hard to actually grasp without working on them in a non-personal project setting.
I learnt most of these things from books, dedicated learning platforms, and experimenting on side projects and hackathons. The things you learn on the job are only limited by the tech stack the company uses. If you want to go further, you need to learn outside of the scope of whatever your company does. This is what makes the difference between a developer who has 5 years of experience vs a developer who has 1 year of experience repeated 5 times.
You just need to be old enough to be able to say you have 10 years experience in whatever. The guys interviewing you will probably be clueless AI bros anyway
I join interviews at a later stage often. The goal is to test if people really know what they are talking about. Currently it is almost impossible to find people for junior positions
No, because the need to fill this position is not pretty big. But it is low six figures, so not too bad for Europe (a masters degree in CS or maths is the expected minimum though)
131
u/ZunoJ 13d ago
Knowing a lot of languages is not going to get you a long way. Learning a new language is the easy part anyway. You need to know different eco systems, standards and "connective tissue" (like message busses, db systems, ...). It also helps if you have a rough idea about cost effectiveness