I going to add and give some opinions about your. First, the post is great, because it covers many problems with contracts and companies looking for developers.
The first point you talk about, is not simple, because so many companies are looking for people who at least have an engineering degree. Obviously, today, there are so many people that know how programming and they are not for the system program.
That's one of the pints most important in all world. For example, I am from Colombia and live there, and my native language is Spanish, but some companies looking for C1 or C2 English level, which to me is a crazy thing, because, so many developers have a maximum of B2, and these must be sufficient for me.
I had been involved many times in this test, and in the end if the test was not finished at all, the company did not check the code, or the process, just said, it if is not finished, goodbye.
I will add one more, the tech lead or some developer of the team, should check the employee publication, because sometimes there are so many skills in the publication, that in the end, just need three or maybe just two, and the others, could be learning during the job.
It's super frustrating to hear that you've experienced some of more disheartening aspects of the process. The language barrier is something that I didn't consider either, and shares the sentiment that regardless of skill level, hiring managers should emphasize, and prioritize a candidates enthusiasm for learning above the perceived skill level!
You are right, but so many problems come from the initial part of the process. For example, if you read, the job vacancy is for the backend, and you can see the publication has a list of a lot of skills that are supposed do you should have like
We are looking for a backend with knowledge on:
Node
Express
Mongo and SQL
And they love to put, is an advantage to have skills like
Docker
Jenkins
CI/CD
AWS
Azure
Java
C#
And you just see the screen like, exactly, what these people are looking for?
Without a doubt. One of the the things that needs to change in the industry, is how job descriptions are written. All too often recruiters or hiring managers who don't understand the landscape write these job descriptions that are completely unrealistic.
The only suggestion I've been able to make to entry level folks who encounter these job descriptions it to just apply anyway. Even if you don't think you're qualified for the job, apply anyway.
The hope is that you get in front of someone who values your ambition and eagerness to learn and grow.
I spent most of my professional life coding in JavaScript and PHP, Go and Rust. Now I am working on a isometric 3D game engine for the Web, PHP Resonance Framework and AI low-code solutions.
They are looking for a Node developer with Mongo and they probably have other projects in C#, have them hosted on Azure, AWS etc. To me this says they are looking for someone who would be able to do their core job and maybe help with something else from the list if the need arises. Speaking from experience
For sure, and there's definitely a way to communicate that hope, especially to juniors. A lot of times the way these "nice to have" skills are presented come off as intimidating for someone searching for their first job. Tacking on these technologies to an entry level role needs to be done carefully so as to encourage folks with less experience to still apply.
Definitely just a communication and expectation adjustment that needs to be made in some cases!
I going to add and give some opinions about your. First, the post is great, because it covers many problems with contracts and companies looking for developers.
The first point you talk about, is not simple, because so many companies are looking for people who at least have an engineering degree. Obviously, today, there are so many people that know how programming and they are not for the system program.
That's one of the pints most important in all world. For example, I am from Colombia and live there, and my native language is Spanish, but some companies looking for C1 or C2 English level, which to me is a crazy thing, because, so many developers have a maximum of B2, and these must be sufficient for me.
I had been involved many times in this test, and in the end if the test was not finished at all, the company did not check the code, or the process, just said, it if is not finished, goodbye.
I will add one more, the tech lead or some developer of the team, should check the employee publication, because sometimes there are so many skills in the publication, that in the end, just need three or maybe just two, and the others, could be learning during the job.
Thanks so much for reading Pedro!
It's super frustrating to hear that you've experienced some of more disheartening aspects of the process. The language barrier is something that I didn't consider either, and shares the sentiment that regardless of skill level, hiring managers should emphasize, and prioritize a candidates enthusiasm for learning above the perceived skill level!
You are right, but so many problems come from the initial part of the process. For example, if you read, the job vacancy is for the backend, and you can see the publication has a list of a lot of skills that are supposed do you should have like
We are looking for a backend with knowledge on:
And they love to put, is an advantage to have skills like
And you just see the screen like, exactly, what these people are looking for?
Without a doubt. One of the the things that needs to change in the industry, is how job descriptions are written. All too often recruiters or hiring managers who don't understand the landscape write these job descriptions that are completely unrealistic.
The only suggestion I've been able to make to entry level folks who encounter these job descriptions it to just apply anyway. Even if you don't think you're qualified for the job, apply anyway.
The hope is that you get in front of someone who values your ambition and eagerness to learn and grow.
They are looking for a Node developer with Mongo and they probably have other projects in C#, have them hosted on Azure, AWS etc. To me this says they are looking for someone who would be able to do their core job and maybe help with something else from the list if the need arises. Speaking from experience
For sure, and there's definitely a way to communicate that hope, especially to juniors. A lot of times the way these "nice to have" skills are presented come off as intimidating for someone searching for their first job. Tacking on these technologies to an entry level role needs to be done carefully so as to encourage folks with less experience to still apply.
Definitely just a communication and expectation adjustment that needs to be made in some cases!
Probably, but the problem, is when they put this, in a junior position.