InformationWeek: The Business Value of Technology

InformationWeek: The Business Value of Technology
InformationWeek Big Data Coverage
= Member Content
Facebook Twitter Share

E-mail | Print | Permalink | LinkedIn | RSS

Microsoft Defends Hiring Foreign Workers


Microsoft says it has 34% more open engineering positions than this time last year, and can't fill them all domestically.




Microsoft Pop-Up Stores: Hands-On Look
Microsoft Pop-Up Stores: Hands-On Look
(click image for larger view and for slideshow)
Microsoft officials this week defended their call for a program that would let companies pay to import foreign programmers and other high-tech workers.

"Every year the economy is requiring another 120,000 people with a computer science degree," said Microsoft general counsel Brad Smith, in response to a question at the company's annual shareholder meeting.

"Right now, if you take all of the great, or not so great, all of the universities across the country, they're only producing 40,000 computer science graduates each year," Smith said Wednesday, in Bellevue, Wash.

Smith was responding to a shareholder who said Microsoft shouldn't be seeking to import high-tech help at a time when so many Americans are unemployed. The questioner said he knew numerous individuals in their 50s who, despite advanced computer science degrees from MIT and other prestigious schools, can't get work.

[ Which U.S. companies hire the most H-1B workers? Read Microsoft Tops H-1B Visa Employer List. ]

Smith said that, although some individuals might fall through the cracks, overall there is a shortage of tech workers in the U.S. "The answer is for any specific individual there may be some specific circumstance that explains a specific result in their life. But when we look at the numbers today, the numbers don't lie," said Smith.

Smith said Microsoft currently has more than 6,000 open jobs, up 19% from a year ago. In engineering alone, the company has 3,400 open positions, up 34% from last year. "We'd like to fill them here," said Smith, adding that it's difficult for Microsoft and other U.S. companies to find all the talent they need domestically.

Smith recently called on Congress to increase the number of high-tech visas available for foreign IT workers. He said the government should issue 20,000 STEM-specific visas each year, in addition to the 65,000 H-1B visas currently available. He also called for 20,000 new green cards for tech workers. Smith said the government should charge companies $10,000 per visa for the former, and $15,000 for the latter.

Sure to fuel the debate over whether the U.S. needs to import more high-tech workers is a report released Friday by the Partnership for A New American Economy.

The lobby group said the unemployment rate for tech workers in the U.S. is just 3.15%, compared to around 8% for all workers. "Given that the U.S. government has defined 'full employment' to be 4 percent, this suggests a skills shortage of STEM professionals with advanced degrees," the group said in the report, titled "Help Wanted."

Groups that represent U.S.-born tech workers, such as The Programmers Guild, have argued that programs like H-1B allow American companies to import cheap labor at the expense of homegrown talent.

On Friday, the House approved a bill that would make 55,000 new green cards available to foreign-born graduates of advanced U.S. STEM programs.

Upgrading isn't the easy decision that Win 7 was. We take a close look at Server 2012, changes to mobility and security, and more in the new Here Comes Windows 8 issue of InformationWeek. Also in this issue: Why you should have the difficult conversations about the value of OS and PC upgrades before discussing Windows 8. (Free registration required.)

Federal agencies must eliminate 800 data centers over the next five years. Find how they plan to do it in the new all-digital issue of InformationWeek Government. Download it now (registration required).




InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS


Advertisement


InformationWeek Reports

report Cloud Implementer's Checklist
Once your agency has completed the business case for a private cloud, how do you actually move ahead with your data center transformation? Our report provides a practical set of steps to get you there, including a "to do" list that will be helpful to anyone on your IT team who's involved in the project. By the time you're done, your data center should be home to a more flexible, on-demand IT services.

report Cloud Compliance in Government
Compute clouds created for government data centers must adhere to a range of specifications designed to support data and system security, privacy, and governance. FISMA, HIPAA, SOX, and SAS 70 are just some of the requirements that have to be taken into account as federal IT pros deploy a shared-services cloud model. In this report, we identify the key specs that need to be factored into any federal cloud architecture.

report Government Cloud Platform Strategy
This report analyzes the key IT infrastructure considerations that must be taken into account for implementing cloud services in federal data centers: software/hardware environment, multi-tenancy, security, virtualization, and management tools. We also explain the key important role that APIs play in supporting hybrid scenarios that tap into public cloud services.

report The Business Case for Government Clouds
This report assesses usage scenarios, barriers, and other variables that factor into the decision of whether and how to implement cloud computing in federal environments.