"Container orchestration": 1. Kubernetes, me: uhm, ok 2. Terraform, me: WTF
My coworker and I were just laughing about that. Not sure how much I can trust this.
Also HTML/CSS as languages? Erm, okay.
Rankings of required skills in software development job listings
51–56 of 56 posts
Re: Rankings of required skills in software development job listings
#52Problem is recruiter's and co are the ones always coming up with such nonsensical lists. As a lot of commenters have mentioned, these lists are meaningless to a seasoned programmers who can adapt with changing time and tech.
Re: Rankings of required skills in software development job listings
#53Earlier quoted context omitted.
While I agree with you, just look at jobs ads. They match the list a lot more than your description of a problem solver.
They do, yes, but that's what companies think they want; it's not what they actually need. And if you present yourself the right way you can get past that and get hired anyway. (Blog post I linked to talks about that in more detail, and I talk a bit more marketing vs. skills here: https://codewithoutrules.com/2017/01/19/specialist-vs-genera... )
But how do you screen for these things without tipping off to candidates that that is what you are looking for? As soon as you explicitly mention a set of requirements, you will have candidates looking to game interview processes built around those requirements.
Re: Rankings of required skills in software development job listings
#54Earlier quoted context omitted.
But few people ask for soft skills, and no one tests for them beyond noting it if you do something wrong. "Must be an excellent communicator" - unless they notice you have a hard time talking to them in the interviewer they don't check for it. They don't ask you to write an email for something, or create a presentation, or explain some difficult technical concept to a non-technical person, etc.
true... it is hard to test or measure soft skills, but the project result depends on them almost the same as technical skills. Btw, those are communication skills. There are many others that are also important
Sure. They also are not tested for.
I'm not saying these things aren't important. Just that it's almost never included in a job description, and it's invariably eye-roll worthy the few times they are, because no one tests for them explicitly anyway.
"Time management skills", "Ability to prioritize effectively", "Able to handle stress in positive ways", "Able to self-task", etc; no one changes their interviews to actually test for these things. Well, except maybe for seeing how someone handles stress, but frankly, we've heard about companies who do that, purposely make the interview as stressful as possible just to see how someone handles it, and we hate the very idea of it.
Re: Rankings of required skills in software development job listings
#55koa is there but no Express. Thats strange
Re: Rankings of required skills in software development job listings
#56Earlier quoted context omitted.
They do, yes, but that's what companies think they want; it's not what they actually need. And if you present yourself the right way you can get past that and get hired anyway. (Blog post I linked to talks about that in more detail, and I talk a bit more marketing vs. skills here: https://codewithoutrules.com/2017/01/19/specialist-vs-genera... )
But how do you screen for these things without tipping off to candidates that that is what you are looking for? As soon as you explicitly mention a set of requirements, you will have candidates looking to game interview processes built around those requirements.
If I'm trying to hire people, why wouldn't I want to "tip people off" to what I want? I'm supposed to lie and then trick people into telling me what they're really capable of? That seems ineffective.
Interviewing people about their experience is a traditional way to verify things. E.g. If I'm looking for someone who can solve hard problems I can ask for examples. If they're beginning programmer who just got handed tasks like "code this function"... they will have no good examples.
I can also explain a problem I'm working on and see how the candidate approaches it.
But writing job posting that hides the fact I need someone who can solve hard problems seems silly.