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. It is paradox that companies want to use the latest technologies and require years of work experience at the same time.
IBM looking for 12 years’ experience in Kubernetes administration
41–50 of 265 posts
Re: IBM looking for 12 years’ experience in Kubernetes administration
#42It's like asking for ten years' experience with Swift. The job descriptions (especially in hidebound companies like Big Blue) tend to have mandated experience levels. HR folks aren't engineers, so they should not be expected to know. However, this should be highly embarrassing to the hiring manager, who I'm sure, was handed the ad text for approval, and probably rubberstamped it without thinking.
> HR folks aren't engineers, so they should not be expected to know.
If you job description is to find someone to fill a position you should know what that position is. This is middle management "I don't need to know exactly what I'm managing" levels of cow manure.
Re: IBM looking for 12 years’ experience in Kubernetes administration
#43Recruiters 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…
The software jobs requirements (where I work) are written by team leads/software engineers, pretty much the same people that would be doing the interviews.
Re: IBM looking for 12 years’ experience in Kubernetes administration
#44Meh. It’s probably just 2 years mistyped. Shouldn’t be on front page HN.
This. To all the people who call this job post "silly", imagine how silly it is if a simple mistake of missing "-" like in "1-2 years" is overblown out of proportions and half the internet is discussing it. I've stumbled upon this "news" a few times during past 2 days. What a waste...
Re: IBM looking for 12 years’ experience in Kubernetes administration
#45I just hope companies get rid of the "hr recruitment" team. These people are utterly clueless folks, who hardly know anything about technology and worse these people call the shots when the time comes to settle on pay package.
Re: IBM looking for 12 years’ experience in Kubernetes administration
#46It's like asking for ten years' experience with Swift. The job descriptions (especially in hidebound companies like Big Blue) tend to have mandated experience levels. HR folks aren't engineers, so they should not be expected to know. However, this should be highly embarrassing to the hiring manager, who I'm sure, was handed the ad text for approval, and probably rubberstamped it without thinking.
>HR folks aren't engineers, so they should not be expected to know.
Yeah, so make the engineers produce the requirements for the particular jobs. HR should not be in the business of defining technical requirements for jobs.
Re: IBM looking for 12 years’ experience in Kubernetes administration
#47Earlier quoted context omitted.
That’s the right attitude to have. I would hire her as my recruiter.
Maybe she could have a hiring manager proof what they’re looking for so it actually makes sense? This just means the first introduction to your company by a potential hire showcases a broken process.
At most jobs I've had the recruiters pretty much always work with the hiring manager on editing the job requirements and all that. Sure it could still just be a mistake, or it could mean the hiring manager wasn't in the loop.
Re: IBM looking for 12 years’ experience in Kubernetes administration
#48It's like asking for ten years' experience with Swift. The job descriptions (especially in hidebound companies like Big Blue) tend to have mandated experience levels. HR folks aren't engineers, so they should not be expected to know. However, this should be highly embarrassing to the hiring manager, who I'm sure, was handed the ad text for approval, and probably rubberstamped it without thinking.
> It's like asking for ten years' experience with Swift.
Translated: we want to hire Chris Lattner (who started developing Swift in July 2010, so has exactly ten years of experience with Swift).
Re: IBM looking for 12 years’ experience in Kubernetes administration
#49It's like asking for ten years' experience with Swift. The job descriptions (especially in hidebound companies like Big Blue) tend to have mandated experience levels. HR folks aren't engineers, so they should not be expected to know. However, this should be highly embarrassing to the hiring manager, who I'm sure, was handed the ad text for approval, and probably rubberstamped it without thinking.
>HR folks aren't engineers, so they should not be expected to know. Yeah, so make the engineers produce the requirements for the particular jobs. HR should not be in the business of defining technical requirements for jobs.
I worked for a hidebound company like that. I would submit a request, which would then get modified by HR.
That was why it was so important for me to review the job descriptions. It was often an iterative process.
Re: IBM looking for 12 years’ experience in Kubernetes administration
#50Recruiters 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.
Asking or not asking a dev doesn't really change anything. The problem that I'd worry about is it signals (rather clearly) that the hiring manager isn't in charge of setting the requirements for the position. Who knows what a hiree is walking in to.