Commentary

Marianne Kolbasuk McGee
Senior Writer, InformationWeek  

H-1B Visa Changes Look Kaput This Year

Moves--or lack of movement--by Congress this week are good news and/or bad news depending on what side of the H-1B visa fence you're on. There seems to be something (and nothing) in it for everyone.

Moves--or lack of movement--by Congress this week are good news and/or bad news depending on what side of the H-1B visa fence you're on. There seems to be something (and nothing) in it for everyone.While hammering out details of a $150 billion-plus spending bill this week, members of Congress agreed not to sneak in any amendments that smell like immigration policy, including any changes to the current H-1B visa program.

That means Congress isn't raising H-1B visa fees this year. A proposal to hike fees to $5,000 from $1,500 was scrapped. Good news for employers.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

But Congress isn't raising the annual H-1B visa cap beyond the current limit of 85,000 either. (Bad news for employers wanting to hire foreign tech workers, good news for U.S. IT workers opposed to the competition.)

But without the hike in H-1B visa fees, there's also no funding available for a new American Competitiveness Scholarship program that would've provided merit-based scholarships of up to $15,000 annually to U.S. students pursuing tech-related degrees.

Isn't that bad news for just about everyone?

The pro H-1B visa lobby says the U.S. isn't producing enough home-grown talent employers need. And the anti-H-1B visa crowd says employers just want to hire cheaper labor from abroad.

The scholarship program might've helped attract more American young (and presumably less expensive) people into the tech-talent pipeline. The scholarships could've also helped older American workers further their education with new degrees.

So, if the U.S. continues its status quo on H-1B visa policies, who are the real winners and real losers in all this? Tell me what you think.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

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.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links