I thought these sort of requirements were so companies could hire H1B candidates? The basic idea is you create an impossible to fill position and then have your chosen H1B candidate lie.
Care to elaborate this a bit, for us outside of USA? I'm genuinely interested - what are advantages for company to hire H1B candidate(s)?
You cannot have more than 10 years of experience in Rails
81–88 of 88 posts
Re: You cannot have more than 10 years of experience in Rails
#82Since there was no indication on the job ad that the position actually required 10 years of Rails experience, I'm going out on a limb and say that they just didn't want you/the author. From this brief article it seems that the author has a inflated ego, I mean I could never mess with an interviewer like that just because I know that people make mistakes. I think that this particular company didn't do anything wrong a…
"This hiring process is messed up." "This guy has an inflated ego. We shouldn't listen to him. DISQUALIFY!"
Pretty much anytime somebody posts a story about bad hiring practices this is the first response I see. Why? What does it add to the discussion but an unhealthy dose of ad hominem?
Re: You cannot have more than 10 years of experience in Rails
#83Earlier quoted context omitted.
You are criticizing the GC process, not the h1b process. The h1b is to address a temporary worker shortage, not put people on a long term immigration track due to high skill. It would be great if we had such a track (beyond people of extreme talent), but we don't.
What temporary worker shortage? If there was one, there would be rising salaries, as we see in the North Dakota oil patch, but in IT wages are stagnant. I'm criticizing US immigration, in general, temporary and permanent, because the present system benefits neither the majority of Americans nor the majority if immigrants. Large employers, though, benefit disproportionately.
You may say there is no benefit for immigrants, but most of my friends in IT (as qualified as any american) make less than a lac a month (comparable to a mcjob). So that's a tough case to make.
Re: You cannot have more than 10 years of experience in Rails
#84Re: You cannot have more than 10 years of experience in Rails
#85"there was also some confusion as to Bootstrap. According to the project manager Bootstrap is also responsive. (No kidding?) I said that’s great because I use Twitter Bootstrap and that is responsive as well. (I was playing games at that point) Then I was told they where not the same? I don’t know if that was the breaking point, but it was amusing." ^ This whole thing makes 0 sense to me. I can't tell who is wrong wi…
For awhile I thought he was maybe ESL, but now I'm leaning towards legitimately a moron.
Poke around the rest of the site and stand in bewilderment at this wonder.
Re: You cannot have more than 10 years of experience in Rails
#86"there was also some confusion as to Bootstrap. According to the project manager Bootstrap is also responsive. (No kidding?) I said that’s great because I use Twitter Bootstrap and that is responsive as well. (I was playing games at that point) Then I was told they where not the same? I don’t know if that was the breaking point, but it was amusing." ^ This whole thing makes 0 sense to me. I can't tell who is wrong wi…
I'm surprised no one here has taken him to task for that horrible first sentence. I can only imagine the response on HN if the roles were reversed.
Re: You cannot have more than 10 years of experience in Rails
#87Hi Chad,
We're sorry you had a bad experience with our interviewing process. Our ad specifically asks for someone that's been "programming professionally for around a decade, have a few years of full stack web experience". We're not looking for people with 10 years of Rails experience...though if Mr. Hannson is interested in a job here, we'd love to talk to him :-).
Our phone screens are not technical interviews. They look to see if you've been building things similar to what you'll work on here, as well as if you'd be a cultural fit. We specifically have non-technical folks do our phone screens to give our programmers as much time possible to actually program. Our screeners do tend to deliver very high quality candidates for initial, technical interviews.
With your specific phone screen, we found two other candidates that were better fits for us and our HR person made a mistake when she told you they had "10+ years of Rails experience". Our bad.
Good luck with your career and if you think you are a good fit for us and that our phone screen missed the mark, let me know and I'd be happy to talk to you personally.
Sincerely,
Eric Scott CEO, Dolphin Micro
Re: You cannot have more than 10 years of experience in Rails
#88Since there was no indication on the job ad that the position actually required 10 years of Rails experience, I'm going out on a limb and say that they just didn't want you/the author. From this brief article it seems that the author has a inflated ego, I mean I could never mess with an interviewer like that just because I know that people make mistakes. I think that this particular company didn't do anything wrong a…
Why is this always the first comment on posts like these? "This hiring process is messed up." "This guy has an inflated ego. We shouldn't listen to him. DISQUALIFY!" Pretty much anytime somebody posts a story about bad hiring practices this is the first response I see. Why? What does it add to the discussion but an unhealthy dose of ad hominem?
Take a look at the post again and you will see the Craigslist ad that the individual responded to. You'll notice that there is no mention of requiring any amount of experience in any framework or language. The ad looks like a normal ad and wouldn't make it close to the front page of HN without the author raising a hubbub.
People make mistakes. That is a general trait of humans. It seems like the interviewer made the mistake when talking about Bootstrap. It could have been a non-technical project manager. It could have been a consulting project manager (since they appear to be a consultancy) we don't know. But then the author criticizes the company for that. Not only that, it seems that he openly mocked the interviewer about the mistake.
Then the problem compounds when the author gets an email from the company that says that they went with two other candidates that have 10+ years experience. Instead of letting it go (as the author doesn't even seem to care) he goes off trying to prove them wrong. Odds are that the company was saying that to be nice. Hearing that is a lot better than something like "Sorry, you're personality sucks and we don't want you" (I'm not saying that is what is going on but it could be an option). It is a line that is hard for the author to dispute since he admittedly doesn't have that experience. Now, keep in mind, that the company may have meant Ruby but instead put Rails. Even the author makes that mistake by calling it Rudy when it makes more sense to write Rails instead of Ruby.
I have seen articles about truly messed up hiring processes on this site, however, this is not one of them. There are only two incidents and one of them the author admits to "playing games". Not only that, but after "playing games" with the project manager the author expected professionalism and courtesy of a follow, despite not showing that to the interviewer. The way I see it is that the author wasted this company's time, then tried to profit off of it by writing a blog post that has ads on it. There is nothing wrong, from what is described in the article, with how the company acted.
"Pretty much anytime somebody posts a story about bad hiring practices this is the first response I see. Why? What does it add to the discussion but an unhealthy dose of ad hominem?"
Honestly, I haven't seen that much but I have not seen a more fitting story about "bad hiring processes" that deserve people to call BS than this one. We have only been given a small glimpse of what happened, so it could be much worse but from what is written and looking at the job posting on Craigslist that was in the post, it doesn't seem like the author has much of a case.
I would be curious to hear what you think about this though. Do you think the author is in the clear for writing something like this? Do you honestly think that the author was a victim of a "messed up hiring process"?