61–70 of 265 posts
Us programmers tend to be very literal-minded, but my understanding is that in some parts of the Middle East, it is common to exaggerate numbers to provide emphasis, where it’s understood that it’s not to be taken literally. So maybe they just wanted someone with “a lot” of experience in Kubernetes. (Strange idea: Maybe writing it this way even acts as a filter for literal-minded people). It probably works better in-…
Recruiters putting silly time requirements on skills is nothing new. My favorite moment of this type was at a meetup for .NET, where a recruiter came in and asked for too many years of experience, and the entire room burst out laughing. She just smiled, accepted the grief we all were giving her, and changed the job description to be accurate. I forget the exact wording she used, but I remember the gist of her respons…
I get that she was actually a nice person who simply didn't know when .NET was invented. But I do not accept that she made a harmless and easily fixed error on the job requirements because of this. Frankly, I'm not that concerned that the job requirements demanded more years of .NET experience then it was possible to have. I am more concerned about all the other requirements that were listed on that job description w…
Outside of careers requiring vocational degrees (like engineering), yes - but for any job posting simply requiring a degree (any degree) has a valuable selective effect of eliminating swathes of objectively unqualified and less-qualified candidates and thus shrinking the pool of people you'd need to call-in for an on-site interview - even though many objectively qualified but non-degree-holding candidates would be eliminated unfairly.
It's a trade-off based around how much value you assign to your recruiter's time.
Recruiters putting silly time requirements on skills is nothing new. My favorite moment of this type was at a meetup for .NET, where a recruiter came in and asked for too many years of experience, and the entire room burst out laughing. She just smiled, accepted the grief we all were giving her, and changed the job description to be accurate. I forget the exact wording she used, but I remember the gist of her respons…
I mean, that’s cool, and better than nothing. But why don’t they ask someone that is qualified to determine those kinds of things before posting the job. At least, that’s what the recruiters at my company do.
Because they don't want to. The recruiter's point stands from the other perspective too: if the technical people wanted their job requirements to be perfect, they'd spend time writing them and not hiring recruiters to do it instead.
This will pre-select suitable candidates that can spout as much gibberish and misunderstandings as their bureaucracy is obviously already used to.
Earlier quoted context omitted.
K8s was originally written in Java, and then ported over to Go.
Really? I haven’t heard that before. Citation, please.
I'd like to add that I find it scary that this basic info can't be found, neither by a cursory web search, nor on wikipedia. Makes you worry about a future generation raised in naive march-of-progress narratives wondering about how things came to be during the "dark ages" (= today) of the web
Obviously a typo, they probably meant 1-2 years, which is realistic. While this is probably not actually the case here, I see it quite often that companies have unrealistic expectations when it comes to work experience with technologies like k8s. For example it is quite common here in Berlin to expect 4+ years of k8s experience. Which is unrealistic to find taking into account that k8s initial release was 6 years ago…
Field engineer stares at table and wants it to swallow him up.
Sun rep just smiles back like nothing is wrong.
That salesman was hugely successful, btw.