My personal objective is to bring outstanding service and technology to any position I can apply it to. I work fast and efficiently to get the job done right, the first time.
Im also 30 years in and I want to say again on this post, that while I was unemployed last year, I sat down, learned React and Vue (from paid services no less, I've got 15+ years of JS under my belt already) and built 2-3 projects in each. Not one company wanted to hear that I knew React/Vue unless I had a minimum 8 years of working/production experience in them. Given the age of these lib's, that would mean I had to start working a real-world job in them on day one of their release. Im not at all saying dont keep learning. I am saying even if you do continually learn, even with 30 years of production experience under your belt in other languages, dont go nuts trying to cram things in that employers wont hire you for, or even worse, that recruiters wont even talk to you about because your MSSQL and MySQL line items on your resume mean you're a backend engineer and that you have no idea how to do frontend because even though React is on your resume, the position 'frontend engineer' isnt. When i started, there was no app/website unless you built both the back and front ends, ...and also did the devops! Tech moves so fast, it lends too much credence to buzz words that cost decent engineers jobs. And yes, find a hobby, Im super guilty of this myself! Good article sir.
I am sorry to hear that. This looks like a crystal clear discrimination.
Looks like you fell into a case of an incompetent recruitment team. And I am saying because, as you already mentioned, 5-6 years before, there was no thing as a full-stack engineer, because we were all fullstack engineers. So saying you have no frontend experience is funny. Especially if you have (in disguise, but you have)
Please dont get discouraged, keep applying to serious companies that have a track record of respect and seriousness. Glassdoor.com is my friend in those cases
My personal objective is to bring outstanding service and technology to any position I can apply it to. I work fast and efficiently to get the job done right, the first time.
It is very laughable indeed and yes, I had met many incompetent recruitment teams during that period of my job search. When I did get in the door, theyd always ask me to prove my skill by writing a todo app in Vue/React, something I have/had on my git already, but they won't accept that either, it had to be written again.
There, in general, seems a massive distrust between companies and programmers that is rarely spoken about. Some coders dont know what theyre doing, but the employers punish those of us who do because of it, or prior experiences with them. Right now, Im counting blessings, working for a great company, who appreciates its devs and Im very happy to have found them.
There, in general, seems a massive distrust between companies and programmers that is rarely spoken about. Some coders dont know what theyre doing, but the employers punish those of us who do because of it, or prior experiences with them.
It is indeed something that is not mentioned often
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.
Im also 30 years in and I want to say again on this post, that while I was unemployed last year, I sat down, learned React and Vue (from paid services no less, I've got 15+ years of JS under my belt already) and built 2-3 projects in each. Not one company wanted to hear that I knew React/Vue unless I had a minimum 8 years of working/production experience in them. Given the age of these lib's, that would mean I had to start working a real-world job in them on day one of their release. Im not at all saying dont keep learning. I am saying even if you do continually learn, even with 30 years of production experience under your belt in other languages, dont go nuts trying to cram things in that employers wont hire you for, or even worse, that recruiters wont even talk to you about because your MSSQL and MySQL line items on your resume mean you're a backend engineer and that you have no idea how to do frontend because even though React is on your resume, the position 'frontend engineer' isnt. When i started, there was no app/website unless you built both the back and front ends, ...and also did the devops! Tech moves so fast, it lends too much credence to buzz words that cost decent engineers jobs. And yes, find a hobby, Im super guilty of this myself! Good article sir.
I am sorry to hear that. This looks like a crystal clear discrimination.
Looks like you fell into a case of an incompetent recruitment team. And I am saying because, as you already mentioned, 5-6 years before, there was no thing as a full-stack engineer, because we were all fullstack engineers. So saying you have no frontend experience is funny. Especially if you have (in disguise, but you have)
Please dont get discouraged, keep applying to serious companies that have a track record of respect and seriousness. Glassdoor.com is my friend in those cases
Merry Christmas :)
It is very laughable indeed and yes, I had met many incompetent recruitment teams during that period of my job search. When I did get in the door, theyd always ask me to prove my skill by writing a todo app in Vue/React, something I have/had on my git already, but they won't accept that either, it had to be written again.
There, in general, seems a massive distrust between companies and programmers that is rarely spoken about. Some coders dont know what theyre doing, but the employers punish those of us who do because of it, or prior experiences with them. Right now, Im counting blessings, working for a great company, who appreciates its devs and Im very happy to have found them.
Happy holidays to all:)
I would love to see an article about
There, in general, seems a massive distrust between companies and programmers that is rarely spoken about. Some coders dont know what theyre doing, but the employers punish those of us who do because of it, or prior experiences with them.It is indeed something that is not mentioned often