3 ms·
Many of the type of IT people Tata et al are hiring are in roles in which native workers either (a) don't want to do or (b) aren't trained to do. Specifically
by threeseed 10y ago
Many of the type of IT people Tata et al are hiring are in roles in which native workers either (a) don't want to do or (b) aren't trained to do.
Specifically BAU type roles where there is no creativity, diversity, career prospects e.g. Oracle/Teradata DBAs, Legacy J2EE Systems, Basic System Administration etc.
And sure they could hire younger, junior developers but actually they aren't suited because companies don't want fresh ideas or innovation or a new technology. They just want someone to keep the lights on. I've hired dozens of people in these roles and it's hard to argue against Tata etc. From the companies perspective it works well.
- pyrophane 10y agoYou can get people to literally haul garbage for a living if you give them a good salary, health care, and decent job security. I don't buy the whole "native workers don't want to do this" argument. Employers don't want to pay enough to entice native workers.
- ashwinaj 10y agohttp://latinosreadytovote.com/wages-rise-california-farms-americans-still-dont-want-job/ http://latinosreadytovote.com/wages-rise-california-farms-am... > Some farmers are even giving laborers benefits normally reserved for white-collar professionals, like 401(k) plans, health insurance, subsidized housing and profit-sharing bonuses. Full-timers at Silverado Farming, for example, get most of those sweeteners, plus 10 paid vacation days, eight paid holidays, and can earn their hourly rate to take English classe Care to explain?
- pyrophane 10y agoI read the article you posted. The argument that "Americans don't want these jobs even when you up the wage and add benefits" is only supported by a couple of anecdotes from growers who have an interest in maintaining the supply of foreign laborers, and I don't think that is sufficient to make the point. I would maintain that there is a wage at which a sufficient number of Americans would be willing to do farm labor. Whether that would raise the price of crops beyond what consumers are willing to pay for them is another question entirely. As an aside, I'm not opposed to foreign workers in the US, but I do find the argument that they are needed because "there aren't any Americans who want to do this" to be a bit disingenuous.
- ashwinaj 10y ago> and I don't think that is sufficient to make the point. This maybe a small sample size but none the less shows that there are jobs that Americans won't do. This is despite the decent pay and benefits. > from growers who have an interest in maintaining the supply of foreign laborers, and I don't think that is sufficient to make the point. Sure, any one who owns a business would want to lower costs. If there is no option, that would have to raise salaries. And yet, no Americans are taking these jobs. So your off the cuff comment "You can get people to literally haul garbage for a living if you give them a good salary, health care, and decent job security." falls flat on it's face.
- stevenwoo 10y agoExcept that's not what the H1-B program is for - exceptional skills. This is the most famous recent example https://www.pri.org/stories/2015-06-05/senator-calls-probe-after-disney-fires-american-workers-uses-h-1b-visas-fly https://www.pri.org/stories/2015-06-05/senator-calls-probe-a... It seems like you are arguing that if someone in America is working a non creative/somewhat static job they should be happy to be replaced with a H1-B employee.
- vizeroth 10y agoYou hire junior developers for those roles because you can pay them less and find the people who work well in your environment, get rid of the ones who don't, and leave the rest to decide for themselves whether they can find something they like about the entry-level work (and somehow continue to live on that wage) or go somewhere else once they have more experience on their resume. I've been through so many long cycles of trying to find someone to fill a developer role where it would have been so much simpler if we could have started with someone who understood the environment and work load up front, rather than finding people who went back to the job search 3 or 4 weeks into it because it wasn't working out (but they were usually smart enough to get another job offer before they quit). I would almost prefer to take someone with little or no programming experience who works in my office with a desire to learn and a strong work ethic and give them the programming job, hire 2 or 3 more people to answer phones on a help desk, and save everyone the pain of reading resumes and interviewing for a developer who ends up negotiating a higher salary, socializing at the help desk from 8 to noon, managing their social media empire from 1 to 5, and either quitting or (somehow) getting fired after a few months so we can start all over again. Yes, I have to train someone, perhaps even more than I would have to train someone who comes on board with some applicable experience, but the alphabet soup that goes out on my job postings isn't easy to replicate on resumes, and doesn't guarantee that I won't need to review the material with them anyway.